Public report of OpenHands/OpenHands, published 21 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 21 October 2026, 14:48 UTC · Survey ID cd_79201e1c47eb438c960f9a45627334e7
OpenHands/OpenHands
Measured 21 October 2026, 14:35 UTC, at code version b70dd46
CAI scoreAt riskDown 9 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 165,311 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Production Readiness, 49
Findings by how serious they are
138 critical2098 serious371 minor
4 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 14:35 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
88of 91 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
2561of 2607 findings point to an exact file and line, so you can open each one in the code. The other 46 concern the repository as a whole, such as missing documentation.
91dimensions across 7 lenses, read from 165,311 lines of product code in 2 projects.
OpenHands/OpenHands scores 51 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 49 and is rated Weak. Its Dependency Hygiene dimension scores 1.5 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 Leaked secret finding(s) in REDACTED Scanning and to resolve the 4 Deprecated finding(s) in Dependency Hygiene. The weakest lenses score close to each other, so improving any of them moves the score.
138 findings are critical: 73 in Static Analysis (SAST), 22 in Dependency Vulnerabilities, 17 in Forms & labels, 16 in Keyboard semantics, two in Circular Imports, two in Dependency Hygiene, two in IaC & Container Security, two in Secrets (history), one in ARIA correctness and one in REDACTED Scanning.
Watchdog couldn't measure 4 dimensions in this code, among them Test Reliability, Internal API Consistency and Navigability, so they are left out of the score. The product code is 165,311 lines, which would take an estimated 2.6 person-years, around €380,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 45%Tests 55%
New since the last survey: 493 findings
These 493 critical or serious findings weren't in the previous survey, on 6 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 395 findings
These 395 critical or serious findings were in the previous survey, on 6 October 2026, and are gone from this one. The first 100 are listed here.
€130,000 to €640,000, for 2,118 to 6,718 hours of work, about 2.6 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 165,311 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 1 point · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
132 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (163 files) · Code Coverage (931 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: agent-settings.tsx, conversation-websocket-context.tsx and REDACTED
What to do: Add tests to these files and have a second person review every change to them, starting with agent-settings.tsx, conversation-websocket-context.tsx and REDACTED.
Where the investment is most exposed · Value at risk
This code would cost about €380,000 to build again, about 2.6 person-years of work. Its weakest lens is Production Readiness, at 49 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.9 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 17% on every change. The history of the code shows how much it changes: about 309,489 lines over the last 90 days, which is about 1,255,150 lines a year. At that pace, the extra work comes to an estimated 239.5 to 1437.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
931 modules, with 960 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 891 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
api.conversation-service.agent-server-conversation-service_types uses types.agent-server.core.base.common, so a change to types.agent-server.core.base.common can break api.conversation-service.agent-server-conversation-service_types, while a change to api.conversation-service.agent-server-conversation-service_types can't break types.agent-server.core.base.common.
Position
Below the diagonal: api.conversation-service.agent-server-conversation-service_types uses a module listed above it, which is the healthy direction.
components.features.automations uses types.automation, so a change to types.automation can break components.features.automations, while a change to components.features.automations can't break types.automation.
Position
Below the diagonal: components.features.automations uses a module listed above it, which is the healthy direction.
components.features.backends uses api.backend-registry.types, so a change to api.backend-registry.types can break components.features.backends, while a change to components.features.backends can't break api.backend-registry.types.
Position
Below the diagonal: components.features.backends uses a module listed above it, which is the healthy direction.
components.features.backends.managed-agents uses api.mars.mars-tunnel-backend, so a change to api.mars.mars-tunnel-backend can break components.features.backends.managed-agents, while a change to components.features.backends.managed-agents can't break api.mars.mars-tunnel-backend.
Position
Below the diagonal: components.features.backends.managed-agents uses a module listed above it, which is the healthy direction.
components.features.home.featured-automations uses types.automation, so a change to types.automation can break components.features.home.featured-automations, while a change to components.features.home.featured-automations can't break types.automation.
Position
Below the diagonal: components.features.home.featured-automations uses a module listed above it, which is the healthy direction.
components.features.mcp-page uses types.mcp-server, so a change to types.mcp-server can break components.features.mcp-page, while a change to components.features.mcp-page can't break types.mcp-server.
Position
Below the diagonal: components.features.mcp-page uses a module listed above it, which is the healthy direction.
components.features.sidebar uses api.backend-registry.types, so a change to api.backend-registry.types can break components.features.sidebar, while a change to components.features.sidebar can't break api.backend-registry.types.
Position
Below the diagonal: components.features.sidebar uses a module listed above it, which is the healthy direction.
hooks uses api.backend-registry.types, so a change to api.backend-registry.types can break hooks, while a change to hooks can't break api.backend-registry.types.
Position
Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
hooks uses api.mars.mars-tunnel-backend, so a change to api.mars.mars-tunnel-backend can break hooks, while a change to hooks can't break api.mars.mars-tunnel-backend.
Position
Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
hooks uses types.agent-server.core.openhands-event, so a change to types.agent-server.core.openhands-event can break hooks, while a change to hooks can't break types.agent-server.core.openhands-event.
Position
Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
types.agent-server.core.events.action-event uses types.agent-server.core.base.common, so a change to types.agent-server.core.base.common can break types.agent-server.core.events.action-event, while a change to types.agent-server.core.events.action-event can't break types.agent-server.core.base.common.
Position
Below the diagonal: types.agent-server.core.events.action-event uses a module listed above it, which is the healthy direction.
api uses api.backend-registry.types, so a change to api.backend-registry.types can break api, while a change to api can't break api.backend-registry.types.
Position
Below the diagonal: api uses a module listed above it, which is the healthy direction.
api uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break api, while a change to api can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: api uses a module listed above it, which is the healthy direction.
api.cloud uses api.backend-registry.types, so a change to api.backend-registry.types can break api.cloud, while a change to api.cloud can't break api.backend-registry.types.
Position
Below the diagonal: api.cloud uses a module listed above it, which is the healthy direction.
api.cloud uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break api.cloud, while a change to api.cloud can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: api.cloud uses a module listed above it, which is the healthy direction.
components.conversation-events.chat.event-content-helpers uses types.agent-server.core.base.common, so a change to types.agent-server.core.base.common can break components.conversation-events.chat.event-content-helpers, while a change to components.conversation-events.chat.event-content-helpers can't break types.agent-server.core.base.common.
Position
Below the diagonal: components.conversation-events.chat.event-content-helpers uses a module listed above it, which is the healthy direction.
components.conversation-events.chat.event-content-helpers uses types.agent-server.core.openhands-event, so a change to types.agent-server.core.openhands-event can break components.conversation-events.chat.event-content-helpers, while a change to components.conversation-events.chat.event-content-helpers can't break types.agent-server.core.openhands-event.
Position
Below the diagonal: components.conversation-events.chat.event-content-helpers uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in components.conversation-events.chat.event-content-helpers uses a type in types.agent-server.core.events.action-event.
components.conversation-events.chat.event-content-helpers uses types.agent-server.core.events.action-event, so a change to types.agent-server.core.events.action-event can break components.conversation-events.chat.event-content-helpers, while a change to components.conversation-events.chat.event-content-helpers can't break types.agent-server.core.events.action-event.
Position
Below the diagonal: components.conversation-events.chat.event-content-helpers uses a module listed above it, which is the healthy direction.
components.features.conversation-panel uses api.backend-registry.types, so a change to api.backend-registry.types can break components.features.conversation-panel, while a change to components.features.conversation-panel can't break api.backend-registry.types.
Position
Below the diagonal: components.features.conversation-panel uses a module listed above it, which is the healthy direction.
components.features.conversation-panel uses components.features.conversation-panel.system-message-modal, so a change to components.features.conversation-panel.system-message-modal can break components.features.conversation-panel, while a change to components.features.conversation-panel can't break components.features.conversation-panel.system-message-modal.
Position
Below the diagonal: components.features.conversation-panel uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.features.conversation-panel uses a type in api.conversation-service.agent-server-conversation-service_types.
components.features.conversation-panel uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break components.features.conversation-panel, while a change to components.features.conversation-panel can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: components.features.conversation-panel uses a module listed above it, which is the healthy direction.
components.features.plugins uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break components.features.plugins, while a change to components.features.plugins can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: components.features.plugins uses a module listed above it, which is the healthy direction.
hooks.query uses api.backend-registry.types, so a change to api.backend-registry.types can break hooks.query, while a change to hooks.query can't break api.backend-registry.types.
Position
Below the diagonal: hooks.query uses a module listed above it, which is the healthy direction.
hooks.query uses api.mars.mars-tunnel-backend, so a change to api.mars.mars-tunnel-backend can break hooks.query, while a change to hooks.query can't break api.mars.mars-tunnel-backend.
Position
Below the diagonal: hooks.query uses a module listed above it, which is the healthy direction.
hooks.query uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break hooks.query, while a change to hooks.query can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: hooks.query uses a module listed above it, which is the healthy direction.
mocks uses types.agent-server.core.openhands-event, so a change to types.agent-server.core.openhands-event can break mocks, while a change to mocks can't break types.agent-server.core.openhands-event.
Position
Below the diagonal: mocks uses a module listed above it, which is the healthy direction.
mocks uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break mocks, while a change to mocks can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: mocks uses a module listed above it, which is the healthy direction.
services uses api.backend-registry.types, so a change to api.backend-registry.types can break services, while a change to services can't break api.backend-registry.types.
Position
Below the diagonal: services uses a module listed above it, which is the healthy direction.
services uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break services, while a change to services can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: services uses a module listed above it, which is the healthy direction.
utils uses api.backend-registry.types, so a change to api.backend-registry.types can break utils, while a change to utils can't break api.backend-registry.types.
Position
Below the diagonal: utils uses a module listed above it, which is the healthy direction.
utils uses types.agent-server.core.openhands-event, so a change to types.agent-server.core.openhands-event can break utils, while a change to utils can't break types.agent-server.core.openhands-event.
Position
Below the diagonal: utils uses a module listed above it, which is the healthy direction.
utils uses api.conversation-service.agent-server-conversation-service_types, so a change to api.conversation-service.agent-server-conversation-service_types can break utils, while a change to utils can't break api.conversation-service.agent-server-conversation-service_types.
Position
Below the diagonal: utils uses a module listed above it, which is the healthy direction.
utils uses types.agent-server.core.events.action-event, so a change to types.agent-server.core.events.action-event can break utils, while a change to utils can't break types.agent-server.core.events.action-event.
Position
Below the diagonal: utils uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 60% · Adequate · gated by D1, D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
115
High / Critical
A03:2025 — Software Supply Chain Failures
37
High / Critical
A02:2025 — Security Misconfiguration
6
High / Critical
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Immediately address the leaked secret in REDACTED and remove four deprecated dependencies to secure the supply chain. Next, expand code coverage for critical components like the loading spinner and toggle button, while cleaning up unused or misclassified dependencies. Finally, establish architectural decision records to ensure long-term maintainability and clear technical context.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Reconcile the README with reality: docs/ACP_AGENTS.md documents the environment variable `CLAUDE_CONFIG_DIR`, but no code, script or configuration file names it; docs/DefenseClaw.md documents the environment variable `OH_LLM__BASE_URL`, but no code, script or configuration file names it; src/api/README.md names `feature-service.api.ts`, but no file or folder `feature-service.api.ts` exists; src/api/README.md names `feature.types.ts`, but no file or folder `feature.types.ts` exists; src/api/README.md names `secrets.types.ts`, but no file or folder `secrets.types.ts` exists.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 138
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 2098
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 371
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 4
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 88 of 91 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 91 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2561 of 2607 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the JavaScript/TypeScript suite (vitest via `npm ci --ignore-scripts` in the repository root (3790 tests)) did not finish re-running within its budget: too large to re-run within its budget.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D31 IaC & Container Security — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Docs/pr-screenshots/dockerfile-language-after.jpg, docs/pr-screenshots/dockerfile-language-before.jpg carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 9 of 11 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `react-router.config.ts`, `src/api/automation-form-session.ts`, `src/components/features/chat/custom-chat-input.tsx`, `src/components/features/conversation-panel/conversation-panel-list-helpers.ts`, `src/components/features/manifest/manifest-icons.ts`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Helm/agent-canvas/templates/statefulset.yaml:3 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
AX7 Slice cohesion — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 252 further occurrence(s) are not listed individually; the score already reflects all 292.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. User interface: 628 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:8010: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:8010/
Call log:
- navigating to "http://127.0.0.1:8010/", waiting until "load"
ran the repo's playwright suite against the booted app but captured no surfaces (suite failed to install/run, or visited no pages) — see runtime diagnostics.
P2 Observability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 295 further occurrence(s) are not listed individually; the score already reflects all 335.
R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 48 further occurrence(s) are not listed individually; the score already reflects all 88.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
188 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was agent-settings.AgentSettingsScreen at 202. A further 7 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being get-language-from-path.getLanguageFromPath at 26 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/utils/get-language-from-path.ts (get-language-from-path.getLanguageFromPath at 26), src/components/features/conversation-panel/conversation-card/conversation-tag-display.ts (conversation-tag-display.getConversationTagLabelKind at 21), src/components/conversation-events/chat/event-content-helpers/get-observation-content.ts (get-observation-content.getObservationContent at 18), scripts/ingress.mjs (ingress.parseArgs at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 182 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with agent-settings.AgentSettingsScreen (cyclomatic 202), conversation-websocket-context.ConversationWebSocketProvider (cyclomatic 161), mcp-server-form.MCPServerForm (cyclomatic 133). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 2.8 to about 3.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 194 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with conversation-websocket-context.ConversationWebSocketProvider (cognitive 241), agent-settings.AgentSettingsScreen (cognitive 205). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 2.0 to about 3.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes5.1 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 164 FunctionTooLong finding(s) in God Classes — start with backend-form-modal.tsx (5), REDACTED (2), automations-list.tsx (2). — One of this dimension's main actionable groups (164 warning-level).
Resolve the 21 FileTooLong finding(s) in God Classes — start with REDACTED, agent-settings.tsx, backend-form-modal.tsx. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 2 ClassTooLong finding(s) in God Classes — start with automation-service.api.ts, agent-server-conversation-service.api.ts. — One of this dimension's main actionable groups (2 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 27.5% — 943 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `npm ci --ignore-scripts` in the repository root).
Resolve the 943 Low coverage finding(s) in Code Coverage — start with loading-spinner.tsx (4), index.ts (3), toggle-button.tsx (3). — One of this dimension's main actionable groups (943 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.8 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
8211 test methods: 8082 unit, 0 integration, 0 BDD, 129 e2e. The JavaScript/TypeScript suite contributes 8209 `it`/`test` case(s) across 877 test file(s) declaring at least one; its tier split is read from package names and paths only. The Python suite contributes 2 test function(s) across 1 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 28 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
30 skipped (12 with a documented reason), 9 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8209 tests.
No assertions: emits browser-compatible ESM when a bundled CommonJS dependency requires a React peer · ×9__tests__/vite-config.test.ts:195
Fixed-sleep synchronisation: waits for a migration already running__tests__/hooks/use-migrate-default-agent-profile.test.ts:237
Mock-dominated test: waits for the restarted server and moves the terminal off tmux · ×170__tests__/api/mars-sandbox-setup.test.ts:38
Skipped (documented): should render suggestions if empty · ×12__tests__/components/chat/chat-interface.test.tsx:291
What to do
Resolve the 18 Skipped test finding(s) in Test Quality — start with mock-llm-partial-stack.spec.ts (3), mock-llm-cross-connect.spec.ts (3), mock-llm-files-and-git.spec.ts (3). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 9 No assertions finding(s) in Test Quality — start with agent-profiles-manager.test.tsx (2), llm-profiles-manager.test.tsx (2), brand-button.test.tsx (2). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with use-migrate-default-agent-profile.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
27 outdated direct production npm dependency(ies) of 52 graded, 0 pinning defect(s), across 1 REDACTED (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Deprecated: eslintREDACTED:159
Deprecated: boolean · ×4REDACTED:9983
Outdated (npm): @heroui/react · ×27
What to do
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 52 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 52 production dependency(ies) this repository's committed lockfile resolves, across 1 product REDACTED manifest(s). Its 49 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: src/routes/agent-settings.tsx (17×202=3434); src/contexts/conversation-websocket-context.tsx (19×161=3059); REDACTED (11×220=2420) Repeated repair below the complexity floor: src/hooks/mutation/use-create-conversation.ts (9 of 15 changes were fixes); src/services/telemetry.ts (7 of 10 changes were fixes); vitest.setup.ts (7 of 7 changes were fixes)
Resolve the 139 Hotspot finding(s) in Churn × Complexity Hotspots — start with agent-settings.tsx, conversation-websocket-context.tsx, REDACTED. — One of this dimension's main actionable groups (139 warning-level).
Resolve the 24 Repeated repair finding(s) in Churn × Complexity Hotspots — start with use-create-conversation.ts, telemetry.ts, vitest.setup.ts. — One of this dimension's main actionable groups (24 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/components/providers/telemetry-provider.tsx. Counted over 653 of the 1360 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
2 deducted task-comment markers across 153329 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with package-library.test.ts, agent-server-adapter.ts. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README (README.md) and the docs directory are both well written: the former introduces OpenHands Agent Canvas as a self-hosted developer control center for coding agents and automations with status beta badges, links to CI, npm, documentation, Slack, and an outline of Quickstart; the latter documents the project's architecture, ACP agent usage, helm chart, API guide, color themes, e2e live-acp tests, and a feature-map verification suite. The READMEs are complete for their respective directories but lack a unified overview (the root README does not describe what the docs/ directory is for) and each document is clipped mid-outline by the scanner, so unshown sections cannot be flagged as missing. The repository's READMEs are comprehensive for their respective topics — the root README gives an overview of what Agent Canvas is, its purpose, and a licence statement. The ACP_AGENTS.md guide explains what ACP agents are (the standard ACP protocol), lists supported providers with default commands, shows a JSON-RPC flowchart, and covers onboarding, agent choice persistence, and the Docker container model; it also documents the repository's architecture/Docs set of seven markdown files. The self-hosting guide walks through provisioning, securing, running, and optionally getting a domain for an exposed VM, with a deployment diagram and security warning.
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 of 2 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
115 finding(s): 0 critical, 73 high, 40 medium, 2 low. 55 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 27 file(s) — `.agents/skills/verify-openhands/references/feature-map/F10-llm-profiles.md`, `.agents/skills/verify-openhands/references/feature-map/F26-runtime-variants.md`, `REDACTED`, `__tests__/components/automations/automation-card.test.tsx` (line 202, line 253), `__tests__/components/automations/automation-list-row.test.tsx` (line 158, line 203), … (+22 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 10 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 51 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (51 issue-level, 0 of them charged here).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17), REDACTED (3). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
19 of 653 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/hooks/use-terminal.ts. Counted over 653 of the 1360 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×19src/hooks/use-terminal.ts:1
Orphaned files with no living knowledge
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with agent-server-adapter.ts, agent-server-conversation-service.api.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.
Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 52 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels6.8 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — src/components/features/alerts/alert-banner.tsx:131, src/components/shared/buttons/scroll-to-bottom-button.tsx:9
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×4) — src/components/features/automations/detail/run-logs-modal.tsx:266, src/components/features/automations/turn-off-confirmation-modal.tsx:25, src/components/features/settings/settings-mobile-drawer.tsx:37, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×4) — REDACTED:2977, REDACTED:3452, src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:298, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — src/components/features/conversation-panel/conversation-card/conversation-card-title.tsx:20, src/components/features/conversation/conversation-name.tsx:150, src/components/features/manifest/manifest-form-field.tsx:198, …
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×4) — src/components/features/settings/llm-profiles/provider-connection-modal.tsx:192, src/components/shared/modals/settings/model-selector.tsx:167, src/components/shared/modals/settings/model-selector.tsx:240, …
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×3) — src/components/features/settings/llm-profiles/provider-connection-modal.tsx:193, src/components/shared/modals/settings/model-selector.tsx:168, src/components/shared/modals/settings/model-selector.tsx:241
This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — src/routes/automation-templates.tsx:45, src/routes/automations-list.tsx:757
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure7.6 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — electron/loading.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×5) — src/components/features/automations/detail/run-logs-modal.tsx:260, src/components/features/automations/turn-off-confirmation-modal.tsx:33, src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:308, …
This <article> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — src/components/features/chat/chat-message.tsx:150
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. (×7) — src/components/features/chat/generic-event-message.tsx:77, src/components/features/conversation/conversation-overview-toggle.tsx:121, src/components/features/conversation/conversation-overview-toggle.tsx:142, …
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/components/features/command-menu/command-menu.tsx:200
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×6) — src/components/features/conversation-panel/conversation-card/conversation-card.tsx:269, src/components/features/conversation-panel/start-task-card/start-task-card.tsx:29, src/components/features/settings/settings-mobile-drawer.tsx:37, …
This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — src/components/features/conversation/conversation-name.tsx:161
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — src/components/shared/modals/modal-backdrop.tsx:71
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — src/ui/dropdown/dropdown.tsx:231
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.spinner` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — electron/loading.html:87
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×10) — src/components/features/automations/search-input.tsx:29, REDACTED:3173, src/components/features/automations/setup/automation-setup-prompt-stack.tsx:450, …
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — REDACTED:2553, src/components/features/automations/setup/automation-setup-prompt-stack.tsx:348, src/routes/agent-settings.tsx:1665
<svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/components/features/backends/device-flow-auth.tsx:362
<div> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — src/components/features/chat/components/chat-input-field.tsx:58
<div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×10) — src/components/features/conversation-panel/hooks-loading-state.tsx:4, src/components/features/conversation-panel/skills-loading-state.tsx:4, src/components/features/diff-viewer/loading-spinner.tsx:14, …
`.chat-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/tailwind.css:371
`.oh-setup-tour-popover .driver-popover-close-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/components/features/setup-guide/tour/tour-theme.css:131
`.oh-setup-tour-popover .driver-popover-close-btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/components/features/setup-guide/tour/tour-theme.css:141
`.environment-switch-overlay > div` moves (`animation: environment-switch-overlay-fade 980ms ease-in-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/index.css:156
`.shine-text` moves (`animation: shine 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/tailwind.css:656
`.gradient-flow` moves (`animation: gradient-slide 1.25s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/tailwind.css:686
`[data-agent-server-ui].driver-fade .driver-overlay` moves (`animation: animate-fade-in 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/components/features/setup-guide/tour/tour-theme.css:163
`[data-agent-server-ui].driver-fade .driver-popover` moves (`animation: animate-fade-in 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/components/features/setup-guide/tour/tour-theme.css:167
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 628 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`MarsBridge` declares 18 required operations: `getAuthState`, `signInWithOAuth`, `savePat`, `setActiveConnection`, `signOut`, `listSessions`, `listAgentConfigs`, `listConfigSessions`, `listSandboxSizes`, `createOpenHandsAgent`, `createSession`, `pauseSession`, `resumeSession`, `destroySession`, `deleteAgentConfig`, `openTunnel`, `closeTunnel`, `getTunnel`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/api/mars/mars-tunnel-backend.ts:158
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`LocalTelemetryConsentBanner` (slice 'analytics') depends on `BrandButton` from slice 'settings'. — src/components/features/analytics/telemetry-consent-banner.tsx:105
`AddAutomationMenu` (slice 'automations') depends on `ContextMenuListItem` from slice 'context-menu'. — src/components/features/automations/add-automation-menu.tsx:97
`AddAutomationMenu` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/add-automation-menu.tsx:129
`AutomationAgentProfileSelector` (slice 'automations') depends on `SettingsDropdownInput` from slice 'settings'. — src/components/features/automations/agent-profile-selector.tsx:33
`AutomationCard` (slice 'automations') depends on `getLastRunTimestamp` from slice 'home'. — src/components/features/automations/automation-card.tsx:111
`AutomationCard` (slice 'automations') depends on `shortenAutomationRunSummary` from slice 'home'. — src/components/features/automations/automation-card.tsx:114
`AutomationCard` (slice 'automations') depends on `shouldShowAutomationRunSummaryHovercard` from slice 'home'. — src/components/features/automations/automation-card.tsx:118
`AutomationCard` (slice 'automations') depends on `SkillCardPillRow` from slice 'skills'. — src/components/features/automations/automation-card.tsx:192
`AutomationCard` (slice 'automations') depends on `AutomationRunActivitySparkline` from slice 'home'. — src/components/features/automations/automation-card.tsx:199
`AutomationListRow` (slice 'automations') depends on `getTriggerEventLabel` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:96
`AutomationListRow` (slice 'automations') depends on `getTriggerScheduleLabel` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:97
`AutomationListRow` (slice 'automations') depends on `getTriggerSource` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:98
`AutomationListRow` (slice 'automations') depends on `deriveRunHealth` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:104
`AutomationListRow` (slice 'automations') depends on `getLastRunTimestamp` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:112
`AutomationListRow` (slice 'automations') depends on `getRunStatusLabelKey` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:120
`AutomationListRow` (slice 'automations') depends on `HomeAutomationRunTooltip` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:131
`AutomationListRow` (slice 'automations') depends on `AutomationHealthIndicator` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:151
`AutomationListRow` (slice 'automations') depends on `formatTriggerSourceLabel` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:177
`AutomationListRow` (slice 'automations') depends on `AutomationRunActivitySparkline` from slice 'home'. — src/components/features/automations/automation-list-row.tsx:232
`AutomationViewToggle` (slice 'automations') depends on `ContextMenuListItem` from slice 'context-menu'. — src/components/features/automations/automation-view-toggle.tsx:111
`BackendUnavailable` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/backend-not-configured.tsx:22
`buildAutomationMetadataPills` (slice 'automations') depends on `SkillCardPill` from slice 'skills'. — src/components/features/automations/build-automation-pills.tsx:21
`buildAutomationMetadataPills` (slice 'automations') depends on `getTriggerEventLabel` from slice 'home'. — src/components/features/automations/build-automation-pills.tsx:37
`buildAutomationMetadataPills` (slice 'automations') depends on `getTriggerSource` from slice 'home'. — src/components/features/automations/build-automation-pills.tsx:50
`buildAutomationMetadataPills` (slice 'automations') depends on `formatTriggerSourceLabel` from slice 'home'. — src/components/features/automations/build-automation-pills.tsx:73
`BuiltInIntegrationChoiceModal` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/built-in-integration-choice-modal.tsx:152
`CreateInstructionsContent` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/create-instructions.tsx:68
`AutomationSubPageNav` (slice 'automations') depends on `SubPageNavItem` from slice 'manifest'. — src/components/features/automations/dashboard/use-automation-sub-page-nav.ts:10
`useAutomationSubPageNav` (slice 'automations') depends on `MANIFEST_ICON_BY_SLUG` from slice 'manifest'. — src/components/features/automations/dashboard/use-automation-sub-page-nav.ts:30
`DebugAutomationButton` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/detail/debug-automation-button.tsx:55
`ScriptSection` (slice 'automations') depends on `HighlightedSourceView` from slice 'files-tab'. — src/components/features/automations/detail/script-section.tsx:115
`GitSyncConfigForm` (slice 'automations') depends on `SettingsSwitch` from slice 'settings'. — src/components/features/automations/git-sync/git-sync-config-form.tsx:265
`GitSyncConfigForm` (slice 'automations') depends on `SettingsInput` from slice 'settings'. — src/components/features/automations/git-sync/git-sync-config-form.tsx:279
`GitSyncConfigForm` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/git-sync/git-sync-config-form.tsx:434
`GitSyncOverviewSection` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/git-sync/git-sync-overview-section.tsx:119
`ImportAutomationPicker` (slice 'automations') depends on `BrandButton` from slice 'settings'. — src/components/features/automations/import-automation-modal.tsx:120
`KebabMenu` (slice 'automations') depends on `ContextMenuListItem` from slice 'context-menu'. — src/components/features/automations/kebab-menu.tsx:102
`RecommendedAutomationsLauncher` (slice 'automations') depends on `InstallServerModal` from slice 'mcp-page'. — src/components/features/automations/recommended-automations-launcher.tsx:435
`buildRecommendedAutomationPills` (slice 'automations') depends on `SkillCardPill` from slice 'skills'. — src/components/features/automations/recommended-automations-section.tsx:172
`AutomationCardIcon` (slice 'automations') depends on `McpLogoStackBadge` from slice 'mcp-page'. — src/components/features/automations/recommended-automations-section.tsx:259
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`onSubmitted` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/components/features/backends/api-key-entry-screen.tsx:105
`onInputChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×4) — src/components/features/backends/managed-agents/digitalocean-new-agent-form.tsx:132, src/components/features/settings/mcp-settings/mcp-server-form.tsx:475, src/components/features/settings/mcp-settings/mcp-server-form.tsx:520, …
`onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — src/components/features/chat/uploaded-files.tsx:56, src/components/features/chat/uploaded-files.tsx:83
`onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/components/features/conversation/conversation-tabs/conversation-tabs.tsx:344
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — src/components/features/home/shared/generic-dropdown-menu.tsx:93
`onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/components/features/mcp-page/install-server-modal.tsx:646
The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/components/features/sidebar/sidebar-onboarding-checklist-llm-complete.ts:45
`onToggle` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/routes/agent-settings.tsx:1333
`clearTelemetryData` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/services/telemetry.ts:907
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×18) — tests/e2e/bind-policy/loopback-bind.spec.ts:142, tests/e2e/canvas-extensions/app-backend-sandbox.spec.ts:103, tests/e2e/conversation-markdown-render-performance.spec.ts:224, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 1 of 2 project(s) that lack one — worth up to 1 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
docs/ACP_AGENTS.md documents the environment variable `CLAUDE_CONFIG_DIR`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ACP_AGENTS.md:97
docs/DefenseClaw.md documents the environment variable `OH_LLM__BASE_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/DefenseClaw.md:130
src/api/README.md names `feature-service.api.ts`, but no file or folder `feature-service.api.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/api/README.md:96
src/api/README.md names `feature.types.ts`, but no file or folder `feature.types.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/api/README.md:97
src/api/README.md names `secrets.types.ts`, but no file or folder `secrets.types.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/api/README.md:97
tests/e2e/live-acp/README.md runs `docker rm -f oh-acp`, but `oh-acp` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/e2e/live-acp/README.md:34
What to do
Reconcile the README with reality: docs/ACP_AGENTS.md documents the environment variable `CLAUDE_CONFIG_DIR`, but no code, script or configuration file names it; docs/DefenseClaw.md documents the environment variable `OH_LLM__BASE_URL`, but no code, script or configuration file names it; src/api/README.md names `feature-service.api.ts`, but no file or folder `feature-service.api.ts` exists; src/api/README.md names `feature.types.ts`, but no file or folder `feature.types.ts` exists; src/api/README.md names `secrets.types.ts`, but no file or folder `secrets.types.ts` exists.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
`src/api/secrets-service.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/secrets-service.ts:38
`src/api/hooks-service.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/hooks-service.ts:37
`src/api/agent-server-compatibility.ts` reports through `console.*` at line 397 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/agent-server-compatibility.ts:397
`src/api/agent-server-adapter.ts` reports through `console.*` at line 1354 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/agent-server-adapter.ts:1354
`src/api/agent-server-adapter.ts` reports through `console.*` at line 1385 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/agent-server-adapter.ts:1385
`src/api/agent-server-adapter.ts` reports through `console.*` at line 1415 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/agent-server-adapter.ts:1415
`src/api/conversation-service/agent-server-conversation-service.api.ts` reports through `console.*` at line 791 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/conversation-service/agent-server-conversation-service.api.ts:791
`src/api/conversation-service/agent-server-conversation-service.api.ts` reports through `console.*` at line 924 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/conversation-service/agent-server-conversation-service.api.ts:924
`src/api/conversation-service/agent-server-conversation-service.api.ts` reports through `console.*` at line 1096 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/conversation-service/agent-server-conversation-service.api.ts:1096
`src/api/event-service/event-service.api.ts` reports through `console.*` at line 130 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/event-service/event-service.api.ts:130
`src/api/mars/mars-sandbox-setup.ts` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/mars/mars-sandbox-setup.ts:105
`src/api/settings-service/settings-service.api.ts` reports through `console.*` at line 612 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/settings-service/settings-service.api.ts:612
`src/api/settings-service/settings-service.api.ts` reports through `console.*` at line 638 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/api/settings-service/settings-service.api.ts:638
`src/components/features/backends/device-flow-auth.tsx` reports through `console.*` at line 107 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/backends/device-flow-auth.tsx:107
`src/components/features/backends/device-flow-auth.tsx` reports through `console.*` at line 172 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/backends/device-flow-auth.tsx:172
`src/components/features/canvas-extensions/canvas-extensions-runtime.tsx` reports through `console.*` at line 313 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/canvas-extensions/canvas-extensions-runtime.tsx:313
`src/components/features/settings/agent-profiles/agent-profiles-manager.tsx` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/agent-profiles/agent-profiles-manager.tsx:44
`src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx` reports through `console.*` at line 262 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:262
`src/components/features/settings/llm-profiles/llm-settings-local-view.tsx` reports through `console.*` at line 236 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:236
`src/components/features/settings/llm-profiles/llm-settings-local-view.tsx` reports through `console.*` at line 423 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:423
`src/components/features/settings/llm-profiles/llm-profiles-manager.tsx` reports through `console.*` at line 91 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/llm-profiles/llm-profiles-manager.tsx:91
`src/components/features/settings/llm-profiles/llm-profiles-manager.tsx` reports through `console.*` at line 130 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/llm-profiles/llm-profiles-manager.tsx:130
`src/components/features/settings/llm-profiles/add-models-modal.tsx` reports through `console.*` at line 292 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/components/features/settings/llm-profiles/add-models-modal.tsx:292
`src/contexts/conversation-websocket-context.tsx` reports through `console.*` at line 599 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/contexts/conversation-websocket-context.tsx:599
`src/contexts/conversation-websocket-context.tsx` reports through `console.*` at line 904 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/contexts/conversation-websocket-context.tsx:904
`src/contexts/conversation-websocket-context.tsx` reports through `console.*` at line 1104 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/contexts/conversation-websocket-context.tsx:1104
`src/contexts/conversation-websocket-context.tsx` reports through `console.*` at line 1117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/contexts/conversation-websocket-context.tsx:1117
`src/extensions/canvas-extension-app-view.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/extensions/canvas-extension-app-view.ts:117
`src/hooks/use-manifest-preflight.ts` reports through `console.*` at line 93 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/use-manifest-preflight.ts:93
`src/hooks/mutation/use-apply-onboarding-agent-profile.ts` reports through `console.*` at line 78 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/mutation/use-apply-onboarding-agent-profile.ts:78
`src/hooks/mutation/sync-agent-profiles.ts` reports through `console.*` at line 97 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/hooks/mutation/sync-agent-profiles.ts:97
`src/manifests/manifest-registry.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/manifests/manifest-registry.ts:32
`src/manifests/manifest-registry.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/manifests/manifest-registry.ts:38
`src/manifests/automation-interface.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/manifests/automation-interface.ts:74
`src/routes/canvas-extension-page.tsx` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/routes/canvas-extension-page.tsx:71
`src/services/secret-request.ts` reports through `console.*` at line 122 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/secret-request.ts:122
`src/services/child-conversation-launch.ts` reports through `console.*` at line 546 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/child-conversation-launch.ts:546
`src/services/canvas-ui.ts` reports through `console.*` at line 116 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/services/canvas-ui.ts:116
`src/utils/sdk-settings-field-metadata.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/sdk-settings-field-metadata.ts:101
`src/utils/sdk-settings-field-metadata.ts` reports through `console.*` at line 160 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/sdk-settings-field-metadata.ts:160
What to do
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 124832 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`mkdirSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/dev-safe.mjs:1032, REDACTED:621
`existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1668
`mkdirSync` in `createFileLogger` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/logger.mjs:58
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
81 duplicated blocks under src/components/features/ have copies in at least two of the sibling directories automations, backends, browser, canvas-extensions, chat, controls (+13 more sibling(s) not listed) — 48 of them are reported below, and 33 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 81 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 81 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 81 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:144
38 duplicated blocks under src/ have copies in at least two of the sibling directories api, components, contexts, hooks, routes, types (+1 more sibling(s) not listed) — 16 of them are reported below, and 22 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/features/chat/error-message-banner.tsx:66
17 duplicated blocks under src/components/features/settings/ have copies in at least two of the sibling directories agent-profiles, llm-profiles, mcp-settings, meta-llm-profiles, secrets-settings — 14 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 17 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:106
10 duplicated blocks under src/components/ have copies in at least two of the sibling directories conversation-events, features, shared — 5 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/conversation-events/chat/task-tracking/task-item.tsx:15
5 duplicated blocks under src/api/ have copies in at least two of the sibling directories agent-profiles-service, backend-registry, conversation-service, mcp-health, meta-profiles-service, profiles-service — 0 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/api/agent-profiles-service/agent-profiles-service.api.ts:61
5 duplicated blocks under src/components/features/home/ have copies in at least two of the sibling directories git-branch-dropdown, git-provider-dropdown, git-repo-dropdown, workspace-dropdown — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:99
src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:106 · src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:85 — the two spans are one implementation copied and then locally edited — 908 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:106
src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:144 · src/components/features/skills/skill-card-pill-row.tsx:88 — the two spans are one implementation copied and then locally edited — 634 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:144
src/components/features/automations/automation-card.tsx:111 · src/components/features/home/featured-automations/pinned-automation-card.tsx:95 — the two spans are one implementation copied and then locally edited — 551 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/automations/automation-card.tsx:111
src/components/features/chat/components/chat-input-llm-profile-picker.tsx:30 · src/components/features/chat/components/chat-input-profile-picker.tsx:19 — the two spans are one implementation copied and then locally edited — 449 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/chat/components/chat-input-llm-profile-picker.tsx:30
src/components/features/canvas-extensions/add-canvas-extension-modal.tsx:19 · src/components/features/plugins/add-plugin-modal.tsx:17 — the two spans are one implementation copied and then locally edited — 453 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/canvas-extensions/add-canvas-extension-modal.tsx:19
src/components/features/automations/automation-list-row.tsx:92 · src/components/features/home/featured-automations/running-automations-list.tsx:62 — the two spans are one implementation copied and then locally edited — 443 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/automations/automation-list-row.tsx:92
src/components/features/chat/components/chat-input-model.tsx:95 · src/components/features/chat/components/chat-input-profile-picker.tsx:83 — the two spans are one implementation copied and then locally edited — 350 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/chat/components/chat-input-model.tsx:95
src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:92 · src/components/features/conversation-panel/local-new-conversation-menu.tsx:69 — the two spans are one implementation copied and then locally edited — 470 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:92
src/components/features/settings/agent-canvas-update-card.tsx:38 · src/components/features/settings/agent-canvas-version-modal.tsx:37 — the two spans are one implementation copied and then locally edited — 402 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/settings/agent-canvas-update-card.tsx:38
src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:99 · REDACTED:196 — the two spans are one implementation copied and then locally edited — 377 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:99
src/components/features/settings/llm-profiles/provider-connection-actions-menu.tsx:33 · src/components/features/settings/meta-llm-profiles/meta-profile-actions-menu.tsx:81 — the two spans are one implementation copied and then locally edited — 510 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/settings/llm-profiles/provider-connection-actions-menu.tsx:33
src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:44 · src/components/features/settings/llm-profiles/profile-actions-menu.tsx:47 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:44
src/components/features/controls/git-tools-submenu.tsx:21 · src/components/features/controls/macros-submenu.tsx:14 — the two spans are one implementation copied and then locally edited — 344 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/controls/git-tools-submenu.tsx:21
src/components/features/automations/automation-card.tsx:85 · src/components/features/automations/automation-list-row.tsx:74 — the two spans are one implementation copied and then locally edited — 306 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/automations/automation-card.tsx:85
src/api/automation-service/automation-service.api.ts:642 · src/api/automation-service/automation-service.api.ts:937 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/api/automation-service/automation-service.api.ts:642
src/hooks/use-resizable-drawer-width.ts:37 · src/hooks/use-resizable-panels.ts:19 — the two spans are one implementation copied and then locally edited — 379 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/hooks/use-resizable-drawer-width.ts:37
src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:34 · src/components/features/settings/llm-profiles/delete-profile-modal.tsx:34 · src/components/features/settings/meta-llm-profiles/delete-meta-profile-modal.tsx:31 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:34
src/components/features/skills/skill-card.tsx:56 · src/components/features/skills/skill-detail-modal.tsx:89 — the two spans are one implementation copied and then locally edited — 257 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/skills/skill-card.tsx:56
src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:1 · src/components/features/settings/llm-profiles/delete-profile-modal.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:1
src/components/features/controls/tools-context-menu.tsx:204 · src/components/features/conversation/conversation-name-context-menu.tsx:205 — the two spans are one implementation copied and then locally edited — 215 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/controls/tools-context-menu.tsx:204
src/contexts/conversation-websocket-context.tsx:671 · src/contexts/conversation-websocket-context.tsx:958 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/contexts/conversation-websocket-context.tsx:671
src/components/features/settings/llm-profiles/delete-profile-modal.tsx:48 · src/components/features/settings/llm-profiles/delete-provider-connection-modal.tsx:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/components/features/settings/llm-profiles/delete-profile-modal.tsx:48
src/components/features/settings/agent-profiles/agent-profile-row.tsx:52 · src/components/features/settings/llm-profiles/profile-row.tsx:48 — the two spans are one implementation copied and then locally edited — 206 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/features/settings/agent-profiles/agent-profile-row.tsx:52
src/components/features/chat/git-control-bar-pr-button.tsx:21 · src/components/features/chat/git-control-bar-push-button.tsx:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/components/features/chat/git-control-bar-pr-button.tsx:21
src/stores/archived-conversations-store.ts:16 · src/stores/pinned-conversations-store.ts:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/stores/archived-conversations-store.ts:16
src/components/features/home/home-recommended-automations-storage.ts:6 · src/components/features/sidebar/sidebar-onboarding-checklist-storage.ts:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/components/features/home/home-recommended-automations-storage.ts:6
playwright.mock-llm-docker.config.ts:45 · playwright.mock-llm.config.ts:26 — the two spans are one implementation copied and then locally edited — 241 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — playwright.mock-llm-docker.config.ts:45
src/components/conversation-events/chat/task-tracking/task-item.tsx:15 · src/components/features/chat/task-tracking/task-item.tsx:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/components/conversation-events/chat/task-tracking/task-item.tsx:15
src/components/features/chat/git-control-bar-pr-button.tsx:23 · src/components/features/chat/git-control-bar-pull-button.tsx:20 · src/components/features/chat/git-control-bar-push-button.tsx:23 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/components/features/chat/git-control-bar-pr-button.tsx:23
src/components/features/conversation-panel/hooks-modal-header.tsx:20 · src/components/features/conversation-panel/skills-modal-header.tsx:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/components/features/conversation-panel/hooks-modal-header.tsx:20
src/components/features/plugins/plugins-toolbar.tsx:29 · src/components/features/skills/skills-toolbar.tsx:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/components/features/plugins/plugins-toolbar.tsx:29
src/components/features/automations/add-automation-menu.tsx:38 · src/components/features/automations/automation-view-toggle.tsx:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/components/features/automations/add-automation-menu.tsx:38
src/components/features/chat/tool-visualizers/primitives/markdown-file-preview.tsx:57 · src/components/features/chat/tool-visualizers/primitives/markdown-file-preview.tsx:99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/components/features/chat/tool-visualizers/primitives/markdown-file-preview.tsx:57
src/components/features/home/open-repository-dialog.tsx:22 · src/components/features/home/open-workspace-dialog.tsx:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/components/features/home/open-repository-dialog.tsx:22
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
__tests__/electron/lib/bundled-runtime-dir.test.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../../electron/lib/bundled-runtime-dir.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — __tests__/electron/lib/bundled-runtime-dir.test.ts:13
src/components/features/conversation-panel/conversation-card/conversation-repo-link.tsx:3 imports react-icons/lib, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/conversation-panel/conversation-card/conversation-repo-link.tsx:3
src/components/features/diff-viewer/file-diff-viewer.tsx:13 imports react-icons/lib, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/diff-viewer/file-diff-viewer.tsx:13
src/components/features/markdown/syntax-highlighter.ts:2 imports react-syntax-highlighter/dist/esm/languages/prism/bash, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:2
src/components/features/markdown/syntax-highlighter.ts:3 imports react-syntax-highlighter/dist/esm/languages/prism/batch, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:3
src/components/features/markdown/syntax-highlighter.ts:4 imports react-syntax-highlighter/dist/esm/languages/prism/c, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:4
src/components/features/markdown/syntax-highlighter.ts:5 imports react-syntax-highlighter/dist/esm/languages/prism/clike, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:5
src/components/features/markdown/syntax-highlighter.ts:6 imports react-syntax-highlighter/dist/esm/languages/prism/clojure, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:6
src/components/features/markdown/syntax-highlighter.ts:7 imports react-syntax-highlighter/dist/esm/languages/prism/cpp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:7
src/components/features/markdown/syntax-highlighter.ts:8 imports react-syntax-highlighter/dist/esm/languages/prism/csharp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:8
src/components/features/markdown/syntax-highlighter.ts:9 imports react-syntax-highlighter/dist/esm/languages/prism/css, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:9
src/components/features/markdown/syntax-highlighter.ts:10 imports react-syntax-highlighter/dist/esm/languages/prism/dart, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:10
src/components/features/markdown/syntax-highlighter.ts:11 imports react-syntax-highlighter/dist/esm/languages/prism/diff, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:11
src/components/features/markdown/syntax-highlighter.ts:12 imports react-syntax-highlighter/dist/esm/languages/prism/docker, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:12
src/components/features/markdown/syntax-highlighter.ts:13 imports react-syntax-highlighter/dist/esm/languages/prism/elixir, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:13
src/components/features/markdown/syntax-highlighter.ts:14 imports react-syntax-highlighter/dist/esm/languages/prism/erlang, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:14
src/components/features/markdown/syntax-highlighter.ts:15 imports react-syntax-highlighter/dist/esm/languages/prism/fsharp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:15
src/components/features/markdown/syntax-highlighter.ts:16 imports react-syntax-highlighter/dist/esm/languages/prism/go, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:16
src/components/features/markdown/syntax-highlighter.ts:17 imports react-syntax-highlighter/dist/esm/languages/prism/graphql, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:17
src/components/features/markdown/syntax-highlighter.ts:18 imports react-syntax-highlighter/dist/esm/languages/prism/groovy, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:18
src/components/features/markdown/syntax-highlighter.ts:19 imports react-syntax-highlighter/dist/esm/languages/prism/haskell, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:19
src/components/features/markdown/syntax-highlighter.ts:20 imports react-syntax-highlighter/dist/esm/languages/prism/hcl, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:20
src/components/features/markdown/syntax-highlighter.ts:21 imports react-syntax-highlighter/dist/esm/languages/prism/http, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:21
src/components/features/markdown/syntax-highlighter.ts:22 imports react-syntax-highlighter/dist/esm/languages/prism/ini, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:22
src/components/features/markdown/syntax-highlighter.ts:23 imports react-syntax-highlighter/dist/esm/languages/prism/java, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:23
src/components/features/markdown/syntax-highlighter.ts:24 imports react-syntax-highlighter/dist/esm/languages/prism/javascript, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:24
src/components/features/markdown/syntax-highlighter.ts:25 imports react-syntax-highlighter/dist/esm/languages/prism/json, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:25
src/components/features/markdown/syntax-highlighter.ts:26 imports react-syntax-highlighter/dist/esm/languages/prism/json5, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:26
src/components/features/markdown/syntax-highlighter.ts:27 imports react-syntax-highlighter/dist/esm/languages/prism/jsx, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:27
src/components/features/markdown/syntax-highlighter.ts:28 imports react-syntax-highlighter/dist/esm/languages/prism/julia, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:28
src/components/features/markdown/syntax-highlighter.ts:29 imports react-syntax-highlighter/dist/esm/languages/prism/kotlin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:29
src/components/features/markdown/syntax-highlighter.ts:30 imports react-syntax-highlighter/dist/esm/languages/prism/less, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:30
src/components/features/markdown/syntax-highlighter.ts:31 imports react-syntax-highlighter/dist/esm/languages/prism/lua, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:31
src/components/features/markdown/syntax-highlighter.ts:32 imports react-syntax-highlighter/dist/esm/languages/prism/makefile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:32
src/components/features/markdown/syntax-highlighter.ts:33 imports react-syntax-highlighter/dist/esm/languages/prism/markdown, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:33
src/components/features/markdown/syntax-highlighter.ts:34 imports react-syntax-highlighter/dist/esm/languages/prism/markup, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:34
src/components/features/markdown/syntax-highlighter.ts:35 imports react-syntax-highlighter/dist/esm/languages/prism/matlab, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:35
src/components/features/markdown/syntax-highlighter.ts:36 imports react-syntax-highlighter/dist/esm/languages/prism/nginx, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:36
src/components/features/markdown/syntax-highlighter.ts:37 imports react-syntax-highlighter/dist/esm/languages/prism/nix, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:37
src/components/features/markdown/syntax-highlighter.ts:38 imports react-syntax-highlighter/dist/esm/languages/prism/objectivec, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/features/markdown/syntax-highlighter.ts:38
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
AgentSettingsScreen has cyclomatic complexity 130 and cognitive complexity 110; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/agent-settings.tsx:382
ConversationPanel has cyclomatic complexity 65 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/conversation-panel/conversation-panel.tsx:84
AutomationsList has cyclomatic complexity 61 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/automations-list.tsx:297
(anonymous) has cyclomatic complexity 56 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/utils/transcript-export/index.ts:271
ConversationCard has cyclomatic complexity 55 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/conversation-panel/conversation-card/conversation-card.tsx:80
ConversationMain has cyclomatic complexity 54 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/conversation/conversation-main/conversation-main.tsx:79
AutomationSetupPanel has cyclomatic complexity 53 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:640
ChatInputActions has cyclomatic complexity 51 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/chat/components/chat-input-actions.tsx:62
EventMessageComponent has cyclomatic complexity 50 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/conversation-events/chat/event-message.tsx:180
(anonymous) has cyclomatic complexity 45 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/contexts/conversation-websocket-context.tsx:648
main has cyclomatic complexity 45 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1507
PinnedAutomationCard has cyclomatic complexity 45 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/home/featured-automations/pinned-automation-card.tsx:58
SetupDialog has cyclomatic complexity 44 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/manifest/manifest-setup-dialog.tsx:101
ChatInterface has cyclomatic complexity 42 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/chat/chat-interface.tsx:88
parseArgs has cyclomatic complexity 41 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/static-server.mjs:88
App has cyclomatic complexity 39 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/root.tsx:234
useBashCommandLogs has cyclomatic complexity 37 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/hooks/query/use-bash-command-logs.ts:142
buildPluginsViewModel has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/plugins/build-plugins-view-model.ts:51
AutomationCard has cyclomatic complexity 37 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/automations/automation-card.tsx:59
ConversationOverviewGitSection has cyclomatic complexity 37 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/features/conversation/conversation-overview-git-section.tsx:36
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.4 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 3453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
src/routes/agent-settings.tsx has 1776 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/agent-settings.tsx:1
src/components/features/backends/backend-form-modal.tsx has 1683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/backends/backend-form-modal.tsx:1
src/contexts/conversation-websocket-context.tsx has 1482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/contexts/conversation-websocket-context.tsx:1
src/api/agent-server-adapter.ts has 1467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/api/agent-server-adapter.ts:1
src/components/features/conversation-panel/conversation-panel.tsx has 1301 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/conversation-panel/conversation-panel.tsx:1
src/api/conversation-service/agent-server-conversation-service.api.ts has 1200 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/api/conversation-service/agent-server-conversation-service.api.ts:1
src/mocks/settings-handlers.ts has 1094 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/mocks/settings-handlers.ts:1
src/api/automation-service/automation-service.api.ts has 1053 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/api/automation-service/automation-service.api.ts:1
src/routes/automations-list.tsx has 878 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/automations-list.tsx:1
src/services/telemetry.ts has 828 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/telemetry.ts:1
src/api/settings-service/settings-service.api.ts has 821 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/api/settings-service/settings-service.api.ts:1
src/components/features/mcp-page/install-server-modal.tsx has 817 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/mcp-page/install-server-modal.tsx:1
electron/main.mjs has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — electron/main.mjs:1
src/components/features/settings/sdk-settings/sdk-section-page.tsx has 751 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/settings/sdk-settings/sdk-section-page.tsx:1
src/components/features/chat/chat-interface.tsx has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/chat/chat-interface.tsx:1
src/components/features/settings/mcp-settings/mcp-server-form.tsx has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/settings/mcp-settings/mcp-server-form.tsx:1
src/manifests/manifest-validation.ts has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/manifests/manifest-validation.ts:1
REDACTED has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
src/manifests/automation-setup.ts has 680 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/manifests/automation-setup.ts:1
src/utils/transcript-export/index.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/transcript-export/index.ts:1
src/components/features/manifest/manifest-setup-dialog.tsx has 657 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/manifest/manifest-setup-dialog.tsx:1
src/components/features/conversation-panel/conversation-panel-list-helpers.ts has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/conversation-panel/conversation-panel-list-helpers.ts:1
src/routes/llm-settings.tsx has 619 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/llm-settings.tsx:1
src/components/features/automations/setup/automation-setup-prompt-stack.tsx has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/automations/setup/automation-setup-prompt-stack.tsx:1
src/components/features/chat/components/chat-input-actions.tsx has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/chat/components/chat-input-actions.tsx:1
src/components/features/settings/llm-profiles/llm-settings-local-view.tsx has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:1
src/utils/utils.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/utils.ts:1
src/mocks/automation-handlers.ts has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/mocks/automation-handlers.ts:1
src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:1
src/constants/acp-providers.ts has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/constants/acp-providers.ts:1
src/services/child-conversation-launch.ts has 507 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/services/child-conversation-launch.ts:1
src/components/features/settings/llm-profiles/add-models-modal.tsx has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/settings/llm-profiles/add-models-modal.tsx:1
src/components/features/automations/recommended-automations-section.tsx has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/automations/recommended-automations-section.tsx:1
src/components/features/backends/managed-agents/managed-agents-view.tsx has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/backends/managed-agents/managed-agents-view.tsx:1
src/hooks/use-tracking.ts has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/hooks/use-tracking.ts:1
src/mocks/conversation-handlers.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/mocks/conversation-handlers.ts:1
src/api/mars/mars-tunnel-backend.ts has 447 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/api/mars/mars-tunnel-backend.ts:1
src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx:1
src/utils/sdk-settings-schema.ts has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/utils/sdk-settings-schema.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.9 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
__tests__/scripts/desktop-icons.test.ts:25 imports '../../electron/build-resources', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — __tests__/scripts/desktop-icons.test.ts:25
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×13) — scripts/seed-automation-ux-data.mjs:1, scripts/brand-dev-electron.mjs:1, scripts/generate-icons.mjs:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
53 outdated package(s); JS/npm CVEs scored in D30
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
This repository declares test tooling, and the ✓ above records that declaration — but __tests__/scripts/desktop-icons.test.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — __tests__/scripts/desktop-icons.test.ts:25
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
2303 file(s) (~410749 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: src/query-client-config.ts imports './i18n/declaration', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here.
Nothing imports this binding — it is safe to review for removal. (×11) — scripts/tunnel-client.mjs:50, src/components/features/controls/agent-status.tsx:191, src/components/features/controls/server-status.tsx:65, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — scripts/dev-safe.mjs:47
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. (×2) — stryker.config.mjs:3, src/components/features/markdown/markdown-renderer.tsx:8
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×2) — __tests__/components/features/markdown/markdown-renderer.test.tsx:3, global.d.ts:17
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
This function unwraps IPv4-MAPPED IPv6 (`::ffff:`, line 96) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 decision at line 93 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this function never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same function declares non-public — and all reach the IPv6 decision un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright. — src/components/features/backends/backend-form-modal.tsx:93
What to do
Each finding names the IPv4 branch that rejects the host and the IPv6 branch that accepts the same host in another notation. Confirm from the two, then unwrap every IPv4-in-IPv6 embedding before classifying, or reject non-native IPv6 outright.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`normalizeComparableValue` is exported, takes a document from its caller (line 175) and hands it to `stableJsonStringify`, which calls itself at line 160 (`stableJsonStringify`) with a piece of `value` (and at line 170) — and nowhere in `stableJsonStringify` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `stableJsonStringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/utils/sdk-settings-schema.ts:160
`hasRedactedMcpSecretLeaf` is exported and takes `value: unknown` from its caller, and it calls itself at line 46 (`hasRedactedMcpSecretLeaf`) with a piece of `value` (and at line 48) — and nowhere in `hasRedactedMcpSecretLeaf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `hasRedactedMcpSecretLeaf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/utils/mcp-config.ts:46
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 5/22 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`api` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — scripts/seed-automation-ux-data.mjs:626
`waitForService` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:275
`waitForServer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — scripts/dev-safe.mjs:962, scripts/dev-extra-backend.mjs:80
`fetchPyPIVersion` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — scripts/check-sdk-version-sync.mjs:219
`fetchPyPIDependencies` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — scripts/check-sdk-version-sync.mjs:252
`reportCanvasAuthenticated` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — src/api/main-app-auth.ts:32
`authenticateWithMainAppCookie` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — src/api/main-app-auth.ts:49
`fetchGithubJson` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/api/git-provider-items-service.ts:111
`fetchForgejoJson` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/api/git-provider-items-service.ts:130
`fetchGitlabJson` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/api/git-provider-items-service.ts:158
`syncTelemetryConsent` awaits `localAutomationAxios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.post(url, { signal })`. — src/api/automation-service/automation-service.api.ts:382
`createAutomation` awaits `localAutomationAxios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.delete(url, { signal })`. — src/api/automation-service/automation-service.api.ts:494
`deleteAutomation` awaits `localAutomationAxios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.delete(url, { signal })`. — src/api/automation-service/automation-service.api.ts:585
`deleteServerDraft` awaits `localAutomationAxios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.delete(url, { signal })`. — src/api/automation-service/automation-service.api.ts:919
`transcribe` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/hooks/chat/use-dictation.ts:50
`queryFn` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/hooks/query/use-workspace-file-content.ts:188
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.0 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`text` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/components/features/chat/mono-component.tsx:6, src/components/features/chat/path-component.tsx:20
``@keyframes ${animationName}{from{background-position:${SHIMMER_TRAVEL}% center}to{background-position:0% center}}`` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:74
`COLOR_THEME_BOOTSTRAP_SCRIPT` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/root.tsx:103
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×31) — electron/main.mjs:137, electron/main.mjs:245, electron/main.mjs:269, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×5) — electron/main.mjs:619, scripts/tunnel-registry.mjs:149, scripts/tunnel-registry.mjs:205, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — scripts/download-node.mjs:281, scripts/download-node.mjs:325, scripts/dev-safe.mjs:1251, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.3 `!` null assertions per 1k TypeScript source lines — 56 assertion(s) across the 162678 source line(s) of the 1322 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/components/conversation-events/chat/event-message-components/critic-result-display.tsx (5), REDACTED (4), src/hooks/query/use-repository-git-items.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 39 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:8010: page.goto: net::ERR_SOCKET_NOT_CONNECTED at http://127.0.0.1:8010/
Call log:
- navigating to "http://127.0.0.1:8010/", waiting until "load"
ran the repo's playwright suite against the booted app but captured no surfaces (suite failed to install/run, or visited no pages) — see runtime diagnostics. This repository also has a user interface (628 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not included
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .py, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 1282 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×7
Hover-only interaction on <div> src/components/features/chat/generic-event-message.tsx:77— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> src/components/features/conversation/conversation-overview-toggle.tsx:121— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> src/components/features/conversation/conversation-overview-toggle.tsx:142— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> src/components/features/sidebar/sidebar-rail-body.tsx:331— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> src/components/shared/buttons/copyable-content-wrapper.tsx:28— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> src/components/ui/resize-handle.tsx:27— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> src/ui/dropdown/dropdown.tsx:159— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC2 · Forms & labels· <input> without a programmatic label · ×6
<input> without a programmatic label REDACTED:2977— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:298— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/components/features/conversation-panel/conversation-card/conversation-card-title.tsx:20— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/features/conversation/conversation-name.tsx:150— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/features/manifest/manifest-form-field.tsx:198— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/components/features/settings/llm-profiles/add-models-modal.tsx:494— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×5
Click handler on a non-interactive <div> src/components/features/conversation-panel/conversation-card/conversation-card.tsx:269— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/components/features/conversation-panel/start-task-card/start-task-card.tsx:29— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/components/features/settings/settings-mobile-drawer.tsx:37— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/components/features/sidebar/sidebar.tsx:227— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/components/shared/modals/modal-backdrop.tsx:71— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×4
Custom control with no accessible name on <div> src/components/features/automations/detail/run-logs-modal.tsx:266— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/components/features/automations/turn-off-confirmation-modal.tsx:25— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/components/features/settings/settings-mobile-drawer.tsx:37— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/components/shared/modals/modal-backdrop.tsx:71— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels· <label> that labels no control · ×3
<label> that labels no control src/components/features/settings/llm-profiles/provider-connection-modal.tsx:193— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control src/components/shared/modals/settings/model-selector.tsx:168— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control src/components/shared/modals/settings/model-selector.tsx:241— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text src/components/features/alerts/alert-banner.tsx:131— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/components/shared/buttons/scroll-to-bottom-button.tsx:9— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <textarea> without a programmatic label · ×2
<textarea> without a programmatic label REDACTED:3452— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label src/routes/agent-settings.tsx:1665— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Hover-only interaction on <article> · ×1
Hover-only interaction on <article> src/components/features/chat/chat-message.tsx:150— This <article> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC4 · Keyboard semantics· Double-click handler on a non-interactive <div> · ×1
Double-click handler on a non-interactive <div> src/components/features/conversation/conversation-name.tsx:161— This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
AC4 · Keyboard semantics· Click handler on a non-interactive <aside> · ×1
Click handler on a non-interactive <aside> src/components/features/sidebar/sidebar.tsx:197— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <nav> · ×1
Click handler on a non-interactive <nav> src/components/shared/compact-section-navigation.tsx:56— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC5 · ARIA correctness· aria-hidden on a focusable element · ×1
aria-hidden on a focusable element src/ui/dropdown/dropdown.tsx:231— aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
Unlisted import 'hast-util-sanitize' __tests__/components/features/markdown/markdown-renderer.test.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
FunctionTooLong: automation-setup-panel.AutomationSetupPanel REDACTED:640— FunctionTooLong — AutomationSetupPanel runs 1403 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1303 over it, 14.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: agent-settings.AgentSettingsScreen src/routes/agent-settings.tsx:382— FunctionTooLong — AgentSettingsScreen runs 1113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1013 over it, 11.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: conversation-websocket-context.ConversationWebSocketProvider src/contexts/conversation-websocket-context.tsx:213— FunctionTooLong — ConversationWebSocketProvider runs 798 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 698 over it, 7.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: mcp-server-form.MCPServerForm src/components/features/settings/mcp-settings/mcp-server-form.tsx:50— FunctionTooLong — MCPServerForm runs 558 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 458 over it, 5.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: install-server-modal.InstallServerModal src/components/features/mcp-page/install-server-modal.tsx:161— FunctionTooLong — InstallServerModal runs 540 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 440 over it, 5.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: automations-list.AutomationsList src/routes/automations-list.tsx:297— FunctionTooLong — AutomationsList runs 469 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 369 over it, 4.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sdk-section-page.SdkSectionPage src/components/features/settings/sdk-settings/sdk-section-page.tsx:191— FunctionTooLong — SdkSectionPage runs 442 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 342 over it, 4.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: manifest-setup-dialog.SetupDialog src/components/features/manifest/manifest-setup-dialog.tsx:101— FunctionTooLong — SetupDialog runs 439 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 339 over it, 4.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: chat-input-actions.ChatInputActions src/components/features/chat/components/chat-input-actions.tsx:62— FunctionTooLong — ChatInputActions runs 427 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 327 over it, 4.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: llm-settings.LlmSettingsScreen src/routes/llm-settings.tsx:122— FunctionTooLong — LlmSettingsScreen runs 382 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 282 over it, 3.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: automation-setup-panel.EventFields REDACTED:3052— FunctionTooLong — EventFields runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: use-tracking.useTracking src/hooks/use-tracking.ts:48— FunctionTooLong — useTracking runs 347 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 247 over it, 3.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: agent-profiles-local-view.AgentProfilesLocalView src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:115— FunctionTooLong — AgentProfilesLocalView runs 334 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 234 over it, 3.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: automation-setup-prompt-stack.AutomationSetupPromptStack src/components/features/automations/setup/automation-setup-prompt-stack.tsx:238— FunctionTooLong — AutomationSetupPromptStack runs 327 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 227 over it, 3.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: managed-agents-view.ManagedAgentsView src/components/features/backends/managed-agents/managed-agents-view.tsx:132— FunctionTooLong — ManagedAgentsView runs 313 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 213 over it, 3.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: llm-settings-local-view.LlmSettingsLocalView src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:98— FunctionTooLong — LlmSettingsLocalView runs 312 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 212 over it, 3.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: git-sync-config-form.GitSyncConfigForm src/components/features/automations/git-sync/git-sync-config-form.tsx:43— FunctionTooLong — GitSyncConfigForm runs 308 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 208 over it, 3.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: meta-llm-settings-view.MetaLlmSettingsView src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx:56— FunctionTooLong — MetaLlmSettingsView runs 307 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 207 over it, 3.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sidebar-rail-body.SidebarRailBody src/components/features/sidebar/sidebar-rail-body.tsx:76— FunctionTooLong — SidebarRailBody runs 303 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 203 over it, 3.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: add-models-modal.AddModelsModal src/components/features/settings/llm-profiles/add-models-modal.tsx:77— FunctionTooLong — AddModelsModal runs 301 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 201 over it, 3.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: pinned-automation-card.PinnedAutomationCard src/components/features/home/featured-automations/pinned-automation-card.tsx:58— FunctionTooLong — PinnedAutomationCard runs 273 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 173 over it, 2.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: workspace-dropdown.WorkspaceDropdown src/components/features/home/workspace-dropdown/workspace-dropdown.tsx:54— FunctionTooLong — WorkspaceDropdown runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: command-menu.CommandMenu src/components/features/command-menu/command-menu.tsx:62— FunctionTooLong — CommandMenu runs 264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 164 over it, 2.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: conversation-card.ConversationCard src/components/features/conversation-panel/conversation-card/conversation-card.tsx:80— FunctionTooLong — ConversationCard runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: recommended-automations-launcher.RecommendedAutomationsLauncher src/components/features/automations/recommended-automations-launcher.tsx:100— FunctionTooLong — RecommendedAutomationsLauncher runs 250 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 150 over it, 2.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: src/routes/agent-settings.tsx src/routes/agent-settings.tsx:382— src/routes/agent-settings.tsx changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 202 in agent-settings.AgentSettingsScreen at line 382. 2 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/routes/agent-settings.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/contexts/conversation-websocket-context.tsx src/contexts/conversation-websocket-context.tsx:213— src/contexts/conversation-websocket-context.tsx changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 161 in conversation-websocket-context.ConversationWebSocketProvider at line 213. 6 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/contexts/conversation-websocket-context.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:640— REDACTED changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 220 in automation-setup-panel.AutomationSetupPanel at line 640. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/conversation-panel/conversation-panel.tsx src/components/features/conversation-panel/conversation-panel.tsx:84— src/components/features/conversation-panel/conversation-panel.tsx changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 121 in conversation-panel.ConversationPanel at line 84. 5 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/conversation-panel/conversation-panel.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/automations-list.tsx src/routes/automations-list.tsx:297— src/routes/automations-list.tsx changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in automations-list.AutomationsList at line 297. 4 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/routes/automations-list.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/chat/chat-interface.tsx src/components/features/chat/chat-interface.tsx:88— src/components/features/chat/chat-interface.tsx changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in chat-interface.ChatInterface at line 88. 7 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/chat/chat-interface.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:115— src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in agent-profiles-local-view.AgentProfilesLocalView at line 115. 6 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/mcp-page/install-server-modal.tsx src/components/features/mcp-page/install-server-modal.tsx:161— src/components/features/mcp-page/install-server-modal.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 107 in install-server-modal.InstallServerModal at line 161. 3 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/mcp-page/install-server-modal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/api/agent-server-adapter.ts src/api/agent-server-adapter.ts:1070— src/api/agent-server-adapter.ts changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in agent-server-adapter.buildStartConversationRequest at line 1070. 16 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/api/agent-server-adapter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/settings/llm-profiles/llm-settings-local-view.tsx src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:98— src/components/features/settings/llm-profiles/llm-settings-local-view.tsx changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in llm-settings-local-view.LlmSettingsLocalView at line 98. 7 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/settings/llm-profiles/llm-settings-local-view.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/settings/mcp-settings/mcp-server-form.tsx src/components/features/settings/mcp-settings/mcp-server-form.tsx:50— src/components/features/settings/mcp-settings/mcp-server-form.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 133 in mcp-server-form.MCPServerForm at line 50. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/settings/mcp-settings/mcp-server-form.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1507— REDACTED changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in dev-with-automation.main at line 1507. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/manifest/manifest-setup-dialog.tsx src/components/features/manifest/manifest-setup-dialog.tsx:101— src/components/features/manifest/manifest-setup-dialog.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 81 in manifest-setup-dialog.SetupDialog at line 101. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/manifest/manifest-setup-dialog.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/chat/components/chat-input-actions.tsx src/components/features/chat/components/chat-input-actions.tsx:62— src/components/features/chat/components/chat-input-actions.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in chat-input-actions.ChatInputActions at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/chat/components/chat-input-actions.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/conversation-panel/conversation-card/conversation-card.tsx src/components/features/conversation-panel/conversation-card/conversation-card.tsx:80— src/components/features/conversation-panel/conversation-card/conversation-card.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 61 in conversation-card.ConversationCard at line 80. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/conversation-panel/conversation-card/conversation-card.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/home/home-chat-launcher.tsx src/components/features/home/home-chat-launcher.tsx:56— src/components/features/home/home-chat-launcher.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in home-chat-launcher.HomeChatLauncher at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/home/home-chat-launcher.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/api/conversation-service/agent-server-conversation-service.api.ts src/api/conversation-service/agent-server-conversation-service.api.ts:517— src/api/conversation-service/agent-server-conversation-service.api.ts changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AgentServerConversationService.createConversation at line 517. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/api/conversation-service/agent-server-conversation-service.api.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/automations/recommended-automations-launcher.tsx src/components/features/automations/recommended-automations-launcher.tsx:100— src/components/features/automations/recommended-automations-launcher.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in recommended-automations-launcher.RecommendedAutomationsLauncher at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/automations/recommended-automations-launcher.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/settings/sdk-settings/sdk-section-page.tsx src/components/features/settings/sdk-settings/sdk-section-page.tsx:191— src/components/features/settings/sdk-settings/sdk-section-page.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 82 in sdk-section-page.SdkSectionPage at line 191. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/settings/sdk-settings/sdk-section-page.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/llm-settings.tsx src/routes/llm-settings.tsx:122— src/routes/llm-settings.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in llm-settings.LlmSettingsScreen at line 122. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/routes/llm-settings.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/dev-safe.mjs scripts/dev-safe.mjs:1009— scripts/dev-safe.mjs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in dev-safe.main at line 1009. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- scripts/dev-safe.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/app-settings.tsx src/routes/app-settings.tsx:45— src/routes/app-settings.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in app-settings.AppSettingsForm at line 45. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/routes/app-settings.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/conversation-events/chat/event-message.tsx src/components/conversation-events/chat/event-message.tsx:180— src/components/conversation-events/chat/event-message.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in event-message.EventMessageComponent at line 180. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/conversation-events/chat/event-message.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/conversation/conversation-main/conversation-main.tsx src/components/features/conversation/conversation-main/conversation-main.tsx:79— src/components/features/conversation/conversation-main/conversation-main.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in conversation-main.ConversationMain at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/conversation/conversation-main/conversation-main.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/features/automations/automation-card.tsx src/components/features/automations/automation-card.tsx:59— src/components/features/automations/automation-card.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in automation-card.AutomationCard at line 59. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/automations/automation-card.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Cross-slice coupling: analytics → settings src/components/features/analytics/telemetry-consent-banner.tsx:105— `LocalTelemetryConsentBanner` (slice 'analytics') depends on `BrandButton` from slice 'settings'.
Cross-slice coupling: automations → context-menu src/components/features/automations/add-automation-menu.tsx:97— `AddAutomationMenu` (slice 'automations') depends on `ContextMenuListItem` from slice 'context-menu'.
Cross-slice coupling: automations → settings src/components/features/automations/add-automation-menu.tsx:129— `AddAutomationMenu` (slice 'automations') depends on `BrandButton` from slice 'settings'.
Cross-slice coupling: automations → settings src/components/features/automations/agent-profile-selector.tsx:33— `AutomationAgentProfileSelector` (slice 'automations') depends on `SettingsDropdownInput` from slice 'settings'.
Cross-slice coupling: automations → home src/components/features/automations/automation-card.tsx:111— `AutomationCard` (slice 'automations') depends on `getLastRunTimestamp` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-card.tsx:114— `AutomationCard` (slice 'automations') depends on `shortenAutomationRunSummary` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-card.tsx:118— `AutomationCard` (slice 'automations') depends on `shouldShowAutomationRunSummaryHovercard` from slice 'home'.
Cross-slice coupling: automations → skills src/components/features/automations/automation-card.tsx:192— `AutomationCard` (slice 'automations') depends on `SkillCardPillRow` from slice 'skills'.
Cross-slice coupling: automations → home src/components/features/automations/automation-card.tsx:199— `AutomationCard` (slice 'automations') depends on `AutomationRunActivitySparkline` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:96— `AutomationListRow` (slice 'automations') depends on `getTriggerEventLabel` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:97— `AutomationListRow` (slice 'automations') depends on `getTriggerScheduleLabel` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:98— `AutomationListRow` (slice 'automations') depends on `getTriggerSource` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:104— `AutomationListRow` (slice 'automations') depends on `deriveRunHealth` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:112— `AutomationListRow` (slice 'automations') depends on `getLastRunTimestamp` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:120— `AutomationListRow` (slice 'automations') depends on `getRunStatusLabelKey` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:131— `AutomationListRow` (slice 'automations') depends on `HomeAutomationRunTooltip` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:151— `AutomationListRow` (slice 'automations') depends on `AutomationHealthIndicator` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:177— `AutomationListRow` (slice 'automations') depends on `formatTriggerSourceLabel` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/automation-list-row.tsx:232— `AutomationListRow` (slice 'automations') depends on `AutomationRunActivitySparkline` from slice 'home'.
Cross-slice coupling: automations → context-menu src/components/features/automations/automation-view-toggle.tsx:111— `AutomationViewToggle` (slice 'automations') depends on `ContextMenuListItem` from slice 'context-menu'.
Cross-slice coupling: automations → settings src/components/features/automations/backend-not-configured.tsx:22— `BackendUnavailable` (slice 'automations') depends on `BrandButton` from slice 'settings'.
Cross-slice coupling: automations → skills src/components/features/automations/build-automation-pills.tsx:21— `buildAutomationMetadataPills` (slice 'automations') depends on `SkillCardPill` from slice 'skills'.
Cross-slice coupling: automations → home src/components/features/automations/build-automation-pills.tsx:37— `buildAutomationMetadataPills` (slice 'automations') depends on `getTriggerEventLabel` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/build-automation-pills.tsx:50— `buildAutomationMetadataPills` (slice 'automations') depends on `getTriggerSource` from slice 'home'.
Cross-slice coupling: automations → home src/components/features/automations/build-automation-pills.tsx:73— `buildAutomationMetadataPills` (slice 'automations') depends on `formatTriggerSourceLabel` from slice 'home'.
Boundary violation [package:test-cross-package-internals] __tests__/electron/lib/bundled-runtime-dir.test.ts:13— __tests__/electron/lib/bundled-runtime-dir.test.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../../electron/lib/bundled-runtime-dir.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:third-party-deep-import] src/components/features/conversation-panel/conversation-card/conversation-repo-link.tsx:3— src/components/features/conversation-panel/conversation-card/conversation-repo-link.tsx:3 imports react-icons/lib, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/diff-viewer/file-diff-viewer.tsx:13— src/components/features/diff-viewer/file-diff-viewer.tsx:13 imports react-icons/lib, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:2— src/components/features/markdown/syntax-highlighter.ts:2 imports react-syntax-highlighter/dist/esm/languages/prism/bash, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:3— src/components/features/markdown/syntax-highlighter.ts:3 imports react-syntax-highlighter/dist/esm/languages/prism/batch, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:4— src/components/features/markdown/syntax-highlighter.ts:4 imports react-syntax-highlighter/dist/esm/languages/prism/c, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:5— src/components/features/markdown/syntax-highlighter.ts:5 imports react-syntax-highlighter/dist/esm/languages/prism/clike, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:6— src/components/features/markdown/syntax-highlighter.ts:6 imports react-syntax-highlighter/dist/esm/languages/prism/clojure, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:7— src/components/features/markdown/syntax-highlighter.ts:7 imports react-syntax-highlighter/dist/esm/languages/prism/cpp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:8— src/components/features/markdown/syntax-highlighter.ts:8 imports react-syntax-highlighter/dist/esm/languages/prism/csharp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:9— src/components/features/markdown/syntax-highlighter.ts:9 imports react-syntax-highlighter/dist/esm/languages/prism/css, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:10— src/components/features/markdown/syntax-highlighter.ts:10 imports react-syntax-highlighter/dist/esm/languages/prism/dart, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:11— src/components/features/markdown/syntax-highlighter.ts:11 imports react-syntax-highlighter/dist/esm/languages/prism/diff, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:12— src/components/features/markdown/syntax-highlighter.ts:12 imports react-syntax-highlighter/dist/esm/languages/prism/docker, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:13— src/components/features/markdown/syntax-highlighter.ts:13 imports react-syntax-highlighter/dist/esm/languages/prism/elixir, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:14— src/components/features/markdown/syntax-highlighter.ts:14 imports react-syntax-highlighter/dist/esm/languages/prism/erlang, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:15— src/components/features/markdown/syntax-highlighter.ts:15 imports react-syntax-highlighter/dist/esm/languages/prism/fsharp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:16— src/components/features/markdown/syntax-highlighter.ts:16 imports react-syntax-highlighter/dist/esm/languages/prism/go, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:17— src/components/features/markdown/syntax-highlighter.ts:17 imports react-syntax-highlighter/dist/esm/languages/prism/graphql, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:18— src/components/features/markdown/syntax-highlighter.ts:18 imports react-syntax-highlighter/dist/esm/languages/prism/groovy, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:19— src/components/features/markdown/syntax-highlighter.ts:19 imports react-syntax-highlighter/dist/esm/languages/prism/haskell, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:20— src/components/features/markdown/syntax-highlighter.ts:20 imports react-syntax-highlighter/dist/esm/languages/prism/hcl, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:21— src/components/features/markdown/syntax-highlighter.ts:21 imports react-syntax-highlighter/dist/esm/languages/prism/http, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:22— src/components/features/markdown/syntax-highlighter.ts:22 imports react-syntax-highlighter/dist/esm/languages/prism/ini, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/features/markdown/syntax-highlighter.ts:23— src/components/features/markdown/syntax-highlighter.ts:23 imports react-syntax-highlighter/dist/esm/languages/prism/java, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Swallowed exception (empty catch) electron/main.mjs:137— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) electron/main.mjs:245— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) electron/main.mjs:269— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) electron/main.mjs:302— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) electron/main.mjs:619— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) scripts/tunnel-registry.mjs:149— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) scripts/tunnel-registry.mjs:205— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) scripts/static-server.mjs:746— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) scripts/proxy-utils.mjs:237— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/mars-oauth.mjs:253— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/mars-api.mjs:140— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/ingress.mjs:242— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) scripts/gen-acp-docker-env.mjs:89— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-uv.mjs:219— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-uv.mjs:220— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-node.mjs:160— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-node.mjs:256— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-node.mjs:294— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-node.mjs:335— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/download-node.mjs:399— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:661— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:285— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/dev-safe.mjs:971— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/dev-safe.mjs:1261— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/dev-extra-backend.mjs:89— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Repeated repair: src/hooks/mutation/use-create-conversation.ts src/hooks/mutation/use-create-conversation.ts:65— src/hooks/mutation/use-create-conversation.ts changed 15 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is use-create-conversation.useCreateConversation at line 65), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): let a Cloud member pick the LLM profile on the home page (OHE-3669) (#18729)”; “fix(agent-profiles): keep the profile on per-launch LLM picks and in /new (#18419)”; “fix(home): show one error toast and keep the prompt when a launch fails (#17985)”; “fix: provide runtime services to named agent profiles (#17279)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/mutation/use-create-conversation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/services/telemetry.ts src/services/telemetry.ts:751— src/services/telemetry.ts changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is telemetry.trackInstall at line 751), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(telemetry): never initialize PostHog under Do Not Track (#18086)”; “fix: consume consent-aware website PostHog handoff (#16976)”; “fix: Disable PostHog autocapture (#17502)”; “fix: Add --disable-telemetry runtime flag for self-hosted canvas (#16908)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/services/telemetry.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: vitest.setup.ts vitest.setup.ts:118— vitest.setup.ts changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is vitest.setup.installXhrGlobalsFallback at line 118), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(test): drain MSW's in-flight requests instead of 30 event-loop turns (#16890)”; “fix: OHE-3110 : remove misleading "No budget limit" line from Token Usage panel (#17264)”; “fix(test): keep ProgressEvent resolvable after jsdom teardown (#17116)”; “fix: prevent silent agent profile downgrade (#16523)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- vitest.setup.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: electron/main.mjs electron/main.mjs:189— electron/main.mjs changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is main.injectBundledNode at line 189), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: fail the launch when the automation backend exits during startup (#18311)”; “fix(desktop): restore the macOS title bar drag region (#17474)”; “fix(desktop): parse window-open URLs instead of prefix-matching localhost (#16961)”; “fix(desktop): ship the bundled Node's npm on Windows (#16381)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- electron/main.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:114— REDACTED changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is dev-static.parseArgs at line 114), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(launcher): create the resolved terminal socket directory (#18368)”; “revert: restore bundled VS Code consumer support (#18048)”; “fix: keep local session keys off externally reachable listeners (#17007)”; “fix: render the VSCode button on self-hosted (local) backends (#16106)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/routes/settings.tsx src/routes/settings.tsx:55— src/routes/settings.tsx changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is settings.SettingsScreen at line 55), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(settings): give the settings screen a definite height (#18256)”; “fix: keep settings and customization usable on tablets (#17910)”; “fix(a11y): one Settings main landmark, Customize aria-current, synced html lang (#18012)”; “fix: block hidden Canvas settings pages when locked to a Cloud host (#17866)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/routes/settings.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: vite.config.ts vite.config.ts:156— vite.config.ts changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is (anonymous) at line 156), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(library): ship a scoped stylesheet with the npm library (#18663)”; “fix(library): preserve ESM peer imports in browser hosts (#18619)”; “fix: keep local session keys off externally reachable listeners (#17007)”; “fix: render the VSCode button on self-hosted (local) backends (#16106)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- vite.config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: tests/e2e/mock-llm/utils/mock-llm-helpers.ts tests/e2e/mock-llm/utils/mock-llm-helpers.ts:352— tests/e2e/mock-llm/utils/mock-llm-helpers.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is retryOnTransient at line 352), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: preserve base_url for subscription LLM configs (#16089)”; “fix(settings): disable save when edits are reverted (#16120)”; “fix: preserve backend scope in conversation links (#16091)”; “fix: Revive local telemetry consent banner (#16183)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- tests/e2e/mock-llm/utils/mock-llm-helpers.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/query/use-cloud-organizations.ts src/hooks/query/use-cloud-organizations.ts:28— src/hooks/query/use-cloud-organizations.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is use-cloud-organizations.useAllCloudOrganizations at line 28), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: back off and stop refetch-on-focus bursts that trip cloud rate limits (#17984)”; “fix: recover stale organization selections (#17671)”; “fix(canvas): hide cloud orgs the server marks is_visible=false (#17624)”; “fix: identify PostHog users with Cloud identity (#16087)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/query/use-cloud-organizations.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/use-settings-nav-items.ts src/hooks/use-settings-nav-items.ts:23— src/hooks/use-settings-nav-items.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is use-settings-nav-items.useSettingsNavItems at line 23), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: block hidden Canvas settings pages when locked to a Cloud host (#17866)”; “fix: scope the settings nav to Application when locked to Cloud (#17045)”; “fix: remove ACP settings access gating (#1908)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/use-settings-nav-items.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/components/features/conversation-panel/hook-matcher-content.tsx src/components/features/conversation-panel/hook-matcher-content.tsx:14— src/components/features/conversation-panel/hook-matcher-content.tsx changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is hook-matcher-content.HookMatcherContent at line 14), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(hooks): pick the Available Hooks text by hook type (#18215)”; “fix(hooks): show prompt and agent hook text in the Available Hooks dialog (#18107)”; “fix(hooks): list workspace hooks in the Available Hooks dialog on local backends (#18031)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/conversation-panel/hook-matcher-content.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/mutation/use-manage-canvas-extensions.ts src/hooks/mutation/use-manage-canvas-extensions.ts:25— src/hooks/mutation/use-manage-canvas-extensions.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is use-manage-canvas-extensions.useInstallCanvasExtension at line 25), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(plugins,apps): show the server's reason once for failed installs and updates (#18025)”; “fix(settings): show the server's message instead of raw HttpError text in profile error toasts (#18030)”; “fix(canvas-extensions): show the install failure reason (#17120)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/mutation/use-manage-canvas-extensions.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/components/features/sidebar/use-sidebar-onboarding-checklist.ts src/components/features/sidebar/use-sidebar-onboarding-checklist.ts:40— src/components/features/sidebar/use-sidebar-onboarding-checklist.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is use-sidebar-onboarding-checklist.useSidebarOnboardingChecklist at line 40), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sidebar): hide the Getting started checklist on a canvas locked to a Cloud host (OHE-3683) (#18739)”; “fix: block hidden Canvas settings pages when locked to a Cloud host (#17866)”; “fix(automations): page the list by offset so Load more works past 100 (#17839)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/sidebar/use-sidebar-onboarding-checklist.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/api/cloud/conversation-service.api.ts src/api/cloud/conversation-service.api.ts:29— src/api/cloud/conversation-service.api.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is conversation-service.api.overlayStoredRepoSelection at line 29), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(conversations): save a connected repository on the cloud conversation (#18158)”; “fix: rename conversation title on cloud backends (#16966)”; “fix: show full workspace file tree in Files tab on cloud backends (OHE-3053) (#16344)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/api/cloud/conversation-service.api.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/utils/custom-toast-handlers.tsx src/utils/custom-toast-handlers.tsx:37— src/utils/custom-toast-handlers.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is custom-toast-handlers.ErrorToastContent at line 37), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(themes): make toast text readable in light themes (#18403)”; “fix(plugins,apps): show the server's reason once for failed installs and updates (#18025)”; “fix(canvas): keep the base path on links that leave the app (#17617)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/utils/custom-toast-handlers.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/components/features/chat/components/context-window-meter.tsx src/components/features/chat/components/context-window-meter.tsx:38— src/components/features/chat/components/context-window-meter.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is context-window-meter.ContextWindowMeter at line 38), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(theme): keep composer context feedback readable (#18504)”; “fix(a11y): close menus and popovers on Escape and return focus (#18044)”; “fix(context-meter): draw the ring track from the foreground, not a border token (#16534)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/features/chat/components/context-window-meter.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/chat/use-chat-input-logic.ts src/hooks/chat/use-chat-input-logic.ts:19— src/hooks/chat/use-chat-input-logic.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is use-chat-input-logic.useChatInputLogic at line 19), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(automations): keep the setup composer out of the Home draft (#18392)”; “fix(home): show one error toast and keep the prompt when a launch fails (#17985)”; “fix(skills): pre-fill the Home composer from Use skill and Create Automation (#18016)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/chat/use-chat-input-logic.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: scripts/dev-extra-backend.mjs scripts/dev-extra-backend.mjs:124— scripts/dev-extra-backend.mjs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is dev-extra-backend.main at line 124), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “revert: restore bundled VS Code consumer support (#18048)”; “fix: clean up dev:extra-backend agent-server on SIGHUP (#16280)”; “fix: render the VSCode button on self-hosted (local) backends (#16106)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- scripts/dev-extra-backend.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/use-telemetry-identity.ts src/hooks/use-telemetry-identity.ts:54— src/hooks/use-telemetry-identity.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is use-telemetry-identity.useTelemetryIdentity at line 54), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: identify PostHog users with Cloud identity (#16087)”; “fix: Track cookie-auth Cloud backend connections (#16113)”; “fix: keep PostHog identity stable for Cloud context (#1892)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/use-telemetry-identity.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/api/backend-registry/active-store.ts src/api/backend-registry/active-store.ts:66— src/api/backend-registry/active-store.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is active-store.computeSnapshot at line 66), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(backends): open on the org the cloud web app hands back (#18228)”; “fix(backends): pin backend identity on sidebar conversation links (#16243)”; “fix(backend-registry): pick a healthy local backend as the fallback (#16173)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/api/backend-registry/active-store.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/query/use-paginated-conversations.ts src/hooks/query/use-paginated-conversations.ts:10— src/hooks/query/use-paginated-conversations.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is use-paginated-conversations.usePaginatedConversations at line 10), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: cloud conversation org scoping (#18130)”; “fix: bound automation run-history fan-out and pause sidebar polling (#16867)”; “fix: keep the events socket alive across refetches and bound hung handshakes (#16732)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/query/use-paginated-conversations.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/components/shared/navigation-link.tsx src/components/shared/navigation-link.tsx:55— src/components/shared/navigation-link.tsx changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is navigation-link.NavigationLink at line 55), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(a11y): one Settings main landmark, Customize aria-current, synced html lang (#18012)”; “fix(canvas): keep the base path on links that leave the app (#17617)”; “fix(backends): pin backend identity on sidebar conversation links (#16243)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/components/shared/navigation-link.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/hooks/use-bash-command-runner.ts src/hooks/use-bash-command-runner.ts:13— src/hooks/use-bash-command-runner.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is use-bash-command-runner.useBashCommandRunner at line 13), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(canvas): respect scoped runtime clients and workspace capabilities (#17387)”; “fix: keep the events socket alive across refetches and bound hung handshakes (#16732)”; “fix(security): authenticate WebSockets outside URLs (#16095)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/hooks/use-bash-command-runner.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/utils/parse-git-remote-url.ts src/utils/parse-git-remote-url.ts:93— src/utils/parse-git-remote-url.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is parse-git-remote-url.parseGitRemoteUrl at line 93), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: recognize Azure DevOps SSH remotes (#17375)”; “fix(git): stop reading a remote URL's port as part of the repository path (#16723)”; “fix: normalize trailing slash in git remote URLs (#16536)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 13:47:02 +00:00' --until='2026-10-21 13:47:02 +00:00' --full-history --no-merges -- src/utils/parse-git-remote-url.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: REDACTED REDACTED— FileTooLong — 2996 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2496 over it, 5.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: routes/agent-settings.tsx src/routes/agent-settings.tsx— FileTooLong — 1397 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: AgentSettingsScreen (382-1818). The bar is 500 significant lines; this is 897 over it, 2.79× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: backends/backend-form-modal.tsx src/components/features/backends/backend-form-modal.tsx— FileTooLong — 1350 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 850 over it, 2.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1046 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 546 over it, 2.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: api/agent-server-adapter.ts src/api/agent-server-adapter.ts— FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 474 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: contexts/conversation-websocket-context.tsx src/contexts/conversation-websocket-context.tsx— FileTooLong — 955 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: ConversationWebSocketProvider (213-1598). The bar is 500 significant lines; this is 455 over it, 1.91× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: conversation-panel/conversation-panel.tsx src/components/features/conversation-panel/conversation-panel.tsx— FileTooLong — 940 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 440 over it, 1.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: conversation-service/agent-server-conversation-service.api.ts src/api/conversation-service/agent-server-conversation-service.api.ts— FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: AgentServerConversationService (479-1302). The bar is 500 significant lines; this is 300 over it, 1.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: automation-service/automation-service.api.ts src/api/automation-service/automation-service.api.ts— FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: AutomationService (381-1169). The bar is 500 significant lines; this is 278 over it, 1.56× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: routes/automations-list.tsx src/routes/automations-list.tsx— FileTooLong — 729 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: AutomationsList (297-929). The bar is 500 significant lines; this is 229 over it, 1.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: mcp-page/install-server-modal.tsx src/components/features/mcp-page/install-server-modal.tsx— FileTooLong — 652 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: InstallServerModal (161-853). The bar is 500 significant lines; this is 152 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: scripts/seed-automation-ux-data.mjs scripts/seed-automation-ux-data.mjs— FileTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 135 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scripts/dev-safe.mjs scripts/dev-safe.mjs— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mcp-settings/mcp-server-form.tsx src/components/features/settings/mcp-settings/mcp-server-form.tsx— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: MCPServerForm (50-777). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: transcript-export/index.ts src/utils/transcript-export/index.ts— FileTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 61 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sdk-settings/sdk-section-page.tsx src/components/features/settings/sdk-settings/sdk-section-page.tsx— FileTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: SdkSectionPage (191-813). The bar is 500 significant lines; this is 54 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: manifest/manifest-setup-dialog.tsx src/components/features/manifest/manifest-setup-dialog.tsx— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: SetupDialog (101-670). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: chat/chat-interface.tsx src/components/features/chat/chat-interface.tsx— FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: setup/automation-setup-prompt-stack.tsx src/components/features/automations/setup/automation-setup-prompt-stack.tsx— FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: AutomationSetupPromptStack (238-594). The bar is 500 significant lines; this is 35 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 15 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: services/telemetry.ts src/services/telemetry.ts— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Skipped test: (unnamed test) tests/e2e/conversation-markdown-render-performance.spec.ts:224— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/conversation-markdown-render-performance.spec.ts:228— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/bind-policy/loopback-bind.spec.ts:142— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/canvas-extensions/app-backend-sandbox.spec.ts:103— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/live/real-agent-server-conversation.spec.ts:97— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/live/real-agent-server-conversation.spec.ts:146— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/backends/mock-llm-partial-stack.spec.ts:191— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/backends/mock-llm-partial-stack.spec.ts:357— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/backends/mock-llm-partial-stack.spec.ts:398— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/backends/mock-llm-cross-connect.spec.ts:349— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/backends/mock-llm-cross-connect.spec.ts:470— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/backends/mock-llm-cross-connect.spec.ts:673— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/conversations/mock-llm-conversation.spec.ts:410— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/files/mock-llm-files-and-git.spec.ts:196— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/files/mock-llm-files-and-git.spec.ts:250— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/files/mock-llm-files-and-git.spec.ts:293— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/settings/mock-llm-acp-auth-banner.spec.ts:172— Skipped — switched off by test.skip
Skipped test: (unnamed test) tests/e2e/mock-llm/settings/mock-llm-acp-agent.spec.ts:336— Skipped — switched off by test.skip
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×17
Animation without a prefers-reduced-motion guard electron/loading.html:87— `.spinner` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/features/backends/device-flow-auth.tsx:362— <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/components/features/conversation-panel/hooks-loading-state.tsx:4— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/components/features/conversation-panel/skills-loading-state.tsx:4— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/components/features/diff-viewer/loading-spinner.tsx:14— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:193— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard REDACTED:293— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/components/features/home/shared/loading-spinner.tsx:20— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/routes/device-verify.tsx:135— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/routes/device-verify.tsx:235— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/routes/mcp.tsx:105— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/ui/dropdown/loading-spinner.tsx:3— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/index.css:156— `.environment-switch-overlay > div` moves (`animation: environment-switch-overlay-fade 980ms ease-in-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/tailwind.css:656— `.shine-text` moves (`animation: shine 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/tailwind.css:686— `.gradient-flow` moves (`animation: gradient-slide 1.25s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/features/setup-guide/tour/tour-theme.css:163— `[data-agent-server-ui].driver-fade .driver-overlay` moves (`animation: animate-fade-in 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/features/setup-guide/tour/tour-theme.css:167— `[data-agent-server-ui].driver-fade .driver-popover` moves (`animation: animate-fade-in 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
X2 · Cancellation propagation· Async function without AbortSignal · ×17
Async function without AbortSignal: api scripts/seed-automation-ux-data.mjs:626— `api` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: waitForService REDACTED:275— `waitForService` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: waitForServer scripts/dev-safe.mjs:962— `waitForServer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: waitForServer scripts/dev-extra-backend.mjs:80— `waitForServer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchPyPIVersion scripts/check-sdk-version-sync.mjs:219— `fetchPyPIVersion` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchPyPIDependencies scripts/check-sdk-version-sync.mjs:252— `fetchPyPIDependencies` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: reportCanvasAuthenticated src/api/main-app-auth.ts:32— `reportCanvasAuthenticated` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`.
Async function without AbortSignal: authenticateWithMainAppCookie src/api/main-app-auth.ts:49— `authenticateWithMainAppCookie` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`.
Async function without AbortSignal: fetchGithubJson src/api/git-provider-items-service.ts:111— `fetchGithubJson` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchForgejoJson src/api/git-provider-items-service.ts:130— `fetchForgejoJson` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchGitlabJson src/api/git-provider-items-service.ts:158— `fetchGitlabJson` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: syncTelemetryConsent src/api/automation-service/automation-service.api.ts:382— `syncTelemetryConsent` awaits `localAutomationAxios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.post(url, { signal })`.
Async function without AbortSignal: createAutomation src/api/automation-service/automation-service.api.ts:494— `createAutomation` awaits `localAutomationAxios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.delete(url, { signal })`.
Async function without AbortSignal: deleteAutomation src/api/automation-service/automation-service.api.ts:585— `deleteAutomation` awaits `localAutomationAxios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.delete(url, { signal })`.
Async function without AbortSignal: deleteServerDraft src/api/automation-service/automation-service.api.ts:919— `deleteServerDraft` awaits `localAutomationAxios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `localAutomationAxios.delete(url, { signal })`.
Async function without AbortSignal: transcribe src/hooks/chat/use-dictation.ts:50— `transcribe` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: queryFn src/hooks/query/use-workspace-file-content.ts:188— `queryFn` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Focus outline removed inline src/components/features/automations/search-input.tsx:29— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline REDACTED:2553— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline REDACTED:3173— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/automations/setup/automation-setup-prompt-stack.tsx:348— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/automations/setup/automation-setup-prompt-stack.tsx:450— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/backends/managed-agents/managed-agents-view.tsx:349— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/chat/components/chat-input-field.tsx:58— <div> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/command-menu/command-menu.tsx:222— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/conversation/conversation-name.tsx:150— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/mcp-page/mcp-toolbar.tsx:42— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/plugins/plugin-picker.tsx:109— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/plugins/plugins-toolbar.tsx:49— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/features/skills/skills-toolbar.tsx:35— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/routes/agent-settings.tsx:1665— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
R4 · Test Coverage· No test reaches this file · ×13
No test reaches this file scripts/seed-automation-ux-data.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/brand-dev-electron.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/generate-icons.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/canvas-extension-page.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file electron/preload-main.cjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/docker-build.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/dev/seed-pending-chat-preview.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file hero.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/entry.client.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/meta-llm-settings.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file electron/preload.cjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/condenser-settings.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/agent-profiles-settings.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×10
Markup wires an event to an empty handler src/components/features/backends/api-key-entry-screen.tsx:105— `onSubmitted` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/backends/managed-agents/digitalocean-new-agent-form.tsx:132— `onInputChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/chat/uploaded-files.tsx:56— `onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/chat/uploaded-files.tsx:83— `onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/conversation/conversation-tabs/conversation-tabs.tsx:344— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/mcp-page/install-server-modal.tsx:646— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/settings/mcp-settings/mcp-server-form.tsx:475— `onInputChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/settings/mcp-settings/mcp-server-form.tsx:520— `onInputChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/features/settings/mcp-settings/mcp-server-form.tsx:568— `onInputChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/routes/agent-settings.tsx:1333— `onToggle` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
No assertions: emits browser-compatible ESM when a bundled CommonJS dependency requires a React peer __tests__/vite-config.test.ts:195— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows the empty state when there are no profiles __tests__/components/settings/agent-profiles/agent-profiles-manager.test.tsx:183— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows an error message when loading fails __tests__/components/settings/agent-profiles/agent-profiles-manager.test.tsx:194— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows empty state when no profiles exist __tests__/components/settings/llm-profiles/llm-profiles-manager.test.tsx:480— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows error message when loading fails __tests__/components/settings/llm-profiles/llm-profiles-manager.test.tsx:502— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should call onClick when clicked __tests__/components/shared/brand-button.test.tsx:36— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should pass a start content __tests__/components/shared/brand-button.test.tsx:57— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render __tests__/hooks/use-terminal.test.tsx:83— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: surfaces automations created since the last visit without a manual refresh __tests__/routes/automations-list.test.tsx:899— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×6
Modal dialog does not manage focus src/components/features/automations/detail/run-logs-modal.tsx:260— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/features/automations/turn-off-confirmation-modal.tsx:33— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/features/command-menu/command-menu.tsx:200— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:308— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/features/skills/skill-card-pill-row.tsx:250— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus src/components/shared/modals/modal-backdrop.tsx:59— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
AC2 · Forms & labels· <fieldset> without a <legend> · ×4
<fieldset> without a <legend> src/components/features/settings/llm-profiles/provider-connection-modal.tsx:192— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> src/components/shared/modals/settings/model-selector.tsx:167— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> src/components/shared/modals/settings/model-selector.tsx:240— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> src/routes/app-settings.tsx:208— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
Sync-over-async blocking scripts/dev-safe.mjs:1032— `mkdirSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:621— `mkdirSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1668— `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/logger.mjs:58— `mkdirSync` in `createFileLogger` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped src/components/features/chat/mono-component.tsx:6— `text` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/components/features/chat/path-component.tsx:20— `text` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:74— ``@keyframes ${animationName}{from{background-position:${SHIMMER_TRAVEL}% center}to{background-position:0% center}}`` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/root.tsx:103— `COLOR_THEME_BOOTSTRAP_SCRIPT` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Swallowed exception (caught, then discarded) scripts/download-node.mjs:281— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) scripts/download-node.mjs:325— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) scripts/dev-safe.mjs:1251— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/components/features/analytics/telemetry-consent-banner.tsx:65— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement src/tailwind.css:371— `.chat-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/components/features/setup-guide/tour/tour-theme.css:131— `.oh-setup-tour-popover .driver-popover-close-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/components/features/setup-guide/tour/tour-theme.css:141— `.oh-setup-tour-popover .driver-popover-close-btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Duplicated block (37 lines × 2 locations) src/components/features/automations/add-automation-menu.tsx:38— src/components/features/automations/add-automation-menu.tsx:38 · src/components/features/automations/automation-view-toggle.tsx:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (37 lines × 2 locations) src/components/features/chat/tool-visualizers/primitives/markdown-file-preview.tsx:57— src/components/features/chat/tool-visualizers/primitives/markdown-file-preview.tsx:57 · src/components/features/chat/tool-visualizers/primitives/markdown-file-preview.tsx:99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (37 lines × 2 locations) src/components/features/home/open-repository-dialog.tsx:22— src/components/features/home/open-repository-dialog.tsx:22 · src/components/features/home/open-workspace-dialog.tsx:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
AC2 · Forms & labels· <SearchInput> field component without a label · ×2
<SearchInput> field component without a label src/routes/automation-templates.tsx:45— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<SearchInput> field component without a label src/routes/automations-list.tsx:757— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
install-server-modal.InstallServerModal::handleHttpServerSubmit (cyclomatic 27) src/components/features/mcp-page/install-server-modal.tsx:380— install-server-modal.InstallServerModal::handleHttpServerSubmit has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: 2 other methods here (install-server-modal.InstallServerModal, install-server-modal.InstallServerModal::handleStdioSubmit) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
install-server-modal.InstallServerModal::handleStdioSubmit (cyclomatic 16) src/components/features/mcp-page/install-server-modal.tsx:469— install-server-modal.InstallServerModal::handleStdioSubmit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (install-server-modal.InstallServerModal, install-server-modal.InstallServerModal::handleHttpServerSubmit) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TodoComment __tests__/package-library.test.ts:73— // TODO(#917): remove @openhands/typescript-client exemption once
TodoComment src/api/agent-server-adapter.ts:396— // TODO(i18n): extract "Conversation" once we add CONVERSATION$DEFAULT_TITLE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
install-server-modal.InstallServerModal::handleHttpServerSubmit (cognitive 26) src/components/features/mcp-page/install-server-modal.tsx:380— install-server-modal.InstallServerModal::handleHttpServerSubmit has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 8, error handling 1 (2 pts), ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: 2 other methods here (install-server-modal.InstallServerModal, install-server-modal.InstallServerModal::handleStdioSubmit) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
install-server-modal.InstallServerModal::handleStdioSubmit (cognitive 24) src/components/features/mcp-page/install-server-modal.tsx:469— install-server-modal.InstallServerModal::handleStdioSubmit has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 5 (7 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (install-server-modal.InstallServerModal, install-server-modal.InstallServerModal::handleHttpServerSubmit) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
mcp-server-form.MCPServerForm::validateForm (cognitive 18) src/components/features/settings/mcp-settings/mcp-server-form.tsx:251— mcp-server-form.MCPServerForm::validateForm has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (mcp-server-form.MCPServerForm, mcp-server-form.MCPServerForm::buildConfig) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
mcp-server-form.MCPServerForm::buildConfig (cognitive 17) src/components/features/settings/mcp-settings/mcp-server-form.tsx:368— mcp-server-form.MCPServerForm::buildConfig has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 3 (6 pts), ternaries 1 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: 2 other methods here (mcp-server-form.MCPServerForm, mcp-server-form.MCPServerForm::validateForm) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ClassTooLong: AutomationService src/api/automation-service/automation-service.api.ts:381— ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 108 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AgentServerConversationService src/api/conversation-service/agent-server-conversation-service.api.ts:479— ClassTooLong — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 86 over it, 1.22× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: agent-server-adapter.ts ↔ type-guards.ts src/api/agent-server-adapter.ts:1— `src/api/agent-server-adapter.ts` and `src/types/agent-server/type-guards.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `da4c7564` feat(secrets): let the agent request a secret through an in-conversat…; `5ce3d0be` feat: add agent-assisted automation form updates (#17201); `e882651e` feat: add a typed agent action for launching local or Cloud child con… — run `git show` on any of them.
Change coupling: agent-server-conversation-service.api.ts ↔ use-create-conversation.ts src/api/conversation-service/agent-server-conversation-service.api.ts:1— `src/api/conversation-service/agent-server-conversation-service.api.ts` and `src/hooks/mutation/use-create-conversation.ts` change together 50% of the time (10 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e9b78030` fix(chat): let a Cloud member pick the LLM profile on the home page (…; `5958302c` fix(agent-profiles): keep the profile on per-launch LLM picks and in …; `5ce3d0be` feat: add agent-assisted automation form updates (#17201) — run `git show` on any of them.
Duplicated block (39 lines × 2 locations) src/components/conversation-events/chat/task-tracking/task-item.tsx:15— src/components/conversation-events/chat/task-tracking/task-item.tsx:15 · src/components/features/chat/task-tracking/task-item.tsx:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (39 lines × 2 locations) src/components/features/conversation-panel/hooks-modal-header.tsx:20— src/components/features/conversation-panel/hooks-modal-header.tsx:20 · src/components/features/conversation-panel/skills-modal-header.tsx:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap src/utils/sdk-settings-schema.ts:160— `normalizeComparableValue` is exported, takes a document from its caller (line 175) and hands it to `stableJsonStringify`, which calls itself at line 160 (`stableJsonStringify`) with a piece of `value` (and at line 170) — and nowhere in `stableJsonStringify` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `stableJsonStringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/utils/mcp-config.ts:46— `hasRedactedMcpSecretLeaf` is exported and takes `value: unknown` from its caller, and it calls itself at line 46 (`hasRedactedMcpSecretLeaf`) with a piece of `value` (and at line 48) — and nowhere in `hasRedactedMcpSecretLeaf` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `hasRedactedMcpSecretLeaf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark electron/loading.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
agent-settings.AgentSettingsScreen (cyclomatic 202) src/routes/agent-settings.tsx:382— agent-settings.AgentSettingsScreen has cyclomatic complexity 202 (threshold 15). Of this number, 125 points are the body's own statements and 77 belong to 34 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
conversation-websocket-context.ConversationWebSocketProvider (cyclomatic 161) src/contexts/conversation-websocket-context.tsx:213— conversation-websocket-context.ConversationWebSocketProvider has cyclomatic complexity 161 (threshold 15). Most of this is not in the body itself: 7 of the 161 points are its own statements and the rest belongs to 28 function literals inside it that branch (lines 648, 922, 1410, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
mcp-server-form.MCPServerForm (cyclomatic 133) src/components/features/settings/mcp-settings/mcp-server-form.tsx:50— mcp-server-form.MCPServerForm has cyclomatic complexity 133 (threshold 15). Of this number, 36 points are the body's own statements and 97 belong to 21 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-panel.ConversationPanel (cyclomatic 121) src/components/features/conversation-panel/conversation-panel.tsx:84— conversation-panel.ConversationPanel has cyclomatic complexity 121 (threshold 15). Of this number, 59 points are the body's own statements and 62 belong to 28 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sdk-section-page.SdkSectionPage (cyclomatic 82) src/components/features/settings/sdk-settings/sdk-section-page.tsx:191— sdk-section-page.SdkSectionPage has cyclomatic complexity 82 (threshold 15). Of this number, 16 points are the body's own statements and 66 belong to 26 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
manifest-setup-dialog.SetupDialog (cyclomatic 81) src/components/features/manifest/manifest-setup-dialog.tsx:101— manifest-setup-dialog.SetupDialog has cyclomatic complexity 81 (threshold 15). Of this number, 43 points are the body's own statements and 38 belong to 19 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
chat-input-actions.ChatInputActions (cyclomatic 78) src/components/features/chat/components/chat-input-actions.tsx:62— chat-input-actions.ChatInputActions has cyclomatic complexity 78 (threshold 15). Of this number, 49 points are the body's own statements and 29 belong to 9 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
chat-interface.ChatInterface (cyclomatic 78) src/components/features/chat/chat-interface.tsx:88— chat-interface.ChatInterface has cyclomatic complexity 78 (threshold 15). Of this number, 41 points are the body's own statements and 37 belong to 12 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
llm-settings.LlmSettingsScreen (cyclomatic 69) src/routes/llm-settings.tsx:122— llm-settings.LlmSettingsScreen has cyclomatic complexity 69 (threshold 15). Most of this is not in the body itself: 4 of the 69 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 231, 354, 561, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
automations-list.AutomationsList (cyclomatic 68) src/routes/automations-list.tsx:297— automations-list.AutomationsList has cyclomatic complexity 68 (threshold 15). Of this number, 52 points are the body's own statements and 16 belong to 12 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
agent-profiles-local-view.AgentProfilesLocalView (cyclomatic 66) src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:115— agent-profiles-local-view.AgentProfilesLocalView has cyclomatic complexity 66 (threshold 15). Of this number, 29 points are the body's own statements and 37 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-card.ConversationCard (cyclomatic 61) src/components/features/conversation-panel/conversation-card/conversation-card.tsx:80— conversation-card.ConversationCard has cyclomatic complexity 61 (threshold 15). Of this number, 50 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
llm-settings-local-view.LlmSettingsLocalView (cyclomatic 60) src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:98— llm-settings-local-view.LlmSettingsLocalView has cyclomatic complexity 60 (threshold 15). Of this number, 27 points are the body's own statements and 33 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-main.ConversationMain (cyclomatic 57) src/components/features/conversation/conversation-main/conversation-main.tsx:79— conversation-main.ConversationMain has cyclomatic complexity 57 (threshold 15). Of this number, 54 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.buildTranscriptEntries (cyclomatic 50) src/utils/transcript-export/index.ts:268— index.buildTranscriptEntries has cyclomatic complexity 50 (threshold 15). Of this number, 42 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
pinned-automation-card.PinnedAutomationCard (cyclomatic 49) src/components/features/home/featured-automations/pinned-automation-card.tsx:58— pinned-automation-card.PinnedAutomationCard has cyclomatic complexity 49 (threshold 15). Of this number, 41 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
event-message.EventMessageComponent (cyclomatic 48) src/components/conversation-events/chat/event-message.tsx:180— event-message.EventMessageComponent has cyclomatic complexity 48 (threshold 15). Of this number, 45 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
add-models-modal.AddModelsModal (cyclomatic 47) src/components/features/settings/llm-profiles/add-models-modal.tsx:77— add-models-modal.AddModelsModal has cyclomatic complexity 47 (threshold 15). Of this number, 22 points are the body's own statements and 25 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
meta-llm-settings-view.MetaLlmSettingsView (cyclomatic 45) src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx:56— meta-llm-settings-view.MetaLlmSettingsView has cyclomatic complexity 45 (threshold 15). Of this number, 21 points are the body's own statements and 24 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automation-setup-panel.AutomationSetupPanel (cyclomatic 44) REDACTED:640— automation-setup-panel.AutomationSetupPanel has cyclomatic complexity 44 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (automation-setup-panel.AutomationSetupPanel::validateRequiredFields) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cloud-new-conversation-menu.CloudNewConversationMenu (cyclomatic 44) src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:81— cloud-new-conversation-menu.CloudNewConversationMenu has cyclomatic complexity 44 (threshold 15). Of this number, 24 points are the body's own statements and 20 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
recommended-automations-launcher.RecommendedAutomationsLauncher (cyclomatic 43) src/components/features/automations/recommended-automations-launcher.tsx:100— recommended-automations-launcher.RecommendedAutomationsLauncher has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 9 of the 43 points are its own statements and the rest belongs to 13 function items inside it that branch (handleSelectAutomation, a function literal at line 168, isBuiltInIntegrationEnabled, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
dev-with-automation.main (cyclomatic 41) REDACTED:1507— dev-with-automation.main has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
root.App (cyclomatic 41) src/root.tsx:234— root.App has cyclomatic complexity 41 (threshold 15). Of this number, 39 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
static-server.parseArgs (cyclomatic 38) scripts/static-server.mjs:88— static-server.parseArgs has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
chat-message.ChatMessage (cyclomatic 38) src/components/features/chat/chat-message.tsx:38— chat-message.ChatMessage has cyclomatic complexity 38 (threshold 15). Of this number, 31 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-tabs.ConversationTabs (cyclomatic 38) src/components/features/conversation/conversation-tabs/conversation-tabs.tsx:34— conversation-tabs.ConversationTabs has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 11 of the 38 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 194, handleTabKeyDown, a function literal at line 187, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
super-admin-setup-guide.SuperAdminSetupGuide (cyclomatic 38) src/components/features/setup-guide/super-admin-setup-guide.tsx:80— super-admin-setup-guide.SuperAdminSetupGuide has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 8 of the 38 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 137, startStepTour, a function literal at line 185, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
managed-agents-view.ManagedAgentsView (cyclomatic 37) src/components/features/backends/managed-agents/managed-agents-view.tsx:132— managed-agents-view.ManagedAgentsView has cyclomatic complexity 37 (threshold 15). Of this number, 25 points are the body's own statements and 12 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
folder-browser-modal.FolderBrowserModal (cyclomatic 37) src/components/features/home/workspace-dropdown/folder-browser-modal.tsx:125— folder-browser-modal.FolderBrowserModal has cyclomatic complexity 37 (threshold 15). Of this number, 19 points are the body's own statements and 18 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
git-control-bar.GitControlBar (cyclomatic 36) src/components/features/chat/git-control-bar.tsx:34— git-control-bar.GitControlBar has cyclomatic complexity 36 (threshold 15). Of this number, 26 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
run-logs-modal.RunLogsModal (cyclomatic 36) src/components/features/automations/detail/run-logs-modal.tsx:199— run-logs-modal.RunLogsModal has cyclomatic complexity 36 (threshold 15). Of this number, 31 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
workspace-selection-form.WorkspaceSelectionForm (cyclomatic 36) src/components/features/home/workspace-selection-form.tsx:68— workspace-selection-form.WorkspaceSelectionForm has cyclomatic complexity 36 (threshold 15). Of this number, 23 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
repo-selection-form.RepositorySelectionForm (cyclomatic 36) src/components/features/home/repo-selection-form.tsx:41— repo-selection-form.RepositorySelectionForm has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 12 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 73, a function literal at line 211, renderRepositorySelector, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
app-settings.AppSettingsForm (cyclomatic 36) src/routes/app-settings.tsx:45— app-settings.AppSettingsForm has cyclomatic complexity 36 (threshold 15). Of this number, 23 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
get-event-content.getObservationEventTitle (cyclomatic 35) src/components/conversation-events/chat/event-content-helpers/get-event-content.tsx:148— get-event-content.getObservationEventTitle has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
automation-card.AutomationCard (cyclomatic 35) src/components/features/automations/automation-card.tsx:59— automation-card.AutomationCard has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
agent-status.AgentStatus (cyclomatic 35) src/components/features/controls/agent-status.tsx:32— agent-status.AgentStatus has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
custom-server-editor.CustomServerEditor (cyclomatic 35) src/components/features/mcp-page/custom-server-editor.tsx:41— custom-server-editor.CustomServerEditor has cyclomatic complexity 35 (threshold 15). Of this number, 17 points are the body's own statements and 18 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-name-context-menu.ConversationNameContextMenu (cyclomatic 34) src/components/features/conversation/conversation-name-context-menu.tsx:92— conversation-name-context-menu.ConversationNameContextMenu has cyclomatic complexity 34 (threshold 15). Of this number, 30 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
file-diff-viewer.FileDiffViewer (cyclomatic 34) src/components/features/diff-viewer/file-diff-viewer.tsx:156— file-diff-viewer.FileDiffViewer has cyclomatic complexity 34 (threshold 15). Of this number, 17 points are the body's own statements and 17 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
secret-form.SecretForm (cyclomatic 34) src/components/features/settings/secrets-settings/secret-form.tsx:31— secret-form.SecretForm has cyclomatic complexity 34 (threshold 15). Of this number, 21 points are the body's own statements and 13 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
tour-engine.startGuidedTour (cyclomatic 33) src/components/features/setup-guide/tour/tour-engine.ts:179— tour-engine.startGuidedTour has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 4 of the 33 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 281, a function literal at line 219, a function literal at line 360, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
get-action-event-title.getActionEventTitleDescriptor (cyclomatic 32) src/components/conversation-events/chat/event-content-helpers/get-action-event-title.ts:30— get-action-event-title.getActionEventTitleDescriptor has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
command-menu.CommandMenu (cyclomatic 32) src/components/features/command-menu/command-menu.tsx:62— command-menu.CommandMenu has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 6 of the 32 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 289, a function literal at line 356, a function literal at line 74, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
conversation-overview-git-section.ConversationOverviewGitSection (cyclomatic 31) src/components/features/conversation/conversation-overview-git-section.tsx:36— conversation-overview-git-section.ConversationOverviewGitSection has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
manage-backends-modal.ManageBackendsModal (cyclomatic 31) src/components/features/backends/manage-backends-modal.tsx:72— manage-backends-modal.ManageBackendsModal has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
automation-export.parseAutomationFile (cyclomatic 30) src/utils/automation-export.ts:189— automation-export.parseAutomationFile has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
change-agent-button.ChangeAgentButton (cyclomatic 29) src/components/features/chat/change-agent-button.tsx:25— change-agent-button.ChangeAgentButton has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 14 of the 29 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 59, 104, 86, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
conversation-name.ConversationName (cyclomatic 29) src/components/features/conversation/conversation-name.tsx:18— conversation-name.ConversationName has cyclomatic complexity 29 (threshold 15). Of this number, 21 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-tabs-context-menu.ConversationTabsContextMenu (cyclomatic 29) src/components/features/conversation/conversation-tabs/conversation-tabs-context-menu.tsx:42— conversation-tabs-context-menu.ConversationTabsContextMenu has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 12 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 190, handlePinToggle, a function literal at line 55, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
automation-list-row.AutomationListRow (cyclomatic 29) src/components/features/automations/automation-list-row.tsx:55— automation-list-row.AutomationListRow has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
git-sync-config-form.GitSyncConfigForm (cyclomatic 29) src/components/features/automations/git-sync/git-sync-config-form.tsx:43— git-sync-config-form.GitSyncConfigForm has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (git-sync-config-form.GitSyncConfigForm::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
git-branch-dropdown.GitBranchDropdown (cyclomatic 29) src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:35— git-branch-dropdown.GitBranchDropdown has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 145, 178, 96, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
setup-llm-step.SetupLlmStep (cyclomatic 29) src/components/features/onboarding/steps/setup-llm-step.tsx:192— setup-llm-step.SetupLlmStep has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 13 of the 29 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 245, handleNext, a function literal at line 221). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
onboarding-modal.OnboardingModal (cyclomatic 29) src/components/features/onboarding/onboarding-modal.tsx:135— onboarding-modal.OnboardingModal has cyclomatic complexity 29 (threshold 15). Of this number, 18 points are the body's own statements and 11 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
openai-subscription-auth-card.OpenAISubscriptionAuthCard (cyclomatic 29) src/components/features/settings/llm-settings/openai-subscription-auth-card.tsx:32— openai-subscription-auth-card.OpenAISubscriptionAuthCard has cyclomatic complexity 29 (threshold 15). Of this number, 16 points are the body's own statements and 13 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sdk-settings-schema.normalizeComparableValue (cyclomatic 29) src/utils/sdk-settings-schema.ts:175— sdk-settings-schema.normalizeComparableValue has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
backend-selector.BackendSelector (cyclomatic 28) src/components/features/backends/backend-selector.tsx:145— backend-selector.BackendSelector has cyclomatic complexity 28 (threshold 15). Of this number, 21 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
local-new-conversation-menu.LocalNewConversationMenu (cyclomatic 28) src/components/features/conversation-panel/local-new-conversation-menu.tsx:61— local-new-conversation-menu.LocalNewConversationMenu has cyclomatic complexity 28 (threshold 15). Of this number, 15 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
check-backend-step.CheckBackendStep (cyclomatic 28) src/components/features/onboarding/steps/check-backend-step.tsx:116— check-backend-step.CheckBackendStep has cyclomatic complexity 28 (threshold 15). Of this number, 21 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
provider-connection-modal.ProviderConnectionModal (cyclomatic 28) src/components/features/settings/llm-profiles/provider-connection-modal.tsx:46— provider-connection-modal.ProviderConnectionModal has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sidebar-rail-body.SidebarRailBody (cyclomatic 28) src/components/features/sidebar/sidebar-rail-body.tsx:76— sidebar-rail-body.SidebarRailBody has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sidebar.Sidebar (cyclomatic 28) src/components/features/sidebar/sidebar.tsx:40— sidebar.Sidebar has cyclomatic complexity 28 (threshold 15). Of this number, 17 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-backends-health.useBackendsHealth (cyclomatic 28) src/hooks/query/use-backends-health.ts:215— use-backends-health.useBackendsHealth has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 229, 295, 258). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
meta-profile-editor.MetaProfileEditor (cyclomatic 27) src/components/features/settings/meta-llm-profiles/meta-profile-editor.tsx:77— meta-profile-editor.MetaProfileEditor has cyclomatic complexity 27 (threshold 15). Of this number, 16 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-bash-command-logs.useBashCommandLogs (cyclomatic 27) src/hooks/query/use-bash-command-logs.ts:142— use-bash-command-logs.useBashCommandLogs has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-unified-vscode-url.useUnifiedVSCodeUrl (cyclomatic 27) src/hooks/query/use-unified-vscode-url.ts:24— use-unified-vscode-url.useUnifiedVSCodeUrl has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
use-chat-input-model-state.useChatInputModelState (cyclomatic 27) src/hooks/use-chat-input-model-state.ts:38— use-chat-input-model-state.useChatInputModelState has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-llm-configured.useLlmConfigured (cyclomatic 27) src/hooks/use-llm-configured.ts:40— use-llm-configured.useLlmConfigured has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
get-observation-result.getObservationResult (cyclomatic 26) src/components/conversation-events/chat/event-content-helpers/get-observation-result.ts:22— get-observation-result.getObservationResult has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
automation-setup-prompt-stack.AutomationSetupPromptStack (cyclomatic 26) src/components/features/automations/setup/automation-setup-prompt-stack.tsx:238— automation-setup-prompt-stack.AutomationSetupPromptStack has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
device-flow-auth.DeviceFlowAuth (cyclomatic 26) src/components/features/backends/device-flow-auth.tsx:71— device-flow-auth.DeviceFlowAuth has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 98, handleStartAuth, a function literal at line 134, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
git-repo-dropdown.GitRepoDropdown (cyclomatic 26) REDACTED:39— git-repo-dropdown.GitRepoDropdown has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 133, 192, 57, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
automation-export.validateTrigger (cyclomatic 26) src/utils/automation-export.ts:56— automation-export.validateTrigger has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dev-with-automation.buildConfig (cyclomatic 25) REDACTED:394— dev-with-automation.buildConfig has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
agent-server-adapter.buildStartConversationRequest (cyclomatic 25) src/api/agent-server-adapter.ts:1070— agent-server-adapter.buildStartConversationRequest has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
messages.Messages (cyclomatic 25) src/components/conversation-events/chat/messages.tsx:32— messages.Messages has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 56, a function literal at line 78, renderEventMessage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
conversation.AppContent (cyclomatic 25) src/routes/conversation.tsx:36— conversation.AppContent has cyclomatic complexity 25 (threshold 15). Of this number, 14 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-overview-context-menu.ConversationOverviewContextMenu (cyclomatic 25) src/components/features/conversation/conversation-overview-context-menu.tsx:149— conversation-overview-context-menu.ConversationOverviewContextMenu has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (handleOpenGitPart, a function literal at line 167, renderMenuRow, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
plugin-launch-modal.PluginLaunchModal (cyclomatic 25) src/components/features/launch/plugin-launch-modal.tsx:30— plugin-launch-modal.PluginLaunchModal has cyclomatic complexity 25 (threshold 15). Of this number, 14 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
manifest-form-field.SetupFormField (cyclomatic 25) src/components/features/manifest/manifest-form-field.tsx:50— manifest-form-field.SetupFormField has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
install-server-modal.InstallServerModal (cyclomatic 25) src/components/features/mcp-page/install-server-modal.tsx:161— install-server-modal.InstallServerModal has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (install-server-modal.InstallServerModal::handleHttpServerSubmit, install-server-modal.InstallServerModal::handleStdioSubmit) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
manifest-validation.checkField (cyclomatic 25) src/manifests/manifest-validation.ts:260— manifest-validation.checkField has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
conversation-local-storage.sanitizeStoredState (cyclomatic 25) src/utils/conversation-local-storage.ts:106— conversation-local-storage.sanitizeStoredState has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
load-complete-events.loadCompleteTranscriptEvents (cyclomatic 25) src/utils/transcript-export/load-complete-events.ts:33— load-complete-events.loadCompleteTranscriptEvents has cyclomatic complexity 25 (threshold 15). Of this number, 17 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
static-server.startStaticServer (cyclomatic 24) scripts/static-server.mjs:658— static-server.startStaticServer has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 695, 750, 735, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
settings-service.api.cloudCompatibleMcpConfig (cyclomatic 24) src/api/settings-service/settings-service.api.ts:310— settings-service.api.cloudCompatibleMcpConfig has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 351, collectStoredHeaders, a function literal at line 324). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
backend-form-modal.BackendForm (cyclomatic 24) src/components/features/backends/backend-form-modal.tsx:498— backend-form-modal.BackendForm has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skill-card-pill-row.SkillCardPillRow (cyclomatic 24) src/components/features/skills/skill-card-pill-row.tsx:62— skill-card-pill-row.SkillCardPillRow has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 137, a function literal at line 75, a function literal at line 100, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
use-draft-persistence.useDraftPersistence (cyclomatic 24) src/hooks/chat/use-draft-persistence.ts:45— use-draft-persistence.useDraftPersistence has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 98, 153, 313). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
api-error-message.getApiErrorMessage (cyclomatic 24) src/utils/api-error-message.ts:102— api-error-message.getApiErrorMessage has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
canvas-extensions.CanvasExtensionsScreen (cyclomatic 24) src/routes/canvas-extensions.tsx:42— canvas-extensions.CanvasExtensionsScreen has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
mcp-config.parseMcpConfig (cyclomatic 24) src/utils/mcp-config.ts:77— mcp-config.parseMcpConfig has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
error-message-banner.ErrorMessageBanner (cyclomatic 23) src/components/features/chat/error-message-banner.tsx:23— error-message-banner.ErrorMessageBanner has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
backend-row.BackendRow (cyclomatic 23) src/components/features/backends/backend-row.tsx:31— backend-row.BackendRow has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automation-git-sync.AutomationGitSync (cyclomatic 23) src/routes/automation-git-sync.tsx:52— automation-git-sync.AutomationGitSync has cyclomatic complexity 23 (threshold 15). Of this number, 13 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sdk-settings-schema.coerceFieldValue (cyclomatic 23) src/utils/sdk-settings-schema.ts:347— sdk-settings-schema.coerceFieldValue has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
activity-log-section.ActivityLogSection (cyclomatic 22) src/components/features/automations/detail/activity-log-section.tsx:30— activity-log-section.ActivityLogSection has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
git-provider-dropdown.GitProviderDropdown (cyclomatic 22) src/components/features/home/git-provider-dropdown/git-provider-dropdown.tsx:29— git-provider-dropdown.GitProviderDropdown has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (formatProviderName, a function literal at line 71, a function literal at line 123, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
workspace-dropdown.WorkspaceDropdown (cyclomatic 22) src/components/features/home/workspace-dropdown/workspace-dropdown.tsx:54— workspace-dropdown.WorkspaceDropdown has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 127, a function literal at line 117, a function literal at line 194, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
llm-profile-form.buildProfileLlmConfig (cyclomatic 22) src/components/features/settings/llm-profiles/llm-profile-form.ts:92— llm-profile-form.buildProfileLlmConfig has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
secrets-settings.SecretsSettingsScreen (cyclomatic 22) src/routes/secrets-settings.tsx:27— secrets-settings.SecretsSettingsScreen has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-confirmation-buttons.ConversationConfirmationButtons (cyclomatic 22) src/components/shared/buttons/conversation-confirmation-buttons.tsx:16— conversation-confirmation-buttons.ConversationConfirmationButtons has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 43, 72, 83, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
model-selector.ModelSelector (cyclomatic 22) src/components/shared/modals/settings/model-selector.tsx:45— model-selector.ModelSelector has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
acp-command.parseCommand (cyclomatic 22) src/utils/acp-command.ts:65— acp-command.parseCommand has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
automation-form-session.patchAutomationFormSession (cyclomatic 21) src/api/automation-form-session.ts:246— automation-form-session.patchAutomationFormSession has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
file-editor.FileEditorCardBody (cyclomatic 21) src/components/features/chat/tool-visualizers/file-editor/file-editor.tsx:53— file-editor.FileEditorCardBody has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
should-render-event.shouldRenderEvent (cyclomatic 21) src/components/conversation-events/chat/event-content-helpers/should-render-event.ts:74— should-render-event.shouldRenderEvent has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
user-assistant-event-message.UserAssistantEventMessageComponent (cyclomatic 21) src/components/conversation-events/chat/event-message-components/user-assistant-event-message.tsx:29— user-assistant-event-message.UserAssistantEventMessageComponent has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (handleBranch, a function literal at line 61, a function literal at line 96, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
conversation-overview-toggle.ConversationOverviewToggle (cyclomatic 21) src/components/features/conversation/conversation-overview-toggle.tsx:31— conversation-overview-toggle.ConversationOverviewToggle has cyclomatic complexity 21 (threshold 15). Of this number, 11 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-card-context-menu.ConversationCardContextMenu (cyclomatic 21) src/components/features/conversation-panel/conversation-card/conversation-card-context-menu.tsx:41— conversation-card-context-menu.ConversationCardContextMenu has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
home-automation-menu.HomeAutomationMenu (cyclomatic 21) src/components/features/home/featured-automations/home-automation-menu.tsx:28— home-automation-menu.HomeAutomationMenu has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 85, a function literal at line 151, a function literal at line 53, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
agent-settings.buildAgentProfileFields (cyclomatic 21) src/routes/agent-settings.tsx:254— agent-settings.buildAgentProfileFields has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
open-repository-modal.OpenRepositoryModal (cyclomatic 20) src/components/features/chat/open-repository-modal.tsx:23— open-repository-modal.OpenRepositoryModal has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-card-actions.ConversationCardActions (cyclomatic 20) src/components/features/conversation-panel/conversation-card/conversation-card-actions.tsx:28— conversation-card-actions.ConversationCardActions has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
home-chat-launcher.HomeChatLauncher (cyclomatic 20) src/components/features/home/home-chat-launcher.tsx:56— home-chat-launcher.HomeChatLauncher has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (home-chat-launcher.HomeChatLauncher::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
skills-plugins.SkillsPluginsScreen (cyclomatic 20) src/routes/skills-plugins.tsx:38— skills-plugins.SkillsPluginsScreen has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skills-settings.SkillsSettingsScreen (cyclomatic 20) src/routes/skills-settings.tsx:44— skills-settings.SkillsSettingsScreen has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mcp-config.buildMcpServerPatch (cyclomatic 20) src/utils/mcp-config.ts:319— mcp-config.buildMcpServerPatch has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
seed-automation-ux-data.insertRuns (cyclomatic 19) scripts/seed-automation-ux-data.mjs:662— seed-automation-ux-data.insertRuns has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
settings-service.api.headersFromMcpAuth (cyclomatic 19) src/api/settings-service/settings-service.api.ts:245— settings-service.api.headersFromMcpAuth has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
mcp-redacted-credentials.substituteRedactedMcpCredentials (cyclomatic 19) src/api/mcp-service/mcp-redacted-credentials.ts:84— mcp-redacted-credentials.substituteRedactedMcpCredentials has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
goal-status-content.GoalStatusContent (cyclomatic 19) src/components/features/chat/goal-status-content.tsx:69— goal-status-content.GoalStatusContent has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
cloud-organization-boundary.CloudOrganizationBoundary (cyclomatic 19) src/components/features/backends/cloud-organization-boundary.tsx:14— cloud-organization-boundary.CloudOrganizationBoundary has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
plugin-detail-modal.PluginDetailModal (cyclomatic 19) src/components/features/plugins/plugin-detail-modal.tsx:26— plugin-detail-modal.PluginDetailModal has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sidebar-nav-link.SidebarNavLink (cyclomatic 19) src/components/features/sidebar/sidebar-nav-link.tsx:57— sidebar-nav-link.SidebarNavLink has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-git-repositories.useGitRepositories (cyclomatic 19) src/hooks/query/use-git-repositories.ts:21— use-git-repositories.useGitRepositories has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-terminal.useTerminal (cyclomatic 19) src/hooks/use-terminal.ts:94— use-terminal.useTerminal has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 139, a function literal at line 183, initializeTerminal, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
automation-detail.AutomationDetail (cyclomatic 19) src/routes/automation-detail.tsx:81— automation-detail.AutomationDetail has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automation-setup-new.AutomationSetupNew (cyclomatic 19) src/routes/automation-setup-new.tsx:31— automation-setup-new.AutomationSetupNew has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 64, 43, 50, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
dropdown.Dropdown (cyclomatic 19) src/ui/dropdown/dropdown.tsx:49— dropdown.Dropdown has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
status.getStatusCode (cyclomatic 19) src/utils/status.ts:64— status.getStatusCode has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
automation-form-session.normalizeDraft (cyclomatic 18) src/api/automation-form-session.ts:138— automation-form-session.normalizeDraft has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentServerConversationService.createConversation (cyclomatic 18) src/api/conversation-service/agent-server-conversation-service.api.ts:517— AgentServerConversationService.createConversation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
get-action-content.getBrowserActionContent (cyclomatic 18) src/components/conversation-events/chat/event-content-helpers/get-action-content.ts:159— get-action-content.getBrowserActionContent has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: get-action-content.getActionContent (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
recommended-automations-section.RecommendedAutomationsSection (cyclomatic 18) src/components/features/automations/recommended-automations-section.tsx:390— recommended-automations-section.RecommendedAutomationsSection has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
automation-setup-draft-service.setupDraftFromServerDraft (cyclomatic 18) src/components/features/automations/setup/automation-setup-draft-service.ts:94— automation-setup-draft-service.setupDraftFromServerDraft has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automation-setup-panel.EventFields (cyclomatic 18) REDACTED:3052— automation-setup-panel.EventFields has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
canvas-extensions-runtime.CanvasExtensionsRuntimeProvider (cyclomatic 18) src/components/features/canvas-extensions/canvas-extensions-runtime.tsx:97— canvas-extensions-runtime.CanvasExtensionsRuntimeProvider has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 171, 306, 194, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
conversation-tag-chips.ConversationTagChips (cyclomatic 18) src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:99— conversation-tag-chips.ConversationTagChips has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 112, 125, 163, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
home-chat-launcher.HomeChatLauncher::handleSubmit (cyclomatic 18) src/components/features/home/home-chat-launcher.tsx:127— home-chat-launcher.HomeChatLauncher::handleSubmit has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (home-chat-launcher.HomeChatLauncher) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
agent-canvas-version-modal.AgentCanvasVersionModal (cyclomatic 18) src/components/features/settings/agent-canvas-version-modal.tsx:50— agent-canvas-version-modal.AgentCanvasVersionModal has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
agent-profile-actions-menu.AgentProfileActionsMenu (cyclomatic 18) src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:42— agent-profile-actions-menu.AgentProfileActionsMenu has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 120, 92, 98, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
profile-actions-menu.ProfileActionsMenu (cyclomatic 18) src/components/features/settings/llm-profiles/profile-actions-menu.tsx:44— profile-actions-menu.ProfileActionsMenu has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 126, 95, 102, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
active-backend-context.ActiveBackendProvider (cyclomatic 18) src/contexts/active-backend-context.tsx:72— active-backend-context.ActiveBackendProvider has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 143, 91, 157, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
resolve-conversation-launch.resolveConversationLaunch (cyclomatic 18) src/hooks/mutation/resolve-conversation-launch.ts:51— resolve-conversation-launch.resolveConversationLaunch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-cloud-sandbox-auto-resume.useCloudSandboxAutoResume (cyclomatic 18) src/hooks/mutation/use-cloud-sandbox-auto-resume.ts:32— use-cloud-sandbox-auto-resume.useCloudSandboxAutoResume has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 81, 49, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-sync-automation-telemetry-consent.useSyncAutomationTelemetryConsent (cyclomatic 18) src/hooks/use-sync-automation-telemetry-consent.ts:19— use-sync-automation-telemetry-consent.useSyncAutomationTelemetryConsent has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 38, 74, 97, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
manifest-validation.checkBundle (cyclomatic 18) src/manifests/manifest-validation.ts:551— manifest-validation.checkBundle has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
handle-event-for-ui.handleEventForUI (cyclomatic 18) src/utils/handle-event-for-ui.ts:275— handle-event-for-ui.handleEventForUI has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SettingsService.saveSettings (cyclomatic 17) src/api/settings-service/settings-service.api.ts:790— SettingsService.saveSettings has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
get-acp-tool-call-content.getACPToolCallContent (cyclomatic 17) src/components/conversation-events/chat/event-content-helpers/get-acp-tool-call-content.ts:185— get-acp-tool-call-content.getACPToolCallContent has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
tool-item.ToolItem (cyclomatic 17) src/components/features/conversation-panel/system-message-modal/tool-item.tsx:34— tool-item.ToolItem has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-tab-nav.ConversationTabNav (cyclomatic 17) src/components/features/conversation/conversation-tabs/conversation-tab-nav.tsx:37— conversation-tab-nav.ConversationTabNav has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
git-sync-config-form.GitSyncConfigForm::handleSubmit (cyclomatic 17) src/components/features/automations/git-sync/git-sync-config-form.tsx:184— git-sync-config-form.GitSyncConfigForm::handleSubmit has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (git-sync-config-form.GitSyncConfigForm) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
automation-setup-panel.AutomationSetupPanel::validateRequiredFields (cyclomatic 17) REDACTED:1438— automation-setup-panel.AutomationSetupPanel::validateRequiredFields has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (automation-setup-panel.AutomationSetupPanel) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
conversation-card-footer.ConversationCardFooter (cyclomatic 17) src/components/features/conversation-panel/conversation-card/conversation-card-footer.tsx:78— conversation-card-footer.ConversationCardFooter has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-layouts-menu.ConversationLayoutsMenu (cyclomatic 17) src/components/features/conversation-panel/conversation-layouts-menu.tsx:115— conversation-layouts-menu.ConversationLayoutsMenu has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (handleMenuKeyDown, a function literal at line 143, a function literal at line 222, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
file-content-viewer.FileContentViewer (cyclomatic 17) src/components/features/files-tab/file-content-viewer.tsx:72— file-content-viewer.FileContentViewer has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mcp-server-health.McpServerHealthSection (cyclomatic 17) src/components/features/mcp-page/mcp-server-health.tsx:72— mcp-server-health.McpServerHealthSection has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
use-modal-focus.useModalFocus.onKeyDown (cyclomatic 17) src/components/shared/modals/use-modal-focus.ts:149— use-modal-focus.useModalFocus.onKeyDown has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
use-load-older-events.useLoadOlderEvents.loadOlder (cyclomatic 17) src/hooks/use-load-older-events.ts:99— use-load-older-events.useLoadOlderEvents.loadOlder has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
tunnel-client.startPortForwardTunnel (cyclomatic 16) scripts/tunnel-client.mjs:101— tunnel-client.startPortForwardTunnel has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 228, bridgeConnection, a function literal at line 186, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
proxy-utils.proxyServerInfoRequest (cyclomatic 16) scripts/proxy-utils.mjs:70— proxy-utils.proxyServerInfoRequest has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 115, 103, 159, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EventService.searchEvents (cyclomatic 16) src/api/event-service/event-service.api.ts:75— EventService.searchEvents has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
McpService.authorizeOAuth (cyclomatic 16) src/api/mcp-service/mcp-service.api.ts:308— McpService.authorizeOAuth has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
get-event-content.getEventContent (cyclomatic 16) src/components/conversation-events/chat/event-content-helpers/get-event-content.tsx:315— get-event-content.getEventContent has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
chat-input-llm-profile-picker.ChatInputLlmProfileMenuContent (cyclomatic 16) src/components/features/chat/components/chat-input-llm-profile-picker.tsx:43— chat-input-llm-profile-picker.ChatInputLlmProfileMenuContent has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
alert-banner.AlertBanner (cyclomatic 16) src/components/features/alerts/alert-banner.tsx:18— alert-banner.AlertBanner has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automations-dashboard-controls.AutomationsDashboardControls (cyclomatic 16) src/components/features/automations/dashboard/automations-dashboard-controls.tsx:59— automations-dashboard-controls.AutomationsDashboardControls has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
configuration-section.ConfigurationSection (cyclomatic 16) src/components/features/automations/detail/configuration-section.tsx:61— configuration-section.ConfigurationSection has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
git-sync-activity-row.GitSyncActivityRow (cyclomatic 16) src/components/features/automations/git-sync/git-sync-activity-row.tsx:40— git-sync-activity-row.GitSyncActivityRow has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
digitalocean-connect-panel.DigitalOceanConnectPanel (cyclomatic 16) src/components/features/backends/managed-agents/digitalocean-connect-panel.tsx:241— digitalocean-connect-panel.DigitalOceanConnectPanel has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
backend-status-label.getBackendStatusLabel (cyclomatic 16) src/components/features/backends/backend-status-label.ts:19— backend-status-label.getBackendStatusLabel has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
tools-context-menu.ToolsContextMenu (cyclomatic 16) src/components/features/controls/tools-context-menu.tsx:51— tools-context-menu.ToolsContextMenu has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-panel-list-helpers.groupConversations (cyclomatic 16) src/components/features/conversation-panel/conversation-panel-list-helpers.ts:549— conversation-panel-list-helpers.groupConversations has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
setup-acp-secrets-step.SetupAcpSecretsStep (cyclomatic 16) src/components/features/onboarding/steps/setup-acp-secrets-step.tsx:59— setup-acp-secrets-step.SetupAcpSecretsStep has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
meta-profile-actions-menu.MetaProfileActionsMenu (cyclomatic 16) src/components/features/settings/meta-llm-profiles/meta-profile-actions-menu.tsx:78— meta-profile-actions-menu.MetaProfileActionsMenu has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
build-skill-pills.buildSkillPills (cyclomatic 16) src/components/features/skills/build-skill-pills.tsx:36— build-skill-pills.buildSkillPills has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-modal-focus.useModalFocus (cyclomatic 16) src/components/shared/modals/use-modal-focus.ts:84— use-modal-focus.useModalFocus has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 118, 98, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-plan-mode-interceptor.usePlanModeInterceptor (cyclomatic 16) src/hooks/chat/use-plan-mode-interceptor.ts:29— use-plan-mode-interceptor.usePlanModeInterceptor has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 44). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
use-workspace-file-content.useWorkspaceFileContent (cyclomatic 16) src/hooks/query/use-workspace-file-content.ts:142— use-workspace-file-content.useWorkspaceFileContent has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: use-workspace-file-content.guessMimeType (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
use-await-context-compaction.useAwaitContextCompaction (cyclomatic 16) src/hooks/use-await-context-compaction.ts:62— use-await-context-compaction.useAwaitContextCompaction has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 112, 71, 96, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
commits-tab.GitCommits (cyclomatic 16) src/routes/commits-tab.tsx:21— commits-tab.GitCommits has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
device-verify.DeviceVerify (cyclomatic 16) src/routes/device-verify.tsx:9— device-verify.DeviceVerify has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: waits for a migration already running __tests__/hooks/use-migrate-default-agent-profile.test.ts:237— This test starts work it did not wait for (`running`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => {
setTimeout(resolve, 10);
})` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Deprecated: eslint REDACTED:159— eslint 9.39.5, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
conversation-websocket-context.ConversationWebSocketProvider (cognitive 241) src/contexts/conversation-websocket-context.tsx:213— conversation-websocket-context.ConversationWebSocketProvider has cognitive complexity 241 (threshold 15). Drivers by points: if/else 88 (158 pts), boolean chains 42, ternaries 12 (28 pts), error handling 5 (7 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 91). Most of this is not in the body itself: 6 of the 241 points are its own statements and the rest belongs to 28 function literals inside it that branch (lines 648, 922, 1410, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
agent-settings.AgentSettingsScreen (cognitive 205) src/routes/agent-settings.tsx:382— agent-settings.AgentSettingsScreen has cognitive complexity 205 (threshold 15). Drivers by points: ternaries 59 (94 pts), boolean chains 70, if/else 33 (41 pts) (nesting depth added 43). Of this number, 120 points are the body's own statements and 85 belong to 34 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-panel.ConversationPanel (cognitive 102) src/components/features/conversation-panel/conversation-panel.tsx:84— conversation-panel.ConversationPanel has cognitive complexity 102 (threshold 15). Drivers by points: boolean chains 41, if/else 36 (39 pts), ternaries 17 (19 pts), loops 3 (nesting depth added 5). Of this number, 35 points are the body's own statements and 67 belong to 28 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
sdk-section-page.SdkSectionPage (cognitive 100) src/components/features/settings/sdk-settings/sdk-section-page.tsx:191— sdk-section-page.SdkSectionPage has cognitive complexity 100 (threshold 15). Drivers by points: if/else 34 (48 pts), boolean chains 18, loops 10 (18 pts), ternaries 12 (15 pts), error handling 1 (nesting depth added 25). Of this number, 16 points are the body's own statements and 84 belong to 26 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.buildTranscriptEntries (cognitive 96) src/utils/transcript-export/index.ts:268— index.buildTranscriptEntries has cognitive complexity 96 (threshold 15). Drivers by points: if/else 23 (48 pts), ternaries 11 (33 pts), boolean chains 11, error handling 2 (3 pts), loops 1 (nesting depth added 48). Of this number, 89 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
llm-settings.LlmSettingsScreen (cognitive 92) src/routes/llm-settings.tsx:122— llm-settings.LlmSettingsScreen has cognitive complexity 92 (threshold 15). Drivers by points: ternaries 27 (46 pts), boolean chains 24, if/else 14 (22 pts) (nesting depth added 27). Most of this is not in the body itself: 2 of the 92 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 231, 561, 354, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
manifest-setup-dialog.SetupDialog (cognitive 67) src/components/features/manifest/manifest-setup-dialog.tsx:101— manifest-setup-dialog.SetupDialog has cognitive complexity 67 (threshold 15). Drivers by points: boolean chains 31, if/else 22, ternaries 10 (13 pts), error handling 1 (nesting depth added 3). Of this number, 32 points are the body's own statements and 35 belong to 19 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
chat-interface.ChatInterface (cognitive 66) src/components/features/chat/chat-interface.tsx:88— chat-interface.ChatInterface has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 26, if/else 17 (21 pts), ternaries 14 (18 pts), error handling 1 (nesting depth added 8). Of this number, 27 points are the body's own statements and 39 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
chat-input-actions.ChatInputActions (cognitive 65) src/components/features/chat/components/chat-input-actions.tsx:62— chat-input-actions.ChatInputActions has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 38, if/else 19 (21 pts), ternaries 5 (6 pts) (nesting depth added 3). Of this number, 40 points are the body's own statements and 25 belong to 9 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
agent-profiles-local-view.AgentProfilesLocalView (cognitive 65) src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:115— agent-profiles-local-view.AgentProfilesLocalView has cognitive complexity 65 (threshold 15). Drivers by points: ternaries 19 (24 pts), boolean chains 21, if/else 13 (15 pts), error handling 4 (5 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 42 belong to 7 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
conversation-card.ConversationCard (cognitive 59) src/components/features/conversation-panel/conversation-card/conversation-card.tsx:80— conversation-card.ConversationCard has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 34, ternaries 9 (13 pts), if/else 5 (8 pts), error handling 2 (4 pts) (nesting depth added 9). Of this number, 43 points are the body's own statements and 16 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
home-chat-launcher.HomeChatLauncher (cognitive 59) src/components/features/home/home-chat-launcher.tsx:56— home-chat-launcher.HomeChatLauncher has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 23, if/else 14 (18 pts), ternaries 8 (13 pts), error handling 3 (5 pts) (nesting depth added 11). Of this number, 17 points are the body's own statements and 42 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-main.ConversationMain (cognitive 58) src/components/features/conversation/conversation-main/conversation-main.tsx:79— conversation-main.ConversationMain has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 22 (35 pts), boolean chains 21, if/else 2 (nesting depth added 13). Of this number, 53 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
llm-settings-local-view.LlmSettingsLocalView (cognitive 57) src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:98— llm-settings-local-view.LlmSettingsLocalView has cognitive complexity 57 (threshold 15). Drivers by points: boolean chains 22, ternaries 14 (20 pts), if/else 10 (12 pts), error handling 3 (nesting depth added 8). Of this number, 24 points are the body's own statements and 33 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pinned-automation-card.PinnedAutomationCard (cognitive 55) src/components/features/home/featured-automations/pinned-automation-card.tsx:58— pinned-automation-card.PinnedAutomationCard has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 25 (36 pts), boolean chains 16, if/else 3 (nesting depth added 11). Of this number, 45 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
event-message.EventMessageComponent (cognitive 52) src/components/conversation-events/chat/event-message.tsx:180— event-message.EventMessageComponent has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 21, if/else 16 (21 pts), ternaries 6 (10 pts) (nesting depth added 9). Of this number, 49 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
meta-llm-settings-view.MetaLlmSettingsView (cognitive 52) src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx:56— meta-llm-settings-view.MetaLlmSettingsView has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 17 (25 pts), if/else 11, boolean chains 8, error handling 4 (5 pts), loops 3 (nesting depth added 9). Of this number, 23 points are the body's own statements and 29 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
automation-card.AutomationCard (cognitive 48) src/components/features/automations/automation-card.tsx:59— automation-card.AutomationCard has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 23 (39 pts), boolean chains 8, if/else 1 (nesting depth added 16). Of this number, 47 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
automations-list.AutomationsList (cognitive 46) src/routes/automations-list.tsx:297— automations-list.AutomationsList has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 25, if/else 10, ternaries 8 (9 pts), error handling 2 (nesting depth added 1). Of this number, 31 points are the body's own statements and 15 belong to 12 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
automation-setup-panel.AutomationSetupPanel (cognitive 45) REDACTED:640— automation-setup-panel.AutomationSetupPanel has cognitive complexity 45 (threshold 15). Drivers by points: if/else 81 (90 pts), ternaries 67 (87 pts), boolean chains 52, error handling 8 (10 pts), loops 4 (nesting depth added 31). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (automation-setup-panel.AutomationSetupPanel::handleTest) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
conversation-overview-git-section.ConversationOverviewGitSection (cognitive 44) src/components/features/conversation/conversation-overview-git-section.tsx:36— conversation-overview-git-section.ConversationOverviewGitSection has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 17 (34 pts), boolean chains 8, if/else 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dev-with-automation.main (cognitive 43) REDACTED:1507— dev-with-automation.main has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 12, ternaries 5 (9 pts), error handling 2 (4 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
load-complete-events.loadCompleteTranscriptEvents (cognitive 42) src/utils/transcript-export/load-complete-events.ts:33— load-complete-events.loadCompleteTranscriptEvents has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 17). Of this number, 27 points are the body's own statements and 15 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
super-admin-setup-guide.SuperAdminSetupGuide (cognitive 41) src/components/features/setup-guide/super-admin-setup-guide.tsx:80— super-admin-setup-guide.SuperAdminSetupGuide has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 13 (19 pts), if/else 14 (15 pts), boolean chains 7 (nesting depth added 7). Most of this is not in the body itself: 8 of the 41 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 137, a function literal at line 185, a function literal at line 346, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
canvas-extensions.CanvasExtensionsScreen (cognitive 41) src/routes/canvas-extensions.tsx:42— canvas-extensions.CanvasExtensionsScreen has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 13 (27 pts), if/else 5 (9 pts), boolean chains 5 (nesting depth added 18). Of this number, 32 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sdk-settings-schema.normalizeComparableValue (cognitive 41) src/utils/sdk-settings-schema.ts:175— sdk-settings-schema.normalizeComparableValue has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 5, ternaries 2 (4 pts), error handling 1 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chat-message.ChatMessage (cognitive 40) src/components/features/chat/chat-message.tsx:38— chat-message.ChatMessage has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 13 (18 pts), boolean chains 17, if/else 5 (nesting depth added 5). Of this number, 33 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
recommended-automations-launcher.RecommendedAutomationsLauncher (cognitive 40) src/components/features/automations/recommended-automations-launcher.tsx:100— recommended-automations-launcher.RecommendedAutomationsLauncher has cognitive complexity 40 (threshold 15). Drivers by points: if/else 26 (27 pts), boolean chains 10, ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 8 of the 40 points are its own statements and the rest belongs to 13 function items inside it that branch (handleSelectAutomation, a function literal at line 168, a function literal at line 192, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
command-menu.CommandMenu (cognitive 40) src/components/features/command-menu/command-menu.tsx:62— command-menu.CommandMenu has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (22 pts), ternaries 9 (14 pts), boolean chains 4 (nesting depth added 10). Most of this is not in the body itself: 5 of the 40 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 289, a function literal at line 74, handleInputKeyDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
acp-command.parseCommand (cognitive 40) src/utils/acp-command.ts:65— acp-command.parseCommand has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 3 (7 pts), boolean chains 6 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
automation-list-row.AutomationListRow (cognitive 38) src/components/features/automations/automation-list-row.tsx:55— automation-list-row.AutomationListRow has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 19 (32 pts), boolean chains 6 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manage-backends-modal.ManageBackendsModal (cognitive 37) src/components/features/backends/manage-backends-modal.tsx:72— manage-backends-modal.ManageBackendsModal has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 18 (28 pts), boolean chains 6, if/else 3 (nesting depth added 10). Of this number, 30 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
llm-profile-form.buildProfileLlmConfig (cognitive 37) src/components/features/settings/llm-profiles/llm-profile-form.ts:92— llm-profile-form.buildProfileLlmConfig has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 3 (7 pts), boolean chains 6 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cloud-new-conversation-menu.CloudNewConversationMenu (cognitive 36) src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:81— cloud-new-conversation-menu.CloudNewConversationMenu has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 19, if/else 12 (13 pts), ternaries 4 (nesting depth added 1). Of this number, 17 points are the body's own statements and 19 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
secret-form.SecretForm (cognitive 36) src/components/features/settings/secrets-settings/secret-form.tsx:31— secret-form.SecretForm has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 18, if/else 6 (10 pts), ternaries 7 (8 pts) (nesting depth added 5). Of this number, 19 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-tabs.ConversationTabs (cognitive 35) src/components/features/conversation/conversation-tabs/conversation-tabs.tsx:34— conversation-tabs.ConversationTabs has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 7, ternaries 5, loops 2 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 194, handleTabKeyDown, a function literal at line 77, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
custom-server-editor.CustomServerEditor (cognitive 35) src/components/features/mcp-page/custom-server-editor.tsx:41— custom-server-editor.CustomServerEditor has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 12 (13 pts), boolean chains 8 (nesting depth added 3). Most of this is not in the body itself: 12 of the 35 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 168, a function literal at line 138, a function literal at line 79, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
managed-agents-view.ManagedAgentsView (cognitive 34) src/components/features/backends/managed-agents/managed-agents-view.tsx:132— managed-agents-view.ManagedAgentsView has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 7 (10 pts), boolean chains 8, error handling 3, loops 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 16 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
backend-selector.BackendSelector (cognitive 34) src/components/features/backends/backend-selector.tsx:145— backend-selector.BackendSelector has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 14 (23 pts), if/else 7, boolean chains 4 (nesting depth added 9). Of this number, 27 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
repo-selection-form.RepositorySelectionForm (cognitive 34) src/components/features/home/repo-selection-form.tsx:41— repo-selection-form.RepositorySelectionForm has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 20, if/else 10 (11 pts), ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 73, a function literal at line 211, renderRepositorySelector, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
workspace-selection-form.WorkspaceSelectionForm (cognitive 33) src/components/features/home/workspace-selection-form.tsx:68— workspace-selection-form.WorkspaceSelectionForm has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 11, if/else 11, ternaries 7 (11 pts) (nesting depth added 4). Of this number, 19 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
sidebar-rail-body.SidebarRailBody (cognitive 33) src/components/features/sidebar/sidebar-rail-body.tsx:76— sidebar-rail-body.SidebarRailBody has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 14 (21 pts), boolean chains 10, if/else 1 (2 pts) (nesting depth added 8). Of this number, 29 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
seed-automation-ux-data.insertRuns (cognitive 32) scripts/seed-automation-ux-data.mjs:662— seed-automation-ux-data.insertRuns has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 13 (27 pts), boolean chains 2, loops 2, if/else 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
file-diff-viewer.FileDiffViewer (cognitive 32) src/components/features/diff-viewer/file-diff-viewer.tsx:156— file-diff-viewer.FileDiffViewer has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 13, ternaries 10 (12 pts), if/else 7 (nesting depth added 2). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 7 function items inside it that branch (renderContent, a function literal at line 208, renderEditorShell, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
openai-subscription-auth-card.OpenAISubscriptionAuthCard (cognitive 32) src/components/features/settings/llm-settings/openai-subscription-auth-card.tsx:32— openai-subscription-auth-card.OpenAISubscriptionAuthCard has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 9 (17 pts), boolean chains 7, if/else 5, error handling 3 (nesting depth added 8). Of this number, 22 points are the body's own statements and 10 belong to 9 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-local-storage.sanitizeStoredState (cognitive 32) src/utils/conversation-local-storage.ts:106— conversation-local-storage.sanitizeStoredState has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 8 (nesting depth added 7). Of this number, 30 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sdk-settings-schema.coerceFieldValue (cognitive 32) src/utils/sdk-settings-schema.ts:347— sdk-settings-schema.coerceFieldValue has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-name-context-menu.ConversationNameContextMenu (cognitive 31) src/components/features/conversation/conversation-name-context-menu.tsx:92— conversation-name-context-menu.ConversationNameContextMenu has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 20, if/else 7 (8 pts), ternaries 3 (nesting depth added 1). Of this number, 26 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-tabs-context-menu.ConversationTabsContextMenu (cognitive 31) src/components/features/conversation/conversation-tabs/conversation-tabs-context-menu.tsx:42— conversation-tabs-context-menu.ConversationTabsContextMenu has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 10, boolean chains 7 (nesting depth added 3). Most of this is not in the body itself: 10 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (handlePinToggle, a function literal at line 190, a function literal at line 55, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
check-backend-step.CheckBackendStep (cognitive 31) src/components/features/onboarding/steps/check-backend-step.tsx:116— check-backend-step.CheckBackendStep has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 14 (17 pts), boolean chains 7, if/else 6 (7 pts) (nesting depth added 4). Of this number, 22 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
setup-llm-step.SetupLlmStep (cognitive 31) src/components/features/onboarding/steps/setup-llm-step.tsx:192— setup-llm-step.SetupLlmStep has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 9, if/else 8, error handling 3 (4 pts) (nesting depth added 5). Most of this is not in the body itself: 13 of the 31 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 245, handleNext, a function literal at line 221). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
mcp-server-form.MCPServerForm (cognitive 31) src/components/features/settings/mcp-settings/mcp-server-form.tsx:50— mcp-server-form.MCPServerForm has cognitive complexity 31 (threshold 15). Drivers by points: if/else 54 (73 pts), boolean chains 62, ternaries 8 (9 pts), loops 2, error handling 1 (nesting depth added 20). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: 2 other methods here (mcp-server-form.MCPServerForm::validateForm, mcp-server-form.MCPServerForm::buildConfig) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
use-draft-persistence.useDraftPersistence (cognitive 31) src/hooks/chat/use-draft-persistence.ts:45— use-draft-persistence.useDraftPersistence has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 9). None of this is in the body itself: all 31 points belong to 3 function literals inside it that branch (lines 153, 98, 313). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
git-control-bar.GitControlBar (cognitive 30) src/components/features/chat/git-control-bar.tsx:34— git-control-bar.GitControlBar has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, if/else 8, ternaries 7. Of this number, 20 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
automation-export.parseAutomationFile (cognitive 30) src/utils/automation-export.ts:189— automation-export.parseAutomationFile has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 14 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mcp-config.buildMcpServerPatch (cognitive 30) src/utils/mcp-config.ts:319— mcp-config.buildMcpServerPatch has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 6 (11 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
static-server.parseArgs (cognitive 29) scripts/static-server.mjs:88— static-server.parseArgs has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 9, match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
settings-service.api.cloudCompatibleMcpConfig (cognitive 29) src/api/settings-service/settings-service.api.ts:310— settings-service.api.cloudCompatibleMcpConfig has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 2 (3 pts), ternaries 3, boolean chains 2, error handling 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 351, collectStoredHeaders, a function literal at line 324). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
messages.Messages (cognitive 29) src/components/conversation-events/chat/messages.tsx:32— messages.Messages has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6, ternaries 5, loops 3 (nesting depth added 5). None of this is in the body itself: all 29 points belong to 8 function items inside it that branch (a function literal at line 78, a function literal at line 56, renderEventMessage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
automation-setup-prompt-stack.AutomationSetupPromptStack (cognitive 29) src/components/features/automations/setup/automation-setup-prompt-stack.tsx:238— automation-setup-prompt-stack.AutomationSetupPromptStack has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 14 (20 pts), boolean chains 6, if/else 2 (3 pts) (nesting depth added 7). Of this number, 25 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tour-engine.startGuidedTour (cognitive 29) src/components/features/setup-guide/tour/tour-engine.ts:179— tour-engine.startGuidedTour has cognitive complexity 29 (threshold 15). Drivers by points: if/else 20, boolean chains 8, loops 1. Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 281, a function literal at line 219, a function literal at line 360, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
folder-browser-modal.FolderBrowserModal (cognitive 28) src/components/features/home/workspace-dropdown/folder-browser-modal.tsx:125— folder-browser-modal.FolderBrowserModal has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, if/else 9, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 138, getBasename, a function literal at line 162, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
use-terminal.useTerminal (cognitive 28) src/hooks/use-terminal.ts:94— use-terminal.useTerminal has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 11). None of this is in the body itself: all 28 points belong to 6 function items inside it that branch (a function literal at line 139, a function literal at line 183, initializeTerminal, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
root.App (cognitive 28) src/root.tsx:234— root.App has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 19, if/else 7, ternaries 2. Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
automation-export.validateTrigger (cognitive 28) src/utils/automation-export.ts:56— automation-export.validateTrigger has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 15, if/else 10 (13 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
get-observation-result.getObservationResult (cognitive 27) src/components/conversation-events/chat/event-content-helpers/get-observation-result.ts:22— get-observation-result.getObservationResult has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
use-bash-command-logs.useBashCommandLogs (cognitive 27) src/hooks/query/use-bash-command-logs.ts:142— use-bash-command-logs.useBashCommandLogs has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 5, boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manifest-validation.checkField (cognitive 27) src/manifests/manifest-validation.ts:260— manifest-validation.checkField has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 7 (nesting depth added 5). Of this number, 20 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
download-node.failOnDanglingSymlinks (cognitive 26) scripts/download-node.mjs:273— download-node.failOnDanglingSymlinks has cognitive complexity 26 (threshold 15). Drivers by points: error handling 3 (11 pts), if/else 4 (10 pts), loops 3 (5 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-panel-list-helpers.groupConversations (cognitive 26) src/components/features/conversation-panel/conversation-panel-list-helpers.ts:549— conversation-panel-list-helpers.groupConversations has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 4 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). Of this number, 21 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider-connection-modal.ProviderConnectionModal (cognitive 26) src/components/features/settings/llm-profiles/provider-connection-modal.tsx:46— provider-connection-modal.ProviderConnectionModal has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, ternaries 8 (9 pts), if/else 5, error handling 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mcp-config.parseMcpConfig (cognitive 26) src/utils/mcp-config.ts:77— mcp-config.parseMcpConfig has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 16, if/else 5 (9 pts), loops 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
check-sdk-version-sync.main (cognitive 25) scripts/check-sdk-version-sync.mjs:336— check-sdk-version-sync.main has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 3 (5 pts), ternaries 1 (4 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
static-server.startStaticServer (cognitive 25) scripts/static-server.mjs:658— static-server.startStaticServer has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 10, loops 2 (3 pts), ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 695, 750, 735, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
should-render-event.shouldRenderEvent (cognitive 25) src/components/conversation-events/chat/event-content-helpers/should-render-event.ts:74— should-render-event.shouldRenderEvent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 6 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-repo-dropdown.GitRepoDropdown (cognitive 25) REDACTED:39— git-repo-dropdown.GitRepoDropdown has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12, ternaries 5 (7 pts), boolean chains 6 (nesting depth added 2). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 133, 57, 101, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
api-error-message.getApiErrorMessage (cognitive 25) src/utils/api-error-message.ts:102— api-error-message.getApiErrorMessage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 10, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
handle-event-for-ui.handleEventForUI (cognitive 25) src/utils/handle-event-for-ui.ts:275— handle-event-for-ui.handleEventForUI has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 4, ternaries 1 (nesting depth added 6). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
change-agent-button.ChangeAgentButton (cognitive 24) src/components/features/chat/change-agent-button.tsx:25— change-agent-button.ChangeAgentButton has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (10 pts), ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 104, 86, 59, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
backend-form-modal.BackendForm (cognitive 24) src/components/features/backends/backend-form-modal.tsx:498— backend-form-modal.BackendForm has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 10, if/else 3 (nesting depth added 3). Of this number, 20 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
local-new-conversation-menu.LocalNewConversationMenu (cognitive 24) src/components/features/conversation-panel/local-new-conversation-menu.tsx:61— local-new-conversation-menu.LocalNewConversationMenu has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 16, if/else 6, ternaries 2. Of this number, 13 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
manifest-form-field.SetupFormField (cognitive 24) src/components/features/manifest/manifest-form-field.tsx:50— manifest-form-field.SetupFormField has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 6, ternaries 4 (6 pts) (nesting depth added 2). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
onboarding-modal.OnboardingModal (cognitive 24) src/components/features/onboarding/onboarding-modal.tsx:135— onboarding-modal.OnboardingModal has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11, boolean chains 8, if/else 5. Of this number, 15 points are the body's own statements and 9 belong to 5 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sidebar.Sidebar (cognitive 24) src/components/features/sidebar/sidebar.tsx:40— sidebar.Sidebar has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 6 (8 pts) (nesting depth added 2). Of this number, 14 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
app-settings.AppSettingsForm (cognitive 24) src/routes/app-settings.tsx:45— app-settings.AppSettingsForm has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 18, ternaries 4, if/else 2. Of this number, 13 points are the body's own statements and 11 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dev-with-automation.buildConfig (cognitive 23) REDACTED:394— dev-with-automation.buildConfig has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
agent-server-adapter.buildStartConversationRequest (cognitive 23) src/api/agent-server-adapter.ts:1070— agent-server-adapter.buildStartConversationRequest has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (12 pts), if/else 10, boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
get-event-content.getObservationEventTitle (cognitive 23) src/components/conversation-events/chat/event-content-helpers/get-event-content.tsx:148— get-event-content.getObservationEventTitle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation.AppContent (cognitive 23) src/routes/conversation.tsx:36— conversation.AppContent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8, ternaries 2 (3 pts) (nesting depth added 3). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 146, 110, 177). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
typing-indicator.deriveLiveActivity (cognitive 23) src/components/features/chat/typing-indicator.tsx:65— typing-indicator.deriveLiveActivity has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
home-automation-menu.HomeAutomationMenu (cognitive 23) src/components/features/home/featured-automations/home-automation-menu.tsx:28— home-automation-menu.HomeAutomationMenu has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 4, boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 85, a function literal at line 151, a function literal at line 53, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
git-branch-dropdown.GitBranchDropdown (cognitive 23) src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:35— git-branch-dropdown.GitBranchDropdown has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (7 pts), ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 145, 178, 96, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
plugin-detail-modal.PluginDetailModal (cognitive 23) src/components/features/plugins/plugin-detail-modal.tsx:26— plugin-detail-modal.PluginDetailModal has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 15 (20 pts), boolean chains 3 (nesting depth added 5). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manifest-validation.checkBundle (cognitive 23) src/manifests/manifest-validation.ts:551— manifest-validation.checkBundle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 6 (nesting depth added 4). Of this number, 17 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
automation-git-sync.AutomationGitSync (cognitive 23) src/routes/automation-git-sync.tsx:52— automation-git-sync.AutomationGitSync has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10, boolean chains 7, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 13 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsService.saveSettings (cognitive 22) src/api/settings-service/settings-service.api.ts:790— SettingsService.saveSettings has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentServerConversationService.createConversation (cognitive 22) src/api/conversation-service/agent-server-conversation-service.api.ts:517— AgentServerConversationService.createConversation has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 5, boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventService.searchEvents (cognitive 22) src/api/event-service/event-service.api.ts:75— EventService.searchEvents has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4, error handling 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
file-editor.FileEditorCardBody (cognitive 22) src/components/features/chat/tool-visualizers/file-editor/file-editor.tsx:53— file-editor.FileEditorCardBody has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 7, ternaries 2 (nesting depth added 4). Of this number, 20 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-overview-context-menu.ConversationOverviewContextMenu (cognitive 22) src/components/features/conversation/conversation-overview-context-menu.tsx:149— conversation-overview-context-menu.ConversationOverviewContextMenu has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10, ternaries 7, boolean chains 5. Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 9 function items inside it that branch (handleOpenGitPart, a function literal at line 167, renderMenuRow, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
conversation-name.ConversationName (cognitive 22) src/components/features/conversation/conversation-name.tsx:18— conversation-name.ConversationName has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 8 (9 pts), ternaries 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
canvas-extensions-runtime.CanvasExtensionsRuntimeProvider (cognitive 22) src/components/features/canvas-extensions/canvas-extensions-runtime.tsx:97— canvas-extensions-runtime.CanvasExtensionsRuntimeProvider has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 3 (4 pts), ternaries 2 (3 pts), loops 2 (nesting depth added 5). None of this is in the body itself: all 22 points belong to 6 function literals inside it that branch (lines 171, 306, 194, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
agent-status.AgentStatus (cognitive 22) src/components/features/controls/agent-status.tsx:32— agent-status.AgentStatus has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 19, if/else 2, ternaries 1. Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-layouts-menu.ConversationLayoutsMenu (cognitive 22) src/components/features/conversation-panel/conversation-layouts-menu.tsx:115— conversation-layouts-menu.ConversationLayoutsMenu has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (13 pts), if/else 7 (8 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (handleMenuKeyDown, a function literal at line 143, a function literal at line 222, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
workspace-dropdown.WorkspaceDropdown (cognitive 22) src/components/features/home/workspace-dropdown/workspace-dropdown.tsx:54— workspace-dropdown.WorkspaceDropdown has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, ternaries 5 (nesting depth added 1). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 127, a function literal at line 117, a function literal at line 184, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
plugin-launch-modal.PluginLaunchModal (cognitive 22) src/components/features/launch/plugin-launch-modal.tsx:30— plugin-launch-modal.PluginLaunchModal has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, if/else 7, ternaries 2. Of this number, 11 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
meta-profile-editor.MetaProfileEditor (cognitive 22) src/components/features/settings/meta-llm-profiles/meta-profile-editor.tsx:77— meta-profile-editor.MetaProfileEditor has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, ternaries 7 (8 pts), if/else 2, loops 2 (nesting depth added 1). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSave, a function literal at line 105, a function literal at line 134, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
use-chat-input-model-state.useChatInputModelState (cognitive 22) src/hooks/use-chat-input-model-state.ts:38— use-chat-input-model-state.useChatInputModelState has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 5, if/else 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skills-settings.SkillsSettingsScreen (cognitive 22) src/routes/skills-settings.tsx:44— skills-settings.SkillsSettingsScreen has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (11 pts), if/else 6, boolean chains 5 (nesting depth added 3). Of this number, 16 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
dropdown.Dropdown (cognitive 22) src/ui/dropdown/dropdown.tsx:49— dropdown.Dropdown has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 5 (7 pts), boolean chains 5 (nesting depth added 4). Of this number, 13 points are the body's own statements and 9 belong to 5 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
check_pr_description.validate_linked_issue_ready (cognitive 22) .github/scripts/check_pr_description.py:296— check_pr_description.validate_linked_issue_ready has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mars-tunnel-backend.waitForMarsAgentServer (cognitive 21) src/api/mars/mars-tunnel-backend.ts:367— mars-tunnel-backend.waitForMarsAgentServer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-overview-toggle.ConversationOverviewToggle (cognitive 21) src/components/features/conversation/conversation-overview-toggle.tsx:31— conversation-overview-toggle.ConversationOverviewToggle has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, ternaries 3 (4 pts) (nesting depth added 2). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (handleToggle, a function literal at line 53, a function literal at line 150, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
automation-setup-draft-service.setupDraftFromServerDraft (cognitive 21) src/components/features/automations/setup/automation-setup-draft-service.ts:94— automation-setup-draft-service.setupDraftFromServerDraft has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (20 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
device-flow-auth.DeviceFlowAuth (cognitive 21) src/components/features/backends/device-flow-auth.tsx:71— device-flow-auth.DeviceFlowAuth has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 5, error handling 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 98, handleStartAuth, a function literal at line 134, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
backend-row.BackendRow (cognitive 21) src/components/features/backends/backend-row.tsx:31— backend-row.BackendRow has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12 (14 pts), boolean chains 7 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
conversation-card-context-menu.ConversationCardContextMenu (cognitive 21) src/components/features/conversation-panel/conversation-card/conversation-card-context-menu.tsx:41— conversation-card-context-menu.ConversationCardContextMenu has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, ternaries 8 (9 pts), if/else 1 (nesting depth added 1). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
conversation-card-actions.ConversationCardActions (cognitive 21) src/components/features/conversation-panel/conversation-card/conversation-card-actions.tsx:28— conversation-card-actions.ConversationCardActions has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8, if/else 4 (nesting depth added 3). Of this number, 11 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
running-automations-list.RunningAutomationRow (cognitive 21) src/components/features/home/featured-automations/running-automations-list.tsx:54— running-automations-list.RunningAutomationRow has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent-canvas-version-modal.AgentCanvasVersionModal (cognitive 21) src/components/features/settings/agent-canvas-version-modal.tsx:50— agent-canvas-version-modal.AgentCanvasVersionModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 3, if/else 3 (nesting depth added 4). Of this number, 16 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
model-selector.ModelSelector (cognitive 21) src/components/shared/modals/settings/model-selector.tsx:45— model-selector.ModelSelector has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 6, ternaries 5. Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 95, a function literal at line 134, handleChangeModel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
use-plan-mode-interceptor.usePlanModeInterceptor (cognitive 21) src/hooks/chat/use-plan-mode-interceptor.ts:29— use-plan-mode-interceptor.usePlanModeInterceptor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8 (nesting depth added 4). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 44). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
use-backends-health.useBackendsHealth (cognitive 21) src/hooks/query/use-backends-health.ts:215— use-backends-health.useBackendsHealth has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, ternaries 7, if/else 5, error handling 1. None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 229, 295, 258). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-await-context-compaction.useAwaitContextCompaction (cognitive 21) src/hooks/use-await-context-compaction.ts:62— use-await-context-compaction.useAwaitContextCompaction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 3 (4 pts), boolean chains 1, loops 1 (nesting depth added 6). None of this is in the body itself: all 21 points belong to 7 function literals inside it that branch (lines 112, 71, 96, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-llm-configured.useLlmConfigured (cognitive 21) src/hooks/use-llm-configured.ts:40— use-llm-configured.useLlmConfigured has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 17, ternaries 4. Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
agent-settings.buildAgentProfileFields (cognitive 21) src/routes/agent-settings.tsx:254— agent-settings.buildAgentProfileFields has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 8, boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
automation-setup-new.AutomationSetupNew (cognitive 21) src/routes/automation-setup-new.tsx:31— automation-setup-new.AutomationSetupNew has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (6 pts), boolean chains 4, error handling 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 64, 43, 50, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
settings-service.api.headersFromMcpAuth (cognitive 20) src/api/settings-service/settings-service.api.ts:245— settings-service.api.headersFromMcpAuth has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 3 (6 pts), boolean chains 5, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
generic-event-message.GenericEventMessage (cognitive 20) src/components/features/chat/generic-event-message.tsx:27— generic-event-message.GenericEventMessage has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (12 pts), boolean chains 5, if/else 2 (3 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
error-message-banner.ErrorMessageBanner (cognitive 20) src/components/features/chat/error-message-banner.tsx:23— error-message-banner.ErrorMessageBanner has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 7, if/else 3, error handling 1. Of this number, 15 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
run-logs-modal.RunLogsModal (cognitive 20) src/components/features/automations/detail/run-logs-modal.tsx:199— run-logs-modal.RunLogsModal has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 6, ternaries 5. Of this number, 15 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skill-card-pill-row.SkillCardPillRow (cognitive 20) src/components/features/skills/skill-card-pill-row.tsx:62— skill-card-pill-row.SkillCardPillRow has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, boolean chains 6, ternaries 2. Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 75, a function literal at line 100, a function literal at line 118, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
resolve-conversation-launch.resolveConversationLaunch (cognitive 20) src/hooks/mutation/resolve-conversation-launch.ts:51— resolve-conversation-launch.resolveConversationLaunch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, ternaries 4 (5 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manifest-validation.checkMode (cognitive 20) src/manifests/manifest-validation.ts:652— manifest-validation.checkMode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
get-acp-tool-call-content.getACPDisplayBlocks (cognitive 19) src/components/conversation-events/chat/event-content-helpers/get-acp-tool-call-content.ts:121— get-acp-tool-call-content.getACPDisplayBlocks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
user-assistant-event-message.UserAssistantEventMessageComponent (cognitive 19) src/components/conversation-events/chat/event-message-components/user-assistant-event-message.tsx:29— user-assistant-event-message.UserAssistantEventMessageComponent has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8, boolean chains 6, if/else 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (handleBranch, a function literal at line 61, a function literal at line 96, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
open-repository-modal.OpenRepositoryModal (cognitive 19) src/components/features/chat/open-repository-modal.tsx:23— open-repository-modal.OpenRepositoryModal has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (9 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 40, a function literal at line 60, handleLaunch, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
automations-dashboard-controls.AutomationsDashboardControls (cognitive 19) src/components/features/automations/dashboard/automations-dashboard-controls.tsx:59— automations-dashboard-controls.AutomationsDashboardControls has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 5, if/else 3 (nesting depth added 4). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent-profile-actions-menu.AgentProfileActionsMenu (cognitive 19) src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:42— agent-profile-actions-menu.AgentProfileActionsMenu has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 120, 98, 92, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
add-models-modal.AddModelsModal::handleSubmit (cognitive 19) src/components/features/settings/llm-profiles/add-models-modal.tsx:249— add-models-modal.AddModelsModal::handleSubmit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (7 pts), error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (add-models-modal.AddModelsModal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
profile-actions-menu.ProfileActionsMenu (cognitive 19) src/components/features/settings/llm-profiles/profile-actions-menu.tsx:44— profile-actions-menu.ProfileActionsMenu has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 126, 102, 95, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
sidebar-nav-link.SidebarNavLink (cognitive 19) src/components/features/sidebar/sidebar-nav-link.tsx:57— sidebar-nav-link.SidebarNavLink has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (7 pts), if/else 3 (4 pts) (nesting depth added 2). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
conversation-confirmation-buttons.ConversationConfirmationButtons (cognitive 19) src/components/shared/buttons/conversation-confirmation-buttons.tsx:16— conversation-confirmation-buttons.ConversationConfirmationButtons has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 8, ternaries 1. Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 43, 72, 83, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
active-backend-context.ActiveBackendProvider (cognitive 19) src/contexts/active-backend-context.tsx:72— active-backend-context.ActiveBackendProvider has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 4). None of this is in the body itself: all 19 points belong to 4 function literals inside it that branch (lines 143, 157, 91, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-cloud-current-user-id.useCloudCurrentUserId (cognitive 19) src/hooks/query/use-cloud-current-user-id.ts:10— use-cloud-current-user-id.useCloudCurrentUserId has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 9). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-git-repositories.useGitRepositories (cognitive 19) src/hooks/query/use-git-repositories.ts:21— use-git-repositories.useGitRepositories has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 7, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 88, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-device-flow.useDeviceFlow.start (cognitive 19) src/hooks/use-device-flow.ts:83— use-device-flow.useDeviceFlow.start has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4 (8 pts), error handling 2, boolean chains 1 (nesting depth added 7). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 94). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
use-sync-telemetry-consent.useSyncTelemetryConsent (cognitive 19) src/hooks/use-sync-telemetry-consent.ts:31— use-sync-telemetry-consent.useSyncTelemetryConsent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 45). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
user-facing-error.collectErrorMessages (cognitive 19) src/utils/user-facing-error.ts:13— user-facing-error.collectErrorMessages has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
device-verify.DeviceVerify (cognitive 19) src/routes/device-verify.tsx:9— device-verify.DeviceVerify has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, ternaries 3 (6 pts), boolean chains 4, error handling 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
proxy-utils.proxyServerInfoRequest (cognitive 18) scripts/proxy-utils.mjs:70— proxy-utils.proxyServerInfoRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, ternaries 4 (6 pts), error handling 2, boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 115, 103, 159, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
McpService.authorizeOAuth (cognitive 18) src/api/mcp-service/mcp-service.api.ts:308— McpService.authorizeOAuth has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, loops 2, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
goal-status-content.GoalStatusContent (cognitive 18) src/components/features/chat/goal-status-content.tsx:69— goal-status-content.GoalStatusContent has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 6, if/else 3, error handling 1 (nesting depth added 2). Of this number, 10 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
right-panel-toggle.RightPanelToggle (cognitive 18) src/components/features/conversation/right-panel-toggle.tsx:27— right-panel-toggle.RightPanelToggle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (7 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (handleToggle). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
conversation-tab-nav.ConversationTabNav (cognitive 18) src/components/features/conversation/conversation-tabs/conversation-tab-nav.tsx:37— conversation-tab-nav.ConversationTabNav has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (13 pts), boolean chains 4, if/else 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
recommended-automations-section.RecommendedAutomationsSection (cognitive 18) src/components/features/automations/recommended-automations-section.tsx:390— recommended-automations-section.RecommendedAutomationsSection has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 13, if/else 2 (3 pts), ternaries 2 (nesting depth added 1). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
automation-setup-panel.AutomationSetupPanel::handleTest (cognitive 18) REDACTED:1522— automation-setup-panel.AutomationSetupPanel::handleTest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 5 (6 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (automation-setup-panel.AutomationSetupPanel) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
backend-selector.buildOptions (cognitive 18) src/components/features/backends/backend-selector.tsx:62— backend-selector.buildOptions has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (8 pts), loops 3 (5 pts), if/else 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-card-preview.ConversationCardPreview (cognitive 18) src/components/features/conversation-panel/conversation-card/conversation-card-preview.tsx:114— conversation-card-preview.ConversationCardPreview has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (17 pts), boolean chains 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
conversation-group-folder-row.ConversationGroupFolderRow (cognitive 18) src/components/features/conversation-panel/conversation-group-folder-row.tsx:42— conversation-group-folder-row.ConversationGroupFolderRow has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 2 (3 pts), boolean chains 2 (nesting depth added 5). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
install-server-modal.InstallServerModal (cognitive 18) src/components/features/mcp-page/install-server-modal.tsx:161— install-server-modal.InstallServerModal has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 49, if/else 29 (40 pts), ternaries 11 (17 pts), loops 6 (8 pts), error handling 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (install-server-modal.InstallServerModal::handleHttpServerSubmit, install-server-modal.InstallServerModal::handleStdioSubmit) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
build-plugins-view-model.buildPluginsViewModel (cognitive 18) src/components/features/plugins/build-plugins-view-model.ts:51— build-plugins-view-model.buildPluginsViewModel has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 3, if/else 2 (3 pts), loops 3 (nesting depth added 5). Of this number, 14 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
add-models-modal.AddModelsModal (cognitive 18) src/components/features/settings/llm-profiles/add-models-modal.tsx:77— add-models-modal.AddModelsModal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 20, ternaries 7 (9 pts), loops 4 (8 pts), error handling 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (add-models-modal.AddModelsModal::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
use-backends-health.probeBackend (cognitive 18) src/hooks/query/use-backends-health.ts:91— use-backends-health.probeBackend has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-auto-refresh-files-on-edit.useAutoRefreshFilesOnEdit (cognitive 18) src/hooks/use-auto-refresh-files-on-edit.ts:70— use-auto-refresh-files-on-edit.useAutoRefreshFilesOnEdit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 7). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 105). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
file-language.getPrismLanguageForFile (cognitive 18) src/utils/file-language.ts:158— file-language.getPrismLanguageForFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-diff-stats.countUnifiedDiffStats (cognitive 18) src/utils/git-diff-stats.ts:8— git-diff-stats.countUnifiedDiffStats has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
injectBundledNode (cognitive 18) electron/main.mjs:189— injectBundledNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4, error handling 1 (3 pts), loops 1 (2 pts), other 1 (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
brand-dev-electron.ensureBundleName (cognitive 17) scripts/brand-dev-electron.mjs:113— brand-dev-electron.ensureBundleName has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
static-server.handleStatic (cognitive 17) scripts/static-server.mjs:598— static-server.handleStatic has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (nesting depth added 4). Of this number, 12 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
automation-form-session.normalizeDraft (cognitive 17) src/api/automation-form-session.ts:138— automation-form-session.normalizeDraft has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 14, boolean chains 2, if/else 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mcp-redacted-credentials.substituteRedactedMcpCredentials (cognitive 17) src/api/mcp-service/mcp-redacted-credentials.ts:84— mcp-redacted-credentials.substituteRedactedMcpCredentials has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 5, ternaries 1 (2 pts), error handling 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
get-event-content.getEventContent (cognitive 17) src/components/conversation-events/chat/event-content-helpers/get-event-content.tsx:315— get-event-content.getEventContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
file-content-viewer.FileContentViewer (cognitive 17) src/components/features/files-tab/file-content-viewer.tsx:72— file-content-viewer.FileContentViewer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
git-provider-dropdown.GitProviderDropdown (cognitive 17) src/components/features/home/git-provider-dropdown/git-provider-dropdown.tsx:29— git-provider-dropdown.GitProviderDropdown has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 5, match/switch 1, ternaries 1. Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 71, a function literal at line 123, a function literal at line 105, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
mars-session-panel.MarsSessionPanel (cognitive 17) src/components/features/sidebar/mars-session-panel.tsx:241— mars-session-panel.MarsSessionPanel has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 11 (13 pts), if/else 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
build-skill-pills.buildSkillPills (cognitive 17) src/components/features/skills/build-skill-pills.tsx:36— build-skill-pills.buildSkillPills has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, loops 3 (5 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-unified-vscode-url.useUnifiedVSCodeUrl (cognitive 17) src/hooks/query/use-unified-vscode-url.ts:24— use-unified-vscode-url.useUnifiedVSCodeUrl has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 3, ternaries 3. Of this number, 16 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
interface-validation.checkAttribute (cognitive 17) REDACTED:500— interface-validation.checkAttribute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manifest-validation.checkRequires (cognitive 17) src/manifests/manifest-validation.ts:186— manifest-validation.checkRequires has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 199, 220). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
manifest-local-validation.validateValue (cognitive 17) src/manifests/manifest-local-validation.ts:224— manifest-local-validation.validateValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
automation-setup.buildActionPayload (cognitive 17) src/manifests/automation-setup.ts:406— automation-setup.buildActionPayload has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
automation-detail.AutomationDetail (cognitive 17) src/routes/automation-detail.tsx:81— automation-detail.AutomationDetail has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automation-form-session.patchAutomationFormSession (cognitive 16) src/api/automation-form-session.ts:246— automation-form-session.patchAutomationFormSession has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
group-events.isGroupableEvent (cognitive 16) src/components/conversation-events/chat/group-events.ts:24— group-events.isGroupableEvent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
run-logs-modal.RunInspectionSummary (cognitive 16) src/components/features/automations/detail/run-logs-modal.tsx:102— run-logs-modal.RunInspectionSummary has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 3, if/else 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
git-sync-config-form.GitSyncConfigForm::handleSubmit (cognitive 16) src/components/features/automations/git-sync/git-sync-config-form.tsx:184— git-sync-config-form.GitSyncConfigForm::handleSubmit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
automation-setup-panel.EventFields (cognitive 16) REDACTED:3052— automation-setup-panel.EventFields has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 6 (7 pts), if/else 2 (nesting depth added 1). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
conversation-card-footer.ConversationCardFooter (cognitive 16) src/components/features/conversation-panel/conversation-card/conversation-card-footer.tsx:78— conversation-card-footer.ConversationCardFooter has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 4, if/else 3 (4 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
meta-profile-actions-menu.MetaProfileActionsMenu (cognitive 16) src/components/features/settings/meta-llm-profiles/meta-profile-actions-menu.tsx:78— meta-profile-actions-menu.MetaProfileActionsMenu has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, ternaries 2 (nesting depth added 1). Of this number, 8 points are the body's own statements and 8 belong to 5 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
use-draft-persistence.useDraftPersistence.saveDraft (cognitive 16) src/hooks/chat/use-draft-persistence.ts:208— use-draft-persistence.useDraftPersistence.saveDraft has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-workspace-file-content.useWorkspaceFileContent (cognitive 16) src/hooks/query/use-workspace-file-content.ts:142— use-workspace-file-content.useWorkspaceFileContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3, boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 188). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
use-drag-resize.useDragResize.startDrag (cognitive 16) src/hooks/use-drag-resize.ts:96— use-drag-resize.useDragResize.startDrag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3 (nesting depth added 2). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (handleDragMove, handleDragEnd). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
automation-setup.deriveErrorMap (cognitive 16) src/manifests/automation-setup.ts:685— automation-setup.deriveErrorMap has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 5 (6 pts), boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (walk, a function literal at line 728, a function literal at line 712). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
handle-event-for-ui.appendStreamingDeltas (cognitive 16) src/utils/handle-event-for-ui.ts:167— handle-event-for-ui.appendStreamingDeltas has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mcp-config.buildRedactionSafeNestedPatch (cognitive 16) src/utils/mcp-config.ts:207— mcp-config.buildRedactionSafeNestedPatch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (6 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
status.getStatusCode (cognitive 16) src/utils/status.ts:64— status.getStatusCode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5, boolean chains 4, match/switch 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: AutomationService src/api/automation-service/automation-service.api.ts:381— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing src/components/features/home/shared/generic-dropdown-menu.tsx:93— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×1
Guard cannot change the result — returns what the code already falls through to src/components/features/sidebar/sidebar-onboarding-checklist-llm-complete.ts:45— The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Fake-async — async method never awaits src/services/telemetry.ts:907— `clearTelemetryData` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplication concentrated across 19 sibling directories (81 clone groups) src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:144— 81 duplicated blocks under src/components/features/ have copies in at least two of the sibling directories automations, backends, browser, canvas-extensions, chat, controls (+13 more sibling(s) not listed) — 48 of them are reported below, and 33 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 81 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 81 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 81 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (38 clone groups) src/components/features/chat/error-message-banner.tsx:66— 38 duplicated blocks under src/ have copies in at least two of the sibling directories api, components, contexts, hooks, routes, types (+1 more sibling(s) not listed) — 16 of them are reported below, and 22 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (17 clone groups) src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:106— 17 duplicated blocks under src/components/features/settings/ have copies in at least two of the sibling directories agent-profiles, llm-profiles, mcp-settings, meta-llm-profiles, secrets-settings — 14 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 17 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (10 clone groups) src/components/conversation-events/chat/task-tracking/task-item.tsx:15— 10 duplicated blocks under src/components/ have copies in at least two of the sibling directories conversation-events, features, shared — 5 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (5 clone groups) src/api/agent-profiles-service/agent-profiles-service.api.ts:61— 5 duplicated blocks under src/api/ have copies in at least two of the sibling directories agent-profiles-service, backend-registry, conversation-service, mcp-health, meta-profiles-service, profiles-service — 0 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (5 clone groups) src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:99— 5 duplicated blocks under src/components/features/home/ have copies in at least two of the sibling directories git-branch-dropdown, git-provider-dropdown, git-repo-dropdown, workspace-dropdown — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (191 matched lines × 2 locations) · ×1
Duplicated block with local edits (191 matched lines × 2 locations) src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:106— src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:106 · src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:85 — the two spans are one implementation copied and then locally edited — 908 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (124 matched lines × 2 locations) · ×1
Duplicated block with local edits (124 matched lines × 2 locations) src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:144— src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:144 · src/components/features/skills/skill-card-pill-row.tsx:88 — the two spans are one implementation copied and then locally edited — 634 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (120 matched lines × 2 locations) · ×1
Duplicated block with local edits (120 matched lines × 2 locations) src/components/features/automations/automation-card.tsx:111— src/components/features/automations/automation-card.tsx:111 · src/components/features/home/featured-automations/pinned-automation-card.tsx:95 — the two spans are one implementation copied and then locally edited — 551 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (111 matched lines × 2 locations) · ×1
Duplicated block with local edits (111 matched lines × 2 locations) src/components/features/chat/components/chat-input-llm-profile-picker.tsx:30— src/components/features/chat/components/chat-input-llm-profile-picker.tsx:30 · src/components/features/chat/components/chat-input-profile-picker.tsx:19 — the two spans are one implementation copied and then locally edited — 449 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (94 matched lines × 2 locations) · ×1
Duplicated block with local edits (94 matched lines × 2 locations) src/components/features/canvas-extensions/add-canvas-extension-modal.tsx:19— src/components/features/canvas-extensions/add-canvas-extension-modal.tsx:19 · src/components/features/plugins/add-plugin-modal.tsx:17 — the two spans are one implementation copied and then locally edited — 453 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (89 matched lines × 2 locations) · ×1
Duplicated block with local edits (89 matched lines × 2 locations) src/components/features/automations/automation-list-row.tsx:92— src/components/features/automations/automation-list-row.tsx:92 · src/components/features/home/featured-automations/running-automations-list.tsx:62 — the two spans are one implementation copied and then locally edited — 443 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (88 matched lines × 2 locations) · ×1
Duplicated block with local edits (88 matched lines × 2 locations) src/components/features/chat/components/chat-input-model.tsx:95— src/components/features/chat/components/chat-input-model.tsx:95 · src/components/features/chat/components/chat-input-profile-picker.tsx:83 — the two spans are one implementation copied and then locally edited — 350 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (84 matched lines × 2 locations) · ×1
Duplicated block with local edits (84 matched lines × 2 locations) src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:92— src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:92 · src/components/features/conversation-panel/local-new-conversation-menu.tsx:69 — the two spans are one implementation copied and then locally edited — 470 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (82 matched lines × 2 locations) · ×1
Duplicated block with local edits (82 matched lines × 2 locations) src/components/features/settings/agent-canvas-update-card.tsx:38— src/components/features/settings/agent-canvas-update-card.tsx:38 · src/components/features/settings/agent-canvas-version-modal.tsx:37 — the two spans are one implementation copied and then locally edited — 402 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (80 matched lines × 2 locations) · ×1
Duplicated block with local edits (80 matched lines × 2 locations) src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:99— src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:99 · REDACTED:196 — the two spans are one implementation copied and then locally edited — 377 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (77 matched lines × 2 locations) · ×1
Duplicated block with local edits (77 matched lines × 2 locations) src/components/features/settings/llm-profiles/provider-connection-actions-menu.tsx:33— src/components/features/settings/llm-profiles/provider-connection-actions-menu.tsx:33 · src/components/features/settings/meta-llm-profiles/meta-profile-actions-menu.tsx:81 — the two spans are one implementation copied and then locally edited — 510 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (69 lines × 2 locations) src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:44— src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:44 · src/components/features/settings/llm-profiles/profile-actions-menu.tsx:47 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (68 matched lines × 2 locations) · ×1
Duplicated block with local edits (68 matched lines × 2 locations) src/components/features/controls/git-tools-submenu.tsx:21— src/components/features/controls/git-tools-submenu.tsx:21 · src/components/features/controls/macros-submenu.tsx:14 — the two spans are one implementation copied and then locally edited — 344 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (61 matched lines × 2 locations) · ×1
Duplicated block with local edits (61 matched lines × 2 locations) src/components/features/automations/automation-card.tsx:85— src/components/features/automations/automation-card.tsx:85 · src/components/features/automations/automation-list-row.tsx:74 — the two spans are one implementation copied and then locally edited — 306 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) src/api/automation-service/automation-service.api.ts:642— src/api/automation-service/automation-service.api.ts:642 · src/api/automation-service/automation-service.api.ts:937 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) src/hooks/use-resizable-drawer-width.ts:37— src/hooks/use-resizable-drawer-width.ts:37 · src/hooks/use-resizable-panels.ts:19 — the two spans are one implementation copied and then locally edited — 379 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (53 lines × 3 locations) src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:34— src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:34 · src/components/features/settings/llm-profiles/delete-profile-modal.tsx:34 · src/components/features/settings/meta-llm-profiles/delete-meta-profile-modal.tsx:31 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) src/components/features/skills/skill-card.tsx:56— src/components/features/skills/skill-card.tsx:56 · src/components/features/skills/skill-detail-modal.tsx:89 — the two spans are one implementation copied and then locally edited — 257 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (52 identical lines × 2 files) src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:1— src/components/features/settings/agent-profiles/delete-agent-profile-modal.tsx:1 · src/components/features/settings/llm-profiles/delete-profile-modal.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) src/components/features/controls/tools-context-menu.tsx:204— src/components/features/controls/tools-context-menu.tsx:204 · src/components/features/conversation/conversation-name-context-menu.tsx:205 — the two spans are one implementation copied and then locally edited — 215 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (50 lines × 2 locations) src/contexts/conversation-websocket-context.tsx:671— src/contexts/conversation-websocket-context.tsx:671 · src/contexts/conversation-websocket-context.tsx:958 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (47 lines × 2 locations) src/components/features/settings/llm-profiles/delete-profile-modal.tsx:48— src/components/features/settings/llm-profiles/delete-profile-modal.tsx:48 · src/components/features/settings/llm-profiles/delete-provider-connection-modal.tsx:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) src/components/features/settings/agent-profiles/agent-profile-row.tsx:52— src/components/features/settings/agent-profiles/agent-profile-row.tsx:52 · src/components/features/settings/llm-profiles/profile-row.tsx:48 — the two spans are one implementation copied and then locally edited — 206 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (44 lines × 2 locations) src/components/features/chat/git-control-bar-pr-button.tsx:21— src/components/features/chat/git-control-bar-pr-button.tsx:21 · src/components/features/chat/git-control-bar-push-button.tsx:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (42 lines × 2 locations) src/stores/archived-conversations-store.ts:16— src/stores/archived-conversations-store.ts:16 · src/stores/pinned-conversations-store.ts:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (41 lines × 2 locations) src/components/features/home/home-recommended-automations-storage.ts:6— src/components/features/home/home-recommended-automations-storage.ts:6 · src/components/features/sidebar/sidebar-onboarding-checklist-storage.ts:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) playwright.mock-llm-docker.config.ts:45— playwright.mock-llm-docker.config.ts:45 · playwright.mock-llm.config.ts:26 — the two spans are one implementation copied and then locally edited — 241 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (39 lines × 3 locations) src/components/features/chat/git-control-bar-pr-button.tsx:23— src/components/features/chat/git-control-bar-pr-button.tsx:23 · src/components/features/chat/git-control-bar-pull-button.tsx:20 · src/components/features/chat/git-control-bar-push-button.tsx:23 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (38 lines × 2 locations) src/components/features/plugins/plugins-toolbar.tsx:29— src/components/features/plugins/plugins-toolbar.tsx:29 · src/components/features/skills/skills-toolbar.tsx:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function AgentSettingsScreen (cyclomatic 130, cognitive 110) src/routes/agent-settings.tsx:382— AgentSettingsScreen has cyclomatic complexity 130 and cognitive complexity 110; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConversationPanel (cyclomatic 65, cognitive 47) src/components/features/conversation-panel/conversation-panel.tsx:84— ConversationPanel has cyclomatic complexity 65 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function AutomationsList (cyclomatic 61, cognitive 45) src/routes/automations-list.tsx:297— AutomationsList has cyclomatic complexity 61 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 56, cognitive 102) src/utils/transcript-export/index.ts:271— (anonymous) has cyclomatic complexity 56 and cognitive complexity 102; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConversationCard (cyclomatic 55, cognitive 46) src/components/features/conversation-panel/conversation-card/conversation-card.tsx:80— ConversationCard has cyclomatic complexity 55 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConversationMain (cyclomatic 54, cognitive 45) src/components/features/conversation/conversation-main/conversation-main.tsx:79— ConversationMain has cyclomatic complexity 54 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function AutomationSetupPanel (cyclomatic 53, cognitive 49) REDACTED:640— AutomationSetupPanel has cyclomatic complexity 53 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ChatInputActions (cyclomatic 51, cognitive 47) src/components/features/chat/components/chat-input-actions.tsx:62— ChatInputActions has cyclomatic complexity 51 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function EventMessageComponent (cyclomatic 50, cognitive 58) src/components/conversation-events/chat/event-message.tsx:180— EventMessageComponent has cyclomatic complexity 50 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 45, cognitive 81) src/contexts/conversation-websocket-context.tsx:648— (anonymous) has cyclomatic complexity 45 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 45, cognitive 47) · ×1
Complex function main (cyclomatic 45, cognitive 47) REDACTED:1507— main has cyclomatic complexity 45 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function PinnedAutomationCard (cyclomatic 45, cognitive 41) src/components/features/home/featured-automations/pinned-automation-card.tsx:58— PinnedAutomationCard has cyclomatic complexity 45 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SetupDialog (cyclomatic 44, cognitive 33) src/components/features/manifest/manifest-setup-dialog.tsx:101— SetupDialog has cyclomatic complexity 44 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ChatInterface (cyclomatic 42, cognitive 27) src/components/features/chat/chat-interface.tsx:88— ChatInterface has cyclomatic complexity 42 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseArgs (cyclomatic 41, cognitive 32) scripts/static-server.mjs:88— parseArgs has cyclomatic complexity 41 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function App (cyclomatic 39, cognitive 29) src/root.tsx:234— App has cyclomatic complexity 39 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function useBashCommandLogs (cyclomatic 37, cognitive 39) src/hooks/query/use-bash-command-logs.ts:142— useBashCommandLogs has cyclomatic complexity 37 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildPluginsViewModel (cyclomatic 37, cognitive 36) src/components/features/plugins/build-plugins-view-model.ts:51— buildPluginsViewModel has cyclomatic complexity 37 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function AutomationCard (cyclomatic 37, cognitive 35) src/components/features/automations/automation-card.tsx:59— AutomationCard has cyclomatic complexity 37 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConversationOverviewGitSection (cyclomatic 37, cognitive 33) src/components/features/conversation/conversation-overview-git-section.tsx:36— ConversationOverviewGitSection has cyclomatic complexity 37 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 3453 lines of code REDACTED:1— REDACTED has 3453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/agent-settings.tsx · ×1
src/routes/agent-settings.tsx: 1776 lines of code src/routes/agent-settings.tsx:1— src/routes/agent-settings.tsx has 1776 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/backends/backend-form-modal.tsx · ×1
src/components/features/backends/backend-form-modal.tsx: 1683 lines of code src/components/features/backends/backend-form-modal.tsx:1— src/components/features/backends/backend-form-modal.tsx has 1683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/contexts/conversation-websocket-context.tsx · ×1
src/contexts/conversation-websocket-context.tsx: 1482 lines of code src/contexts/conversation-websocket-context.tsx:1— src/contexts/conversation-websocket-context.tsx has 1482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/api/agent-server-adapter.ts · ×1
src/api/agent-server-adapter.ts: 1467 lines of code src/api/agent-server-adapter.ts:1— src/api/agent-server-adapter.ts has 1467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/conversation-panel/conversation-panel.tsx · ×1
src/components/features/conversation-panel/conversation-panel.tsx: 1301 lines of code src/components/features/conversation-panel/conversation-panel.tsx:1— src/components/features/conversation-panel/conversation-panel.tsx has 1301 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/api/conversation-service/agent-server-conversation-service.api.ts · ×1
src/api/conversation-service/agent-server-conversation-service.api.ts: 1200 lines of code src/api/conversation-service/agent-server-conversation-service.api.ts:1— src/api/conversation-service/agent-server-conversation-service.api.ts has 1200 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/mocks/settings-handlers.ts · ×1
src/mocks/settings-handlers.ts: 1094 lines of code src/mocks/settings-handlers.ts:1— src/mocks/settings-handlers.ts has 1094 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/api/automation-service/automation-service.api.ts · ×1
src/api/automation-service/automation-service.api.ts: 1053 lines of code src/api/automation-service/automation-service.api.ts:1— src/api/automation-service/automation-service.api.ts has 1053 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/automations-list.tsx · ×1
src/routes/automations-list.tsx: 878 lines of code src/routes/automations-list.tsx:1— src/routes/automations-list.tsx has 878 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/services/telemetry.ts: 828 lines of code src/services/telemetry.ts:1— src/services/telemetry.ts has 828 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/api/settings-service/settings-service.api.ts · ×1
src/api/settings-service/settings-service.api.ts: 821 lines of code src/api/settings-service/settings-service.api.ts:1— src/api/settings-service/settings-service.api.ts has 821 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/mcp-page/install-server-modal.tsx · ×1
src/components/features/mcp-page/install-server-modal.tsx: 817 lines of code src/components/features/mcp-page/install-server-modal.tsx:1— src/components/features/mcp-page/install-server-modal.tsx has 817 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
electron/main.mjs: 805 lines of code electron/main.mjs:1— electron/main.mjs has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/settings/sdk-settings/sdk-section-page.tsx · ×1
src/components/features/settings/sdk-settings/sdk-section-page.tsx: 751 lines of code src/components/features/settings/sdk-settings/sdk-section-page.tsx:1— src/components/features/settings/sdk-settings/sdk-section-page.tsx has 751 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/chat/chat-interface.tsx · ×1
src/components/features/chat/chat-interface.tsx: 713 lines of code src/components/features/chat/chat-interface.tsx:1— src/components/features/chat/chat-interface.tsx has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/settings/mcp-settings/mcp-server-form.tsx · ×1
src/components/features/settings/mcp-settings/mcp-server-form.tsx: 713 lines of code src/components/features/settings/mcp-settings/mcp-server-form.tsx:1— src/components/features/settings/mcp-settings/mcp-server-form.tsx has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/manifests/manifest-validation.ts · ×1
src/manifests/manifest-validation.ts: 708 lines of code src/manifests/manifest-validation.ts:1— src/manifests/manifest-validation.ts has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 699 lines of code REDACTED:1— REDACTED has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/manifests/automation-setup.ts · ×1
src/manifests/automation-setup.ts: 680 lines of code src/manifests/automation-setup.ts:1— src/manifests/automation-setup.ts has 680 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/utils/transcript-export/index.ts · ×1
src/utils/transcript-export/index.ts: 668 lines of code src/utils/transcript-export/index.ts:1— src/utils/transcript-export/index.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/manifest/manifest-setup-dialog.tsx · ×1
src/components/features/manifest/manifest-setup-dialog.tsx: 657 lines of code src/components/features/manifest/manifest-setup-dialog.tsx:1— src/components/features/manifest/manifest-setup-dialog.tsx has 657 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/conversation-panel/conversation-panel-list-helpers.ts · ×1
src/components/features/conversation-panel/conversation-panel-list-helpers.ts: 647 lines of code src/components/features/conversation-panel/conversation-panel-list-helpers.ts:1— src/components/features/conversation-panel/conversation-panel-list-helpers.ts has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/llm-settings.tsx · ×1
src/routes/llm-settings.tsx: 619 lines of code src/routes/llm-settings.tsx:1— src/routes/llm-settings.tsx has 619 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/automations/setup/automation-setup-prompt-stack.tsx · ×1
src/components/features/automations/setup/automation-setup-prompt-stack.tsx: 582 lines of code src/components/features/automations/setup/automation-setup-prompt-stack.tsx:1— src/components/features/automations/setup/automation-setup-prompt-stack.tsx has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/chat/components/chat-input-actions.tsx · ×1
src/components/features/chat/components/chat-input-actions.tsx: 561 lines of code src/components/features/chat/components/chat-input-actions.tsx:1— src/components/features/chat/components/chat-input-actions.tsx has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/settings/llm-profiles/llm-settings-local-view.tsx · ×1
src/components/features/settings/llm-profiles/llm-settings-local-view.tsx: 526 lines of code src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:1— src/components/features/settings/llm-profiles/llm-settings-local-view.tsx has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/utils/utils.ts: 521 lines of code src/utils/utils.ts:1— src/utils/utils.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/mocks/automation-handlers.ts · ×1
src/mocks/automation-handlers.ts: 518 lines of code src/mocks/automation-handlers.ts:1— src/mocks/automation-handlers.ts has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx · ×1
src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx: 512 lines of code src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:1— src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/constants/acp-providers.ts · ×1
src/constants/acp-providers.ts: 508 lines of code src/constants/acp-providers.ts:1— src/constants/acp-providers.ts has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/services/child-conversation-launch.ts · ×1
src/services/child-conversation-launch.ts: 507 lines of code src/services/child-conversation-launch.ts:1— src/services/child-conversation-launch.ts has 507 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/settings/llm-profiles/add-models-modal.tsx · ×1
src/components/features/settings/llm-profiles/add-models-modal.tsx: 498 lines of code src/components/features/settings/llm-profiles/add-models-modal.tsx:1— src/components/features/settings/llm-profiles/add-models-modal.tsx has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/automations/recommended-automations-section.tsx · ×1
src/components/features/automations/recommended-automations-section.tsx: 497 lines of code src/components/features/automations/recommended-automations-section.tsx:1— src/components/features/automations/recommended-automations-section.tsx has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/backends/managed-agents/managed-agents-view.tsx · ×1
src/components/features/backends/managed-agents/managed-agents-view.tsx: 490 lines of code src/components/features/backends/managed-agents/managed-agents-view.tsx:1— src/components/features/backends/managed-agents/managed-agents-view.tsx has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/hooks/use-tracking.ts: 457 lines of code src/hooks/use-tracking.ts:1— src/hooks/use-tracking.ts has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/mocks/conversation-handlers.ts · ×1
src/mocks/conversation-handlers.ts: 453 lines of code src/mocks/conversation-handlers.ts:1— src/mocks/conversation-handlers.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/api/mars/mars-tunnel-backend.ts · ×1
src/api/mars/mars-tunnel-backend.ts: 447 lines of code src/api/mars/mars-tunnel-backend.ts:1— src/api/mars/mars-tunnel-backend.ts has 447 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx · ×1
src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx: 439 lines of code src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx:1— src/components/features/settings/meta-llm-profiles/meta-llm-settings-view.tsx has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/utils/sdk-settings-schema.ts · ×1
src/utils/sdk-settings-schema.ts: 433 lines of code src/utils/sdk-settings-schema.ts:1— src/utils/sdk-settings-schema.ts has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage· This test file cannot be loaded · ×1
This test file cannot be loaded __tests__/scripts/desktop-icons.test.ts:25— __tests__/scripts/desktop-icons.test.ts:25 imports '../../electron/build-resources', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded __tests__/scripts/desktop-icons.test.ts:25— This repository declares test tooling, and the ✓ above records that declaration — but __tests__/scripts/desktop-icons.test.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Unlisted import '@stryker-mutator/api' stryker.config.mjs:3— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unlisted import 'unified' src/components/features/markdown/markdown-renderer.tsx:8— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unused dependency '@stryker-mutator/vitest-runner' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X14 · Bypassable address classification· IP classification is bypassable through an IPv4-in-IPv6 embedding · ×1
IP classification is bypassable through an IPv4-in-IPv6 embedding src/components/features/backends/backend-form-modal.tsx:93— This function unwraps IPv4-MAPPED IPv6 (`::ffff:`, line 96) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 decision at line 93 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this function never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same function declares non-public — and all reach the IPv6 decision un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright.
Mock-dominated test: waits for the restarted server and moves the terminal off tmux __tests__/api/mars-sandbox-setup.test.ts:38— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: leaves a ready sandbox and an explicit tool list alone __tests__/api/mars-sandbox-setup.test.ts:61— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: creates custom bundle drafts with entrypoint and setup script path __tests__/components/automations/automation-setup-panel.test.tsx:1063— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: deletes the persisted draft after a successful create __tests__/components/automations/automation-setup-panel.test.tsx:1968— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: toasts the API's message when creating an automation fails __tests__/components/automations/automation-setup-panel.test.tsx:2151— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: lands in the session's latest conversation after connecting __tests__/components/backends/managed-agents-view.test.tsx:152— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: captures backend_added with source manage_backends_modal when adding from here __tests__/components/backends/manage-backends-modal.test.tsx:656— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: captures backend_added once with manual connection metadata __tests__/components/backends/add-backend-modal.test.tsx:539— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not restore scroll geometry saved by a previous conversation __tests__/components/chat/chat-interface.test.tsx:438— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: shows an error toast when microphone access is denied __tests__/components/chat/chat-dictation-button.test.tsx:121— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: releases the microphone when unmounted during the permission prompt __tests__/components/chat/chat-dictation-button.test.tsx:180— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: calls onCodeClick and onClose when code is selected __tests__/components/features/chat/change-agent-context-menu.test.tsx:44— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: treats the launched profile as current inside a blank conversation __tests__/components/features/chat/components/chat-input-profile-picker.test.tsx:103— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: persists the choice as the default (conversationId null) in the home ACP case __tests__/components/features/chat/components/chat-input-model.test.tsx:332— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: uses the latest navigation context when a command runs __tests__/components/features/command-menu/command-menu.test.tsx:486— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: launches a conversation for the selected workspace __tests__/components/features/conversation-panel/local-new-conversation-menu.test.tsx:200— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: navigates away after the active conversation is deleted successfully even when another deletion fails __tests__/components/features/conversation-panel/conversation-panel-filters.test.tsx:657— This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not navigate away when the active conversation fails to delete __tests__/components/features/conversation-panel/conversation-panel-filters.test.tsx:712— This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: starts and ends a drag without bubbling to the surrounding list __tests__/components/features/conversation-panel/conversation-group-folder-interactions.test.tsx:324— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call onDelete when the delete button is clicked __tests__/components/features/conversation-panel/conversation-card.test.tsx:400— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call onArchive when the archive button is clicked __tests__/components/features/conversation-panel/conversation-card.test.tsx:424— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: closes the context menu when downloading the conversation fails __tests__/components/features/conversation-panel/conversation-card.test.tsx:448— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: clicking the selectedRepository should not trigger the onClick handler __tests__/components/features/conversation-panel/conversation-card.test.tsx:478— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not call onChange title __tests__/components/features/conversation-panel/conversation-card.test.tsx:553— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: clicking the title should trigger the onClick handler __tests__/components/features/conversation-panel/conversation-card.test.tsx:578— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
+ 145 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×40
Console output used as the logging channel src/api/secrets-service.ts:38— `src/api/secrets-service.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/hooks-service.ts:37— `src/api/hooks-service.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/agent-server-compatibility.ts:397— `src/api/agent-server-compatibility.ts` reports through `console.*` at line 397 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/agent-server-adapter.ts:1354— `src/api/agent-server-adapter.ts` reports through `console.*` at line 1354 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/agent-server-adapter.ts:1385— `src/api/agent-server-adapter.ts` reports through `console.*` at line 1385 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/agent-server-adapter.ts:1415— `src/api/agent-server-adapter.ts` reports through `console.*` at line 1415 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/conversation-service/agent-server-conversation-service.api.ts:791— `src/api/conversation-service/agent-server-conversation-service.api.ts` reports through `console.*` at line 791 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/conversation-service/agent-server-conversation-service.api.ts:924— `src/api/conversation-service/agent-server-conversation-service.api.ts` reports through `console.*` at line 924 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/conversation-service/agent-server-conversation-service.api.ts:1096— `src/api/conversation-service/agent-server-conversation-service.api.ts` reports through `console.*` at line 1096 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/event-service/event-service.api.ts:130— `src/api/event-service/event-service.api.ts` reports through `console.*` at line 130 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/mars/mars-sandbox-setup.ts:105— `src/api/mars/mars-sandbox-setup.ts` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/settings-service/settings-service.api.ts:612— `src/api/settings-service/settings-service.api.ts` reports through `console.*` at line 612 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/api/settings-service/settings-service.api.ts:638— `src/api/settings-service/settings-service.api.ts` reports through `console.*` at line 638 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/backends/device-flow-auth.tsx:107— `src/components/features/backends/device-flow-auth.tsx` reports through `console.*` at line 107 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/backends/device-flow-auth.tsx:172— `src/components/features/backends/device-flow-auth.tsx` reports through `console.*` at line 172 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/canvas-extensions/canvas-extensions-runtime.tsx:313— `src/components/features/canvas-extensions/canvas-extensions-runtime.tsx` reports through `console.*` at line 313 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/agent-profiles/agent-profiles-manager.tsx:44— `src/components/features/settings/agent-profiles/agent-profiles-manager.tsx` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx:262— `src/components/features/settings/agent-profiles/agent-profiles-local-view.tsx` reports through `console.*` at line 262 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:236— `src/components/features/settings/llm-profiles/llm-settings-local-view.tsx` reports through `console.*` at line 236 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/llm-profiles/llm-settings-local-view.tsx:423— `src/components/features/settings/llm-profiles/llm-settings-local-view.tsx` reports through `console.*` at line 423 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/llm-profiles/llm-profiles-manager.tsx:91— `src/components/features/settings/llm-profiles/llm-profiles-manager.tsx` reports through `console.*` at line 91 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/llm-profiles/llm-profiles-manager.tsx:130— `src/components/features/settings/llm-profiles/llm-profiles-manager.tsx` reports through `console.*` at line 130 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/components/features/settings/llm-profiles/add-models-modal.tsx:292— `src/components/features/settings/llm-profiles/add-models-modal.tsx` reports through `console.*` at line 292 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/contexts/conversation-websocket-context.tsx:599— `src/contexts/conversation-websocket-context.tsx` reports through `console.*` at line 599 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel src/contexts/conversation-websocket-context.tsx:904— `src/contexts/conversation-websocket-context.tsx` reports through `console.*` at line 904 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Duplicated predicate src/hooks/query/use-active-conversation.ts:13— `!!conversationId && conversationId.startsWith("task-")` appears character-identically in 2 files — src/hooks/query/use-active-conversation.ts, src/hooks/query/use-task-polling.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/api/agent-server-adapter.ts:746— `!!value && typeof value === "object" && !Array.isArray(value)` appears character-identically in 6 files — src/api/agent-server-adapter.ts, src/api/mcp-service/mcp-redacted-credentials.ts, src/api/settings-service/settings-service.api.ts, src/hooks/use-migrate-default-agent-profile.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:413— `!Array.isArray(options) || options.length === 0` appears character-identically in 2 files — REDACTED, src/manifests/manifest-validation.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/chat/error-message-banner.tsx:78— `!Number.isFinite(lineHeight) || lineHeight <= 0` appears character-identically in 2 files — src/components/features/chat/error-message-banner.tsx, src/utils/custom-toast-handlers.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/dev-extra-backend.mjs:31— `!Number.isInteger(parsed) || parsed <= 0` appears character-identically in 2 files — scripts/dev-extra-backend.mjs, scripts/dev-safe.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx:86— `!anchorElement || portalStyle !== undefined` appears character-identically in 2 files — src/components/features/settings/agent-profiles/agent-profile-actions-menu.tsx, src/components/features/settings/llm-profiles/profile-actions-menu.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx:165— `!container || typeof ResizeObserver === "undefined"` appears character-identically in 2 files — src/components/features/conversation-panel/conversation-card/conversation-tag-chips.tsx, src/components/features/skills/skill-card-pill-row.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/conversation-events/chat/event-message.tsx:419— `!isActionEvent(event) && !isObservationEvent(event)` appears character-identically in 2 files — src/components/conversation-events/chat/event-message.tsx, src/components/conversation-events/chat/messages.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/conversation/conversation-overview-git-items-panel.tsx:82— `!isConnected || !repository || !provider` appears character-identically in 2 files — src/components/features/conversation/conversation-overview-git-items-panel.tsx, src/components/features/conversation/conversation-overview-git-section.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/skills/extensions-mobile-hub.tsx:27— `!isNoBackend(backend) && backend.kind === "cloud"` appears character-identically in 2 files — src/components/features/skills/extensions-mobile-hub.tsx, src/components/features/skills/extensions-navigation.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/automations/setup/automation-setup-draft-service.ts:261— `!response || typeof response !== "object"` appears character-identically in 2 files — src/components/features/automations/setup/automation-setup-draft-service.ts, src/hooks/query/use-automations.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/chat/utils/chat-input.utils.ts:131— `!selection || selection.rangeCount === 0` appears character-identically in 2 files — src/components/features/chat/utils/chat-input.utils.ts, src/hooks/chat/use-slash-command.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/conversation-panel/cloud-new-conversation-menu.tsx:256— `!useFixedPlacement && cn("absolute top-full mt-0", popoverClassName)` appears character-identically in 2 files — src/components/features/conversation-panel/cloud-new-conversation-menu.tsx, src/components/features/conversation-panel/local-new-conversation-menu.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/dev-extra-backend.mjs:72— `(error && typeof error === "object" && "code" in error && error.code === "ENOENT") || /ENOENT/.test(String(error))` appears character-identically in 2 files — scripts/dev-extra-backend.mjs, scripts/dev-safe.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/skills/extensions-mobile-hub.tsx:38— `CLOUD_HIDDEN_EXTENSION_PATHS.has(item.to) && isCloudBackend` appears character-identically in 2 files — src/components/features/skills/extensions-mobile-hub.tsx, src/components/features/skills/extensions-navigation.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/chat/chat-message.tsx:108— `Number.isFinite(lineHeight) && lineHeight > 0` appears character-identically in 2 files — src/components/features/chat/chat-message.tsx, src/components/features/chat/user-message-body.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx:129— `actionAndChanges.type === useCombobox.stateChangeTypes.InputClick && state.isOpen` appears character-identically in 4 files — src/components/features/home/git-branch-dropdown/git-branch-dropdown.tsx, REDACTED, src/components/features/home/workspace-dropdown/workspace-dropdown.tsx, src/ui/dropdown/dropdown.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/hooks/query/use-paginated-conversations.ts:16— `active.backend.kind !== "cloud" || !!active.orgId` appears character-identically in 2 files — src/hooks/query/use-paginated-conversations.ts, src/hooks/query/use-user-conversation.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/api/conversation-service/agent-server-conversation-service.api.ts:1044— `active.kind === "cloud" && !conversationUrl` appears character-identically in 2 files — src/api/conversation-service/agent-server-conversation-service.api.ts, src/api/runtime-service/agent-server-runtime-service.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/backends/managed-agents/digitalocean-connect-panel.tsx:348— `agentsQuery.isFetching && "animate-spin"` appears character-identically in 2 files — src/components/features/backends/managed-agents/digitalocean-connect-panel.tsx, src/components/features/backends/managed-agents/managed-agents-view.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/automations/automation-card.tsx:81— `automation.trigger.schedule_human || automation.trigger.type` appears character-identically in 2 files — src/components/features/automations/automation-card.tsx, src/components/features/home/featured-automations/pinned-automation-card.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/hooks/mutation/use-apply-onboarding-agent-profile.ts:43— `backend.kind === "local" && !isNoBackend(backend)` appears character-identically in 4 files — src/hooks/mutation/use-apply-onboarding-agent-profile.ts, src/hooks/use-migrate-default-agent-profile.ts, src/hooks/use-migrate-enabled-skills.ts, src/hooks/use-skill-enablement.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/features/settings/llm-profiles/llm-profiles-manager.tsx:48— `backend.kind === "local" || (backend.kind === "cloud" && !!orgId)` appears character-identically in 2 files — src/components/features/settings/llm-profiles/llm-profiles-manager.tsx, src/components/features/settings/llm-profiles/llm-settings-local-view.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:265— `code !== 0 && code !== null && !shuttingDown` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/conversation-events/chat/event-content-helpers/get-observation-content.ts:253— `command === "plan" && taskList.length > 0` appears character-identically in 2 files — src/components/conversation-events/chat/event-content-helpers/get-observation-content.ts, src/components/conversation-events/chat/task-tracking/task-tracking-observation-content.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file src/hooks/use-terminal.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/chat/plan-preview.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/utils/file-language.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/api/agent-server-home.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/hooks/query/use-branch-data.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/conversation-events/chat/hooks/use-plan-preview-events.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/home/git-repo-dropdown/use-repository-data.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/hooks/chat/use-file-handling.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/utils/file-tree.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/utils/suggestions/repo-suggestions.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/controls/git-tools-submenu.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/utils/file-processing.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/controls/macros-submenu.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/conversation-events/chat/event-message-components/skill-item-expanded.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/ui/typography.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/files-tab/highlighted-source-view.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/backends/environment-switch-store.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/conversation-panel/system-message-modal/tool-item.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/components/features/home/git-branch-dropdown/branch-dropdown-menu.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Disabled test tests/e2e/bind-policy/loopback-bind.spec.ts:142— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/canvas-extensions/app-backend-sandbox.spec.ts:103— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/conversation-markdown-render-performance.spec.ts:224— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/conversation-markdown-render-performance.spec.ts:228— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/live/real-agent-server-conversation.spec.ts:97— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/live/real-agent-server-conversation.spec.ts:146— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/backends/mock-llm-cross-connect.spec.ts:349— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/backends/mock-llm-cross-connect.spec.ts:470— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/backends/mock-llm-cross-connect.spec.ts:673— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/backends/mock-llm-partial-stack.spec.ts:191— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/backends/mock-llm-partial-stack.spec.ts:357— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/backends/mock-llm-partial-stack.spec.ts:398— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/conversations/mock-llm-conversation.spec.ts:410— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/files/mock-llm-files-and-git.spec.ts:196— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/files/mock-llm-files-and-git.spec.ts:250— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/files/mock-llm-files-and-git.spec.ts:293— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/settings/mock-llm-acp-agent.spec.ts:336— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/mock-llm/settings/mock-llm-acp-auth-banner.spec.ts:172— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Silent fallback default in catch scripts/mars-tunnel-bridge.mjs:94— `readMarsDefaults` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:198— `requestHostname` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/backend-registry/health-storage.ts:56— `readStoredHealth` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/backend-registry/storage.ts:146— `readStoredBackends` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/conversation-metadata-store.ts:75— `readAll` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/automation-setup-handoff-store.ts:23— `readHandoffs` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/automation-setup-plugins.ts:48— `parseAutomationSetupPluginList` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/backend-registry/last-conversation-store.ts:31— `readMap` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/plugins-service.ts:86— `getPluginsMarketplace` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/plugins-service.ts:114— `getLocalPlugins` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/api/plugins-management-service.ts:85— `listInstalledPlugins` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/components/providers/telemetry-provider.tsx:118— `getConsumedNonceMap` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/hooks/use-responder-url-secret.ts:47— `useResponderUrlSecret` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/utils/remembered-acp-models.ts:31— `parseLists` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/utils/websocket-url.ts:43— `extractPathPrefix` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch tests/e2e/live/scripts/extract-live-e2e-media.mjs:132— `resolveExistingMediaPath` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
README/code drift docs/ACP_AGENTS.md:97— docs/ACP_AGENTS.md documents the environment variable `CLAUDE_CONFIG_DIR`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/DefenseClaw.md:130— docs/DefenseClaw.md documents the environment variable `OH_LLM__BASE_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/api/README.md:96— src/api/README.md names `feature-service.api.ts`, but no file or folder `feature-service.api.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/api/README.md:97— src/api/README.md names `feature.types.ts`, but no file or folder `feature.types.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/api/README.md:97— src/api/README.md names `secrets.types.ts`, but no file or folder `secrets.types.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/e2e/live-acp/README.md:34— tests/e2e/live-acp/README.md runs `docker rm -f oh-acp`, but `oh-acp` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Deprecated: boolean REDACTED:9983— boolean 3.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:13228— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:13963— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:18742— rimraf 2.6.3 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Unused export 'default' src/components/features/controls/agent-status.tsx:191— Nothing imports this binding — it is safe to review for removal.
Unused export 'default' src/components/features/controls/server-status.tsx:65— Nothing imports this binding — it is safe to review for removal.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 628 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Fat interface: MarsBridge (18 required operations) src/api/mars/mars-tunnel-backend.ts:158— `MarsBridge` declares 18 required operations: `getAuthState`, `signInWithOAuth`, `savePat`, `setActiveConnection`, `signOut`, `listSessions`, `listAgentConfigs`, `listConfigSessions`, `listSandboxSizes`, `createOpenHandsAgent`, `createSession`, `pauseSession`, `resumeSession`, `destroySession`, `deleteAgentConfig`, `openTunnel`, `closeTunnel`, `getTunnel`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: src/components/features/plugins/build-plugins-view-model.ts, src/api/plugins-service.ts, src/api/plugins-management-service.ts, src/utils/responder-deployment.ts, src/utils/mcp-credential-validation.ts, src/hooks/use-pinned-home-route.ts, src/components/features/home/featured-automations/build-home-automation-menu-items.tsx, src/hooks/query/use-manifest-prerequisites.ts (+2 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 7 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (21 single-owned of 653 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 653 of the 1360 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) (+1 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/components/providers/telemetry-provider.tsx, src/utils/automation-disabled-reason.ts, src/components/features/markdown/syntax-highlighter.ts, src/components/features/markdown/remark-github-alerts.ts, src/components/features/conversation-panel/conversation-group-folder-list.tsx, src/components/features/markdown/markdown-table-scroll.tsx, src/api/llm-subscription-service.ts, src/api/mcp-service/mcp-redacted-credentials.ts (+3 more).
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (164218 LoC, 1940 module-visible types across 144 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 19 of 653 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 653 of the 1360 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/hooks/use-terminal.ts, src/components/features/chat/plan-preview.tsx, src/utils/file-language.ts, src/hooks/query/use-branch-data.ts, src/components/conversation-events/chat/hooks/use-plan-preview-events.ts, src/components/features/home/git-repo-dropdown/use-repository-data.tsx, src/hooks/chat/use-file-handling.ts, src/utils/file-tree.ts (and 11 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 124832 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
R7 · Dead Code· Unused export 'TUNNEL_PING_INTERVAL_MS' · ×1
Unused export 'TUNNEL_PING_INTERVAL_MS' scripts/tunnel-client.mjs:50— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CONVERSATION_TAG_VALUE_MAX_LENGTH' · ×1
Unused export 'CONVERSATION_TAG_VALUE_MAX_LENGTH' src/components/features/conversation-panel/edit-conversation-tags-modal.tsx:20— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CONTEXT_FILL_DANGER_PERCENT' · ×1
Unused export 'CONTEXT_FILL_DANGER_PERCENT' src/components/features/conversation/usage-panel/context-meter.tsx:9— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'BranchDropdownMenuProps' · ×1
Unused export 'BranchDropdownMenuProps' src/components/features/home/git-branch-dropdown/branch-dropdown-menu.tsx:10— Nothing imports this binding — it is safe to review for removal.
Unused export 'planHeadings' src/components/features/markdown/plan-components.tsx:152— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'ComboboxCaretButton' · ×1
Unused export 'ComboboxCaretButton' src/ui/combobox-caret.tsx:41— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CronScheduleValidation' · ×1
Unused export 'CronScheduleValidation' src/utils/automation-schedule.ts:81— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'createAxiosNotFoundErrorObject' · ×1
Unused export 'createAxiosNotFoundErrorObject' test-utils.tsx:101— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'createAxiosError' · ×1
Unused export 'createAxiosError' test-utils.tsx:117— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'DEFAULT_VITE_PORT' · ×1
Unused module-local declaration 'DEFAULT_VITE_PORT' scripts/dev-safe.mjs:47— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 5/22 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) reduce the strict null checking score — ~0.3 `!` null assertions per 1k TypeScript source lines — 56 assertion(s) across the 162678 source line(s) of the 1322 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/components/conversation-events/chat/event-message-components/critic-result-display.tsx (5), REDACTED (4), src/hooks/query/use-repository-git-items.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Subsumed condition operand src/components/features/settings/sdk-settings/schema-field.tsx:43— `field.key.endsWith("_url")` can never decide this `||` — every value satisfying `field.key.endsWith("_url")` also satisfies `field.key.endsWith("url")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Outdated (npm): @heroui/react — @heroui/react is pinned at 2.8.10; registry.npmjs.org publishes 3.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @microlink/react-json-view — @microlink/react-json-view is pinned at 1.31.25; registry.npmjs.org publishes 1.31.41 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-router/node — @react-router/node is pinned at 7.18.2; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-router/serve — @react-router/serve is pinned at 7.18.2; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tanstack/react-query — @tanstack/react-query is pinned at 5.103.1; registry.npmjs.org publishes 5.104.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): axios — axios is pinned at 1.18.0; registry.npmjs.org publishes 1.20.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): driver.js — driver.js is pinned at 1.3.6; registry.npmjs.org publishes 1.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): framer-motion — framer-motion is pinned at 12.38.0; registry.npmjs.org publishes 14.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next — i18next is pinned at 26.4.2; registry.npmjs.org publishes 26.5.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next-http-backend — i18next-http-backend is pinned at 4.0.2; registry.npmjs.org publishes 4.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): isbot — isbot is pinned at 5.2.1; registry.npmjs.org publishes 5.2.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): lucide-react — lucide-react is pinned at 1.25.0; registry.npmjs.org publishes 1.61.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): mdast-util-from-markdown — mdast-util-from-markdown is pinned at 2.0.3; registry.npmjs.org publishes 2.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): monaco-editor — monaco-editor is pinned at 0.56.0; registry.npmjs.org publishes 0.57.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): posthog-js — posthog-js is pinned at 1.415.0; registry.npmjs.org publishes 1.438.13 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react — react is pinned at 19.3.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-dom — react-dom is pinned at 19.3.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-hot-toast — react-hot-toast is pinned at 2.6.0; registry.npmjs.org publishes 2.6.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-i18next — react-i18next is pinned at 17.0.14; registry.npmjs.org publishes 17.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-icons — react-icons is pinned at 5.6.0; registry.npmjs.org publishes 5.7.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-router — react-router is pinned at 7.18.2; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-syntax-highlighter — react-syntax-highlighter is pinned at 16.1.1; registry.npmjs.org publishes 16.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): shell-quote — shell-quote is pinned at 1.9.0; registry.npmjs.org publishes 1.12.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): uuid — uuid is pinned at 14.0.1; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): vite — vite is pinned at 8.0.16; registry.npmjs.org publishes 8.3.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): should render suggestions if empty __tests__/components/chat/chat-interface.test.tsx:291— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should reflect external value changes __tests__/components/ui/dropdown.test.tsx:384— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should call onChange when selection changes __tests__/components/ui/dropdown.test.tsx:385— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should not update internal state when controlled __tests__/components/ui/dropdown.test.tsx:386— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should manage selection state internally __tests__/components/ui/dropdown.test.tsx:390— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should call onChange when selection changes __tests__/components/ui/dropdown.test.tsx:391— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should support defaultValue prop __tests__/components/ui/dropdown.test.tsx:392— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): (unnamed test) __tests__/scripts/dev-with-automation.test.ts:1063— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) __tests__/scripts/dev-with-automation.test.ts:1275— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) __tests__/scripts/dev-with-automation.test.ts:1305— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) __tests__/scripts/dev-safe.test.ts:1115— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) __tests__/scripts/dev-extra-backend.test.ts:97— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `react-router.config.ts`, `src/api/automation-form-session.ts`, `src/components/features/chat/custom-chat-input.tsx`, `src/components/features/conversation-panel/conversation-panel-list-helpers.ts`, `src/components/features/manifest/manifest-icons.ts`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
Run 01a15ee3-ccdd-73a9-962e-c039f9a58a6d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 138 · Warnings: 2098 · Recommendations: 332 · Info: 39 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 14:35 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.