Public report of BloopAI/vibe-kanban, published 26 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, 26 October 2026, 02:36 UTC · Survey ID cd_6b1df411aa804381970da7b046ed8dcf
BloopAI/vibe-kanban
Measured 26 October 2026, 02:32 UTC, at code version d5cbb53
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 2 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: 197,723 lines of product code in 39 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Production Readiness, 25
Findings by how serious they are
205 critical1214 serious437 minor
11 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
26 October 2026, 02:32 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 ▸
95of 95 dimensions measured by tools.
1770of 1856 findings point to an exact file and line, so you can open each one in the code. The other 86 concern the repository as a whole, such as missing documentation.
95dimensions across 8 lenses, read from 197,723 lines of product code in 39 projects.
BloopAI/vibe-kanban is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because three passwords or keys sit in the current code. It scores 41 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 25, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 14 points. Documenting the recovery plan comes next, worth about 4 points. Raising Production Readiness to 62 would lift the score to about 55.
Fifty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-two known security holes in the packages the code depends on can be used by attackers, and fifteen secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Passing outside input through environment variables would fix the eight pipeline steps that put outside input straight into a shell command, and the nine places where the code runs text as code or as a command need a direct call instead. The 29 controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 197,723 lines, about €170,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.
If Production Readiness rose from 25 to 62, the lowest score rated Strong, the score would rise from 41 to about 55.
Code composition: what the lines of code are
Product code 99%Tests 1%
New since the last survey: 105 findings
These 105 critical or serious findings weren't in the previous survey, on 12 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: 922 findings
These 922 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
€57,000 to €280,000, for 943 to 2,991 hours of work, about 1.2 person-years for 1 to 3 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 41. 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: 197,723 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
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 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3).
Raises the score by about 14 points · Low effort · Secret Scanning
2
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Raises the score by about 4 points · Medium effort · DR & Backup
3
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €170,000 to build again, about 1.2 person-years of work. Its weakest lens is Production Readiness, at 25 (Critical). 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 3 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 14 points for low effort, because it clears the 3 Secret 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 6.9 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 6,442 lines over the last 90 days, which is about 26,126 lines a year. At that pace, the extra work comes to an estimated 1.8 to 10.5 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, never less than 2% to 5% and never more than 40% to 60% in all; 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 · Code Duplication · 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 — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
919 modules, with 994 dependencies between them. 6 loops run through 22 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 879 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.
deployment uses executors.executors.opencode.types, so a change to executors.executors.opencode.types can break deployment, while a change to deployment can't break executors.executors.opencode.types.
Position
Below the diagonal: deployment uses a module listed above it, which is the healthy direction.
deployment uses relay_control.signing, so a change to relay_control.signing can break deployment, while a change to deployment can't break relay_control.signing.
Position
Below the diagonal: deployment uses a module listed above it, which is the healthy direction.
executors.env uses executors.command, so a change to executors.command can break executors.env, while a change to executors.env can't break executors.command.
Position
Below the diagonal: executors.env uses a module listed above it, which is the healthy direction.
executors.logs.utils.entry_index uses utils.msg_store, so a change to utils.msg_store can break executors.logs.utils.entry_index, while a change to executors.logs.utils.entry_index can't break utils.msg_store.
Position
Below the diagonal: executors.logs.utils.entry_index uses a module listed above it, which is the healthy direction.
19→27 executors.profile uses executors.executorspart of a loop✕
Connections
2 pairs of types, where a type in executors.profile uses a type in executors.executors.
executors.profile uses executors.executors, so a change to executors.executors can break executors.profile, while a change to executors.profile can't break executors.executors.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.web-core.src.features.workspace-chat.model uses shared.types, so a change to shared.types can break packages.web-core.src.features.workspace-chat.model, while a change to packages.web-core.src.features.workspace-chat.model can't break shared.types.
Position
Below the diagonal: packages.web-core.src.features.workspace-chat.model uses a module listed above it, which is the healthy direction.
packages.web-core.src.pages.workspaces uses packages.web-core.src.shared.types.actions, so a change to packages.web-core.src.shared.types.actions can break packages.web-core.src.pages.workspaces, while a change to packages.web-core.src.pages.workspaces can't break packages.web-core.src.shared.types.actions.
Position
Below the diagonal: packages.web-core.src.pages.workspaces uses a module listed above it, which is the healthy direction.
packages.web-core.src.shared.hooks uses packages.web-core.src.shared.types.actions, so a change to packages.web-core.src.shared.types.actions can break packages.web-core.src.shared.hooks, while a change to packages.web-core.src.shared.hooks can't break packages.web-core.src.shared.types.actions.
Position
Below the diagonal: packages.web-core.src.shared.hooks uses a module listed above it, which is the healthy direction.
packages.web-core.src.shared.hooks uses shared.types, so a change to shared.types can break packages.web-core.src.shared.hooks, while a change to packages.web-core.src.shared.hooks can't break shared.types.
Position
Below the diagonal: packages.web-core.src.shared.hooks uses a module listed above it, which is the healthy direction.
packages.web-core.src.shared.lib uses shared.types, so a change to shared.types can break packages.web-core.src.shared.lib, while a change to packages.web-core.src.shared.lib can't break shared.types.
Position
Below the diagonal: packages.web-core.src.shared.lib uses a module listed above it, which is the healthy direction.
server.middleware.signed_ws uses relay_control.signing, so a change to relay_control.signing can break server.middleware.signed_ws, while a change to server.middleware.signed_ws can't break relay_control.signing.
Position
Below the diagonal: server.middleware.signed_ws uses a module listed above it, which is the healthy direction.
services.services.config.editor uses executors.command, so a change to executors.command can break services.services.config.editor, while a change to services.services.config.editor can't break executors.command.
Position
Below the diagonal: services.services.config.editor uses a module listed above it, which is the healthy direction.
executors.actions uses executors.env, so a change to executors.env can break executors.actions, while a change to executors.actions can't break executors.env.
Position
Below the diagonal: executors.actions uses a module listed above it, which is the healthy direction.
executors.executors uses utils.msg_store, so a change to utils.msg_store can break executors.executors, while a change to executors.executors can't break utils.msg_store.
Position
Below the diagonal: executors.executors uses a module listed above it, which is the healthy direction.
executors.executors uses executors.env, so a change to executors.env can break executors.executors, while a change to executors.executors can't break executors.env.
Position
Below the diagonal: executors.executors uses a module listed above it, which is the healthy direction.
executors.executors uses executors.profile, so a change to executors.profile can break executors.executors, while a change to executors.executors can't break executors.profile.
Position
Below the diagonal: executors.executors uses a module listed above it, which is the healthy direction.
executors.executors.codex.client uses executors.env, so a change to executors.env can break executors.executors.codex.client, while a change to executors.executors.codex.client can't break executors.env.
Position
Below the diagonal: executors.executors.codex.client uses a module listed above it, which is the healthy direction.
services.services.config.versions.v1 uses executors.profile, so a change to executors.profile can break services.services.config.versions.v1, while a change to services.services.config.versions.v1 can't break executors.profile.
Position
Below the diagonal: services.services.config.versions.v1 uses a module listed above it, which is the healthy direction.
services.services.config.versions.v1 uses services.services.config.editor, so a change to services.services.config.editor can break services.services.config.versions.v1, while a change to services.services.config.versions.v1 can't break services.services.config.editor.
Position
Below the diagonal: services.services.config.versions.v1 uses a module listed above it, which is the healthy direction.
db.models.execution_process uses api_types.workspace, so a change to api_types.workspace can break db.models.execution_process, while a change to db.models.execution_process can't break api_types.workspace.
Position
Below the diagonal: db.models.execution_process uses a module listed above it, which is the healthy direction.
db.models.execution_process uses executors.actions, so a change to executors.actions can break db.models.execution_process, while a change to db.models.execution_process can't break executors.actions.
Position
Below the diagonal: db.models.execution_process uses a module listed above it, which is the healthy direction.
executors.executors.codex uses executors.command, so a change to executors.command can break executors.executors.codex, while a change to executors.executors.codex can't break executors.command.
Position
Below the diagonal: executors.executors.codex uses a module listed above it, which is the healthy direction.
executors.executors.codex uses utils.msg_store, so a change to utils.msg_store can break executors.executors.codex, while a change to executors.executors.codex can't break utils.msg_store.
Position
Below the diagonal: executors.executors.codex uses a module listed above it, which is the healthy direction.
executors.executors.codex uses executors.env, so a change to executors.env can break executors.executors.codex, while a change to executors.executors.codex can't break executors.env.
Position
Below the diagonal: executors.executors.codex uses a module listed above it, which is the healthy direction.
executors.executors.codex uses executors.profile, so a change to executors.profile can break executors.executors.codex, while a change to executors.executors.codex can't break executors.profile.
Position
Below the diagonal: executors.executors.codex uses a module listed above it, which is the healthy direction.
executors.executors.codex uses executors.executors, so a change to executors.executors can break executors.executors.codex, while a change to executors.executors.codex can't break executors.executors.
Position
Below the diagonal: executors.executors.codex uses a module listed above it, which is the healthy direction.
executors.executors.codex uses executors.executors.codex.client, so a change to executors.executors.codex.client can break executors.executors.codex, while a change to executors.executors.codex can't break executors.executors.codex.client.
Position
Below the diagonal: executors.executors.codex uses a module listed above it, which is the healthy direction.
executors.executors.opencode.sdk uses executors.executors.opencode.types, so a change to executors.executors.opencode.types can break executors.executors.opencode.sdk, while a change to executors.executors.opencode.sdk can't break executors.executors.opencode.types.
Position
Below the diagonal: executors.executors.opencode.sdk uses a module listed above it, which is the healthy direction.
executors.executors.opencode.sdk uses executors.env, so a change to executors.env can break executors.executors.opencode.sdk, while a change to executors.executors.opencode.sdk can't break executors.env.
Position
Below the diagonal: executors.executors.opencode.sdk uses a module listed above it, which is the healthy direction.
executors.executors.opencode.sdk uses executors.executors, so a change to executors.executors can break executors.executors.opencode.sdk, while a change to executors.executors.opencode.sdk can't break executors.executors.
Position
Below the diagonal: executors.executors.opencode.sdk uses a module listed above it, which is the healthy direction.
executors.executors.opencode.sdk uses executors.executors.codex.client, so a change to executors.executors.codex.client can break executors.executors.opencode.sdk, while a change to executors.executors.opencode.sdk can't break executors.executors.codex.client.
Position
Below the diagonal: executors.executors.opencode.sdk uses a module listed above it, which is the healthy direction.
executors.executors.claude uses executors.command, so a change to executors.command can break executors.executors.claude, while a change to executors.executors.claude can't break executors.command.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.claude uses utils.msg_store, so a change to utils.msg_store can break executors.executors.claude, while a change to executors.executors.claude can't break utils.msg_store.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.claude uses executors.env, so a change to executors.env can break executors.executors.claude, while a change to executors.executors.claude can't break executors.env.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.claude uses executors.logs.utils.entry_index, so a change to executors.logs.utils.entry_index can break executors.executors.claude, while a change to executors.executors.claude can't break executors.logs.utils.entry_index.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.claude uses executors.profile, so a change to executors.profile can break executors.executors.claude, while a change to executors.executors.claude can't break executors.profile.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.claude uses executors.executors, so a change to executors.executors can break executors.executors.claude, while a change to executors.executors.claude can't break executors.executors.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.claude uses executors.executors.opencode.sdk, so a change to executors.executors.opencode.sdk can break executors.executors.claude, while a change to executors.executors.claude can't break executors.executors.opencode.sdk.
Position
Below the diagonal: executors.executors.claude uses a module listed above it, which is the healthy direction.
executors.executors.codex.normalize_logs uses utils.msg_store, so a change to utils.msg_store can break executors.executors.codex.normalize_logs, while a change to executors.executors.codex.normalize_logs can't break utils.msg_store.
Position
Below the diagonal: executors.executors.codex.normalize_logs uses a module listed above it, which is the healthy direction.
executors.executors.codex.normalize_logs uses executors.logs.utils.entry_index, so a change to executors.logs.utils.entry_index can break executors.executors.codex.normalize_logs, while a change to executors.executors.codex.normalize_logs can't break executors.logs.utils.entry_index.
Position
Below the diagonal: executors.executors.codex.normalize_logs uses a module listed above it, which is the healthy direction.
executors.executors.codex.normalize_logs uses executors.executors.codex, so a change to executors.executors.codex can break executors.executors.codex.normalize_logs, while a change to executors.executors.codex.normalize_logs can't break executors.executors.codex.
Position
Below the diagonal: executors.executors.codex.normalize_logs uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses executors.command, so a change to executors.command can break executors.executors.opencode, while a change to executors.executors.opencode can't break executors.command.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses utils.msg_store, so a change to utils.msg_store can break executors.executors.opencode, while a change to executors.executors.opencode can't break utils.msg_store.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses executors.env, so a change to executors.env can break executors.executors.opencode, while a change to executors.executors.opencode can't break executors.env.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses executors.profile, so a change to executors.profile can break executors.executors.opencode, while a change to executors.executors.opencode can't break executors.profile.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses executors.executors, so a change to executors.executors can break executors.executors.opencode, while a change to executors.executors.opencode can't break executors.executors.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses executors.executors.codex.client, so a change to executors.executors.codex.client can break executors.executors.opencode, while a change to executors.executors.opencode can't break executors.executors.codex.client.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
executors.executors.opencode uses executors.executors.opencode.sdk, so a change to executors.executors.opencode.sdk can break executors.executors.opencode, while a change to executors.executors.opencode can't break executors.executors.opencode.sdk.
Position
Below the diagonal: executors.executors.opencode uses a module listed above it, which is the healthy direction.
services.services.container uses api_types.workspace, so a change to api_types.workspace can break services.services.container, while a change to services.services.container can't break api_types.workspace.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.container uses db, so a change to db can break services.services.container, while a change to services.services.container can't break db.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.container uses git, so a change to git can break services.services.container, while a change to services.services.container can't break git.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.container uses utils.msg_store, so a change to utils.msg_store can break services.services.container, while a change to services.services.container can't break utils.msg_store.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.container uses executors.profile, so a change to executors.profile can break services.services.container, while a change to services.services.container can't break executors.profile.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.container uses executors.actions, so a change to executors.actions can break services.services.container, while a change to services.services.container can't break executors.actions.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.container uses db.models.execution_process, so a change to db.models.execution_process can break services.services.container, while a change to services.services.container can't break db.models.execution_process.
Position
Below the diagonal: services.services.container uses a module listed above it, which is the healthy direction.
services.services.remote_client uses executors.executors.codex.normalize_logs, so a change to executors.executors.codex.normalize_logs can break services.services.remote_client, while a change to services.services.remote_client can't break executors.executors.codex.normalize_logs.
Position
Below the diagonal: services.services.remote_client uses a module listed above it, which is the healthy direction.
local_deployment.container uses api_types.workspace, so a change to api_types.workspace can break local_deployment.container, while a change to local_deployment.container can't break api_types.workspace.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses db, so a change to db can break local_deployment.container, while a change to local_deployment.container can't break db.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses executors.executors.opencode.types, so a change to executors.executors.opencode.types can break local_deployment.container, while a change to local_deployment.container can't break executors.executors.opencode.types.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses git, so a change to git can break local_deployment.container, while a change to local_deployment.container can't break git.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses executors.actions, so a change to executors.actions can break local_deployment.container, while a change to local_deployment.container can't break executors.actions.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses db.models.execution_process, so a change to db.models.execution_process can break local_deployment.container, while a change to local_deployment.container can't break db.models.execution_process.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses services.services.container, so a change to services.services.container can break local_deployment.container, while a change to local_deployment.container can't break services.services.container.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
local_deployment.container uses services.services.remote_client, so a change to services.services.remote_client can break local_deployment.container, while a change to local_deployment.container can't break services.services.remote_client.
Position
Below the diagonal: local_deployment.container uses a module listed above it, which is the healthy direction.
relay_hosts uses relay_control.signing, so a change to relay_control.signing can break relay_hosts, while a change to relay_hosts can't break relay_control.signing.
Position
Below the diagonal: relay_hosts uses a module listed above it, which is the healthy direction.
relay_hosts uses services.services.remote_client, so a change to services.services.remote_client can break relay_hosts, while a change to relay_hosts can't break services.services.remote_client.
Position
Below the diagonal: relay_hosts uses a module listed above it, which is the healthy direction.
local_deployment uses executors.executors.opencode.types, so a change to executors.executors.opencode.types can break local_deployment, while a change to local_deployment can't break executors.executors.opencode.types.
Position
Below the diagonal: local_deployment uses a module listed above it, which is the healthy direction.
local_deployment uses relay_control.signing, so a change to relay_control.signing can break local_deployment, while a change to local_deployment can't break relay_control.signing.
Position
Below the diagonal: local_deployment uses a module listed above it, which is the healthy direction.
local_deployment uses local_deployment.container, so a change to local_deployment.container can break local_deployment, while a change to local_deployment can't break local_deployment.container.
Position
Below the diagonal: local_deployment uses a module listed above it, which is the healthy direction.
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
113
High / Critical
A03:2025 — Software Supply Chain Failures
81
High / Critical
A02:2025 — Security Misconfiguration
12
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Immediately resolve the three leaked secrets in REDACTED and codify disaster recovery by documenting RTO/RPO and restore procedures in infrastructure as code. Clean up the dependency tree by removing unused packages and explicitly declaring imports, then significantly improve test coverage by adding tests for currently unreached production modules. Finally, enhance accessibility by making custom controls keyboard-operable and ensuring anchors have valid hrefs.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3).
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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 — 205
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 — 1214
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 — 437
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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. 95 of 95 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. 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 — 95 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, 1770 of 1856 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.
D8 Code Coverage — 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. Coverage NOT MEASURED: test source is present (.rs, .ts) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D10 Test Quality — 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. The 6 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 6 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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 source is present (.rs, .ts) and this repository declares a Cargo test suite (repository root, 53 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — 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.
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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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. `packages/web-core/src/features/workspace-chat/model/conversation-row-model.ts`, `packages/web-core/src/features/workspace-chat/model/deriveConversationEntries.ts`, `packages/web-core/src/features/workspace-chat/model/deriveConversationSemanticTimeline.ts`, `packages/web-core/src/shared/actions/index.ts`, `packages/web-core/src/shared/dialogs/command-bar/commandBar/useResolvedPage.ts` 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.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AC2 Forms & labels — 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
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. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.remote-server.environment.VIBEKANBAN_REMOTE_JWT_SECRET: required variable VIBEKANBAN_REMOTE_JWT_SECRET is missing a value: set in .env.remote; runtime evidence skipped.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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. 241 further occurrence(s) are not listed individually; the score already reflects all 281.
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. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
R4 Test Coverage — 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. 636 further occurrence(s) are not listed individually; the score already reflects all 676.
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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
X4 Structured logging — 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. 492 further occurrence(s) are not listed individually; the score already reflects all 532.
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.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
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 Secret Scanning: Secret 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
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.
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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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.
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.
171 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was KanbanIssuePanelContainer.KanbanIssuePanelContainer at 121. A further 9 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 ApiError::into_response at 53 — they are counted neither in the figure above nor in this dimension's score. 3 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: crates/executors/src/executors/opencode/types.rs (SdkEvent::parse at 20), packages/web-core/src/shared/components/IdeIcon.tsx (IdeIcon.IdeIcon at 16), packages/web-core/src/shared/providers/remote/ProjectProvider.tsx (ProjectProvider.ProjectProvider at 16). 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.
+ 143 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 20 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with KanbanIssuePanelContainer.KanbanIssuePanelContainer (cyclomatic 121), RemoteProjectsSettingsSection.RemoteProjectsSettingsSection (cyclomatic 107), executors::executors::codex::normalize_logs::normalize_logs (cyclomatic 101). — 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 20 together lifts Cyclomatic Complexity from 5.0 to about 6.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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.
+ 166 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 120 down to 120 or less in Cognitive Complexity — start with ClaudeLogProcessor::normalize_entries (cognitive 234), executors::executors::codex::normalize_logs::normalize_logs (cognitive 230), executors::executors::droid::normalize_logs::normalize_logs (cognitive 173). — 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 6 together lifts Cognitive Complexity from 3.2 to about 4.4/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.9 / 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 148 FunctionTooLong finding(s) in God Classes — start with normalize_logs.rs (7), pr.rs (3), RemoteProjectsSettingsSection.tsx (2). — One of this dimension's main actionable groups (148 warning-level).
Resolve the 45 FileTooLong finding(s) in God Classes — start with normalize_logs.rs (4), lib.rs (3), container.rs (2). — One of this dimension's main actionable groups (45 warning-level).
Resolve the 23 ClassTooLong finding(s) in God Classes — start with container.rs (2), lib.rs, claude.rs. — One of this dimension's main actionable groups (23 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.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
213 duplicated block group(s) detected. A further 15 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .tsx, .ts (51% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 83 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with auth.rs (2), notifications.rs (2), project_statuses.rs (2). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 14 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with sdk.rs, cli.rs, issue_comment_reactions.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with sftp.rs, mod.rs, auth.rs. — One of this dimension's main actionable groups (13 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.0 / 10Strong✓ 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.
39 production modules (Cargo+npm), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 12 module(s) off the main sequence, with abstractness counted on 38 of the 39 (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).
Off the main sequence: api-types · ×12
Unstable project deployment
Unstable project local-deployment
What to do
Resolve the 12 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 1 Unstable project deployment finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project local-deployment finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
D9 · Test Distribution10.0 / 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.
272 test methods: 222 unit, 50 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 6 `it`/`test` case(s) across 1 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 266 `#[test]` function(s) across 53 file(s) declaring at least one; its unit/integration split is Cargo's own — 3 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6 tests. Measured on the JavaScript/TypeScript suite only — at least 6 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
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.
47 outdated, 0 yanked direct Cargo dependencies. 122 of 139 direct crates were graded against crates.io (0 not published there, 17 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×47
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Enforce Secret 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 1091 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 16 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
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.
32 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/web-core/src/features/kanban/ui/KanbanContainer.tsx. Counted over 660 of the 1115 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 · ×3
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.
8 deducted task-comment markers across 193820 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 7 TodoComment finding(s) in Explicit Debt — start with WorkspaceProvider.tsx, utils.ts, config.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with filesystem_watcher.rs. — One of this dimension's main actionable groups (1 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: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 79 document(s) read across 1 unit(s).
✓ 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 domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
2 domain type(s) cross context boundaries across 4 contexts.
Cross-context type AppBarHostStatus (ui → web-core)packages/web-core/src/shared/hooks/useRemoteCloudHosts.ts:9
Cross-context type RepoAction (ui → web-core)packages/web-core/src/shared/stores/useUiPreferencesStore.ts:848
What to do
Resolve the 1 Cross-context type AppBarHostStatus (ui → web-core) finding(s) in Boundary Type-Coupling — start with useRemoteCloudHosts.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Cross-context type RepoAction (ui → web-core) finding(s) in Boundary Type-Coupling — start with useUiPreferencesStore.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
6 of 38 build units (Cargo, 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: Secret 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.
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).
113 finding(s): 0 critical, 90 high, 23 medium, 0 low. 47 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 5 file(s) — `packages/web-core/src/features/workspace-chat/model/conversation-row-model.ts` (line 224), `packages/web-core/src/features/workspace-chat/model/deriveConversationEntries.ts` (lines 25–26), `packages/web-core/src/features/workspace-chat/model/deriveConversationSemanticTimeline.ts` (line 125), `packages/web-core/src/shared/actions/index.ts` (line 413, line 441, line 455, …), `packages/web-core/src/shared/dialogs/command-bar/commandBar/useResolvedPage.ts` (line 38) — 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 6 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) charged to Static Analysis (SAST) — the other 47 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (51 issue-level, 4 of them charged here).
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
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.
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED (5), REDACTED. — One of this dimension's main actionable groups (17 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 10 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED (2). — One of this dimension's main actionable groups (10 warning-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.
278 of 660 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/relay-webrtc/src/client.rs. Counted over 660 of the 1115 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 273 Orphaned file finding(s) in Knowledge Freshness — start with streams.rs (2), export.rs (2), proxy.rs (2). — One of this dimension's main actionable groups (273 recommendation-level).
Resolve the 5 Orphaned knowledge finding(s) in Knowledge Freshness — start with lib.rs (2), client.rs, provider.rs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
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 3 Change coupling finding(s) in Change Coupling — start with CreateModeProvider.tsx, scratch.rs, useCreateModeState.ts. — One of this dimension's main actionable groups (3 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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. — 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 the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_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 & labels5.1 / 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). (×10) — packages/remote-web/src/app/layout/RemoteAppShell.tsx:305, packages/ui/src/components/ColorPicker.tsx:68, packages/ui/src/components/GuideDialogShell.tsx:78, …
This <span> 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. — packages/ui/src/components/CollapsibleSectionHeader.tsx:100
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. (×10) — packages/ui/src/components/CreateRepoDialog.tsx:94, packages/ui/src/components/CreateRepoDialog.tsx:109, packages/web-core/src/features/export/ui/ExportChooseProjects.tsx:89, …
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. (×9) — packages/ui/src/components/CreateRepoDialog.tsx:97, packages/ui/src/components/CreateRepoDialog.tsx:113, packages/ui/src/components/InputField.tsx:110, …
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. (×2) — packages/ui/src/components/GuideDialogShell.tsx:37, packages/ui/src/components/KeyboardDialog.tsx:138
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — packages/web-core/src/features/export/ui/ExportChooseProjects.tsx:90, packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:344, packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:591, …
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — packages/web-core/src/pages/workspaces/GitHubCommentRenderer.tsx:43
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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. — packages/web-core/src/shared/components/org/MemberListItem.tsx:78
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name 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) — packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:235, packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:267
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.
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.
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> 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. (×2) — packages/ui/src/components/AppBar.tsx:512, packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:385
This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. (×8) — packages/ui/src/components/ChatAggregatedToolEntries.tsx:46, packages/ui/src/components/ChatAggregatedToolEntries.tsx:96, packages/ui/src/components/ChatAggregatedToolEntries.tsx:132, …
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×16) — packages/ui/src/components/DeleteWorkspaceDialog.tsx:82, packages/ui/src/components/DeleteWorkspaceDialog.tsx:117, packages/ui/src/components/FileTreeNode.tsx:76, …
This <span> 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. — packages/ui/src/components/TurnNavigationPopup.tsx:121
This <span> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. (×3) — packages/ui/src/components/attachment-node.tsx:263, packages/ui/src/components/image-node.tsx:460, packages/ui/src/components/pr-comment-card.tsx:81
This <span> 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. — REDACTED:104
This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. (×2) — packages/ui/src/components/pr-comment-card.tsx:122, packages/web-core/src/shared/dialogs/settings/settings/RemoteCloudHostsSettingsCard.tsx:381
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}. — packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:278
This <div> announces itself as a role="switch" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="switch" or point aria-activedescendant at it. (×4) — packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:307, packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:365, packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:462, …
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.
The switch role requires aria-checked to convey its state. Add it. (×2) — packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:462, packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:501
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 0.8s 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. — crates/tauri-app/splash/index.html:27
<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) — packages/ui/src/components/AutoExpandingTextarea.tsx:67, packages/ui/src/components/AutoResizeTextarea.tsx:152, packages/ui/src/components/Textarea.tsx:10
<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). (×3) — packages/ui/src/components/Dropdown.tsx:343, packages/ui/src/components/Input.tsx:39, packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:268
<span> moves — its `animate-ping` 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:. — packages/ui/src/components/ToolStatusDot.tsx:35
`diffs-container [slot='hover-slot'] button` 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. — packages/web-core/src/app/styles/diff-style-overrides.css:974
`diffs-container [slot="hover-slot"] button` 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. — packages/ui/src/styles/diff-style-overrides.css:973
`.diff-tailwindcss-wrapper .transition-transform` moves (`transition-property: transform`) 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. (×2) — packages/web-core/src/app/styles/diff-style-overrides.css:370, packages/ui/src/styles/diff-style-overrides.css:370
`.chat-box-running::before` moves (`animation: border-flash 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. — packages/web-core/src/app/styles/new/index.css:401
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
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.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 354 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
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) 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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
`@vibe/web-core` is a Domain project but references `@vibe/ui`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — packages/web-core/package.json:55
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.
`ProjectContextValue` declares 31 required operations: `retry`, `insertIssue`, `updateIssue`, `removeIssue`, `insertStatus`, `updateStatus`, `removeStatus`, `insertTag`, `updateTag`, `removeTag`, `insertIssueAssignee`, `removeIssueAssignee`, `insertIssueFollower`, `removeIssueFollower`, `insertIssueTag`, `removeIssueTag`, `insertIssueRelationship`, `removeIssueRelationship`, `insertPullRequestIssue`, `removePullRequestIssue`, `getIssue`, `getIssuesForStatus`, `getAssigneesForIssue`, `getFollowersForIssue`, `getTagsForIssue`, `getTagObjectsForIssue`, `getRelationshipsForIssue`, `getStatus`, `getTag`, `getPullRequestsForIssue`, `getWorkspacesForIssue`. 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. — packages/web-core/src/shared/hooks/useProjectContext.ts:44
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No in-app HTTPS enforcement, but the server reads the forwarded scheme (X-Forwarded-Proto, actix's connection_info().scheme(), Rocket's proxy_proto_header) — a TLS-terminating reverse proxy sits in front of it, where serving TLS in the app would be wrong. Verify the reverse proxy enforces TLS. — crates/preview-proxy/src/lib.rs:514
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
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.
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:308
`onProjectsDragEnd` 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. — packages/remote-web/src/app/layout/RemoteAppShell.tsx:269
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. — REDACTED:77
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×4) — packages/local-web/src/routeTree.gen.ts:1, packages/local-web/src/routeTree.gen.ts:3, packages/remote-web/src/routeTree.gen.ts:1, …
`selectFile` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useChangesView.ts:29
`scrollToFile` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useChangesView.ts:30
`viewFileInChanges` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/web-core/src/shared/hooks/useChangesView.ts:31, packages/web-core/src/shared/hooks/useChangesView.ts:38
`registerScrollToFile` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useChangesView.ts:34
`setLogSearchQuery` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useLogsPanel.ts:41
`setLogMatchIndices` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useLogsPanel.ts:42
`handleLogPrevMatch` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useLogsPanel.ts:43
`handleLogNextMatch` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/web-core/src/shared/hooks/useLogsPanel.ts:44
`viewProcessInPanel` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/web-core/src/shared/hooks/useLogsPanel.ts:45, packages/web-core/src/shared/hooks/useLogsPanel.ts:53
`viewToolContentInPanel` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/web-core/src/shared/hooks/useLogsPanel.ts:46, packages/web-core/src/shared/hooks/useLogsPanel.ts:54
`expandTerminal` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/web-core/src/shared/hooks/useLogsPanel.ts:47, packages/web-core/src/shared/hooks/useLogsPanel.ts:55
`collapseTerminal` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/web-core/src/shared/hooks/useLogsPanel.ts:48, packages/web-core/src/shared/hooks/useLogsPanel.ts:56
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
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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 35 of 38 project(s) that lack one — worth up to 1.8 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.
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.
Only 20/22 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `npx-cli`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
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.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ 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.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`Client::builder()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — crates/preview-proxy/src/lib.rs:43, crates/server/src/routes/releases.rs:23
`reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/remote/src/app.rs:136
`Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/review/src/api.rs:79
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
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.
`fs.existsSync` in `installAndLaunchMacOS` 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) — REDACTED:91, REDACTED:95
`fs.readdirSync` in `installAndLaunchMacOS` 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:101
`fs.rmSync` in `installAndLaunchMacOS` 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:120
`execSync` in `installAndLaunchMacOS` 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:126
`fs.existsSync` in `installAndLaunchLinux` 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) — REDACTED:154, REDACTED:158
`fs.readdirSync` in `installAndLaunchLinux` 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:165
`fs.chmodSync` in `installAndLaunchLinux` 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:172
`fs.existsSync` in `installAndLaunchWindows` 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. (×3) — REDACTED:203, REDACTED:240, REDACTED:258
`fs.readdirSync` in `installAndLaunchWindows` 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:209
`execSync` in `installAndLaunchWindows` 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) — REDACTED:225, REDACTED:234
`fs.existsSync` in `ensureBinary` 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) — npx-cli/src/download.ts:167, npx-cli/src/download.ts:179
`fs.mkdirSync` in `ensureBinary` 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. — npx-cli/src/download.ts:181
`fs.existsSync` in `ensureDesktopBundle` 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. (×3) — npx-cli/src/download.ts:213, npx-cli/src/download.ts:238, npx-cli/src/download.ts:258
`fs.readdirSync` in `ensureDesktopBundle` 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. — npx-cli/src/download.ts:214
`fs.mkdirSync` in `ensureDesktopBundle` 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. — npx-cli/src/download.ts:242
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.
58 duplicated blocks under packages/ have copies in at least two of the sibling directories local-web, remote-web, ui, web-core — 41 of them are reported below, and 17 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 58 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 58 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 58 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. — packages/remote-web/src/app/layout/RemoteAppShell.tsx:151
41 duplicated blocks under packages/web-core/src/ have copies in at least two of the sibling directories features, integrations, pages, shared — 15 of them are reported below, and 26 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 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 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 41 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. — packages/web-core/src/features/workspace/model/hooks/usePreviewDevServer.ts:2
17 duplicated blocks under packages/web-core/src/shared/dialogs/ have copies in at least two of the sibling directories auth, command-bar, org, scripts, settings, shared (+1 more sibling(s) not listed) — 12 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 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. — packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:55
12 duplicated blocks under packages/web-core/src/shared/ have copies in at least two of the sibling directories components, dialogs, hooks, lib, providers, stores (+1 more sibling(s) not listed) — 4 of them are reported below, and 8 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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. — packages/web-core/src/shared/hooks/useUserSystemController.ts:159
packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:63 · packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:124 — the two spans are one implementation copied and then locally edited — 1177 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. — packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:63
packages/remote-web/src/app/layout/RemoteAppShell.tsx:151 · packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:272 — the two spans are one implementation copied and then locally edited — 740 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. — packages/remote-web/src/app/layout/RemoteAppShell.tsx:151
packages/ui/src/components/attachment-node.tsx:54 · packages/ui/src/components/image-node.tsx:75 — the two spans are one implementation copied and then locally edited — 878 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. — packages/ui/src/components/attachment-node.tsx:54
packages/ui/src/components/Dropdown.tsx:13 · packages/ui/src/components/DropdownMenu.tsx:7 — the two spans are one implementation copied and then locally edited — 812 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. — packages/ui/src/components/Dropdown.tsx:13
packages/local-web/src/app/navigation/AppNavigation.ts:45 · packages/remote-web/src/app/navigation/AppNavigation.ts:30 — the two spans are one implementation copied and then locally edited — 619 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. — packages/local-web/src/app/navigation/AppNavigation.ts:45
packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:55 · packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:97 — the two spans are one implementation copied and then locally edited — 604 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. — packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:55
packages/ui/src/components/RenameSessionDialog.tsx:27 · packages/ui/src/components/RenameWorkspaceDialog.tsx:27 — the two spans are one implementation copied and then locally edited — 431 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. — packages/ui/src/components/RenameSessionDialog.tsx:27
packages/web-core/src/pages/workspaces/VSCodeWorkspacePage.tsx:38 · packages/web-core/src/pages/workspaces/WorkspacesMainContainer.tsx:44 — the two spans are one implementation copied and then locally edited — 526 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. — packages/web-core/src/pages/workspaces/VSCodeWorkspacePage.tsx:38
packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:254 · packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:510 — the two spans are one implementation copied and then locally edited — 523 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. — packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:254
packages/remote-web/src/shared/lib/relay/ws.ts:48 · packages/remote-web/src/shared/lib/webrtc/dataChannelWebSocket.ts:17 — the two spans are one implementation copied and then locally edited — 452 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. — packages/remote-web/src/shared/lib/relay/ws.ts:48
packages/remote-web/src/pages/InvitationCompletePage.tsx:22 · packages/remote-web/src/pages/LoginCompletePage.tsx:27 — the two spans are one implementation copied and then locally edited — 275 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. — packages/remote-web/src/pages/InvitationCompletePage.tsx:22
packages/ui/src/components/KanbanAssignee.tsx:22 · packages/ui/src/components/UserAvatar.tsx:18 — the two spans are one implementation copied and then locally edited — 471 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. — packages/ui/src/components/KanbanAssignee.tsx:22
packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:280 · packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:397 — the two spans are one implementation copied and then locally edited — 292 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. — packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:280
packages/web-core/src/shared/components/tasks/AgentSelector.tsx:21 · packages/web-core/src/shared/components/tasks/ConfigSelector.tsx:22 — the two spans are one implementation copied and then locally edited — 173 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. — packages/web-core/src/shared/components/tasks/AgentSelector.tsx:21
packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:130 · packages/web-core/src/shared/dialogs/org/InviteMemberDialog.tsx:108 — the two spans are one implementation copied and then locally edited — 320 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. — packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:130
packages/web-core/src/shared/components/tasks/BranchSelector.tsx:113 · packages/web-core/src/shared/components/ui-new/containers/SearchableDropdownContainer.tsx:53 — the two spans are one implementation copied and then locally edited — 366 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. — packages/web-core/src/shared/components/tasks/BranchSelector.tsx:113
packages/web-core/src/features/workspace/model/hooks/usePreviewDevServer.ts:2 · packages/web-core/src/shared/hooks/useDevServer.ts:2 — these 2 files are line-for-line copies of one another — 58 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. — packages/web-core/src/features/workspace/model/hooks/usePreviewDevServer.ts:2
packages/web-core/src/features/workspace-chat/model/hooks/useMessageEditRetry.ts:15 · packages/web-core/src/shared/hooks/useRetryProcess.ts:16 — 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. — packages/web-core/src/features/workspace-chat/model/hooks/useMessageEditRetry.ts:15
packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx:29 · packages/web-core/src/shared/components/ui-new/containers/NavbarContainer.tsx:46 — 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. — packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx:29
packages/ui/src/components/ChatFileEntry.tsx:100 · packages/ui/src/components/ChatFileEntry.tsx:168 — 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. — packages/ui/src/components/ChatFileEntry.tsx:100
packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:37 · packages/web-core/src/shared/dialogs/org/InviteMemberDialog.tsx:45 — the two spans are one implementation copied and then locally edited — 233 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. — packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:37
packages/remote-web/src/routes/hosts.$hostId.workspaces.tsx:142 · packages/ui/src/components/WorkspaceSummary.tsx:126 — the two spans are one implementation copied and then locally edited — 133 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. — packages/remote-web/src/routes/hosts.$hostId.workspaces.tsx:142
packages/ui/src/components/ChatTodoList.tsx:14 · packages/ui/src/components/TodoProgressPopup.tsx:16 — the two spans are one implementation copied and then locally edited — 280 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. — packages/ui/src/components/ChatTodoList.tsx:14
packages/remote-web/src/app/providers/RemoteActionsProvider.tsx:178 · packages/web-core/src/shared/providers/ActionsProvider.tsx:322 — the two spans are one implementation copied and then locally edited — 131 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. — packages/remote-web/src/app/providers/RemoteActionsProvider.tsx:178
packages/ui/src/components/FileTagTypeaheadPlugin.tsx:388 · packages/ui/src/components/SlashCommandTypeaheadPlugin.tsx:107 — the two spans are one implementation copied and then locally edited — 239 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. — packages/ui/src/components/FileTagTypeaheadPlugin.tsx:388
packages/web-core/src/shared/providers/WorkspaceProvider.tsx:199 · packages/web-core/src/shared/providers/remote/ProjectProvider.tsx:281 — 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. — packages/web-core/src/shared/providers/WorkspaceProvider.tsx:199
packages/ui/src/components/ComponentInfoKeyboardPlugin.tsx:16 · packages/ui/src/components/ImageKeyboardPlugin.tsx:16 — 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. — packages/ui/src/components/ComponentInfoKeyboardPlugin.tsx:16
packages/web-core/src/shared/dialogs/command-bar/BranchRebaseDialog.tsx:93 · packages/web-core/src/shared/dialogs/command-bar/RebaseDialog.tsx:267 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/web-core/src/shared/dialogs/command-bar/BranchRebaseDialog.tsx:93
packages/web-core/src/integrations/remote/IssueProvider.tsx:16 · packages/web-core/src/shared/providers/remote/ProjectProvider.tsx:31 — the two spans are one implementation copied and then locally edited — 286 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. — packages/web-core/src/integrations/remote/IssueProvider.tsx:16
packages/web-core/src/shared/dialogs/command-bar/SelectionDialog.tsx:107 · packages/web-core/src/shared/dialogs/command-bar/selections/ProjectSelectionDialog.tsx:278 — the two spans are one implementation copied and then locally edited — 247 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. — packages/web-core/src/shared/dialogs/command-bar/SelectionDialog.tsx:107
packages/ui/src/components/ChatAggregatedDiffEntries.tsx:228 · packages/ui/src/components/ChatAggregatedToolEntries.tsx:70 — the two spans are one implementation copied and then locally edited — 199 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. — packages/ui/src/components/ChatAggregatedDiffEntries.tsx:228
packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:560 · packages/web-core/src/pages/kanban/IssueWorkspacesSectionContainer.tsx:52 — the two spans are one implementation copied and then locally edited — 216 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. — packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:560
packages/web-core/src/shared/hooks/useProfiles.ts:38 · packages/web-core/src/shared/hooks/useProfiles.ts:111 — 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. — packages/web-core/src/shared/hooks/useProfiles.ts:38
packages/web-core/src/shared/lib/relayBackendApi.ts:124 · packages/web-core/src/shared/lib/remoteApi.ts:55 — 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. — packages/web-core/src/shared/lib/relayBackendApi.ts:124
packages/web-core/src/features/onboarding/ui/LandingPage.tsx:380 · packages/web-core/src/features/onboarding/ui/LandingPage.tsx:417 — 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. — packages/web-core/src/features/onboarding/ui/LandingPage.tsx:380
packages/ui/src/components/PreviewBrowser.tsx:264 · packages/ui/src/components/PreviewBrowser.tsx:438 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/ui/src/components/PreviewBrowser.tsx:264
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.
packages/web-core/src/shared/actions/index.ts:77 imports packages/web-core/src/features/create-mode/model/createModeSeedStore.ts against the feature-sliced rules. — packages/web-core/src/shared/actions/index.ts:77
packages/web-core/src/shared/components/CreateChatBoxContainer.tsx:4 imports packages/web-core/src/features/create-mode/model/useCreateMode.ts against the feature-sliced rules. — packages/web-core/src/shared/components/CreateChatBoxContainer.tsx:4
packages/web-core/src/shared/components/CreateModeRepoPickerBar.tsx:16 imports packages/web-core/src/features/create-mode/model/useCreateMode.ts against the feature-sliced rules. — packages/web-core/src/shared/components/CreateModeRepoPickerBar.tsx:16
packages/web-core/src/shared/components/VirtualizedProcessLogs.tsx:11 imports @phosphor-icons/react/dist/ssr, 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. — packages/web-core/src/shared/components/VirtualizedProcessLogs.tsx:11
packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:53 imports packages/web-core/src/pages/workspaces/AppBarNotificationBellContainer.tsx against the feature-sliced rules. — packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:53
packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:54 imports packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx against the feature-sliced rules. — packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:54
What to do
Fix the listed violations: respect the layer/slice order — import only through a slice's public index and never upward into a higher layer (5 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (1 row).
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.
SessionChatBox has cyclomatic complexity 71 and cognitive complexity 56; 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. — packages/ui/src/components/SessionChatBox.tsx:223
PreviewBrowser has cyclomatic complexity 61 and cognitive complexity 56; 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. — packages/ui/src/components/PreviewBrowser.tsx:94
(anonymous) has cyclomatic complexity 53 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. — packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:44
ModelSelectorContainer has cyclomatic complexity 52 and cognitive complexity 43; 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. — packages/web-core/src/shared/components/ModelSelectorContainer.tsx:60
resolveLocalDestinationFromPath has cyclomatic complexity 52 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 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. — packages/local-web/src/app/navigation/AppNavigation.ts:28
ImageComponent has cyclomatic complexity 51 and cognitive complexity 68; 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. — packages/ui/src/components/image-node.tsx:189
KanbanIssuePanel has cyclomatic complexity 49 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. — packages/ui/src/components/KanbanIssuePanel.tsx:159
ChatFileEntry has cyclomatic complexity 46 and cognitive complexity 40; 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. — packages/ui/src/components/ChatFileEntry.tsx:48
LinkPrToIssueContent has cyclomatic complexity 46 and cognitive complexity 37; 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. — packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:39
GitOperations has cyclomatic complexity 41 and cognitive complexity 28; 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. — packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:42
GeneralSettingsSection has cyclomatic complexity 40 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. — packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:57
SessionChatBoxContainer has cyclomatic complexity 40 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. — packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:143
IssueWorkspaceCard has cyclomatic complexity 35 and cognitive complexity 28; 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. — packages/ui/src/components/IssueWorkspaceCard.tsx:110
OrganizationsSettingsSection has cyclomatic complexity 35 and cognitive complexity 28; 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. — packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:45
WorkspacesLayout has cyclomatic complexity 34 and cognitive complexity 31; 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. — packages/web-core/src/pages/workspaces/WorkspacesLayout.tsx:47
OnboardingSignInPage has cyclomatic complexity 34 and cognitive complexity 28; 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. — packages/web-core/src/features/onboarding/ui/OnboardingSignInPage.tsx:74
resolveRemoteDestinationFromPath has cyclomatic complexity 33 and cognitive complexity 26; 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. — packages/remote-web/src/app/navigation/AppNavigation.ts:19
ElectricTestPage has cyclomatic complexity 32 and cognitive complexity 26; 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. — packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:887
(anonymous) has cyclomatic complexity 32 and cognitive complexity 25; 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. — packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:34
RemoteAppShell has cyclomatic complexity 31 and cognitive complexity 28; 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. — packages/remote-web/src/app/layout/RemoteAppShell.tsx:54
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.1 / 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.
packages/web-core/src/shared/lib/api.ts has 1537 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/lib/api.ts:1
packages/web-core/src/shared/actions/index.ts has 1465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/actions/index.ts:1
packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx has 1409 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:1
packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx has 1294 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx:1
packages/web-core/src/pages/workspaces/ElectricTestPage.tsx has 1054 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:1
packages/web-core/src/features/kanban/ui/KanbanContainer.tsx has 1051 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:1
packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx has 1035 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:1
packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx has 1017 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx:1
packages/web-core/src/shared/stores/useUiPreferencesStore.ts has 887 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/stores/useUiPreferencesStore.ts:1
packages/ui/src/components/SessionChatBox.tsx has 876 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/ui/src/components/SessionChatBox.tsx:1
REDACTED has 854 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
packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:1
packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx has 776 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx:1
packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx has 771 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx:1
REDACTED has 711 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
packages/web-core/src/shared/lib/electric/collections.ts has 691 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/lib/electric/collections.ts:1
packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:1
packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx has 639 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx:1
packages/web-core/src/shared/components/WYSIWYGEditor.tsx has 638 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/components/WYSIWYGEditor.tsx:1
packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx has 626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx:1
packages/ui/src/components/PreviewBrowser.tsx has 610 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/ui/src/components/PreviewBrowser.tsx:1
packages/web-core/src/features/create-mode/model/useCreateModeState.ts has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/create-mode/model/useCreateModeState.ts:1
packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:1
packages/ui/src/components/AppBar.tsx has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/ui/src/components/AppBar.tsx:1
packages/local-web/src/routeTree.gen.ts has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/local-web/src/routeTree.gen.ts:1
packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx has 539 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx:1
packages/web-core/src/features/onboarding/ui/LandingPage.tsx has 538 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/onboarding/ui/LandingPage.tsx:1
packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx has 534 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:1
packages/web-core/src/shared/keyboard/registry.ts has 534 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/keyboard/registry.ts:1
packages/ui/src/components/FileTagTypeaheadPlugin.tsx has 530 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/ui/src/components/FileTagTypeaheadPlugin.tsx:1
packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx:1
packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:1
packages/ui/src/components/KanbanIssuePanel.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. — packages/ui/src/components/KanbanIssuePanel.tsx:1
packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx 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. — packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:1
packages/ui/src/components/image-node.tsx has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/ui/src/components/image-node.tsx:1
packages/web-core/src/shared/components/ModelSelectorContainer.tsx has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/components/ModelSelectorContainer.tsx:1
packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx has 488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:1
packages/ui/src/components/WorkspacesSidebar.tsx has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/ui/src/components/WorkspacesSidebar.tsx:1
packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts:1
packages/remote-web/src/routeTree.gen.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/remote-web/src/routeTree.gen.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 Coverage0.0 / 10Critical✓ 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.
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. (×40) — packages/web-core/src/shared/lib/api.ts:1, packages/web-core/src/shared/actions/index.ts:1, packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx: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.
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 package.json 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: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.9 / 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.
Nothing imports this binding — it is safe to review for removal. (×2) — packages/local-web/src/app/providers/ClickedElementsProvider.tsx:34, packages/remote-web/src/shared/lib/webrtc/connectionManager.ts:37
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.
Declared in packages/local-web/package.json 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. (×3)
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 Rust 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 serves HTTP itself (`axum::serve(` (crates/server/src/main.rs:130)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
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.
a rustls `ServerCertVerifier` that accepts every certificate (`AcceptAllCerts`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on. (×2) — crates/relay-tunnel-core/src/tls.rs:16, crates/services/src/services/remote_client.rs:180
Set: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−0.5 on this card.) The server: `axum::serve(` (crates/server/src/main.rs:130).
What to do
Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `crates/relay-tunnel-core/src/tls.rs:16` (a rustls `ServerCertVerifier` that accepts every certificate (`AcceptAllCerts`)), `crates/services/src/services/remote_client.rs:180` (`.danger_accept_invalid_certs(true)`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Add Strict-Transport-Security beside the headers the Rust server already sets.
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.
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 document10.0 / 10Exemplary○ Nothing flagged
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.
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/20 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.
`downloadBlobUrl` 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) — packages/web-core/src/shared/lib/attachmentUtils.ts:2, packages/ui/src/components/image-node.tsx:89
`playSound` 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 })`. — packages/web-core/src/shared/lib/utils.ts:17
`fetchDiscordOnlineCount` 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 })`. — packages/web-core/src/shared/hooks/useDiscordOnlineCount.ts:5
`fetchGitHubStars` 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 })`. — packages/web-core/src/shared/hooks/useGitHubStars.ts:3
`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 })`. (×2) — packages/ui/src/components/attachment-node.tsx:121, packages/ui/src/components/image-node.tsx:151
`initOAuth` 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 })`. — packages/remote-web/src/shared/lib/api.ts:50
`getAuthMethods` 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 })`. — packages/remote-web/src/shared/lib/api.ts:70
`redeemOAuth` 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 })`. — packages/remote-web/src/shared/lib/api.ts:80
`localLogin` 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 })`. — packages/remote-web/src/shared/lib/api.ts:100
`getInvitation` 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 })`. — packages/remote-web/src/shared/lib/api.ts:115
`acceptInvitation` 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 })`. — packages/remote-web/src/shared/lib/api.ts:125
`refreshTokens` 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 })`. — packages/remote-web/src/shared/lib/api.ts:142
`requestLocalApiViaRelay` 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 })`. — packages/remote-web/src/shared/lib/relayHostApi.ts:38
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 unescaped3.5 / 10Weak✓ 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.
`svg` 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. — packages/web-core/src/shared/components/MermaidDiagram.tsx:84
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.
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 `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements 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. (×40) — scripts/build-bippy-bundle.mjs:89, REDACTED:68, packages/web-core/src/shared/stores/useUiPreferencesStore.ts:34, …
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 `package.json` 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.
`trace!` at line 109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:109
`info!` at line 114 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:114
`info!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:128
`debug!` at line 235 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:235
`debug!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:241
`debug!` at line 246 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:246
`debug!` at line 251 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:251
`debug!` at line 260 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:260
`debug!` at line 263 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:263
`debug!` at line 292 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:292
`info!` at line 324 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:324
`warn!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:331
`info!` at line 355 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:355
`debug!` at line 379 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:379
`debug!` at line 393 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:393
`error!` at line 396 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:396
`debug!` at line 429 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:429
`info!` at line 479 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:479
`debug!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/worktree-manager/src/worktree_manager.rs:531
`warn!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:233
`info!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:241
`error!` at line 248 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:248
`info!` at line 255 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:255
`info!` at line 267 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:267
`warn!` at line 270 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:270
`info!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:301
`debug!` at line 314 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:314
`error!` at line 338 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:338
`debug!` at line 348 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:348
`info!` at line 362 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:362
`debug!` at line 399 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:399
`info!` at line 409 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:409
`info!` at line 432 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:432
`debug!` at line 448 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:448
`info!` at line 486 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:486
`info!` at line 513 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:513
`error!` at line 530 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:530
`debug!` at line 559 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:559
`error!` at line 569 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:569
`warn!` at line 582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/workspace-manager/src/workspace_manager.rs:582
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.
5/7 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.6 `!` null assertions per 1k TypeScript source lines — 66 assertion(s) across the 107681 source line(s) of the 680 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: packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx (11), packages/remote-web/src/shared/lib/webrtc/dataChannelWebSocket.ts (4), packages/web-core/src/features/create-mode/model/createModeBootstrap.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 — 8 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 evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a struct, Diesel table, SeaORM entity or SQL migration table named for it — a SeaORM ActiveModelBehavior hook or database trigger that records each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 41 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; 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 — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.remote-server.environment.VIBEKANBAN_REMOTE_JWT_SECRET: required variable VIBEKANBAN_REMOTE_JWT_SECRET is missing a value: set in .env.remote; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
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.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.js,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
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'.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb. 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.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. 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· Click handler on a non-interactive <div> · ×13
Click handler on a non-interactive <div> packages/ui/src/components/DeleteWorkspaceDialog.tsx:82— 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> packages/ui/src/components/DeleteWorkspaceDialog.tsx:117— 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> packages/ui/src/components/FileTreeNode.tsx:76— 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> packages/ui/src/components/GuideDialogShell.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> packages/ui/src/components/KeyboardDialog.tsx:138— 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> packages/ui/src/components/MobileDrawer.tsx:16— 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> packages/ui/src/components/PierreConversationDiff.tsx:286— 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> packages/ui/src/components/TypeaheadMenu.tsx:365— 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> packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:188— 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> packages/web-core/src/shared/dialogs/settings/SettingsDialog.tsx:247— 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> packages/web-core/src/shared/dialogs/settings/settings/SettingsComponents.tsx:82— 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> packages/web-core/src/shared/dialogs/shared/FolderPickerDialog.tsx:251— 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> packages/web-core/src/shared/dialogs/shared/KeyboardShortcutsDialog.tsx:223— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· <button> with no accessible text · ×10
<button> with no accessible text packages/remote-web/src/app/layout/RemoteAppShell.tsx:305— 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 packages/ui/src/components/ColorPicker.tsx:68— 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 packages/ui/src/components/GuideDialogShell.tsx:78— 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 packages/ui/src/components/GuideDialogShell.tsx:117— 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 packages/ui/src/components/GuideDialogShell.tsx:124— 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 packages/ui/src/components/InputField.tsx:175— 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 packages/ui/src/components/IssueCommentsSection.tsx:222— 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 packages/ui/src/components/IssueCommentsSection.tsx:301— 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 packages/ui/src/components/IssueCommentsSection.tsx:391— 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 packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:434— 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· <label> that labels no control · ×10
<label> that labels no control packages/ui/src/components/CreateRepoDialog.tsx:94— 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 packages/ui/src/components/CreateRepoDialog.tsx:109— 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 packages/web-core/src/features/export/ui/ExportChooseProjects.tsx:89— 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 packages/web-core/src/features/onboarding/ui/LandingPage.tsx:458— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:333— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:343— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:580— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:590— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:823— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:960— 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· <input> without a programmatic label · ×10
<input> without a programmatic label packages/ui/src/components/CreateRepoDialog.tsx:97— 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 packages/ui/src/components/CreateRepoDialog.tsx:113— 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 packages/ui/src/components/InputField.tsx:110— 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 packages/ui/src/components/PreviewBrowser.tsx:185— 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 packages/ui/src/components/PreviewBrowser.tsx:336— 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 packages/web-core/src/features/onboarding/ui/LandingPage.tsx:461— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:334— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:344— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:581— 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 packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:591— 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· Clickable role="button" that no keyboard user can reach · ×8
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatAggregatedToolEntries.tsx:46— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatAggregatedToolEntries.tsx:96— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatAggregatedToolEntries.tsx:132— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatCollapsedThinking.tsx:50— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatErrorMessage.tsx:18— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatSystemMessage.tsx:18— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatTodoList.tsx:33— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/ui/src/components/ChatToolSummary.tsx:70— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Orphaned knowledge crates/relay-webrtc/src/client.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge crates/relay-hosts/src/lib.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge crates/remote/src/auth/provider.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge crates/relay-client/src/lib.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC4 · Keyboard semantics· Clickable role="switch" that no keyboard user can reach · ×4
Clickable role="switch" that no keyboard user can reach packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:307— This <div> announces itself as a role="switch" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="switch" or point aria-activedescendant at it.
Clickable role="switch" that no keyboard user can reach packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:365— This <div> announces itself as a role="switch" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="switch" or point aria-activedescendant at it.
Clickable role="switch" that no keyboard user can reach packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:462— This <div> announces itself as a role="switch" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="switch" or point aria-activedescendant at it.
Clickable role="switch" that no keyboard user can reach packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:501— This <div> announces itself as a role="switch" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="switch" or point aria-activedescendant at it.
Focusable <span> isn't keyboard-operable packages/ui/src/components/attachment-node.tsx:263— This <span> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
Focusable <span> isn't keyboard-operable packages/ui/src/components/image-node.tsx:460— This <span> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
Focusable <span> isn't keyboard-operable packages/ui/src/components/pr-comment-card.tsx:81— This <span> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
D30 · Dependency Vulnerabilities· High vulnerability · ×3
REDACTED
REDACTED
REDACTED
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×2
Custom control with no accessible name on <div> packages/ui/src/components/GuideDialogShell.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> packages/ui/src/components/KeyboardDialog.tsx:138— 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· <select> without a programmatic label · ×2
<select> without a programmatic label packages/web-core/src/features/export/ui/ExportChooseProjects.tsx:90— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:963— 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· Hover-only interaction on <div> · ×2
Hover-only interaction on <div> packages/ui/src/components/AppBar.tsx:512— 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> packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:385— 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.
Focusable <div> isn't keyboard-operable packages/ui/src/components/pr-comment-card.tsx:122— This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
Focusable <div> isn't keyboard-operable packages/web-core/src/shared/dialogs/settings/settings/RemoteCloudHostsSettingsCard.tsx:381— This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <p> · ×2
Click handler on a non-interactive <p> packages/web-core/src/shared/components/NormalizedConversation/EditDiffRenderer.tsx:104— 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 <p> packages/web-core/src/shared/components/NormalizedConversation/FileChangeRenderer.tsx:137— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
role="switch" missing required aria-checked packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:462— The switch role requires aria-checked to convey its state. Add it.
role="switch" missing required aria-checked packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:501— The switch role requires aria-checked to convey its state. Add it.
TLS certificate validation disabled crates/relay-tunnel-core/src/tls.rs:16— a rustls `ServerCertVerifier` that accepts every certificate (`AcceptAllCerts`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on.
TLS certificate validation disabled crates/services/src/services/remote_client.rs:180— a rustls `ServerCertVerifier` that accepts every certificate (`AcceptAllCerts`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on.
AC2 · Forms & labels· Custom control with no accessible name on <span> · ×1
Custom control with no accessible name on <span> packages/ui/src/components/CollapsibleSectionHeader.tsx:100— This <span> 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· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:824— 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.
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name packages/web-core/src/pages/workspaces/GitHubCommentRenderer.tsx:43— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC4 · Keyboard semantics· Hover-only interaction on <span> · ×1
Hover-only interaction on <span> packages/ui/src/components/TurnNavigationPopup.tsx:121— This <span> 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 <span> · ×1
Double-click handler on a non-interactive <span> REDACTED:104— This <span> 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 <tr> · ×1
Click handler on a non-interactive <tr> packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:157— 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 <span> · ×1
Click handler on a non-interactive <span> packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:278— 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}.
Dependency-rule violation: @vibe/web-core (Domain) → @vibe/ui (Web) packages/web-core/package.json:55— `@vibe/web-core` is a Domain project but references `@vibe/ui`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
FunctionTooLong: RemoteProjectsSettingsSection.RemoteProjectsSettingsSection packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:336— FunctionTooLong — RemoteProjectsSettingsSection runs 848 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 748 over it, 8.48× 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: executors::executors::codex::normalize_logs::normalize_logs crates/executors/src/executors/codex/normalize_logs.rs:1488— FunctionTooLong — executors::executors::codex::normalize_logs::normalize_logs runs 736 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 636 over it, 7.36× 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: KanbanContainer.KanbanContainer packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:125— FunctionTooLong — KanbanContainer runs 735 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 635 over it, 7.35× 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: KanbanIssuePanelContainer.KanbanIssuePanelContainer packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx:77— FunctionTooLong — KanbanIssuePanelContainer runs 719 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 619 over it, 7.19× 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: SessionChatBoxContainer.SessionChatBoxContainer packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:143— FunctionTooLong — SessionChatBoxContainer runs 701 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 601 over it, 7.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: GeneralSettingsSection.GeneralSettingsSection packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:57— FunctionTooLong — GeneralSettingsSection runs 634 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 534 over it, 6.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: SessionChatBox.SessionChatBox packages/ui/src/components/SessionChatBox.tsx:223— FunctionTooLong — SessionChatBox runs 577 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 477 over it, 5.77× 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: PreviewBrowserContainer.PreviewBrowserContainer REDACTED:174— FunctionTooLong — PreviewBrowserContainer runs 508 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 408 over it, 5.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: executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns crates/executors/src/executors/acp/normalize_logs.rs:34— FunctionTooLong — executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns runs 478 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 378 over it, 4.78× 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: PreviewBrowser.PreviewBrowser packages/ui/src/components/PreviewBrowser.tsx:94— FunctionTooLong — PreviewBrowser runs 475 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 375 over it, 4.75× 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: executors::executors::droid::normalize_logs::normalize_logs crates/executors/src/executors/droid/normalize_logs.rs:25— FunctionTooLong — executors::executors::droid::normalize_logs::normalize_logs runs 461 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 361 over it, 4.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: ReposSettingsSection.ReposSettingsSection packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:130— FunctionTooLong — ReposSettingsSection runs 451 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 351 over it, 4.51× 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: LinkPrToIssueDialog.LinkPrToIssueContent packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:39— FunctionTooLong — LinkPrToIssueContent runs 410 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 310 over it, 4.10× 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: SharedAppLayout.SharedAppLayout packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:59— FunctionTooLong — SharedAppLayout runs 390 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 290 over it, 3.90× 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: ModelSelectorContainer.ModelSelectorContainer packages/web-core/src/shared/components/ModelSelectorContainer.tsx:60— FunctionTooLong — ModelSelectorContainer runs 387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 287 over it, 3.87× 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: OrganizationsSettingsSection.OrganizationsSettingsSection packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:45— FunctionTooLong — OrganizationsSettingsSection runs 387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 287 over it, 3.87× 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: GitOperations.GitOperations packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:42— FunctionTooLong — GitOperations runs 385 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 285 over it, 3.85× 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: LandingPage.LandingPage packages/web-core/src/features/onboarding/ui/LandingPage.tsx:149— FunctionTooLong — LandingPage runs 350 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 250 over it, 3.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.
FunctionTooLong: FileTagTypeaheadPlugin.FileTagTypeaheadPlugin packages/ui/src/components/FileTagTypeaheadPlugin.tsx:132— FunctionTooLong — FileTagTypeaheadPlugin 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: AgentsSettingsSection.AgentsSettingsSection packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx:39— FunctionTooLong — AgentsSettingsSection 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: useConversationHistory.useConversationHistory packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts:29— FunctionTooLong — useConversationHistory runs 346 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× 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: RemoteAppShell.RemoteAppShell packages/remote-web/src/app/layout/RemoteAppShell.tsx:54— FunctionTooLong — RemoteAppShell runs 345 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 245 over it, 3.45× 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: RelaySettingsSection.LocalRelaySettingsSectionContent packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx:188— FunctionTooLong — LocalRelaySettingsSectionContent runs 336 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 236 over it, 3.36× 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: KanbanIssuePanel.KanbanIssuePanel packages/ui/src/components/KanbanIssuePanel.tsx:159— FunctionTooLong — KanbanIssuePanel 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: OAuthDialog.OAuthDialogImpl packages/web-core/src/shared/dialogs/global/OAuthDialog.tsx:35— FunctionTooLong — OAuthDialogImpl runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.21× 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.
FileTooLong: codex/normalize_logs.rs crates/executors/src/executors/codex/normalize_logs.rs— FileTooLong — 2011 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1511 over it, 4.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.
FileTooLong: executors/claude.rs crates/executors/src/executors/claude.rs— FileTooLong — 1991 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1491 over it, 3.98× 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: opencode/sdk.rs crates/executors/src/executors/opencode/sdk.rs— FileTooLong — 1283 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 41 free functions. The bar is 500 significant lines; this is 783 over it, 2.57× 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: actions/index.ts packages/web-core/src/shared/actions/index.ts— FileTooLong — 1184 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: Actions (174-1533). The bar is 500 significant lines; this is 684 over it, 2.37× 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: settings/RemoteProjectsSettingsSection.tsx packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx— FileTooLong — 1175 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: RemoteProjectsSettingsSection (336-1471). The bar is 500 significant lines; this is 675 over it, 2.35× 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: src/lib.rs crates/git/src/lib.rs— FileTooLong — 1147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: GitService (2 blocks, 144-1693). The bar is 500 significant lines; this is 647 over it, 2.29× 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: lib/api.ts packages/web-core/src/shared/lib/api.ts— FileTooLong — 1128 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 628 over it, 2.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: opencode/normalize_logs.rs crates/executors/src/executors/opencode/normalize_logs.rs— FileTooLong — 1110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 610 over it, 2.22× 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: src/container.rs crates/local-deployment/src/container.rs— FileTooLong — 1079 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: LocalContainerService (3 blocks, 69-1634). The bar is 500 significant lines; this is 579 over it, 2.16× 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: ui/DisplayConversationEntry.tsx packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx— FileTooLong — 1024 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 524 over it, 2.05× 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: executors/cursor.rs crates/executors/src/executors/cursor.rs— FileTooLong — 1005 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 505 over it, 2.01× 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/container.rs crates/services/src/services/container.rs— FileTooLong — 927 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: ContainerService (88-1392). The bar is 500 significant lines; this is 427 over it, 1.85× 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: droid/normalize_logs.rs crates/executors/src/executors/droid/normalize_logs.rs— FileTooLong — 913 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 413 over it, 1.83× 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: ui/KanbanContainer.tsx packages/web-core/src/features/kanban/ui/KanbanContainer.tsx— FileTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: KanbanContainer (125-1153). The bar is 500 significant lines; this is 336 over it, 1.67× 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: ui/SessionChatBoxContainer.tsx packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx— FileTooLong — 811 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: SessionChatBoxContainer (143-1130). The bar is 500 significant lines; this is 311 over it, 1.62× 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: kanban/KanbanIssuePanelContainer.tsx packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx— FileTooLong — 787 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: KanbanIssuePanelContainer (77-1113). The bar is 500 significant lines; this is 287 over it, 1.57× 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/github_app.rs crates/remote/src/routes/github_app.rs— FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 278 over it, 1.56× 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: components/SessionChatBox.tsx packages/ui/src/components/SessionChatBox.tsx— FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: SessionChatBox (223-924). The bar is 500 significant lines; this is 256 over it, 1.51× 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: codex/client.rs crates/executors/src/executors/codex/client.rs— FileTooLong — 728 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: AppServerClient (3 blocks, 48-920). The bar is 500 significant lines; this is 228 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: services/remote_client.rs crates/services/src/services/remote_client.rs— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 85% of them inside a single declaration: RemoteClient (4 blocks, 142-1033). The bar is 500 significant lines; this is 216 over it, 1.43× 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: tools/remote_issues.rs crates/mcp/src/task_server/tools/remote_issues.rs— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: McpServer (2 blocks, 254-919). The bar is 500 significant lines; this is 206 over it, 1.41× 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: settings/GeneralSettingsSection.tsx packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx— FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: GeneralSettingsSection (57-848). The bar is 500 significant lines; this is 190 over it, 1.38× 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: stores/useUiPreferencesStore.ts packages/web-core/src/shared/stores/useUiPreferencesStore.ts— FileTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 183 over it, 1.37× 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: workspaces/ChangesPanelContainer.tsx packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx— FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 144 over it, 1.29× 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: ui/ConversationListContainer.tsx packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx— FileTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: ConversationList (147-886). The bar is 500 significant lines; this is 133 over it, 1.27× 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.
+ 20 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/web-core/src/shared/lib/api.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 packages/web-core/src/shared/actions/index.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 packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.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 packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.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 packages/web-core/src/features/kanban/ui/KanbanContainer.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 packages/web-core/src/pages/workspaces/ElectricTestPage.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 packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.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 packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.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 packages/web-core/src/shared/stores/useUiPreferencesStore.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 REDACTED: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 packages/ui/src/components/SessionChatBox.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 packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.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 packages/web-core/src/pages/workspaces/ChangesPanelContainer.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 packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.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 packages/web-core/src/shared/lib/electric/collections.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 REDACTED: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 packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.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 packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.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 packages/web-core/src/shared/components/WYSIWYGEditor.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 packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.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 packages/web-core/src/features/create-mode/model/useCreateModeState.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 packages/ui/src/components/PreviewBrowser.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 packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.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 packages/ui/src/components/FileTagTypeaheadPlugin.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 packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.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.
Swallowed exception (empty catch) scripts/build-bippy-bundle.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) REDACTED:68— 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) packages/web-core/src/shared/stores/useUiPreferencesStore.ts:34— 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) packages/web-core/src/shared/stores/useUiPreferencesStore.ts:833— 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) packages/web-core/src/shared/providers/TerminalProvider.tsx:370— 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) packages/web-core/src/shared/lib/relayBackendApi.ts:222— 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) packages/web-core/src/shared/lib/streamJsonPatchEntries.ts:64— 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) packages/web-core/src/shared/lib/zoom.ts:14— 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) packages/web-core/src/shared/lib/zoom.ts:27— 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) packages/web-core/src/shared/hooks/useKanbanIssueComposerScratch.ts:39— 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) packages/web-core/src/shared/hooks/useLocalStorageScratch.ts:24— 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) packages/web-core/src/shared/hooks/useLocalStorageScratch.ts:32— 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) packages/web-core/src/shared/hooks/useLocalStorageScratch.ts:83— 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) packages/web-core/src/shared/hooks/useLocalStorageScratch.ts:134— 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:181— 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) packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx:113— 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) packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx: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) packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx: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) packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:162— 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) packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:179— 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) packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:890— 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) packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:915— 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) packages/web-core/src/shared/dialogs/command-bar/CreatePRDialog.tsx:128— 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) packages/web-core/src/shared/dialogs/command-bar/ForcePushDialog.tsx:52— 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) packages/web-core/src/shared/components/TagManager.tsx:42— 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.
ClassTooLong: GitService crates/git/src/lib.rs:59— ClassTooLong — 1029 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 69 methods, 2 blocks, lines 144-1693. The bar is 400 significant lines; this is 629 over it, 2.57× 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: LocalContainerService crates/local-deployment/src/container.rs:69— ClassTooLong — 1008 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 30 methods, 3 blocks, lines 69-1634. The bar is 400 significant lines; this is 608 over it, 2.52× 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: ClaudeLogProcessor crates/executors/src/executors/claude.rs:726— ClassTooLong — 961 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 2 blocks, lines 726-2077. The bar is 400 significant lines; this is 561 over it, 2.40× 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: ContainerService crates/services/src/services/container.rs:88— ClassTooLong — 855 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 41 methods. The bar is 400 significant lines; this is 455 over it, 2.14× 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: RemoteProjectsSettingsSection packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:1— ClassTooLong — 848 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 448 over it, 2.12× 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: KanbanContainer packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:1— ClassTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 335 over it, 1.84× 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: KanbanIssuePanelContainer packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx:1— ClassTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 319 over it, 1.80× 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: SessionChatBoxContainer packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:1— ClassTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 301 over it, 1.75× 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: GeneralSettingsSection packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:1— ClassTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 234 over it, 1.59× 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: AppServerClient crates/executors/src/executors/codex/client.rs:48— ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 35 methods, 3 blocks, lines 48-920. The bar is 400 significant lines; this is 233 over it, 1.58× 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: RemoteClient crates/services/src/services/remote_client.rs:142— ClassTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 69 methods, 4 blocks, lines 142-1033. The bar is 400 significant lines; this is 206 over it, 1.52× 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: SessionChatBox packages/ui/src/components/SessionChatBox.tsx:1— ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 177 over it, 1.44× 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: GitCli crates/git/src/cli.rs:45— ClassTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 44 methods, 2 blocks, lines 80-923. The bar is 400 significant lines; this is 164 over it, 1.41× 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: IssueRepository crates/remote/src/db/issues.rs:30— ClassTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods. The bar is 400 significant lines; this is 130 over it, 1.33× 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: PreviewBrowserContainer REDACTED:1— ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), 7 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: PreviewBrowser packages/ui/src/components/PreviewBrowser.tsx:1— ClassTooLong — 475 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 75 over it, 1.19× 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: ExecutionProcess crates/db/src/models/execution_process.rs:62— ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 2 blocks, lines 62-682. The bar is 400 significant lines; this is 51 over it, 1.13× 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: ReposSettingsSection packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:1— ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 51 over it, 1.13× 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: Codex crates/executors/src/executors/codex.rs:153— ClassTooLong — 446 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 3 blocks, lines 153-762. The bar is 400 significant lines; this is 46 over it, 1.12× 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: Opencode crates/executors/src/executors/opencode.rs:46— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 46-770. The bar is 400 significant lines; this is 30 over it, 1.08× 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: LogState crates/executors/src/executors/opencode/normalize_logs.rs:214— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 2 blocks, lines 214-817. The bar is 400 significant lines; this is 20 over it, 1.05× 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: CursorAgent crates/executors/src/executors/cursor.rs:42— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 3 blocks, lines 42-696. The bar is 400 significant lines; this is 9 over it, 1.02× 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: GitHubAppRepository2 crates/remote/src/db/github_app.rs:53— ClassTooLong — 403 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 2 blocks, lines 53-558. The bar is 400 significant lines; this is 3 over it, 1.01× 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.
Sync-over-async blocking REDACTED:91— `fs.existsSync` in `installAndLaunchMacOS` 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:95— `fs.existsSync` in `installAndLaunchMacOS` 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:101— `fs.readdirSync` in `installAndLaunchMacOS` 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:120— `fs.rmSync` in `installAndLaunchMacOS` 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:126— `execSync` in `installAndLaunchMacOS` 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:154— `fs.existsSync` in `installAndLaunchLinux` 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:158— `fs.existsSync` in `installAndLaunchLinux` 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:165— `fs.readdirSync` in `installAndLaunchLinux` 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:172— `fs.chmodSync` in `installAndLaunchLinux` 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:203— `fs.existsSync` in `installAndLaunchWindows` 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:209— `fs.readdirSync` in `installAndLaunchWindows` 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:225— `execSync` in `installAndLaunchWindows` 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:234— `execSync` in `installAndLaunchWindows` 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:240— `fs.existsSync` in `installAndLaunchWindows` 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:258— `fs.existsSync` in `installAndLaunchWindows` 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 npx-cli/src/download.ts:167— `fs.existsSync` in `ensureBinary` 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 npx-cli/src/download.ts:179— `fs.existsSync` in `ensureBinary` 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 npx-cli/src/download.ts:181— `fs.mkdirSync` in `ensureBinary` 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 npx-cli/src/download.ts:213— `fs.existsSync` in `ensureDesktopBundle` 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 npx-cli/src/download.ts:214— `fs.readdirSync` in `ensureDesktopBundle` 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 npx-cli/src/download.ts:238— `fs.existsSync` in `ensureDesktopBundle` 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 npx-cli/src/download.ts:242— `fs.mkdirSync` in `ensureDesktopBundle` 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 npx-cli/src/download.ts:258— `fs.existsSync` in `ensureDesktopBundle` 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.
MethodTooLong: ClaudeLogProcessor.normalize_entries crates/executors/src/executors/claude.rs:1231— MethodTooLong — normalize_entries runs 526 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 426 over it, 5.26× 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.
MethodTooLong: CursorAgent.normalize_logs crates/executors/src/executors/cursor.rs:265— MethodTooLong — normalize_logs runs 243 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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.
MethodTooLong: AcpAgentHarness.bootstrap_acp_connection crates/executors/src/executors/acp/harness.rs:189— MethodTooLong — bootstrap_acp_connection runs 226 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× 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.
MethodTooLong: LocalContainerService.spawn_exit_monitor crates/local-deployment/src/container.rs:480— MethodTooLong — spawn_exit_monitor runs 209 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× 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.
MethodTooLong: IssueRepository.search crates/remote/src/db/issues.rs:63— MethodTooLong — search runs 182 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 82 over it, 1.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.
MethodTooLong: Opencode.discover_options crates/executors/src/executors/opencode.rs:527— MethodTooLong — discover_options runs 163 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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.
MethodTooLong: ContainerService.start_execution crates/services/src/services/container.rs:1133— MethodTooLong — start_execution runs 156 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× 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.
MethodTooLong: ApiError.into_response crates/server/src/error.rs:317— MethodTooLong — into_response runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× 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.
MethodTooLong: LocalDeployment.new crates/local-deployment/src/lib.rs:92— MethodTooLong — new runs 147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 47 over it, 1.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.
MethodTooLong: Server.run crates/remote/src/app.rs:33— MethodTooLong — run runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.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.
MethodTooLong: ContainerService.stream_normalized_logs crates/services/src/services/container.rs:830— MethodTooLong — stream_normalized_logs runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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.
MethodTooLong: WebRtcClient.connect crates/relay-webrtc/src/client.rs:262— MethodTooLong — connect runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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.
MethodTooLong: CursorToolCall.to_action_and_content crates/executors/src/executors/cursor.rs:904— MethodTooLong — to_action_and_content runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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.
MethodTooLong: ClaudeLogProcessor.extract_action_type crates/executors/src/executors/claude.rs:1061— MethodTooLong — extract_action_type runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 27 over it, 1.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.
MethodTooLong: ClaudeCode.discover_options crates/executors/src/executors/claude.rs:405— MethodTooLong — discover_options runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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.
MethodTooLong: AppServerClient.handle_server_request crates/executors/src/executors/codex/client.rs:303— MethodTooLong — handle_server_request runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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.
MethodTooLong: ToolCallState.apply_tool_data crates/executors/src/executors/opencode/normalize_logs.rs:1050— MethodTooLong — apply_tool_data runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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.
Duplicated block (10 lines × 2) crates/embedded-ssh/src/handler.rs:119— crates/embedded-ssh/src/handler.rs:119-128 | crates/embedded-ssh/src/handler.rs:140-149 — 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 (10 lines × 2) crates/executors/src/executors/claude.rs:498— crates/executors/src/executors/claude.rs:498-507 | crates/executors/src/executors/opencode.rs:592-601 — before extracting anything, compare `crates/executors/src/executors/claude.rs` and `crates/executors/src/executors/opencode.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) crates/executors/src/executors/codex/normalize_logs.rs:353— crates/executors/src/executors/codex/normalize_logs.rs:353-362 | crates/executors/src/executors/droid/normalize_logs.rs:1046-1055 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/executors/src/executors/opencode/sdk.rs:306— crates/executors/src/executors/opencode/sdk.rs:306-315 | crates/executors/src/executors/opencode/slash_commands.rs:463-472 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:79— crates/relay-tunnel/src/server_bin/auth.rs:79-88 | crates/remote/src/auth/jwt.rs:180-189 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:92— crates/relay-tunnel/src/server_bin/auth.rs:92-101 | crates/remote/src/auth/jwt.rs:193-202 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/remote/src/github_app/service.rs:129— crates/remote/src/github_app/service.rs:129-138 | crates/remote/src/github_app/service.rs:437-446 — 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 (10 lines × 2) crates/remote/src/routes/export.rs:225— crates/remote/src/routes/export.rs:225-234 | crates/remote/src/routes/export.rs:250-259 — 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 (10 lines × 2) crates/remote/src/routes/github_app.rs:947— crates/remote/src/routes/github_app.rs:947-956 | crates/remote/src/routes/github_app.rs:1020-1029 — 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 (10 lines × 2) crates/remote/src/routes/issue_assignees.rs:73— crates/remote/src/routes/issue_assignees.rs:73-82 | crates/remote/src/routes/issue_assignees.rs:144-153 — 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 (10 lines × 2) crates/remote/src/routes/notifications.rs:161— crates/remote/src/routes/notifications.rs:161-170 | crates/remote/src/routes/pull_request_issues.rs:178-187 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/remote/src/routes/notifications.rs:214— crates/remote/src/routes/notifications.rs:214-223 | crates/remote/src/routes/pull_request_issues.rs:230-239 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/remote/src/routes/organization_members.rs:440— crates/remote/src/routes/organization_members.rs:440-449 | crates/remote/src/routes/organization_members.rs:552-561 — 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 (10 lines × 2) crates/remote/src/routes/project_statuses.rs:155— crates/remote/src/routes/project_statuses.rs:155-164 | crates/remote/src/routes/tags.rs:137-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/remote/src/routes/project_statuses.rs:330— crates/remote/src/routes/project_statuses.rs:330-339 | crates/remote/src/routes/projects.rs:251-260 — before extracting anything, compare `crates/remote/src/routes/project_statuses.rs` and `crates/remote/src/routes/projects.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) crates/server/src/routes/repo.rs:281— crates/server/src/routes/repo.rs:281-290 | crates/server/src/routes/repo.rs:321-330 — 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 (10 lines × 2) crates/server/src/routes/workspaces/pr.rs:193— crates/server/src/routes/workspaces/pr.rs:193-202 | crates/server/src/routes/workspaces/pr.rs:395-404 — 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×16
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
X2 · Cancellation propagation· Async function without AbortSignal · ×15
Async function without AbortSignal: downloadBlobUrl packages/web-core/src/shared/lib/attachmentUtils.ts:2— `downloadBlobUrl` 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: playSound packages/web-core/src/shared/lib/utils.ts:17— `playSound` 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: fetchDiscordOnlineCount packages/web-core/src/shared/hooks/useDiscordOnlineCount.ts:5— `fetchDiscordOnlineCount` 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: fetchGitHubStars packages/web-core/src/shared/hooks/useGitHubStars.ts:3— `fetchGitHubStars` 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 packages/ui/src/components/attachment-node.tsx:121— `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 })`.
Async function without AbortSignal: downloadBlobUrl packages/ui/src/components/image-node.tsx:89— `downloadBlobUrl` 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 packages/ui/src/components/image-node.tsx:151— `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 })`.
Async function without AbortSignal: initOAuth packages/remote-web/src/shared/lib/api.ts:50— `initOAuth` 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: getAuthMethods packages/remote-web/src/shared/lib/api.ts:70— `getAuthMethods` 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: redeemOAuth packages/remote-web/src/shared/lib/api.ts:80— `redeemOAuth` 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: localLogin packages/remote-web/src/shared/lib/api.ts:100— `localLogin` 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: getInvitation packages/remote-web/src/shared/lib/api.ts:115— `getInvitation` 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: acceptInvitation packages/remote-web/src/shared/lib/api.ts:125— `acceptInvitation` 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: refreshTokens packages/remote-web/src/shared/lib/api.ts:142— `refreshTokens` 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: requestLocalApiViaRelay packages/remote-web/src/shared/lib/relayHostApi.ts:38— `requestLocalApiViaRelay` 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 })`.
executors::executors::codex::normalize_logs::normalize_logs (cognitive 230) crates/executors/src/executors/codex/normalize_logs.rs:1488— executors::executors::codex::normalize_logs::normalize_logs has cognitive complexity 230 (threshold 15). Drivers by points: if/else 64 (186 pts), loops 8 (27 pts), match/switch 5 (15 pts), boolean chains 2 (nesting depth added 151). 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.
executors::executors::droid::normalize_logs::normalize_logs (cognitive 173) crates/executors/src/executors/droid/normalize_logs.rs:25— executors::executors::droid::normalize_logs::normalize_logs has cognitive complexity 173 (threshold 15). Drivers by points: if/else 36 (139 pts), match/switch 7 (27 pts), boolean chains 6, loops 1 (nesting depth added 123). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns (cognitive 94) crates/executors/src/executors/acp/normalize_logs.rs:34— executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns has cognitive complexity 94 (threshold 15). Drivers by points: if/else 56 (139 pts), match/switch 6 (10 pts), loops 4 (7 pts), boolean chains 3 (nesting depth added 90). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type, executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::extract_file_changes) 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.
executors::executors::opencode::sdk::process_event_stream (cognitive 72) crates/executors/src/executors/opencode/sdk.rs:1256— executors::executors::opencode::sdk::process_event_stream has cognitive complexity 72 (threshold 15). Drivers by points: if/else 15 (36 pts), match/switch 10 (32 pts), boolean chains 3, loops 1 (nesting depth added 43). 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.
executors::executors::codex::normalize_logs::handle_direct_item_completed (cognitive 48) crates/executors/src/executors/codex/normalize_logs.rs:1033— executors::executors::codex::normalize_logs::handle_direct_item_completed has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (42 pts), loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 28). 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.
executors::executors::codex::slash_commands::fetch_status_message (cognitive 43) crates/executors/src/executors/codex/slash_commands.rs:342— executors::executors::codex::slash_commands::fetch_status_message has cognitive complexity 43 (threshold 15). Drivers by points: if/else 25 (38 pts), match/switch 3 (4 pts), boolean chains 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.
executors::executors::qa_mock::perform_file_operations (cognitive 26) crates/executors/src/executors/qa_mock.rs:125— executors::executors::qa_mock::perform_file_operations has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 4 (14 pts), if/else 6 (12 pts) (nesting depth added 16). 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.
executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type (cognitive 25) crates/executors/src/executors/acp/normalize_logs.rs:366— executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 3 (5 pts) (nesting depth added 10). 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. This shape REPEATS in the file: 2 other methods here (executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns, executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::extract_file_changes) 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.
executors::mcp_config::adapt_opencode (cognitive 25) crates/executors/src/mcp_config.rs:291— executors::mcp_config::adapt_opencode has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 3 (11 pts), if/else 3 (8 pts), loops 2 (5 pts), boolean chains 1 (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.
executors::executors::cursor::mcp::ensure_mcp_server_trust_impl (cognitive 24) crates/executors/src/executors/cursor/mcp.rs:19— executors::executors::cursor::mcp::ensure_mcp_server_trust_impl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 5 (8 pts), boolean chains 2, loops 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, 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.
executors::executors::opencode::sdk::run_request_with_control (cognitive 23) crates/executors/src/executors/opencode/sdk.rs:448— executors::executors::opencode::sdk::run_request_with_control has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 6 (8 pts), loops 2 (3 pts) (nesting depth added 11). 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.
executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::extract_file_changes (cognitive 17) crates/executors/src/executors/acp/normalize_logs.rs:538— executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::extract_file_changes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 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. This shape REPEATS in the file: 2 other methods here (executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns, executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type) 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.
executors::executors::codex::normalize_logs::handle_direct_item_started (cognitive 17) crates/executors/src/executors/codex/normalize_logs.rs:889— executors::executors::codex::normalize_logs::handle_direct_item_started has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (7 pts), match/switch 1 (nesting depth added 10). 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.
executors::executors::opencode::slash_commands::execute (cognitive 17) crates/executors/src/executors/opencode/slash_commands.rs:336— executors::executors::opencode::slash_commands::execute has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 7 (9 pts), if/else 6 (7 pts), boolean chains 1 (nesting depth added 3). 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.
Duplicated block (5 lines × 2) crates/executors/src/executors/opencode/sdk.rs:1377— crates/executors/src/executors/opencode/sdk.rs:1377-1381 | crates/executors/src/executors/opencode/sdk.rs:1497-1501 — 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 (5 lines × 2) crates/git-host/src/azure/cli.rs:163— crates/git-host/src/azure/cli.rs:163-167 | crates/git-host/src/github/cli.rs:167-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/remote/src/routes/issue_comment_reactions.rs:171— crates/remote/src/routes/issue_comment_reactions.rs:171-175 | crates/remote/src/routes/issue_comment_reactions.rs:233-237 — 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 (5 lines × 2) crates/remote/src/routes/issue_comments.rs:54— crates/remote/src/routes/issue_comments.rs:54-58 | crates/remote/src/shape_routes.rs:520-524 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/remote/src/routes/project_statuses.rs:55— crates/remote/src/routes/project_statuses.rs:55-59 | crates/remote/src/shape_routes.rs:293-298 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/remote/src/routes/projects.rs:51— crates/remote/src/routes/projects.rs:51-55 | crates/remote/src/shape_routes.rs:192-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/remote/src/routes/tags.rs:48— crates/remote/src/routes/tags.rs:48-52 | crates/remote/src/shape_routes.rs:276-280 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/remote/src/routes/tokens.rs:116— crates/remote/src/routes/tokens.rs:116-120 | crates/remote/src/routes/tokens.rs:222-226 — 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 (5 lines × 2) crates/server/src/routes/workspaces/git.rs:297— crates/server/src/routes/workspaces/git.rs:297-301 | crates/server/src/routes/workspaces/git.rs:350-354 — 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 (5 lines × 2) crates/server/src/routes/organizations.rs:95— crates/server/src/routes/organizations.rs:95-101 | crates/server/src/routes/remote/issues.rs:66-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/remote/src/routes/github_app.rs:669— crates/remote/src/routes/github_app.rs:669-673 | crates/remote/src/routes/github_app.rs:718-725 — 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 (5 lines × 2) crates/executors/src/executors/claude.rs:650— crates/executors/src/executors/claude.rs:650-654 | crates/executors/src/executors/codex.rs:670-674 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) crates/mcp/src/task_server/tools/remote_issues.rs:472— crates/mcp/src/task_server/tools/remote_issues.rs:472-476 | crates/mcp/src/task_server/tools/remote_issues.rs:498-502 — 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 (5 lines × 2) crates/remote/src/azure_blob.rs:467— crates/remote/src/azure_blob.rs:467-471 | crates/remote/src/shared_key_auth.rs:152-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×13
Duplicated block (11 lines × 2) crates/embedded-ssh/src/sftp.rs:356— crates/embedded-ssh/src/sftp.rs:356-366 | crates/embedded-ssh/src/sftp.rs:432-442 — 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 (11 lines × 2) crates/mcp/src/task_server/tools/mod.rs:117— crates/mcp/src/task_server/tools/mod.rs:117-127 | crates/mcp/src/task_server/tools/mod.rs:147-157 — 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 (11 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:167— crates/relay-tunnel/src/server_bin/auth.rs:167-177 | crates/remote/src/auth/middleware.rs:101-111 — before extracting anything, compare `crates/relay-tunnel/src/server_bin/auth.rs` and `crates/remote/src/auth/middleware.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) crates/relay-webrtc/src/client.rs:201— crates/relay-webrtc/src/client.rs:201-211 | crates/relay-webrtc/src/peer.rs:52-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) crates/remote/src/routes/pull_request_issues.rs:121— crates/remote/src/routes/pull_request_issues.rs:121-131 | crates/remote/src/routes/pull_requests.rs:115-125 — before extracting anything, compare `crates/remote/src/routes/pull_request_issues.rs` and `crates/remote/src/routes/pull_requests.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) crates/review/src/github.rs:121— crates/review/src/github.rs:121-131 | crates/review/src/github.rs:176-186 — 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 (11 lines × 2) crates/server/src/routes/repo.rs:267— crates/server/src/routes/repo.rs:267-277 | crates/server/src/routes/repo.rs:307-317 — 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 (11 lines × 2) crates/server/src/routes/workspaces/codex_setup.rs:25— crates/server/src/routes/workspaces/codex_setup.rs:25-35 | crates/server/src/routes/workspaces/cursor_setup.rs:25-35 — before extracting anything, compare `crates/server/src/routes/workspaces/codex_setup.rs` and `crates/server/src/routes/workspaces/cursor_setup.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) crates/services/src/services/config/versions/v4.rs:118— crates/services/src/services/config/versions/v4.rs:118-128 | crates/services/src/services/config/versions/v5.rs:81-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) crates/services/src/services/notification.rs:133— crates/services/src/services/notification.rs:133-143 | crates/services/src/services/notification.rs:211-221 — 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 (11 lines × 2) crates/relay-tunnel/src/server_bin/config.rs:43— crates/relay-tunnel/src/server_bin/config.rs:43-53 | crates/remote/src/config.rs:448-458 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) crates/executors/src/executors/opencode/sdk.rs:572— crates/executors/src/executors/opencode/sdk.rs:572-582 | crates/executors/src/executors/opencode/sdk.rs:600-610 — 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 (11 lines × 2) crates/remote/src/routes/tokens.rs:138— crates/remote/src/routes/tokens.rs:138-148 | crates/remote/src/routes/tokens.rs:240-250 — 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.
Off the main sequence: api-types — api-types: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: client-info — client-info: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: relay-control — relay-control: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: relay-types — relay-types: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: remote-info — remote-info: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: trusted-key-auth — trusted-key-auth: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: ws-bridge — ws-bridge: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: git — git: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: utils — utils: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Off the main sequence: db — db: abstractness 0.00, instability 0.22, distance 0.78 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: worktree-manager — worktree-manager: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: executors — executors: abstractness 0.04, instability 0.25, distance 0.71 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
executors::executors::codex::normalize_logs::normalize_logs (cyclomatic 101) crates/executors/src/executors/codex/normalize_logs.rs:1488— executors::executors::codex::normalize_logs::normalize_logs has cyclomatic complexity 101 (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.
executors::executors::droid::normalize_logs::normalize_logs (cyclomatic 62) crates/executors/src/executors/droid/normalize_logs.rs:25— executors::executors::droid::normalize_logs::normalize_logs has cyclomatic complexity 62 (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.
executors::executors::opencode::sdk::process_event_stream (cyclomatic 37) crates/executors/src/executors/opencode/sdk.rs:1256— executors::executors::opencode::sdk::process_event_stream has cyclomatic complexity 37 (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.
executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns (cyclomatic 35) crates/executors/src/executors/acp/normalize_logs.rs:34— executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns 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. This shape REPEATS in the file: one other method here (executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type) 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.
executors::executors::codex::normalize_logs::handle_direct_item_completed (cyclomatic 30) crates/executors/src/executors/codex/normalize_logs.rs:1033— executors::executors::codex::normalize_logs::handle_direct_item_completed has cyclomatic complexity 30 (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.
executors::executors::codex::slash_commands::fetch_status_message (cyclomatic 27) crates/executors/src/executors/codex/slash_commands.rs:342— executors::executors::codex::slash_commands::fetch_status_message 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.
executors::executors::cursor::mcp::ensure_mcp_server_trust_impl (cyclomatic 21) crates/executors/src/executors/cursor/mcp.rs:19— executors::executors::cursor::mcp::ensure_mcp_server_trust_impl 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.
executors::executors::opencode::sdk::run_request_with_control (cyclomatic 21) crates/executors/src/executors/opencode/sdk.rs:448— executors::executors::opencode::sdk::run_request_with_control has cyclomatic complexity 21 (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.
executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type (cyclomatic 20) crates/executors/src/executors/acp/normalize_logs.rs:366— executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns::map_to_action_type 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 (executors::executors::acp::normalize_logs::normalize_logs_with_suppressed_stderr_patterns) 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.
executors::executors::opencode::slash_commands::execute (cyclomatic 20) crates/executors/src/executors/opencode/slash_commands.rs:336— executors::executors::opencode::slash_commands::execute has cyclomatic complexity 20 (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.
executors::executors::codex::normalize_logs::handle_direct_notification (cyclomatic 19) crates/executors/src/executors/codex/normalize_logs.rs:1289— executors::executors::codex::normalize_logs::handle_direct_notification has cyclomatic complexity 19 (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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×11
Duplicated block (9 lines × 2) crates/embedded-ssh/src/sftp.rs:172— crates/embedded-ssh/src/sftp.rs:172-180 | crates/embedded-ssh/src/sftp.rs:203-211 — 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 (9 lines × 2) crates/executors/src/executors/claude.rs:1909— crates/executors/src/executors/claude.rs:1909-1917 | crates/executors/src/executors/codex/normalize_logs.rs:2648-2656 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/git-host/src/azure/mod.rs:56— crates/git-host/src/azure/mod.rs:56-64 | crates/git-host/src/github/mod.rs:142-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/mcp/src/task_server/tools/remote_issues.rs:281— crates/mcp/src/task_server/tools/remote_issues.rs:281-289 | crates/mcp/src/task_server/tools/remote_issues.rs:385-393 — 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 (9 lines × 2) crates/remote/src/auth/handoff.rs:189— crates/remote/src/auth/handoff.rs:189-197 | crates/remote/src/auth/handoff.rs:238-246 — 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 (9 lines × 2) crates/remote/src/routes/issues.rs:350— crates/remote/src/routes/issues.rs:350-358 | crates/remote/src/routes/issues.rs:412-420 — 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 (9 lines × 2) crates/remote/src/routes/pull_request_issues.rs:134— crates/remote/src/routes/pull_request_issues.rs:134-142 | crates/remote/src/routes/pull_requests.rs:315-324 — before extracting anything, compare `crates/remote/src/routes/pull_request_issues.rs` and `crates/remote/src/routes/pull_requests.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) crates/remote/src/routes/pull_requests.rs:146— crates/remote/src/routes/pull_requests.rs:146-154 | crates/remote/src/routes/pull_requests.rs:345-353 — 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 (9 lines × 2) crates/services/src/services/config/versions/v3.rs:27— crates/services/src/services/config/versions/v3.rs:27-35 | crates/services/src/services/config/versions/v5.rs:29-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) crates/services/src/services/diff_stream.rs:391— crates/services/src/services/diff_stream.rs:391-399 | crates/services/src/services/diff_stream.rs:600-608 — 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 (9 lines × 2) crates/remote/src/github_app/service.rs:327— crates/remote/src/github_app/service.rs:327-339 | crates/remote/src/github_app/service.rs:359-367 — 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 (13 lines × 2) crates/executors/src/executors/claude.rs:456— crates/executors/src/executors/claude.rs:456-468 | crates/executors/src/executors/opencode.rs:566-578 — before extracting anything, compare `crates/executors/src/executors/claude.rs` and `crates/executors/src/executors/opencode.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) crates/executors/src/executors/codex.rs:264— crates/executors/src/executors/codex.rs:264-276 | crates/executors/src/executors/gemini.rs:158-170 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) crates/executors/src/executors/opencode/sdk.rs:1352— crates/executors/src/executors/opencode/sdk.rs:1352-1364 | crates/executors/src/executors/opencode/sdk.rs:1475-1487 — 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 (13 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:213— crates/relay-tunnel/src/server_bin/auth.rs:213-225 | crates/remote/src/auth/middleware.rs:160-172 — before extracting anything, compare `crates/relay-tunnel/src/server_bin/auth.rs` and `crates/remote/src/auth/middleware.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) crates/remote/src/routes/pull_requests.rs:129— crates/remote/src/routes/pull_requests.rs:129-141 | crates/remote/src/routes/pull_requests.rs:328-341 — 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 (13 lines × 2) crates/remote/src/shape_route.rs:225— crates/remote/src/shape_route.rs:225-237 | crates/remote/src/shape_route.rs:245-257 — 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 (13 lines × 2) crates/server/src/routes/scratch.rs:50— crates/server/src/routes/scratch.rs:50-62 | crates/server/src/routes/scratch.rs:74-86 — 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 (13 lines × 2) crates/services/src/services/config/versions/v2.rs:119— crates/services/src/services/config/versions/v2.rs:119-131 | crates/services/src/services/config/versions/v3.rs:77-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) crates/remote/src/auth/provider.rs:301— crates/remote/src/auth/provider.rs:301-314 | crates/remote/src/auth/provider.rs:645-657 — 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 (13 lines × 2) crates/remote/src/db/invitations.rs:47— crates/remote/src/db/invitations.rs:47-59 | crates/remote/src/db/invitations.rs:105-117 — 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 (12 lines × 2) crates/db/src/models/repo.rs:359— crates/db/src/models/repo.rs:359-370 | crates/db/src/models/repo.rs:379-390 — 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 (12 lines × 2) crates/remote/src/routes/attachments.rs:377— crates/remote/src/routes/attachments.rs:377-388 | crates/remote/src/routes/attachments.rs:402-413 — 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 (12 lines × 2) crates/remote/src/routes/issue_followers.rs:72— crates/remote/src/routes/issue_followers.rs:72-83 | crates/remote/src/routes/issue_followers.rs:125-136 — 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 (12 lines × 2) crates/remote/src/routes/issue_relationships.rs:77— crates/remote/src/routes/issue_relationships.rs:77-88 | crates/remote/src/routes/issue_relationships.rs:131-142 — 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 (12 lines × 2) crates/remote/src/routes/issue_tags.rs:72— crates/remote/src/routes/issue_tags.rs:72-83 | crates/remote/src/routes/issue_tags.rs:121-132 — 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 (12 lines × 2) crates/remote/src/routes/pull_request_issues.rs:82— crates/remote/src/routes/pull_request_issues.rs:82-93 | crates/remote/src/routes/pull_request_issues.rs:199-210 — 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 (12 lines × 2) crates/server/src/main.rs:133— crates/server/src/main.rs:133-144 | crates/server/src/startup.rs:64-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) crates/server/src/routes/sessions/mod.rs:261— crates/server/src/routes/sessions/mod.rs:261-272 | crates/server/src/routes/sessions/review.rs:48-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) crates/server/src/routes/workspaces/git.rs:800— crates/server/src/routes/workspaces/git.rs:800-811 | crates/server/src/routes/workspaces/git.rs:824-835 — 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 (12 lines × 2) crates/server/src/routes/config.rs:297— crates/server/src/routes/config.rs:297-308 | crates/server/src/routes/config.rs:335-346 — 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 (8 lines × 2) crates/executors/src/executors/claude.rs:73— crates/executors/src/executors/claude.rs:73-81 | crates/executors/src/executors/codex/normalize_logs.rs:1458-1465 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/executors/src/executors/opencode/sdk.rs:564— crates/executors/src/executors/opencode/sdk.rs:564-571 | crates/executors/src/executors/opencode/sdk.rs:592-599 — 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 (8 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:122— crates/relay-tunnel/src/server_bin/auth.rs:122-129 | crates/remote/src/auth/middleware.rs:41-48 — before extracting anything, compare `crates/relay-tunnel/src/server_bin/auth.rs` and `crates/remote/src/auth/middleware.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) crates/remote/src/github_app/service.rs:209— crates/remote/src/github_app/service.rs:209-216 | crates/remote/src/github_app/service.rs:441-448 — 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 (8 lines × 2) crates/remote/src/routes/issue_comment_reactions.rs:145— crates/remote/src/routes/issue_comment_reactions.rs:145-152 | crates/remote/src/routes/issue_comment_reactions.rs:289-296 — 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 (8 lines × 2) crates/remote/src/shape_route.rs:174— crates/remote/src/shape_route.rs:174-181 | crates/remote/src/shape_route.rs:197-204 — 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 (8 lines × 2) crates/review/src/github.rs:238— crates/review/src/github.rs:238-245 | crates/review/src/github.rs:255-262 — 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 (8 lines × 2) crates/utils/src/diff.rs:90— crates/utils/src/diff.rs:90-97 | crates/utils/src/diff.rs:173-180 — 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 (8 lines × 2) crates/remote/src/routes/export.rs:216— crates/remote/src/routes/export.rs:216-224 | crates/remote/src/routes/export.rs:309-316 — 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 (8 lines × 2) crates/services/src/services/config/versions/v2.rs:266— crates/services/src/services/config/versions/v2.rs:266-273 | crates/utils/src/lib.rs:87-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/executors/src/executors/codex/client.rs:688— crates/executors/src/executors/codex/client.rs:688-694 | crates/executors/src/executors/codex/client.rs:715-721 — 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 (7 lines × 2) crates/git-host/src/azure/mod.rs:169— crates/git-host/src/azure/mod.rs:169-175 | crates/git-host/src/azure/mod.rs:213-219 — 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 (7 lines × 2) crates/mcp/src/task_server/tools/issue_tags.rs:104— crates/mcp/src/task_server/tools/issue_tags.rs:104-110 | crates/mcp/src/task_server/tools/issue_tags.rs:133-139 — 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 (7 lines × 2) crates/remote/src/routes/organization_members.rs:120— crates/remote/src/routes/organization_members.rs:120-126 | crates/remote/src/routes/organization_members.rs:194-200 — 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 (7 lines × 2) crates/remote/src/routes/project_statuses.rs:264— crates/remote/src/routes/project_statuses.rs:264-270 | crates/remote/src/routes/projects.rs:207-213 — before extracting anything, compare `crates/remote/src/routes/project_statuses.rs` and `crates/remote/src/routes/projects.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) crates/trusted-key-auth/src/key_confirmation.rs:68— crates/trusted-key-auth/src/key_confirmation.rs:68-74 | crates/trusted-key-auth/src/key_confirmation.rs:90-96 — 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 (7 lines × 2) crates/remote/src/routes/tokens.rs:149— crates/remote/src/routes/tokens.rs:149-155 | crates/remote/src/routes/tokens.rs:251-259 — 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 (7 lines × 2) crates/remote/src/routes/oauth.rs:279— crates/remote/src/routes/oauth.rs:279-285 | crates/remote/src/routes/oauth.rs:296-303 — 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 (7 lines × 2) crates/executors/src/executors/opencode/slash_commands.rs:269— crates/executors/src/executors/opencode/slash_commands.rs:269-275 | crates/executors/src/executors/opencode/slash_commands.rs:289-295 — 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 (7 lines × 2) crates/executors/src/executors/gemini.rs:49— crates/executors/src/executors/gemini.rs:49-55 | crates/executors/src/executors/qwen.rs:45-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
TodoComment packages/web-core/src/shared/providers/WorkspaceProvider.tsx:57— // TODO: Support multiple repos - currently only fetches comments from the primary repo. — 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.
TodoComment packages/web-core/src/shared/lib/utils.ts:5— // TODO: Re-enable twMerge after migration to tailwind v4 — 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.
TodoComment crates/server/src/routes/config.rs:104— // TODO: update frontend, BE schema has changed, this replaces GET /config and /config/constants — 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.
TodoComment crates/relay-tunnel-core/src/client.rs:102— // TODO: fix dev servers — 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.
TodoComment crates/local-deployment/src/lib.rs:217— // TODO: Handle this more gracefully — 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.
TodoComment crates/git-host/src/azure/mod.rs:255— // TODO: Implement list_open_prs for Azure DevOps — 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.
TodoComment crates/executors/src/executors/claude.rs:1054— // TODO: Add proper ToolResult support to NormalizedEntry when the type system supports it — 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.
Duplicated block (8 lines × 3) crates/executors/src/executors/acp/harness.rs:94— crates/executors/src/executors/acp/harness.rs:94-101 | crates/executors/src/executors/acp/harness.rs:147-154 | crates/executors/src/executors/claude.rs:630-637 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 3) crates/executors/src/executors/claude.rs:607— crates/executors/src/executors/claude.rs:607-614 | crates/executors/src/executors/codex.rs:264-271 | crates/executors/src/executors/gemini.rs:158-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) crates/executors/src/executors/codex/client.rs:996— crates/executors/src/executors/codex/client.rs:996-1003 | crates/executors/src/executors/codex/jsonrpc.rs:227-234 | crates/executors/src/executors/opencode/sdk.rs:69-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 3) crates/mcp/src/task_server/tools/repos.rs:146— crates/mcp/src/task_server/tools/repos.rs:146-153 | crates/mcp/src/task_server/tools/repos.rs:175-182 | crates/mcp/src/task_server/tools/repos.rs:204-211 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) crates/remote/src/routes/issue_comment_reactions.rs:135— crates/remote/src/routes/issue_comment_reactions.rs:135-142 | crates/remote/src/routes/issue_comment_reactions.rs:213-220 | crates/remote/src/routes/issue_comment_reactions.rs:272-279 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) crates/remote/src/routes/pull_request_issues.rs:111— crates/remote/src/routes/pull_request_issues.rs:111-118 | crates/remote/src/routes/pull_requests.rs:105-112 | crates/remote/src/routes/pull_requests.rs:290-297 — before extracting anything, compare `crates/remote/src/routes/pull_request_issues.rs` and `crates/remote/src/routes/pull_requests.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) crates/relay-tunnel/src/server_bin/auth.rs:79— crates/relay-tunnel/src/server_bin/auth.rs:79-87 | crates/remote/src/auth/jwt.rs:180-188 | crates/remote/src/auth/jwt.rs:205-212 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Focus outline removed inline packages/ui/src/components/AutoExpandingTextarea.tsx:67— <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 packages/ui/src/components/AutoResizeTextarea.tsx:152— <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 packages/ui/src/components/Dropdown.tsx:343— <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 packages/ui/src/components/Input.tsx:39— <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 packages/ui/src/components/Textarea.tsx:10— <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 packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:268— <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).
server::routes::terminal::handle_terminal_ws (cognitive 31) crates/server/src/routes/terminal.rs:95— server::routes::terminal::handle_terminal_ws has cognitive complexity 31 (threshold 15). Drivers by points: if/else 4 (16 pts), match/switch 5 (14 pts), loops 1 (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.
server::routes::workspaces::pr::attach_existing_pr (cognitive 27) crates/server/src/routes/workspaces/pr.rs:390— server::routes::workspaces::pr::attach_existing_pr has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 3 (5 pts), boolean chains 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.
server::routes::config::handle_executor_discovered_options_ws (cognitive 20) crates/server/src/routes/config.rs:613— server::routes::config::handle_executor_discovered_options_ws has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 3 (8 pts), loops 1 (2 pts) (nesting depth added 13). 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.
server::routes::workspaces::git::rename_branch (cognitive 20) crates/server/src/routes/workspaces/git.rs:558— server::routes::workspaces::git::rename_branch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (5 pts), match/switch 1 (2 pts) (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.
server::routes::workspaces::pr::create_pr (cognitive 20) crates/server/src/routes/workspaces/pr.rs:188— server::routes::workspaces::pr::create_pr has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 6 (8 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.
server::routes::workspaces::git::get_workspace_branch_status (cognitive 18) crates/server/src/routes/workspaces/git.rs:363— server::routes::workspaces::git::get_workspace_branch_status has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (6 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.
Duplicated block (18 lines × 2) crates/executors/src/executors/claude.rs:439— crates/executors/src/executors/claude.rs:439-456 | crates/executors/src/executors/claude.rs:468-485 — 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 (18 lines × 2) crates/relay-webrtc/src/client.rs:532— crates/relay-webrtc/src/client.rs:532-549 | crates/relay-webrtc/src/client.rs:570-587 — 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 (18 lines × 2) crates/remote/src/routes/pull_requests.rs:102— crates/remote/src/routes/pull_requests.rs:102-119 | crates/remote/src/routes/pull_requests.rs:287-304 — 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 (18 lines × 2) crates/server/src/routes/execution_processes.rs:176— crates/server/src/routes/execution_processes.rs:176-193 | crates/server/src/routes/execution_processes.rs:250-267 — 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 (18 lines × 2) crates/services/src/services/container.rs:918— crates/services/src/services/container.rs:918-935 | crates/services/src/services/container.rs:937-954 — 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 (18 lines × 2) crates/remote/src/db/auth.rs:201— crates/remote/src/db/auth.rs:201-218 | crates/remote/src/db/auth.rs:247-264 — 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 (15 lines × 2) crates/executors/src/executors/claude/client.rs:75— crates/executors/src/executors/claude/client.rs:75-89 | crates/executors/src/executors/claude/client.rs:169-183 — 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 (15 lines × 2) crates/executors/src/executors/opencode/normalize_logs.rs:434— crates/executors/src/executors/opencode/normalize_logs.rs:434-448 | crates/executors/src/executors/opencode/normalize_logs.rs:475-489 — 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 (15 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:178— crates/relay-tunnel/src/server_bin/auth.rs:178-192 | crates/remote/src/auth/middleware.rs:116-130 — before extracting anything, compare `crates/relay-tunnel/src/server_bin/auth.rs` and `crates/remote/src/auth/middleware.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) crates/remote/src/routes/review.rs:422— crates/remote/src/routes/review.rs:422-436 | crates/remote/src/routes/review.rs:475-489 — 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 (15 lines × 2) crates/review/src/claude_session.rs:391— crates/review/src/claude_session.rs:391-405 | crates/review/src/claude_session.rs:420-434 — 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 (15 lines × 2) crates/server/src/routes/workspaces/git.rs:275— crates/server/src/routes/workspaces/git.rs:275-289 | crates/server/src/routes/workspaces/git.rs:329-343 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×5
Animation without a prefers-reduced-motion guard crates/tauri-app/splash/index.html:27— `.spinner` moves (`animation: spin 0.8s 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 packages/ui/src/components/ToolStatusDot.tsx:35— <span> moves — its `animate-ping` 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 packages/web-core/src/app/styles/diff-style-overrides.css:370— `.diff-tailwindcss-wrapper .transition-transform` moves (`transition-property: transform`) 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 packages/web-core/src/app/styles/new/index.css:401— `.chat-box-running::before` moves (`animation: border-flash 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 packages/ui/src/styles/diff-style-overrides.css:370— `.diff-tailwindcss-wrapper .transition-transform` moves (`transition-property: transform`) 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.
TooManyMethods: McpServer crates/mcp/src/task_server/mod.rs:50— TooManyMethods — 82 methods, declared across 13 files: tools/mod.rs (22), tools/remote_issues.rs (19), task_server/mod.rs (10), tools/sessions.rs (8), +9 more file(s). The bar is 30 methods; this is 52 over it, 2.73× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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.
TooManyMethods: GitService crates/git/src/lib.rs:59— TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× 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.
TooManyMethods: RemoteClient crates/services/src/services/remote_client.rs:142— TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× 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.
TooManyMethods: GitCli crates/git/src/cli.rs:45— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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.
TooManyMethods: AppServerClient crates/executors/src/executors/codex/client.rs:48— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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.
Duplicated block (9 lines × 3) crates/executors/src/executors/acp/normalize_logs.rs:687— crates/executors/src/executors/acp/normalize_logs.rs:687-695 | crates/executors/src/executors/droid/normalize_logs.rs:678-686 | crates/executors/src/logs/stderr_processor.rs:43-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) crates/remote/src/routes/projects.rs:73— crates/remote/src/routes/projects.rs:73-81 | crates/remote/src/routes/projects.rs:143-151 | crates/remote/src/routes/projects.rs:282-290 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) crates/remote/src/routes/tags.rs:70— crates/remote/src/routes/tags.rs:70-78 | crates/remote/src/routes/tags.rs:129-137 | crates/remote/src/routes/tags.rs:169-177 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) crates/remote/src/github_app/service.rs:316— crates/remote/src/github_app/service.rs:316-324 | crates/remote/src/github_app/service.rs:348-356 | crates/remote/src/github_app/service.rs:373-381 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) crates/executors/src/executors/opencode/sdk.rs:631— crates/executors/src/executors/opencode/sdk.rs:631-639 | crates/executors/src/executors/opencode/sdk.rs:717-725 | crates/executors/src/executors/opencode/sdk.rs:789-797 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
ClaudeLogProcessor::normalize_entries (cyclomatic 99) crates/executors/src/executors/claude.rs:1231— ClaudeLogProcessor::normalize_entries has cyclomatic complexity 99 (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.
ClaudeLogProcessor::generate_concise_content (cyclomatic 31) crates/executors/src/executors/claude.rs:1959— ClaudeLogProcessor::generate_concise_content 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.
ClaudeLogProcessor::extract_action_type (cyclomatic 27) crates/executors/src/executors/claude.rs:1061— ClaudeLogProcessor::extract_action_type has cyclomatic complexity 27 (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.
ClaudeLogProcessor::process_logs (cyclomatic 19) crates/executors/src/executors/claude.rs:762— ClaudeLogProcessor::process_logs 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. This is NOT this file's highest cyclomatic complexity: ClaudeToolData::get_name (cyclomatic 21) 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 function is counted neither in this dimension's figures nor in its score.
remote::routes::github_app::handle_callback (cyclomatic 19) crates/remote/src/routes/github_app.rs:466— remote::routes::github_app::handle_callback has cyclomatic complexity 19 (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.
remote::routes::tokens::refresh_token (cyclomatic 19) crates/remote/src/routes/tokens.rs:103— remote::routes::tokens::refresh_token has cyclomatic complexity 19 (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.
remote::digest::email::build_digest_copy (cyclomatic 16) crates/remote/src/digest/email.rs:101— remote::digest::email::build_digest_copy has cyclomatic complexity 16 (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.
remote::routes::export::export_data (cyclomatic 16) crates/remote/src/routes/export.rs:28— remote::routes::export::export_data has cyclomatic complexity 16 (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.
ClaudeLogProcessor::normalize_entries (cognitive 234) crates/executors/src/executors/claude.rs:1231— ClaudeLogProcessor::normalize_entries has cognitive complexity 234 (threshold 15). Drivers by points: if/else 71 (193 pts), match/switch 7 (16 pts), loops 5 (14 pts), boolean chains 11 (nesting depth added 140). 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.
ClaudeLogProcessor::process_logs (cognitive 43) crates/executors/src/executors/claude.rs:762— ClaudeLogProcessor::process_logs has cognitive complexity 43 (threshold 15). Drivers by points: if/else 7 (25 pts), match/switch 3 (9 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 28). 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.
ClaudeLogProcessor::generate_concise_content (cognitive 43) crates/executors/src/executors/claude.rs:1959— ClaudeLogProcessor::generate_concise_content has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (34 pts), match/switch 4 (8 pts), boolean chains 1 (nesting depth added 22). 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.
ClaudeLogProcessor::extract_action_type (cognitive 16) crates/executors/src/executors/claude.rs:1061— ClaudeLogProcessor::extract_action_type has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 5). 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.
ContainerService::stream_normalized_logs (cognitive 35) crates/services/src/services/container.rs:830— ContainerService::stream_normalized_logs has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 5 (10 pts), loops 2 (4 pts), boolean chains 1 (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.
ContainerService::start_execution (cognitive 25) crates/services/src/services/container.rs:1133— ContainerService::start_execution has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 3 (4 pts), boolean chains 1, 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.
ContainerService::discover_executor_options (cognitive 16) crates/services/src/services/container.rs:101— ContainerService::discover_executor_options has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (4 pts), boolean chains 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.
ContainerService::try_stop (cognitive 16) crates/services/src/services/container.rs:707— ContainerService::try_stop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (4 pts), boolean chains 1, match/switch 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.
remote::routes::export::export_data (cognitive 24) crates/remote/src/routes/export.rs:28— remote::routes::export::export_data has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 6 (9 pts), match/switch 1 (4 pts), boolean chains 2 (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.
remote::routes::github_app::handle_callback (cognitive 20) crates/remote/src/routes/github_app.rs:466— remote::routes::github_app::handle_callback has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), match/switch 3, boolean chains 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.
remote::attachments::cleanup::cleanup_expired_attachments (cognitive 17) crates/remote/src/attachments/cleanup.rs:64— remote::attachments::cleanup::cleanup_expired_attachments has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 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.
remote::db::electric_publications::ensure_electric_publications (cognitive 16) crates/remote/src/db/electric_publications.rs:18— remote::db::electric_publications::ensure_electric_publications has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 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.
Duplicated block (16 lines × 2) crates/executors/src/executors/acp/harness.rs:118— crates/executors/src/executors/acp/harness.rs:118-133 | crates/executors/src/executors/acp/harness.rs:171-186 — 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 (16 lines × 2) crates/remote/src/routes/organization_members.rs:412— crates/remote/src/routes/organization_members.rs:412-427 | crates/remote/src/routes/organization_members.rs:522-537 — 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 (16 lines × 2) crates/server/src/routes/filesystem.rs:24— crates/server/src/routes/filesystem.rs:24-39 | crates/server/src/routes/filesystem.rs:57-72 — 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 (16 lines × 2) crates/server/src/routes/workspaces/pr.rs:273— crates/server/src/routes/workspaces/pr.rs:273-288 | crates/server/src/routes/workspaces/pr.rs:420-435 — 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 (14 lines × 2) crates/executors/src/executors/qwen.rs:88— crates/executors/src/executors/qwen.rs:88-101 | crates/executors/src/executors/qwen.rs:122-135 — 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 (14 lines × 2) crates/git/src/cli.rs:352— crates/git/src/cli.rs:352-365 | crates/git/src/cli.rs:380-393 — 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 (14 lines × 2) crates/remote/src/routes/project_statuses.rs:281— crates/remote/src/routes/project_statuses.rs:281-295 | crates/remote/src/routes/projects.rs:223-236 — before extracting anything, compare `crates/remote/src/routes/project_statuses.rs` and `crates/remote/src/routes/projects.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) crates/remote/src/routes/organization_members.rs:622— crates/remote/src/routes/organization_members.rs:622-635 | crates/remote/src/routes/organization_members.rs:667-680 — 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 (12 lines × 3) crates/remote/src/mail.rs:183— crates/remote/src/mail.rs:183-194 | crates/remote/src/mail.rs:224-235 | crates/remote/src/mail.rs:265-276 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) crates/remote/src/routes/project_statuses.rs:80— crates/remote/src/routes/project_statuses.rs:80-91 | crates/remote/src/routes/project_statuses.rs:144-155 | crates/remote/src/routes/project_statuses.rs:193-204 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) crates/review/src/api.rs:102— crates/review/src/api.rs:102-113 | crates/review/src/api.rs:163-174 | crates/review/src/api.rs:187-198 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) crates/server/src/routes/execution_processes.rs:244— crates/server/src/routes/execution_processes.rs:244-255 | crates/server/src/routes/scratch.rs:125-136 | crates/server/src/routes/workspaces/streams.rs:111-122 — before extracting anything, compare `crates/server/src/routes/execution_processes.rs` and `crates/server/src/routes/scratch.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) crates/executors/src/actions/script.rs:56— crates/executors/src/actions/script.rs:56-61 | crates/executors/src/executors/opencode.rs:115-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/relay-webrtc/src/client.rs:652— crates/relay-webrtc/src/client.rs:652-657 | crates/relay-webrtc/src/client.rs:664-669 — 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 (6 lines × 2) crates/remote/src/analytics.rs:65— crates/remote/src/analytics.rs:65-70 | crates/services/src/services/analytics.rs:73-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/server/src/middleware/origin.rs:99— crates/server/src/middleware/origin.rs:99-104 | crates/server/src/middleware/relay_request_signature.rs:294-300 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Outbound HTTP without resilience crates/preview-proxy/src/lib.rs:43— `Client::builder()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/remote/src/app.rs:136— `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/review/src/api.rs:79— `Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/server/src/routes/releases.rs:23— `Client::builder()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC2 · Forms & labels· <Select> field component without a label · ×3
<Select> field component without a label packages/web-core/src/shared/components/org/MemberListItem.tsx:78— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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.
<Select> field component without a label packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:235— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name 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.
<Select> field component without a label packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:267— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name 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.
server::routes::workspaces::pr::create_pr (cyclomatic 21) crates/server/src/routes/workspaces/pr.rs:188— server::routes::workspaces::pr::create_pr has cyclomatic complexity 21 (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.
server::error::remote_client_error (cyclomatic 19) crates/server/src/error.rs:211— server::error::remote_client_error has cyclomatic complexity 19 (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. This is NOT this file's highest cyclomatic complexity: ApiError::into_response (cyclomatic 53) 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 function is counted neither in this dimension's figures nor in its score.
server::routes::workspaces::pr::attach_existing_pr (cyclomatic 19) crates/server/src/routes/workspaces/pr.rs:390— server::routes::workspaces::pr::attach_existing_pr 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.
services::services::filesystem_watcher::async_watcher (cognitive 94) crates/services/src/services/filesystem_watcher.rs:455— services::services::filesystem_watcher::async_watcher has cognitive complexity 94 (threshold 15). Drivers by points: if/else 12 (47 pts), loops 9 (39 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 70). 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.
services::services::execution_process::migrate_execution_logs_to_files (cognitive 24) crates/services/src/services/execution_process.rs:30— services::services::execution_process::migrate_execution_logs_to_files has cognitive complexity 24 (threshold 15). Drivers by points: if/else 19 (23 pts), loops 1 (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.
services::services::execution_process::spawn_stream_raw_logs_to_storage (cognitive 24) crates/services/src/services/execution_process.rs:256— services::services::execution_process::spawn_stream_raw_logs_to_storage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 3 (8 pts), loops 1 (2 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.
EventService::stream_execution_processes_for_session_raw (cognitive 59) crates/services/src/services/events/streams.rs:16— EventService::stream_execution_processes_for_session_raw has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (44 pts), match/switch 3 (9 pts), boolean chains 6 (nesting depth added 40). 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.
EventService::create_hook (cognitive 45) crates/services/src/services/events.rs:59— EventService::create_hook has cognitive complexity 45 (threshold 15). Drivers by points: match/switch 10 (24 pts), if/else 8 (17 pts), boolean chains 4 (nesting depth added 23). 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.
EventService::stream_workspaces_raw (cognitive 28) crates/services/src/services/events/streams.rs:227— EventService::stream_workspaces_raw has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (21 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 18). 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.
LogState::update_tool_status (cognitive 32) crates/executors/src/executors/codex/normalize_logs.rs:488— LogState::update_tool_status has cognitive complexity 32 (threshold 15). Drivers by points: if/else 18 (30 pts), loops 1 (2 pts) (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.
LogState::handle_part_update (cognitive 18) crates/executors/src/executors/opencode/normalize_logs.rs:414— LogState::handle_part_update has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 pts), 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.
LogState::handle_permission_asked (cognitive 18) crates/executors/src/executors/opencode/normalize_logs.rs:699— LogState::handle_permission_asked has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, match/switch 1 (2 pts) (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.
Change coupling: CreateModeProvider.tsx ↔ CreateChatBoxContainer.tsx packages/web-core/src/features/create-mode/model/CreateModeProvider.tsx:1— `packages/web-core/src/features/create-mode/model/CreateModeProvider.tsx` and `packages/web-core/src/shared/components/CreateChatBoxContainer.tsx` change together 73% of the time (8 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 8 shared commits counted here, the most recent 3 are `c778e01a` Fix workspace image uploads dropped during legacy cleanup (Vibe Kanba… (at that commit the files were still `frontend/src/contexts/CreateModeContext.tsx` and `frontend/src/components/ui-new/containers/CreateChatBoxContainer.tsx`); `3cd96d21` Revert and reimplement recent model selection (#2811) (at that commit the files were still `frontend/src/contexts/CreateModeContext.tsx` and `frontend/src/components/ui-new/containers/CreateChatBoxContainer.tsx`); `efab316b` Skip create-mode repo picker when defaults are available (#2809) (at that commit the files were still `frontend/src/contexts/CreateModeContext.tsx` and `frontend/src/components/ui-new/containers/CreateChatBoxContainer.tsx`) — run `git show` on any of them.
Change coupling: scratch.rs ↔ useUiPreferencesStore.ts crates/db/src/models/scratch.rs:1— `crates/db/src/models/scratch.rs` and `packages/web-core/src/shared/stores/useUiPreferencesStore.ts` change together 59% of the time (10 of the 17 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `40223b41` feat: add "Hide blocked" filter toggle to kanban board (Vibe Kanban) …; `45056ed4` Persist draft workspace creation preference in scratch (Vibe Kanban) …; `113e956a` feat: persist last selected org and project in scratch store (#2921) — run `git show` on any of them.
Change coupling: useCreateModeState.ts ↔ CreateChatBoxContainer.tsx packages/web-core/src/features/create-mode/model/useCreateModeState.ts:1— `packages/web-core/src/features/create-mode/model/useCreateModeState.ts` and `packages/web-core/src/shared/components/CreateChatBoxContainer.tsx` change together 56% of the time (9 of the 16 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 9 shared commits counted here, the most recent 3 are `c778e01a` Fix workspace image uploads dropped during legacy cleanup (Vibe Kanba… (at that commit the files were still `frontend/src/hooks/useCreateModeState.ts` and `frontend/src/components/ui-new/containers/CreateChatBoxContainer.tsx`); `bdf34725` Use executor_config in workspace create flow and fix create defaults … (at that commit the files were still `frontend/src/hooks/useCreateModeState.ts` and `frontend/src/components/ui-new/containers/CreateChatBoxContainer.tsx`); `3cd96d21` Revert and reimplement recent model selection (#2811) (at that commit the files were still `frontend/src/hooks/useCreateModeState.ts` and `frontend/src/components/ui-new/containers/CreateChatBoxContainer.tsx`) — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/git-host/src/azure/mod.rs:77— crates/git-host/src/azure/mod.rs:77-129 | crates/git-host/src/azure/mod.rs:131-161 | crates/git-host/src/azure/mod.rs:168-205 | crates/git-host/src/azure/mod.rs:212-248 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/mcp/src/task_server/tools/sessions.rs:153— crates/mcp/src/task_server/tools/sessions.rs:153-191 | crates/mcp/src/task_server/tools/sessions.rs:197-222 | crates/mcp/src/task_server/tools/workspaces.rs:180-208 | crates/mcp/src/task_server/tools/workspaces.rs:220-249 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/remote/src/routes/review.rs:323— crates/remote/src/routes/review.rs:323-332 | crates/remote/src/routes/review.rs:354-363 | crates/remote/src/routes/review.rs:369-378 | crates/remote/src/routes/review.rs:384-393 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (19 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:193— crates/relay-tunnel/src/server_bin/auth.rs:193-211 | crates/remote/src/auth/middleware.rs:138-156 — before extracting anything, compare `crates/relay-tunnel/src/server_bin/auth.rs` and `crates/remote/src/auth/middleware.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) crates/server/src/routes/attachments.rs:156— crates/server/src/routes/attachments.rs:156-174 | crates/server/src/routes/workspaces/attachments.rs:255-273 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19 lines × 2) crates/services/src/services/diff_stream.rs:401— crates/services/src/services/diff_stream.rs:401-419 | crates/services/src/services/diff_stream.rs:611-629 — 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 (11 lines × 3) crates/executors/src/executors/acp/normalize_logs.rs:706— crates/executors/src/executors/acp/normalize_logs.rs:706-716 | crates/executors/src/executors/claude.rs:92-102 | crates/executors/src/executors/codex/normalize_logs.rs:1476-1486 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (11 lines × 3) crates/remote/src/routes/workspaces.rs:207— crates/remote/src/routes/workspaces.rs:207-217 | crates/remote/src/routes/workspaces.rs:243-253 | crates/remote/src/routes/workspaces.rs:279-289 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) crates/services/src/services/remote_client.rs:799— crates/services/src/services/remote_client.rs:799-809 | crates/services/src/services/remote_client.rs:845-855 | crates/services/src/services/remote_client.rs:901-911 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) crates/remote/src/routes/issue_comments.rs:79— crates/remote/src/routes/issue_comments.rs:79-88 | crates/remote/src/routes/issue_comments.rs:168-177 | crates/remote/src/routes/issue_comments.rs:221-230 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) crates/remote/src/routes/pull_requests.rs:161— crates/remote/src/routes/pull_requests.rs:161-170 | crates/remote/src/routes/pull_requests.rs:248-257 | crates/remote/src/routes/pull_requests.rs:360-369 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) crates/server/src/routes/workspaces/git.rs:184— crates/server/src/routes/workspaces/git.rs:184-193 | crates/server/src/routes/workspaces/git.rs:273-282 | crates/server/src/routes/workspaces/git.rs:327-336 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) crates/remote/src/routes/issue_comment_reactions.rs:144— crates/remote/src/routes/issue_comment_reactions.rs:144-150 | crates/remote/src/routes/issue_comment_reactions.rs:229-235 | crates/remote/src/routes/issue_comment_reactions.rs:288-294 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) crates/remote/src/routes/issues.rs:246— crates/remote/src/routes/issues.rs:246-252 | crates/remote/src/routes/issues.rs:349-355 | crates/remote/src/routes/issues.rs:411-417 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) crates/remote/src/routes/export.rs:222— crates/remote/src/routes/export.rs:222-228 | crates/remote/src/routes/export.rs:247-253 | crates/remote/src/routes/export.rs:274-280 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) crates/mcp/src/task_server/tools/sessions.rs:232— crates/mcp/src/task_server/tools/sessions.rs:232-237 | crates/mcp/src/task_server/tools/sessions.rs:271-276 | crates/mcp/src/task_server/tools/sessions.rs:334-339 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) crates/remote/src/routes/review.rs:327— crates/remote/src/routes/review.rs:327-332 | crates/remote/src/routes/review.rs:358-363 | crates/remote/src/routes/review.rs:388-393 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) crates/remote/src/mail.rs:197— crates/remote/src/mail.rs:197-202 | crates/remote/src/mail.rs:238-243 | crates/remote/src/mail.rs:279-284 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×2
Focus outline removed in CSS without a :focus replacement packages/web-core/src/app/styles/diff-style-overrides.css:974— `diffs-container [slot='hover-slot'] button` 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 packages/ui/src/styles/diff-style-overrides.css:973— `diffs-container [slot="hover-slot"] button` 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.
EventService::create_hook (cyclomatic 39) crates/services/src/services/events.rs:59— EventService::create_hook has cyclomatic complexity 39 (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.
EventService::stream_execution_processes_for_session_raw (cyclomatic 24) crates/services/src/services/events/streams.rs:16— EventService::stream_execution_processes_for_session_raw 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.
services::services::filesystem_watcher::async_watcher (cyclomatic 26) crates/services/src/services/filesystem_watcher.rs:455— services::services::filesystem_watcher::async_watcher 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.
services::services::execution_process::migrate_execution_logs_to_files (cyclomatic 18) crates/services/src/services/execution_process.rs:30— services::services::execution_process::migrate_execution_logs_to_files 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.
ContainerService::stream_normalized_logs (cyclomatic 22) crates/services/src/services/container.rs:830— ContainerService::stream_normalized_logs 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.
ContainerService::start_execution (cyclomatic 21) crates/services/src/services/container.rs:1133— ContainerService::start_execution 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.
relay_webrtc::peer::run_peer (cyclomatic 20) crates/relay-webrtc/src/peer.rs:106— relay_webrtc::peer::run_peer has cyclomatic complexity 20 (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.
relay_webrtc::peer::proxy_request (cyclomatic 18) crates/relay-webrtc/src/peer.rs:294— relay_webrtc::peer::proxy_request has cyclomatic complexity 18 (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.
DiffStreamManager::handle_reconcile (cyclomatic 20) crates/services/src/services/diff_stream.rs:464— DiffStreamManager::handle_reconcile 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.
DiffStreamManager::run (cyclomatic 18) crates/services/src/services/diff_stream.rs:228— DiffStreamManager::run has cyclomatic complexity 18 (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.
LocalContainerService::spawn_exit_monitor (cognitive 90) crates/local-deployment/src/container.rs:480— LocalContainerService::spawn_exit_monitor has cognitive complexity 90 (threshold 15). Drivers by points: if/else 31 (71 pts), boolean chains 12, match/switch 4 (7 pts) (nesting depth added 43). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LocalContainerService::extract_last_assistant_message (cognitive 16) crates/local-deployment/src/container.rs:897— LocalContainerService::extract_last_assistant_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (14 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
relay_webrtc::peer::run_peer (cognitive 29) crates/relay-webrtc/src/peer.rs:106— relay_webrtc::peer::run_peer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 5 (9 pts), loops 3 (5 pts), boolean chains 2 (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.
relay_webrtc::peer::proxy_request (cognitive 18) crates/relay-webrtc/src/peer.rs:294— relay_webrtc::peer::proxy_request has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), match/switch 4 (6 pts), loops 3 (5 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.
GitService::status_entry_to_diff (cognitive 25) crates/git/src/lib.rs:435— GitService::status_entry_to_diff has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 4 (6 pts), 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.
GitService::get_all_branches (cognitive 16) crates/git/src/lib.rs:1017— GitService::get_all_branches has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 2 (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.
DiffStreamManager::handle_reconcile (cognitive 25) crates/services/src/services/diff_stream.rs:464— DiffStreamManager::handle_reconcile has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 3 (4 pts), boolean chains 2, loops 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.
DiffStreamManager::run (cognitive 23) crates/services/src/services/diff_stream.rs:228— DiffStreamManager::run has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 3 (10 pts), loops 1 (nesting depth added 13). 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.
FileSearchCache::search_files_no_cache (cognitive 22) crates/services/src/services/file_search.rs:226— FileSearchCache::search_files_no_cache has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 5 (8 pts), loops 2 (3 pts), boolean chains 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.
FileSearchCache::build_file_index (cognitive 17) crates/services/src/services/file_search.rs:383— FileSearchCache::build_file_index has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3, boolean chains 2 (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.
ProtocolPeer::read_loop (cognitive 17) crates/executors/src/executors/claude/protocol.rs:49— ProtocolPeer::read_loop has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 2 (7 pts), loops 1 (nesting depth added 11). 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.
ProtocolPeer::handle_control_request (cognitive 17) crates/executors/src/executors/claude/protocol.rs:107— ProtocolPeer::handle_control_request has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 3 (5 pts) (nesting depth added 10). 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.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) crates/git-host/src/github/mod.rs:55— crates/git-host/src/github/mod.rs:55-88 | crates/git-host/src/github/mod.rs:95-129 | crates/git-host/src/github/mod.rs:163-221 | crates/git-host/src/github/mod.rs:223-255 | crates/git-host/src/github/mod.rs:262-298 | crates/git-host/src/github/mod.rs:359-394 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) crates/services/src/services/config/versions/v2.rs:56— crates/services/src/services/config/versions/v2.rs:56-98 | crates/services/src/services/config/versions/v3.rs:25-49 | crates/services/src/services/config/versions/v4.rs:47-90 | crates/services/src/services/config/versions/v5.rs:27-53 | crates/services/src/services/config/versions/v6.rs:47-100 | crates/services/src/services/config/versions/v7.rs:57-106 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (20 lines × 2) crates/executors/src/executors/claude.rs:422— crates/executors/src/executors/claude.rs:422-441 | crates/executors/src/executors/opencode.rs:544-563 — before extracting anything, compare `crates/executors/src/executors/claude.rs` and `crates/executors/src/executors/opencode.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) crates/remote/src/routes/issue_comment_reactions.rs:215— crates/remote/src/routes/issue_comment_reactions.rs:215-234 | crates/remote/src/routes/issue_comment_reactions.rs:274-293 — 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 (16–18 lines × 2) crates/executors/src/executors/opencode/sdk.rs:660— crates/executors/src/executors/opencode/sdk.rs:660-677 | crates/executors/src/executors/opencode/sdk.rs:744-759 — 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 (16–18 lines × 2) crates/remote/src/routes/github_app.rs:298— crates/remote/src/routes/github_app.rs:298-315 | crates/remote/src/routes/github_app.rs:429-444 — 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 (15 lines × 3) crates/remote/src/db/issue_comments.rs:69— crates/remote/src/db/issue_comments.rs:69-83 | crates/remote/src/db/issues.rs:383-398 | crates/remote/src/db/project_statuses.rs:115-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (15 lines × 3) crates/server/src/routes/execution_processes.rs:184— crates/server/src/routes/execution_processes.rs:184-198 | crates/server/src/routes/execution_processes.rs:258-272 | crates/server/src/routes/scratch.rs:139-153 — before extracting anything, compare `crates/server/src/routes/execution_processes.rs` and `crates/server/src/routes/scratch.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) crates/git-host/src/azure/mod.rs:117— crates/git-host/src/azure/mod.rs:117-129 | crates/git-host/src/azure/mod.rs:149-161 | crates/git-host/src/azure/mod.rs:193-205 | crates/git-host/src/azure/mod.rs:236-248 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) crates/remote/src/routes/github_app.rs:135— crates/remote/src/routes/github_app.rs:135-147 | crates/remote/src/routes/github_app.rs:259-271 | crates/remote/src/routes/github_app.rs:292-304 | crates/remote/src/routes/github_app.rs:423-435 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 5) crates/remote/src/routes/github_app.rs:138— crates/remote/src/routes/github_app.rs:138-147 | crates/remote/src/routes/github_app.rs:262-271 | crates/remote/src/routes/github_app.rs:295-304 | crates/remote/src/routes/github_app.rs:426-435 | crates/remote/src/routes/organizations.rs:155-164 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 5) crates/server/src/routes/execution_processes.rs:173— crates/server/src/routes/execution_processes.rs:173-182 | crates/server/src/routes/execution_processes.rs:247-256 | crates/server/src/routes/scratch.rs:128-137 | crates/server/src/routes/workspaces/streams.rs:71-80 | crates/server/src/routes/workspaces/streams.rs:114-123 — before extracting anything, compare `crates/server/src/routes/execution_processes.rs` and `crates/server/src/routes/scratch.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9–10 lines × 2) crates/remote/src/routes/review.rs:264— crates/remote/src/routes/review.rs:264-273 | crates/remote/src/routes/review.rs:294-302 — 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 (9–10 lines × 2) crates/worktree-manager/src/worktree_manager.rs:96— crates/worktree-manager/src/worktree_manager.rs:96-105 | crates/worktree-manager/src/worktree_manager.rs:408-416 — 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 (8 lines × 4) crates/executors/src/executors/amp.rs:59— crates/executors/src/executors/amp.rs:59-66 | crates/executors/src/executors/cursor.rs:200-207 | crates/executors/src/executors/cursor.rs:241-248 | crates/executors/src/executors/droid.rs:119-126 — before extracting anything, compare `crates/executors/src/executors/amp.rs` and `crates/executors/src/executors/cursor.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) crates/remote/src/routes/issues.rs:505— crates/remote/src/routes/issues.rs:505-512 | crates/remote/src/routes/pull_request_issues.rs:111-118 | crates/remote/src/routes/pull_requests.rs:105-112 | crates/remote/src/routes/pull_requests.rs:290-297 — before extracting anything, compare `crates/remote/src/routes/pull_request_issues.rs` and `crates/remote/src/routes/pull_requests.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) crates/server/src/routes/remote/issue_assignees.rs:63— crates/server/src/routes/remote/issue_assignees.rs:63-67 | crates/server/src/routes/remote/issue_relationships.rs:49-53 | crates/server/src/routes/remote/issue_tags.rs:58-62 | crates/server/src/routes/remote/issues.rs:75-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (5 lines × 4) crates/remote/src/routes/review.rs:324— crates/remote/src/routes/review.rs:324-328 | crates/remote/src/routes/review.rs:355-359 | crates/remote/src/routes/review.rs:370-374 | crates/remote/src/routes/review.rs:385-389 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication· Duplicated block with local edits (68 matched lines × 2 locations) · ×2
Duplicated block with local edits (68 matched lines × 2 locations) packages/ui/src/components/KanbanAssignee.tsx:22— packages/ui/src/components/KanbanAssignee.tsx:22 · packages/ui/src/components/UserAvatar.tsx:18 — the two spans are one implementation copied and then locally edited — 471 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 with local edits (68 matched lines × 2 locations) packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:280— packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:280 · packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:397 — the two spans are one implementation copied and then locally edited — 292 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 (44 matched lines × 2 locations) · ×2
Duplicated block with local edits (44 matched lines × 2 locations) packages/remote-web/src/app/providers/RemoteActionsProvider.tsx:178— packages/remote-web/src/app/providers/RemoteActionsProvider.tsx:178 · packages/web-core/src/shared/providers/ActionsProvider.tsx:322 — the two spans are one implementation copied and then locally edited — 131 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 with local edits (44 matched lines × 2 locations) packages/ui/src/components/FileTagTypeaheadPlugin.tsx:388— packages/ui/src/components/FileTagTypeaheadPlugin.tsx:388 · packages/ui/src/components/SlashCommandTypeaheadPlugin.tsx:107 — the two spans are one implementation copied and then locally edited — 239 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 (42 lines × 2 locations) packages/ui/src/components/ComponentInfoKeyboardPlugin.tsx:16— packages/ui/src/components/ComponentInfoKeyboardPlugin.tsx:16 · packages/ui/src/components/ImageKeyboardPlugin.tsx:16 — 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) packages/web-core/src/shared/dialogs/command-bar/BranchRebaseDialog.tsx:93— packages/web-core/src/shared/dialogs/command-bar/BranchRebaseDialog.tsx:93 · packages/web-core/src/shared/dialogs/command-bar/RebaseDialog.tsx:267 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×2
Duplicated block with local edits (41 matched lines × 2 locations) packages/web-core/src/integrations/remote/IssueProvider.tsx:16— packages/web-core/src/integrations/remote/IssueProvider.tsx:16 · packages/web-core/src/shared/providers/remote/ProjectProvider.tsx:31 — the two spans are one implementation copied and then locally edited — 286 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 with local edits (41 matched lines × 2 locations) packages/web-core/src/shared/dialogs/command-bar/SelectionDialog.tsx:107— packages/web-core/src/shared/dialogs/command-bar/SelectionDialog.tsx:107 · packages/web-core/src/shared/dialogs/command-bar/selections/ProjectSelectionDialog.tsx:278 — the two spans are one implementation copied and then locally edited — 247 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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 354 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.
KanbanIssuePanelContainer.KanbanIssuePanelContainer (cyclomatic 121) packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx:77— KanbanIssuePanelContainer.KanbanIssuePanelContainer has cyclomatic complexity 121 (threshold 15). Of this number, 17 points are the body's own statements and 104 belong to 30 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.
RemoteProjectsSettingsSection.RemoteProjectsSettingsSection (cyclomatic 107) packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:336— RemoteProjectsSettingsSection.RemoteProjectsSettingsSection has cyclomatic complexity 107 (threshold 15). Of this number, 29 points are the body's own statements and 78 belong to 30 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.
SessionChatBoxContainer.SessionChatBoxContainer (cyclomatic 100) packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:143— SessionChatBoxContainer.SessionChatBoxContainer has cyclomatic complexity 100 (threshold 15). Of this number, 34 points are the body's own statements and 66 belong to 30 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.
PreviewBrowserContainer.PreviewBrowserContainer (cyclomatic 98) REDACTED:174— PreviewBrowserContainer.PreviewBrowserContainer has cyclomatic complexity 98 (threshold 15). Most of this is not in the body itself: 8 of the 98 points are its own statements and the rest belongs to 30 function literals inside it that branch (lines 698, 272, 368, …). 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.
ConversationListContainer.ConversationList (cyclomatic 84) packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx:150— ConversationListContainer.ConversationList has cyclomatic complexity 84 (threshold 15). Of this number, 19 points are the body's own statements and 65 belong to 23 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.
LinkPrToIssueDialog.LinkPrToIssueContent (cyclomatic 80) packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:39— LinkPrToIssueDialog.LinkPrToIssueContent has cyclomatic complexity 80 (threshold 15). Of this number, 46 points are the body's own statements and 34 belong to 17 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.
ModelSelectorContainer.ModelSelectorContainer (cyclomatic 73) packages/web-core/src/shared/components/ModelSelectorContainer.tsx:60— ModelSelectorContainer.ModelSelectorContainer has cyclomatic complexity 73 (threshold 15). Of this number, 31 points are the body's own statements and 42 belong to 15 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.
RestoreLogsDialog.RestoreLogsDialogImpl (cyclomatic 71) packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:44— RestoreLogsDialog.RestoreLogsDialogImpl has cyclomatic complexity 71 (threshold 15). Of this number, 57 points are the body's own statements and 14 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.
KanbanContainer.KanbanContainer (cyclomatic 70) packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:125— KanbanContainer.KanbanContainer has cyclomatic complexity 70 (threshold 15). Most of this is not in the body itself: 9 of the 70 points are its own statements and the rest belongs to 28 function literals inside it that branch (lines 500, 659, 791, …). 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.
KanbanIssuePanel.KanbanIssuePanel (cyclomatic 69) packages/ui/src/components/KanbanIssuePanel.tsx:159— KanbanIssuePanel.KanbanIssuePanel has cyclomatic complexity 69 (threshold 15). Of this number, 49 points are the body's own statements and 20 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.
FileTagTypeaheadPlugin.FileTagTypeaheadPlugin (cyclomatic 67) packages/ui/src/components/FileTagTypeaheadPlugin.tsx:132— FileTagTypeaheadPlugin.FileTagTypeaheadPlugin has cyclomatic complexity 67 (threshold 15). Most of this is not in the body itself: 5 of the 67 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 454, 396, 195, …). 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.
PreviewBrowser.PreviewBrowser (cyclomatic 67) packages/ui/src/components/PreviewBrowser.tsx:94— PreviewBrowser.PreviewBrowser has cyclomatic complexity 67 (threshold 15). Of this number, 59 points are the body's own statements and 8 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.
ReposSettingsSection.ReposSettingsSection (cyclomatic 67) packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:130— ReposSettingsSection.ReposSettingsSection has cyclomatic complexity 67 (threshold 15). Of this number, 21 points are the body's own statements and 46 belong to 14 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.
image-node.createImageNode.ImageComponent (cyclomatic 66) packages/ui/src/components/image-node.tsx:189— image-node.createImageNode.ImageComponent has cyclomatic complexity 66 (threshold 15). Of this number, 49 points are the body's own statements and 17 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.
GitOperations.GitOperations (cyclomatic 65) packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:42— GitOperations.GitOperations has cyclomatic complexity 65 (threshold 15). Of this number, 33 points are the body's own statements and 32 belong to 15 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.
ScriptFixerDialog.ScriptFixerDialogImpl (cyclomatic 64) packages/web-core/src/shared/dialogs/scripts/ScriptFixerDialog.tsx:48— ScriptFixerDialog.ScriptFixerDialogImpl has cyclomatic complexity 64 (threshold 15). Of this number, 27 points are the body's own statements and 37 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.
GeneralSettingsSection.GeneralSettingsSection (cyclomatic 64) packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:57— GeneralSettingsSection.GeneralSettingsSection has cyclomatic complexity 64 (threshold 15). Of this number, 32 points are the body's own statements and 32 belong to 15 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.
OnboardingSignInPage.OnboardingSignInPage (cyclomatic 60) packages/web-core/src/features/onboarding/ui/OnboardingSignInPage.tsx:74— OnboardingSignInPage.OnboardingSignInPage has cyclomatic complexity 60 (threshold 15). Of this number, 32 points are the body's own statements and 28 belong to 8 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.
SessionChatBox.SessionChatBox (cyclomatic 59) packages/ui/src/components/SessionChatBox.tsx:223— SessionChatBox.SessionChatBox has cyclomatic complexity 59 (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 (SessionChatBox.SessionChatBox::renderActionButtons) 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.
AgentsSettingsSection.AgentsSettingsSection (cyclomatic 58) packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx:39— AgentsSettingsSection.AgentsSettingsSection has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 13 of the 58 points are its own statements and the rest belongs to 14 function items inside it that branch (deleteConfiguration, handleExecutorConfigSave, handleSave, …). 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.
OrganizationsSettingsSection.OrganizationsSettingsSection (cyclomatic 57) packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:45— OrganizationsSettingsSection.OrganizationsSettingsSection has cyclomatic complexity 57 (threshold 15). Of this number, 33 points are the body's own statements and 24 belong to 12 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.
McpSettingsSection.McpSettingsSection (cyclomatic 57) packages/web-core/src/shared/dialogs/settings/settings/McpSettingsSection.tsx:26— McpSettingsSection.McpSettingsSection has cyclomatic complexity 57 (threshold 15). Of this number, 23 points are the body's own statements and 34 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.
useCreateModeState.useCreateModeState (cyclomatic 56) packages/web-core/src/features/create-mode/model/useCreateModeState.ts:248— useCreateModeState.useCreateModeState has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 14 of the 56 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 406, 290, 499, …). 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.
CreateWorkspaceFromPrDialog.CreateWorkspaceFromPrDialogImpl (cyclomatic 55) packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:34— CreateWorkspaceFromPrDialog.CreateWorkspaceFromPrDialogImpl has cyclomatic complexity 55 (threshold 15). Of this number, 29 points are the body's own statements and 26 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.
AppNavigation.resolveLocalDestinationFromPath (cyclomatic 52) packages/local-web/src/app/navigation/AppNavigation.ts:28— AppNavigation.resolveLocalDestinationFromPath has cyclomatic complexity 52 (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.
SharedAppLayout.SharedAppLayout (cyclomatic 50) packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:59— SharedAppLayout.SharedAppLayout has cyclomatic complexity 50 (threshold 15). Of this number, 22 points are the body's own statements and 28 belong to 12 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.
RemoteCloudHostsSettingsCard.RemoteCloudHostsSettingsCardContent (cyclomatic 50) packages/web-core/src/shared/dialogs/settings/settings/RemoteCloudHostsSettingsCard.tsx:28— RemoteCloudHostsSettingsCard.RemoteCloudHostsSettingsCardContent has cyclomatic complexity 50 (threshold 15). Of this number, 21 points are the body's own statements and 29 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.
ChatFileEntry.ChatFileEntry (cyclomatic 49) packages/ui/src/components/ChatFileEntry.tsx:48— ChatFileEntry.ChatFileEntry has cyclomatic complexity 49 (threshold 15). Of this number, 45 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.
CreatePRDialog.CreatePRDialogImpl (cyclomatic 49) packages/web-core/src/shared/dialogs/command-bar/CreatePRDialog.tsx:61— CreatePRDialog.CreatePRDialogImpl has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 11 of the 49 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 177, a function literal at line 147, a function literal at line 113, …). 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.
WorkspacesLayout.WorkspacesLayout (cyclomatic 47) packages/web-core/src/pages/workspaces/WorkspacesLayout.tsx:47— WorkspacesLayout.WorkspacesLayout has cyclomatic complexity 47 (threshold 15). Of this number, 32 points are the body's own statements and 15 belong to 6 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.
CursorAgent::normalize_logs (cyclomatic 47) crates/executors/src/executors/cursor.rs:265— CursorAgent::normalize_logs has cyclomatic complexity 47 (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.
RemoteAppShell.RemoteAppShell (cyclomatic 46) packages/remote-web/src/app/layout/RemoteAppShell.tsx:54— RemoteAppShell.RemoteAppShell has cyclomatic complexity 46 (threshold 15). Of this number, 26 points are the body's own statements and 20 belong to 11 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.
WorkspacesSidebarContainer.WorkspacesSidebarContainer (cyclomatic 46) packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx:254— WorkspacesSidebarContainer.WorkspacesSidebarContainer has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 9 of the 46 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 481, 405, 441, …). 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.
LandingPage.LandingPage (cyclomatic 45) packages/web-core/src/features/onboarding/ui/LandingPage.tsx:149— LandingPage.LandingPage has cyclomatic complexity 45 (threshold 15). Of this number, 16 points are the body's own statements and 29 belong to 10 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.
ProjectSelectionDialog.ProjectSelectionContent (cyclomatic 43) packages/web-core/src/shared/dialogs/command-bar/selections/ProjectSelectionDialog.tsx:60— ProjectSelectionDialog.ProjectSelectionContent has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 4 of the 43 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 201, 115, 173, …). 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.
LocalContainerService::spawn_exit_monitor (cyclomatic 43) crates/local-deployment/src/container.rs:480— LocalContainerService::spawn_exit_monitor has cyclomatic complexity 43 (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.
CreateChatBoxContainer.CreateChatBoxContainer (cyclomatic 42) packages/web-core/src/shared/components/CreateChatBoxContainer.tsx:39— CreateChatBoxContainer.CreateChatBoxContainer has cyclomatic complexity 42 (threshold 15). Of this number, 19 points are the body's own statements and 23 belong to 8 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.
ProcessesTab.ProcessesTab (cyclomatic 41) packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:26— ProcessesTab.ProcessesTab has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 15 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 187, getStatusIcon, getStatusColor, …). 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.
IssueCommentsSectionContainer.IssueCommentsSectionContent (cyclomatic 40) packages/web-core/src/pages/kanban/IssueCommentsSectionContainer.tsx:58— IssueCommentsSectionContainer.IssueCommentsSectionContent has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 3 of the 40 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 224, 319, 260, …). 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.
ChangesPanelContainer.ChangesPanelContainer (cyclomatic 39) packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx:597— ChangesPanelContainer.ChangesPanelContainer has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 2 of the 39 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 724, 772, 609, …). 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.
WYSIWYGEditor.WYSIWYGEditor (cyclomatic 39) packages/web-core/src/shared/components/WYSIWYGEditor.tsx:251— WYSIWYGEditor.WYSIWYGEditor has cyclomatic complexity 39 (threshold 15). Of this number, 23 points are the body's own statements and 16 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.
KeyboardCommandsPlugin.KeyboardCommandsPlugin (cyclomatic 38) packages/ui/src/components/KeyboardCommandsPlugin.tsx:30— KeyboardCommandsPlugin.KeyboardCommandsPlugin has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 89, 154, 179, …). 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.
RelaySettingsSection.LocalRelaySettingsSectionContent (cyclomatic 38) packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx:188— RelaySettingsSection.LocalRelaySettingsSectionContent has cyclomatic complexity 38 (threshold 15). Of this number, 25 points are the body's own statements and 13 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.
ContextMenu.WebviewContextMenu (cyclomatic 37) packages/web-core/src/integrations/vscode/ContextMenu.tsx:68— ContextMenu.WebviewContextMenu has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to 10 function items inside it that branch (onCut, a function literal at line 79, onCopy, …). 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.
TerminalProvider.TerminalProvider (cyclomatic 36) packages/web-core/src/shared/providers/TerminalProvider.tsx:157— TerminalProvider.TerminalProvider has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 17 function literals inside it that branch (lines 344, 361, 197, …). 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.
ChatSubagentEntry.ChatSubagentEntry (cyclomatic 35) packages/ui/src/components/ChatSubagentEntry.tsx:40— ChatSubagentEntry.ChatSubagentEntry has cyclomatic complexity 35 (threshold 15). Of this number, 18 points are the body's own statements and 17 belong to 5 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.
useConversationHistory.useConversationHistory (cyclomatic 35) packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts:29— useConversationHistory.useConversationHistory has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 393, 437, 473, …). 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.
NavbarContainer.NavbarContainer (cyclomatic 35) packages/web-core/src/shared/components/ui-new/containers/NavbarContainer.tsx:116— NavbarContainer.NavbarContainer has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 15 of the 35 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 223, 162, 281, …). 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.
ToolCallState::apply_tool_data (cyclomatic 34) crates/executors/src/executors/opencode/normalize_logs.rs:1050— ToolCallState::apply_tool_data has cyclomatic complexity 34 (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.
AppNavigation.resolveRemoteDestinationFromPath (cyclomatic 33) packages/remote-web/src/app/navigation/AppNavigation.ts:19— AppNavigation.resolveRemoteDestinationFromPath has cyclomatic complexity 33 (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.
IssueWorkspaceCard.IssueWorkspaceCard (cyclomatic 32) packages/ui/src/components/IssueWorkspaceCard.tsx:110— IssueWorkspaceCard.IssueWorkspaceCard has cyclomatic complexity 32 (threshold 15). Of this number, 30 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.
Navbar.Navbar (cyclomatic 32) packages/ui/src/components/Navbar.tsx:185— Navbar.Navbar has cyclomatic complexity 32 (threshold 15). Of this number, 25 points are the body's own statements and 7 belong to 5 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.
ChatAggregatedDiffEntries.ChatAggregatedDiffEntries (cyclomatic 31) packages/ui/src/components/ChatAggregatedDiffEntries.tsx:184— ChatAggregatedDiffEntries.ChatAggregatedDiffEntries has cyclomatic complexity 31 (threshold 15). Of this number, 20 points are the body's own statements and 11 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.
FileTreeNode.FileTreeNode (cyclomatic 31) packages/ui/src/components/FileTreeNode.tsx:46— FileTreeNode.FileTreeNode has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 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.
WorkspaceSummary.WorkspaceSummary (cyclomatic 31) packages/ui/src/components/WorkspaceSummary.tsx:53— WorkspaceSummary.WorkspaceSummary has cyclomatic complexity 31 (threshold 15). Of this number, 29 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.
PendingApprovalEntry.PendingApprovalEntry (cyclomatic 31) packages/web-core/src/shared/components/NormalizedConversation/PendingApprovalEntry.tsx:172— PendingApprovalEntry.PendingApprovalEntry has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 214, 246, 297, …). 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.
AcpAgentHarness::bootstrap_acp_connection (cyclomatic 31) crates/executors/src/executors/acp/harness.rs:189— AcpAgentHarness::bootstrap_acp_connection 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.
preview_proxy::http_proxy_handler (cyclomatic 31) crates/preview-proxy/src/lib.rs:455— preview_proxy::http_proxy_handler 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.
AskUserQuestionBanner.AskUserQuestionBanner (cyclomatic 30) packages/ui/src/components/AskUserQuestionBanner.tsx:28— AskUserQuestionBanner.AskUserQuestionBanner has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 64, 104, 134, …). 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.
InputField.InputField (cyclomatic 30) packages/ui/src/components/InputField.tsx:22— InputField.InputField has cyclomatic complexity 30 (threshold 15). Of this number, 15 points are the body's own statements and 15 belong to 7 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.
ProjectRightSidebarContainer.ProjectRightSidebarContainer (cyclomatic 30) packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx:359— ProjectRightSidebarContainer.ProjectRightSidebarContainer has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 461, 425, 440, …). 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.
RepoCard.RepoCard (cyclomatic 29) packages/ui/src/components/RepoCard.tsx:68— RepoCard.RepoCard has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 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.
attachment-node.createAttachmentNode.AttachmentComponent (cyclomatic 29) packages/ui/src/components/attachment-node.tsx:156— attachment-node.createAttachmentNode.AttachmentComponent has cyclomatic complexity 29 (threshold 15). Of this number, 24 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.
useJsonPatchWsStream.useJsonPatchWsStream (cyclomatic 29) packages/web-core/src/shared/hooks/useJsonPatchWsStream.ts:33— useJsonPatchWsStream.useJsonPatchWsStream has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 65, a function literal at line 103, 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.
CodeBlockEscapePlugin.CodeBlockEscapePlugin (cyclomatic 28) packages/ui/src/components/CodeBlockEscapePlugin.tsx:23— CodeBlockEscapePlugin.CodeBlockEscapePlugin 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 29, 81, 63). 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.
PasteMarkdownPlugin.PasteMarkdownPlugin (cyclomatic 28) packages/ui/src/components/PasteMarkdownPlugin.tsx:29— PasteMarkdownPlugin.PasteMarkdownPlugin 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 7 function items inside it that branch (a function literal at line 52, a function literal at line 112, readRawClipboardText, …). 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.
useLogStream.useLogStream (cyclomatic 28) packages/web-core/src/shared/hooks/useLogStream.ts:12— useLogStream.useLogStream 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 9 function literals inside it that branch (lines 47, 83, 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.
useUiPreferencesStore.useUiPreferencesStore (cyclomatic 28) packages/web-core/src/shared/stores/useUiPreferencesStore.ts:448— useUiPreferencesStore.useUiPreferencesStore 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 13 function literals inside it that branch (lines 551, 576, 525, …). 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.
hosts.$hostId.workspaces.MobileWorkspacesList (cyclomatic 27) packages/remote-web/src/routes/hosts.$hostId.workspaces.tsx:46— hosts.$hostId.workspaces.MobileWorkspacesList has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 104). 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.
AppBar.AppBar (cyclomatic 27) packages/ui/src/components/AppBar.tsx:198— AppBar.AppBar has cyclomatic complexity 27 (threshold 15). Of this number, 17 points are the body's own statements and 10 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.
CommandBar.CommandBar (cyclomatic 27) packages/ui/src/components/CommandBar.tsx:180— CommandBar.CommandBar has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 266, 199). 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.
ChangesPanelContainer.DiffFileItem (cyclomatic 27) packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx:321— ChangesPanelContainer.DiffFileItem has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 440, 550, 372, …). 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.
SearchableTagDropdownContainer.SearchableTagDropdownContainer (cyclomatic 27) packages/web-core/src/shared/components/SearchableTagDropdownContainer.tsx:19— SearchableTagDropdownContainer.SearchableTagDropdownContainer has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 99, 37, 64, …). 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.
ResolveConflictsDialog.ResolveConflictsDialogImpl (cyclomatic 27) packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:47— ResolveConflictsDialog.ResolveConflictsDialogImpl has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 141, a function literal at line 99, a function literal at line 69, …). 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.
GitService::status_entry_to_diff (cyclomatic 27) crates/git/src/lib.rs:435— GitService::status_entry_to_diff has cyclomatic complexity 27 (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.
HomePage.HomePage (cyclomatic 26) packages/remote-web/src/pages/HomePage.tsx:38— HomePage.HomePage has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 6 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.
GitPanelContainer.GitPanelContainer (cyclomatic 26) packages/web-core/src/pages/workspaces/GitPanelContainer.tsx:23— GitPanelContainer.GitPanelContainer has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 61, 139, 37, …). 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.
LoginPage.LoginPage (cyclomatic 25) packages/remote-web/src/pages/LoginPage.tsx:20— LoginPage.LoginPage has cyclomatic complexity 25 (threshold 15). Of this number, 18 points are the body's own statements and 7 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.
SessionChatBox.SessionChatBox::renderActionButtons (cyclomatic 25) packages/ui/src/components/SessionChatBox.tsx:380— SessionChatBox.SessionChatBox::renderActionButtons 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: one other method here (SessionChatBox.SessionChatBox) 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.
WorkspacesSidebar.WorkspacesSidebar (cyclomatic 25) packages/ui/src/components/WorkspacesSidebar.tsx:169— WorkspacesSidebar.WorkspacesSidebar has cyclomatic complexity 25 (threshold 15). Of this number, 17 points are the body's own statements and 8 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.
createModeBootstrap.resolveCreateModeBootstrap (cyclomatic 25) packages/web-core/src/features/create-mode/model/createModeBootstrap.ts:83— createModeBootstrap.resolveCreateModeBootstrap 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.
FolderPickerDialog.FolderPickerDialogImpl (cyclomatic 25) packages/web-core/src/shared/dialogs/shared/FolderPickerDialog.tsx:35— FolderPickerDialog.FolderPickerDialogImpl has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (loadDirectory, a function literal at line 250, a function literal at line 49, …). 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.
notificationMessage.getGroupedNotificationSegments (cyclomatic 25) packages/web-core/src/shared/lib/notificationMessage.ts:71— notificationMessage.getGroupedNotificationSegments has cyclomatic complexity 25 (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.
SlashCommandTypeaheadPlugin.SlashCommandTypeaheadPlugin (cyclomatic 24) packages/ui/src/components/SlashCommandTypeaheadPlugin.tsx:46— SlashCommandTypeaheadPlugin.SlashCommandTypeaheadPlugin has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 129, 83, 69, …). 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.
useGitOperations.useGitOperations (cyclomatic 24) packages/web-core/src/shared/hooks/useGitOperations.ts:11— useGitOperations.useGitOperations has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 61, 21, 37, …). 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.
KanbanCardContent.KanbanCardContent (cyclomatic 23) packages/ui/src/components/KanbanCardContent.tsx:143— KanbanCardContent.KanbanCardContent has cyclomatic complexity 23 (threshold 15). 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, 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-row-model.classifyRowFamily (cyclomatic 23) packages/web-core/src/features/workspace-chat/model/conversation-row-model.ts:108— conversation-row-model.classifyRowFamily 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.
CreateModeRepoPickerBar.CreateModeRepoPickerBar (cyclomatic 23) packages/web-core/src/shared/components/CreateModeRepoPickerBar.tsx:73— CreateModeRepoPickerBar.CreateModeRepoPickerBar has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to 6 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.
AppNavigation.destinationToLocalTarget (cyclomatic 22) packages/local-web/src/app/navigation/AppNavigation.ts:175— AppNavigation.destinationToLocalTarget 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.
FileTreeContainer.FileTreeContainer (cyclomatic 22) packages/web-core/src/pages/workspaces/FileTreeContainer.tsx:33— FileTreeContainer.FileTreeContainer has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 159, 59, 133, …). 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.
StartReviewDialog.StartReviewDialogImpl (cyclomatic 22) packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:37— StartReviewDialog.StartReviewDialogImpl 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 5 function items inside it that branch (a function literal at line 83, a function literal at line 57, handleNewSessionChange, …). 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.
appNavigation.resolveKanbanRouteState (cyclomatic 22) packages/web-core/src/shared/lib/routes/appNavigation.ts:198— appNavigation.resolveKanbanRouteState has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 2 function literals inside it that branch. 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.
ChatAggregatedToolEntries.ChatAggregatedToolEntries (cyclomatic 21) packages/ui/src/components/ChatAggregatedToolEntries.tsx:28— ChatAggregatedToolEntries.ChatAggregatedToolEntries has cyclomatic complexity 21 (threshold 15). Of this number, 14 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.
CreateOrganizationDialog.CreateOrganizationDialogImpl (cyclomatic 21) packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:24— CreateOrganizationDialog.CreateOrganizationDialogImpl 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 7 function items inside it that branch (validateSlug, validateName, a function literal at line 56, …). 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.
useAzureAttachments.useAzureAttachments.uploadFiles (cyclomatic 21) packages/web-core/src/shared/hooks/useAzureAttachments.ts:153— useAzureAttachments.useAzureAttachments.uploadFiles has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 9 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.
CursorToolCall::to_action_and_content (cyclomatic 21) crates/executors/src/executors/cursor.rs:904— CursorToolCall::to_action_and_content 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. This is NOT this file's highest cyclomatic complexity: executors::executors::cursor::resolve_cursor_model_name (cyclomatic 37) 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 function is counted neither in this dimension's figures nor in its score.
KeyboardDialog.Dialog (cyclomatic 20) packages/ui/src/components/KeyboardDialog.tsx:29— KeyboardDialog.Dialog has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 61, 89, 115, …). 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.
ChatAggregatedDiffEntries.DiffEntry (cyclomatic 20) packages/ui/src/components/ChatAggregatedDiffEntries.tsx:111— ChatAggregatedDiffEntries.DiffEntry has cyclomatic complexity 20 (threshold 15). Of this number, 18 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.
BranchSelector.BranchSelector (cyclomatic 20) packages/web-core/src/shared/components/tasks/BranchSelector.tsx:103— BranchSelector.BranchSelector has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 234, 161, 184, …). 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.
CommandBarDialog.CommandBarContent (cyclomatic 20) packages/web-core/src/shared/dialogs/command-bar/CommandBarDialog.tsx:38— CommandBarDialog.CommandBarContent has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 105, 67, 88, …). 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.
OAuthDialog.OAuthDialogImpl::renderContent (cyclomatic 20) packages/web-core/src/shared/dialogs/global/OAuthDialog.tsx:244— OAuthDialog.OAuthDialogImpl::renderContent has cyclomatic complexity 20 (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.
AssigneeSelectionDialog.AssigneeSelectionContent (cyclomatic 20) packages/web-core/src/shared/dialogs/kanban/AssigneeSelectionDialog.tsx:50— AssigneeSelectionDialog.AssigneeSelectionContent has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 166, 145, 117, …). 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.
TagEditDialog.TagEditDialogImpl (cyclomatic 20) packages/web-core/src/shared/dialogs/shared/TagEditDialog.tsx:27— TagEditDialog.TagEditDialogImpl has cyclomatic complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 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.
PrCommentsDialog.PrCommentsDialogImpl (cyclomatic 20) packages/web-core/src/shared/dialogs/tasks/PrCommentsDialog.tsx:36— PrCommentsDialog.PrCommentsDialogImpl has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 5 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.
hooks.useShape (cyclomatic 20) packages/web-core/src/shared/integrations/electric/hooks.ts:86— hooks.useShape has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 125, 149, 221, …). 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.
ActionsProvider.ActionsProvider (cyclomatic 20) packages/web-core/src/shared/providers/ActionsProvider.tsx:42— ActionsProvider.ActionsProvider has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 267, 97, 228, …). 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.
LogState::update_tool_status (cyclomatic 20) crates/executors/src/executors/codex/normalize_logs.rs:488— LogState::update_tool_status 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.
WebRtcClient::connect (cyclomatic 20) crates/relay-webrtc/src/client.rs:262— WebRtcClient::connect 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.
AppNavigation.destinationToRemoteTarget (cyclomatic 19) packages/remote-web/src/app/navigation/AppNavigation.ts:115— AppNavigation.destinationToRemoteTarget has cyclomatic complexity 19 (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.
ChatEntryContainer.ChatEntryContainer (cyclomatic 19) packages/ui/src/components/ChatEntryContainer.tsx:64— ChatEntryContainer.ChatEntryContainer has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 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.
component-info-node.ComponentInfoComponent (cyclomatic 19) REDACTED:49— component-info-node.ComponentInfoComponent 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.
IssueWorkspacesSectionContainer.IssueWorkspacesSectionContainer (cyclomatic 19) packages/web-core/src/pages/kanban/IssueWorkspacesSectionContainer.tsx:34— IssueWorkspacesSectionContainer.IssueWorkspacesSectionContainer has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 239, 210, 54, …). 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.
RetryEditorInline.RetryEditorInline (cyclomatic 19) packages/web-core/src/shared/components/NormalizedConversation/RetryEditorInline.tsx:19— RetryEditorInline.RetryEditorInline has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 99, 70, 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.
WorkspaceSelectionDialog.WorkspaceSelectionContent (cyclomatic 19) packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx:58— WorkspaceSelectionDialog.WorkspaceSelectionContent has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 116, 279, 138, …). 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.
RemoteProjectsSettingsSection.StatusRow (cyclomatic 19) packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:155— RemoteProjectsSettingsSection.StatusRow has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 207, handleNameKeyDown, handleNameBlur, …). 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.
useIssueShortcuts.useIssueShortcuts (cyclomatic 19) packages/web-core/src/shared/keyboard/useIssueShortcuts.ts:23— useIssueShortcuts.useIssueShortcuts 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 10 function literals inside it that branch (lines 82, 215, 70, …). 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.
FileTree.FileTree (cyclomatic 18) packages/ui/src/components/FileTree.tsx:49— FileTree.FileTree has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
ModelList.ModelList (cyclomatic 18) packages/ui/src/components/ModelList.tsx:122— ModelList.ModelList has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 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.
useCreateModeState.draftReducer (cyclomatic 18) packages/web-core/src/features/create-mode/model/useCreateModeState.ts:91— useCreateModeState.draftReducer 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, 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.
useKanbanFilters.useKanbanFilters.filteredIssues (cyclomatic 18) packages/web-core/src/features/kanban/model/hooks/useKanbanFilters.ts:74— useKanbanFilters.useKanbanFilters.filteredIssues has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 114, 151, 85, …). 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.
CreateRemoteProjectDialog.CreateRemoteProjectDialogImpl (cyclomatic 18) packages/web-core/src/shared/dialogs/org/CreateRemoteProjectDialog.tsx:36— CreateRemoteProjectDialog.CreateRemoteProjectDialogImpl has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (validateName, handleCreate, handleKeyDown, …). 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.
SettingsDialog.SettingsDialogContent (cyclomatic 18) packages/web-core/src/shared/dialogs/settings/SettingsDialog.tsx:155— SettingsDialog.SettingsDialogContent 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 4 function literals inside it that branch (lines 164, 190, 219, …). 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.
useIssueSelectionStore.useIssueSelectionStore (cyclomatic 18) packages/web-core/src/shared/stores/useIssueSelectionStore.ts:28— useIssueSelectionStore.useIssueSelectionStore 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 3 function literals inside it that branch (lines 93, 34, 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.
Server::run (cyclomatic 18) crates/remote/src/app.rs:33— Server::run 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.
RemoteNavbarContainer.RemoteNavbarContainer (cyclomatic 17) packages/remote-web/src/app/layout/RemoteNavbarContainer.tsx:106— RemoteNavbarContainer.RemoteNavbarContainer has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 192, 154, 174, …). 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.
SequenceTracker.SequenceTrackerProvider (cyclomatic 17) packages/web-core/src/shared/keyboard/SequenceTracker.tsx:51— SequenceTracker.SequenceTrackerProvider has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 95, 147, 67, …). 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.
SshSessionHandler::spawn_stdio_session (cyclomatic 17) crates/embedded-ssh/src/handler.rs:48— SshSessionHandler::spawn_stdio_session has cyclomatic complexity 17 (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.
PlainTextLogProcessor::process (cyclomatic 17) crates/executors/src/logs/plain_text_processor.rs:194— PlainTextLogProcessor::process 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.
cli.extractAndRun (cyclomatic 16) REDACTED:126— cli.extractAndRun 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.
ToolbarPlugin.ToolbarPlugin (cyclomatic 16) packages/ui/src/components/ToolbarPlugin.tsx:46— ToolbarPlugin.ToolbarPlugin 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 76, 56, 137, …). 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.
useTodos.useTodos (cyclomatic 16) packages/web-core/src/features/workspace-chat/model/hooks/useTodos.ts:16— useTodos.useTodos 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 2 function literals inside it that branch (lines 17, 38). 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.
useConversationVirtualizer.useConversationVirtualizer (cyclomatic 16) packages/web-core/src/features/workspace-chat/model/useConversationVirtualizer.ts:148— useConversationVirtualizer.useConversationVirtualizer 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 299, 263, 195, …). 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.
DisplayConversationEntry.AggregatedGroupEntry (cyclomatic 16) packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx:1138— DisplayConversationEntry.AggregatedGroupEntry 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 3 function items inside it that branch (getDisplayProps, a function literal at line 1148, a function literal at line 1198). 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. This is NOT this file's highest cyclomatic complexity: DisplayConversationEntry.DisplayConversationEntry (cyclomatic 17) 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.
GhCliSetupDialog.GhCliSetupDialogImpl (cyclomatic 16) packages/web-core/src/shared/dialogs/auth/GhCliSetupDialog.tsx:124— GhCliSetupDialog.GhCliSetupDialogImpl has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (handleRunSetup, handleRunSetup::isGhCliSetupError, handleClose, …). 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.
RebaseDialog.RebaseDialogContent::handleConfirm (cyclomatic 16) packages/web-core/src/shared/dialogs/command-bar/RebaseDialog.tsx:171— RebaseDialog.RebaseDialogContent::handleConfirm 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.
fileTreeUtils.buildFileTree (cyclomatic 16) packages/web-core/src/shared/lib/fileTreeUtils.ts:7— fileTreeUtils.buildFileTree 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.
JsonRpcPeer::spawn (cyclomatic 16) crates/executors/src/executors/codex/jsonrpc.rs:67— JsonRpcPeer::spawn 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.
McpServer::list_issues (cyclomatic 16) crates/mcp/src/task_server/tools/remote_issues.rs:322— McpServer::list_issues has cyclomatic complexity 16 (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.
getComponentInfo (cyclomatic 16) REDACTED:191— getComponentInfo has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 234). 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.
FixmeComment crates/services/src/services/filesystem_watcher.rs:149— // FIXME: capture file-type information earlier (e.g., when we add — 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.
KanbanIssuePanelContainer.KanbanIssuePanelContainer (cognitive 149) packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx:77— KanbanIssuePanelContainer.KanbanIssuePanelContainer has cognitive complexity 149 (threshold 15). Drivers by points: if/else 69 (93 pts), boolean chains 36, ternaries 9 (10 pts), loops 4 (9 pts), error handling 1 (nesting depth added 30). Most of this is not in the body itself: 13 of the 149 points are its own statements and the rest belongs to 30 function literals inside it that branch (lines 655, 818, 472, …). 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.
CursorAgent::normalize_logs (cognitive 124) crates/executors/src/executors/cursor.rs:265— CursorAgent::normalize_logs has cognitive complexity 124 (threshold 15). Drivers by points: if/else 32 (87 pts), match/switch 6 (25 pts), boolean chains 7, loops 3 (5 pts) (nesting depth added 76). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PreviewBrowser.PreviewBrowser (cognitive 121) packages/ui/src/components/PreviewBrowser.tsx:94— PreviewBrowser.PreviewBrowser has cognitive complexity 121 (threshold 15). Drivers by points: ternaries 30 (85 pts), boolean chains 25, if/else 4 (10 pts), match/switch 1 (nesting depth added 61). Of this number, 109 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RemoteProjectsSettingsSection.RemoteProjectsSettingsSection (cognitive 113) packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:336— RemoteProjectsSettingsSection.RemoteProjectsSettingsSection has cognitive complexity 113 (threshold 15). Drivers by points: if/else 40 (50 pts), boolean chains 28, ternaries 14 (23 pts), error handling 8, loops 4 (nesting depth added 19). Of this number, 29 points are the body's own statements and 84 belong to 30 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.
SessionChatBoxContainer.SessionChatBoxContainer (cognitive 105) packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:143— SessionChatBoxContainer.SessionChatBoxContainer has cognitive complexity 105 (threshold 15). Drivers by points: if/else 39 (48 pts), ternaries 24 (28 pts), boolean chains 21, error handling 4, loops 2 (4 pts) (nesting depth added 15). Of this number, 28 points are the body's own statements and 77 belong to 30 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.
PreviewBrowserContainer.PreviewBrowserContainer (cognitive 93) REDACTED:174— PreviewBrowserContainer.PreviewBrowserContainer has cognitive complexity 93 (threshold 15). Drivers by points: if/else 50 (56 pts), boolean chains 22, ternaries 14 (15 pts) (nesting depth added 7). Most of this is not in the body itself: 7 of the 93 points are its own statements and the rest belongs to 30 function literals inside it that branch (lines 368, 698, 272, …). 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.
ConversationListContainer.ConversationList (cognitive 84) packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx:150— ConversationListContainer.ConversationList has cognitive complexity 84 (threshold 15). Drivers by points: if/else 48 (59 pts), boolean chains 20, loops 4, ternaries 1 (nesting depth added 11). Most of this is not in the body itself: 11 of the 84 points are its own statements and the rest belongs to 23 function items inside it that branch (a function literal at line 704, a function literal at line 476, a function literal at line 566, …). 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.
ScriptFixerDialog.ScriptFixerDialogImpl (cognitive 84) packages/web-core/src/shared/dialogs/scripts/ScriptFixerDialog.tsx:48— ScriptFixerDialog.ScriptFixerDialogImpl has cognitive complexity 84 (threshold 15). Drivers by points: ternaries 22 (43 pts), if/else 16 (21 pts), boolean chains 17, error handling 3 (nesting depth added 26). Of this number, 26 points are the body's own statements and 58 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.
image-node.createImageNode.ImageComponent (cognitive 83) packages/ui/src/components/image-node.tsx:189— image-node.createImageNode.ImageComponent has cognitive complexity 83 (threshold 15). Drivers by points: if/else 29 (48 pts), boolean chains 29, ternaries 5 (6 pts) (nesting depth added 20). Of this number, 62 points are the body's own statements and 21 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.
FileTagTypeaheadPlugin.FileTagTypeaheadPlugin (cognitive 75) packages/ui/src/components/FileTagTypeaheadPlugin.tsx:132— FileTagTypeaheadPlugin.FileTagTypeaheadPlugin has cognitive complexity 75 (threshold 15). Drivers by points: if/else 30 (42 pts), boolean chains 19, ternaries 6, loops 2 (5 pts), error handling 3 (nesting depth added 15). Most of this is not in the body itself: 2 of the 75 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 396, 454, 195, …). 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.
KanbanContainer.KanbanContainer (cognitive 75) packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:125— KanbanContainer.KanbanContainer has cognitive complexity 75 (threshold 15). Drivers by points: if/else 31 (46 pts), boolean chains 12, ternaries 8 (9 pts), loops 8 (nesting depth added 16). Most of this is not in the body itself: 9 of the 75 points are its own statements and the rest belongs to 28 function literals inside it that branch (lines 450, 543, 659, …). 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.
ModelSelectorContainer.ModelSelectorContainer (cognitive 71) packages/web-core/src/shared/components/ModelSelectorContainer.tsx:60— ModelSelectorContainer.ModelSelectorContainer has cognitive complexity 71 (threshold 15). Drivers by points: if/else 23 (29 pts), ternaries 22 (24 pts), boolean chains 17, loops 1 (nesting depth added 8). Of this number, 25 points are the body's own statements and 46 belong to 15 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.
preview_proxy::http_proxy_handler (cognitive 71) crates/preview-proxy/src/lib.rs:455— preview_proxy::http_proxy_handler has cognitive complexity 71 (threshold 15). Drivers by points: if/else 21 (44 pts), loops 6 (18 pts), boolean chains 5, match/switch 3 (4 pts) (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CreatePRDialog.CreatePRDialogImpl (cognitive 69) packages/web-core/src/shared/dialogs/command-bar/CreatePRDialog.tsx:61— CreatePRDialog.CreatePRDialogImpl has cognitive complexity 69 (threshold 15). Drivers by points: ternaries 13 (29 pts), if/else 21 (24 pts), boolean chains 15, error handling 1 (nesting depth added 19). Most of this is not in the body itself: 14 of the 69 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 177, a function literal at line 147, a function literal at line 113, …). 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.
ReposSettingsSection.ReposSettingsSection (cognitive 69) packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:130— ReposSettingsSection.ReposSettingsSection has cognitive complexity 69 (threshold 15). Drivers by points: if/else 26 (31 pts), boolean chains 24, ternaries 7 (10 pts), error handling 3, loops 1 (nesting depth added 8). Of this number, 17 points are the body's own statements and 52 belong to 14 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.
SessionChatBox.SessionChatBox (cognitive 61) packages/ui/src/components/SessionChatBox.tsx:223— SessionChatBox.SessionChatBox has cognitive complexity 61 (threshold 15). Drivers by points: ternaries 23 (53 pts), boolean chains 43, if/else 22 (26 pts), match/switch 1 (nesting depth added 34). 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 (SessionChatBox.SessionChatBox::renderActionButtons) 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.
GeneralSettingsSection.GeneralSettingsSection (cognitive 61) packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:57— GeneralSettingsSection.GeneralSettingsSection has cognitive complexity 61 (threshold 15). Drivers by points: boolean chains 24, if/else 21 (22 pts), ternaries 10 (12 pts), error handling 2, loops 1 (nesting depth added 3). Of this number, 29 points are the body's own statements and 32 belong to 15 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.
LinkPrToIssueDialog.LinkPrToIssueContent (cognitive 60) packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:39— LinkPrToIssueDialog.LinkPrToIssueContent has cognitive complexity 60 (threshold 15). Drivers by points: boolean chains 24, if/else 22 (23 pts), ternaries 7 (8 pts), match/switch 3 (4 pts), error handling 1 (nesting depth added 3). Of this number, 28 points are the body's own statements and 32 belong to 17 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.
ProjectSelectionDialog.ProjectSelectionContent (cognitive 59) packages/web-core/src/shared/dialogs/command-bar/selections/ProjectSelectionDialog.tsx:60— ProjectSelectionDialog.ProjectSelectionContent has cognitive complexity 59 (threshold 15). Drivers by points: if/else 31 (45 pts), loops 5 (8 pts), boolean chains 4, match/switch 1, ternaries 1 (nesting depth added 17). Most of this is not in the body itself: 3 of the 59 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 201, 115, 99, …). 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.
AgentsSettingsSection.AgentsSettingsSection (cognitive 56) packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx:39— AgentsSettingsSection.AgentsSettingsSection has cognitive complexity 56 (threshold 15). Drivers by points: boolean chains 23, if/else 17 (19 pts), error handling 8 (10 pts), ternaries 3 (4 pts) (nesting depth added 5). Most of this is not in the body itself: 11 of the 56 points are its own statements and the rest belongs to 14 function items inside it that branch (deleteConfiguration, a function literal at line 78, createConfiguration, …). 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.
GitOperations.GitOperations (cognitive 55) packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:42— GitOperations.GitOperations has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 19, if/else 19, ternaries 9 (15 pts), error handling 2 (nesting depth added 6). Of this number, 21 points are the body's own statements and 34 belong to 15 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.
fileTreeUtils.buildFileTree (cognitive 55) packages/web-core/src/shared/lib/fileTreeUtils.ts:7— fileTreeUtils.buildFileTree has cognitive complexity 55 (threshold 15). Drivers by points: if/else 7 (27 pts), ternaries 4 (20 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 40). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ToolCallState::apply_tool_data (cognitive 55) crates/executors/src/executors/opencode/normalize_logs.rs:1050— ToolCallState::apply_tool_data has cognitive complexity 55 (threshold 15). Drivers by points: if/else 21 (48 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 30). 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.
KanbanIssuePanel.KanbanIssuePanel (cognitive 54) packages/ui/src/components/KanbanIssuePanel.tsx:159— KanbanIssuePanel.KanbanIssuePanel has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 31, if/else 9 (13 pts), ternaries 9 (10 pts) (nesting depth added 5). Of this number, 33 points are the body's own statements and 21 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.
IssueCommentsSectionContainer.IssueCommentsSectionContent (cognitive 54) packages/web-core/src/pages/kanban/IssueCommentsSectionContainer.tsx:58— IssueCommentsSectionContainer.IssueCommentsSectionContent has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (24 pts), ternaries 9 (14 pts), boolean chains 6, error handling 3 (5 pts), loops 3 (5 pts) (nesting depth added 15). Most of this is not in the body itself: 2 of the 54 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 260, 319, 224, …). 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.
ProcessesTab.ProcessesTab (cognitive 53) packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:26— ProcessesTab.ProcessesTab has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 13 (33 pts), boolean chains 10, if/else 6, error handling 2, match/switch 2 (nesting depth added 20). Of this number, 24 points are the body's own statements and 29 belong to 8 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CreateWorkspaceFromPrDialog.CreateWorkspaceFromPrDialogImpl (cognitive 53) packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:34— CreateWorkspaceFromPrDialog.CreateWorkspaceFromPrDialogImpl has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 9 (20 pts), boolean chains 16, if/else 13, match/switch 2 (4 pts) (nesting depth added 13). Of this number, 32 points are the body's own statements and 21 belong to 11 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.
AcpAgentHarness::bootstrap_acp_connection (cognitive 53) crates/executors/src/executors/acp/harness.rs:189— AcpAgentHarness::bootstrap_acp_connection has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (28 pts), match/switch 9 (17 pts), loops 5, boolean chains 3 (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.
OnboardingSignInPage.OnboardingSignInPage (cognitive 52) packages/web-core/src/features/onboarding/ui/OnboardingSignInPage.tsx:74— OnboardingSignInPage.OnboardingSignInPage has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 21, ternaries 9 (16 pts), if/else 13 (14 pts), match/switch 1 (nesting depth added 8). Of this number, 29 points are the body's own statements and 23 belong to 8 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.
useCreateModeState.useCreateModeState (cognitive 49) packages/web-core/src/features/create-mode/model/useCreateModeState.ts:248— useCreateModeState.useCreateModeState has cognitive complexity 49 (threshold 15). Drivers by points: if/else 29, boolean chains 14, ternaries 4, error handling 2. Most of this is not in the body itself: 8 of the 49 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 406, 290, 451, …). 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.
ChangesPanelContainer.ChangesPanelContainer (cognitive 48) packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx:597— ChangesPanelContainer.ChangesPanelContainer has cognitive complexity 48 (threshold 15). Drivers by points: if/else 27 (37 pts), loops 4 (5 pts), boolean chains 4, ternaries 2 (nesting depth added 11). Most of this is not in the body itself: 1 of the 48 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 724, 772, 710, …). 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.
SharedAppLayout.SharedAppLayout (cognitive 47) packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:59— SharedAppLayout.SharedAppLayout has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 20, if/else 15 (16 pts), ternaries 6 (8 pts), error handling 3 (nesting depth added 3). Of this number, 18 points are the body's own statements and 29 belong to 12 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.
WorkspacesSidebarContainer.WorkspacesSidebarContainer (cognitive 46) packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx:254— WorkspacesSidebarContainer.WorkspacesSidebarContainer has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 11, ternaries 9 (10 pts), loops 3 (nesting depth added 2). Most of this is not in the body itself: 8 of the 46 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 481, 405, 441, …). 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.
OrganizationsSettingsSection.OrganizationsSettingsSection (cognitive 46) packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:45— OrganizationsSettingsSection.OrganizationsSettingsSection has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 16, ternaries 7 (9 pts), error handling 3 (nesting depth added 3). Of this number, 19 points are the body's own statements and 27 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.
WorkspacesLayout.WorkspacesLayout (cognitive 45) packages/web-core/src/pages/workspaces/WorkspacesLayout.tsx:47— WorkspacesLayout.WorkspacesLayout has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 21, if/else 11 (13 pts), ternaries 8 (11 pts) (nesting depth added 5). Of this number, 27 points are the body's own statements and 18 belong to 6 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.
CreateChatBoxContainer.CreateChatBoxContainer (cognitive 45) packages/web-core/src/shared/components/CreateChatBoxContainer.tsx:39— CreateChatBoxContainer.CreateChatBoxContainer has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 9 (16 pts), boolean chains 12 (nesting depth added 9). Of this number, 20 points are the body's own statements and 25 belong to 8 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.
ChatFileEntry.ChatFileEntry (cognitive 43) packages/ui/src/components/ChatFileEntry.tsx:48— ChatFileEntry.ChatFileEntry has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 24, ternaries 10 (15 pts), if/else 4 (nesting depth added 5). Of this number, 39 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.
RestoreLogsDialog.RestoreLogsDialogImpl (cognitive 43) packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:44— RestoreLogsDialog.RestoreLogsDialogImpl has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 34, ternaries 5, if/else 4. Of this number, 32 points are the body's own statements and 11 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.
ContextMenu.WebviewContextMenu (cognitive 42) packages/web-core/src/integrations/vscode/ContextMenu.tsx:68— ContextMenu.WebviewContextMenu has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 9, error handling 5 (8 pts) (nesting depth added 7). Most of this is not in the body itself: 3 of the 42 points are its own statements and the rest belongs to 10 function items inside it that branch (onCut, onCopy, 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.
RemoteCloudHostsSettingsCard.RemoteCloudHostsSettingsCardContent (cognitive 42) packages/web-core/src/shared/dialogs/settings/settings/RemoteCloudHostsSettingsCard.tsx:28— RemoteCloudHostsSettingsCard.RemoteCloudHostsSettingsCardContent has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17, boolean chains 13, ternaries 7 (10 pts), error handling 2 (nesting depth added 3). Of this number, 16 points are the body's own statements and 26 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.
LandingPage.LandingPage (cognitive 41) packages/web-core/src/features/onboarding/ui/LandingPage.tsx:149— LandingPage.LandingPage has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 17, ternaries 12, if/else 11, error handling 1. Most of this is not in the body itself: 13 of the 41 points are its own statements and the rest belongs to 10 function items inside it that branch (handleContinue, a function literal at line 485, a function literal at line 214, …). 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.
OAuthDialog.OAuthDialogImpl (cognitive 41) packages/web-core/src/shared/dialogs/global/OAuthDialog.tsx:35— OAuthDialog.OAuthDialogImpl has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 15, ternaries 4 (6 pts), error handling 1, match/switch 1 (nesting depth added 5). None of this is in the body itself: all 41 points belong to 11 function items inside it that branch (a function literal at line 107, renderContent, 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.
FolderPickerDialog.FolderPickerDialogImpl (cognitive 41) packages/web-core/src/shared/dialogs/shared/FolderPickerDialog.tsx:35— FolderPickerDialog.FolderPickerDialogImpl has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 9 (26 pts), boolean chains 8, if/else 6, error handling 1 (nesting depth added 17). Most of this is not in the body itself: 12 of the 41 points are its own statements and the rest belongs to 9 function items inside it that branch (loadDirectory, a function literal at line 250, a function literal at line 49, …). 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.
KeyboardCommandsPlugin.KeyboardCommandsPlugin (cognitive 40) packages/ui/src/components/KeyboardCommandsPlugin.tsx:30— KeyboardCommandsPlugin.KeyboardCommandsPlugin has cognitive complexity 40 (threshold 15). Drivers by points: if/else 24 (28 pts), boolean chains 9, ternaries 1 (2 pts), loops 1 (nesting depth added 5). None of this is in the body itself: all 40 points belong to 8 function literals inside it that branch (lines 89, 179, 60, …). 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.
useConversationHistory.useConversationHistory (cognitive 40) packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts:29— useConversationHistory.useConversationHistory has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (27 pts), boolean chains 5, loops 5, ternaries 1 (3 pts) (nesting depth added 9). None of this is in the body itself: all 40 points belong to 8 function literals inside it that branch (lines 393, 437, 364, …). 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.
WYSIWYGEditor.WYSIWYGEditor (cognitive 40) packages/web-core/src/shared/components/WYSIWYGEditor.tsx:251— WYSIWYGEditor.WYSIWYGEditor has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 17, ternaries 7 (10 pts), if/else 7 (9 pts), error handling 3, loops 1 (nesting depth added 5). Of this number, 22 points are the body's own statements and 18 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.
AppNavigation.resolveLocalDestinationFromPath (cognitive 39) packages/local-web/src/app/navigation/AppNavigation.ts:28— AppNavigation.resolveLocalDestinationFromPath has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 14 (28 pts), boolean chains 9, if/else 1, match/switch 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.
RemoteAppShell.RemoteAppShell (cognitive 39) packages/remote-web/src/app/layout/RemoteAppShell.tsx:54— RemoteAppShell.RemoteAppShell has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 17, if/else 12, ternaries 6 (9 pts), error handling 1 (nesting depth added 3). Of this number, 20 points are the body's own statements and 19 belong to 11 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.
useAzureAttachments.useAzureAttachments.uploadFiles (cognitive 39) packages/web-core/src/shared/hooks/useAzureAttachments.ts:153— useAzureAttachments.useAzureAttachments.uploadFiles has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 8 (19 pts), if/else 7 (14 pts), boolean chains 2, error handling 1 (2 pts), loops 2 (nesting depth added 19). Of this number, 21 points are the body's own statements and 18 belong to 9 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.
JsonRpcPeer::spawn (cognitive 39) crates/executors/src/executors/codex/jsonrpc.rs:67— JsonRpcPeer::spawn has cognitive complexity 39 (threshold 15). Drivers by points: if/else 5 (24 pts), match/switch 4 (14 pts), loops 1 (nesting depth added 29). 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.
PasteMarkdownPlugin.PasteMarkdownPlugin (cognitive 38) packages/ui/src/components/PasteMarkdownPlugin.tsx:29— PasteMarkdownPlugin.PasteMarkdownPlugin has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 6, error handling 2 (3 pts) (nesting depth added 13). None of this is in the body itself: all 38 points belong to 7 function items inside it that branch (a function literal at line 52, a function literal at line 112, readRawClipboardText, …). 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.
CommandBar.CommandBar (cognitive 37) packages/ui/src/components/CommandBar.tsx:180— CommandBar.CommandBar has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 8, loops 2 (3 pts), ternaries 1 (nesting depth added 12). Most of this is not in the body itself: 2 of the 37 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 199, 266). 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.
WorkspacesSidebar.WorkspacesSidebar (cognitive 36) packages/ui/src/components/WorkspacesSidebar.tsx:169— WorkspacesSidebar.WorkspacesSidebar has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (22 pts), boolean chains 11, if/else 3 (nesting depth added 14). Of this number, 28 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
createModeBootstrap.resolveCreateModeBootstrap (cognitive 36) packages/web-core/src/features/create-mode/model/createModeBootstrap.ts:83— createModeBootstrap.resolveCreateModeBootstrap has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 7, ternaries 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.
PrCommentsDialog.PrCommentsDialogImpl (cognitive 35) packages/web-core/src/shared/dialogs/tasks/PrCommentsDialog.tsx:36— PrCommentsDialog.PrCommentsDialogImpl has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 9 (27 pts), if/else 5, boolean chains 3 (nesting depth added 18). Of this number, 17 points are the body's own statements and 18 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NavbarContainer.NavbarContainer (cognitive 33) packages/web-core/src/shared/components/ui-new/containers/NavbarContainer.tsx:116— NavbarContainer.NavbarContainer has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 13, ternaries 5 (6 pts) (nesting depth added 2). Most of this is not in the body itself: 12 of the 33 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 223, 162, 281, …). 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.
ExecutorConfigs::compute_overrides (cognitive 32) crates/executors/src/profile.rs:361— ExecutorConfigs::compute_overrides has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 4 (7 pts), boolean chains 1 (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.
AskUserQuestionBanner.AskUserQuestionBanner (cognitive 30) packages/ui/src/components/AskUserQuestionBanner.tsx:28— AskUserQuestionBanner.AskUserQuestionBanner has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 12, loops 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 64, 104, 45, …). 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.
ChatSubagentEntry.ChatSubagentEntry (cognitive 30) packages/ui/src/components/ChatSubagentEntry.tsx:40— ChatSubagentEntry.ChatSubagentEntry has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, if/else 10, ternaries 5. Of this number, 15 points are the body's own statements and 15 belong to 5 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.
PendingApprovalEntry.PendingApprovalEntry (cognitive 30) packages/web-core/src/shared/components/NormalizedConversation/PendingApprovalEntry.tsx:172— PendingApprovalEntry.PendingApprovalEntry has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 13, if/else 10 (12 pts), ternaries 3 (4 pts), error handling 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 214, 246, 229, …). 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.
Navbar.Navbar (cognitive 29) packages/ui/src/components/Navbar.tsx:185— Navbar.Navbar has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 15, ternaries 7 (12 pts), if/else 2 (nesting depth added 5). Of this number, 25 points are the body's own statements and 4 belong to 5 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.
ProjectRightSidebarContainer.ProjectRightSidebarContainer (cognitive 29) packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx:359— ProjectRightSidebarContainer.ProjectRightSidebarContainer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 461, 425, 380, …). 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.
AssigneeSelectionDialog.AssigneeSelectionContent (cognitive 29) packages/web-core/src/shared/dialogs/kanban/AssigneeSelectionDialog.tsx:50— AssigneeSelectionDialog.AssigneeSelectionContent has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 166, 117, 145, …). 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.
RelaySettingsSection.LocalRelaySettingsSectionContent (cognitive 29) packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx:188— RelaySettingsSection.LocalRelaySettingsSectionContent has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 17, if/else 9, error handling 2, ternaries 1. Of this number, 18 points are the body's own statements and 11 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.
TerminalProvider.TerminalProvider (cognitive 29) packages/web-core/src/shared/providers/TerminalProvider.tsx:157— TerminalProvider.TerminalProvider has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 13, error handling 1 (nesting depth added 1). None of this is in the body itself: all 29 points belong to 17 function literals inside it that branch (lines 344, 210, 197, …). 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.
ChatAggregatedDiffEntries.ChatAggregatedDiffEntries (cognitive 28) packages/ui/src/components/ChatAggregatedDiffEntries.tsx:184— ChatAggregatedDiffEntries.ChatAggregatedDiffEntries has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 17, if/else 5 (6 pts), ternaries 4, loops 1 (nesting depth added 1). 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, 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.
WebRtcClient::connect (cognitive 28) crates/relay-webrtc/src/client.rs:262— WebRtcClient::connect has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 3 (6 pts), boolean chains 2, loops 2 (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.
getComponentInfo (cognitive 28) REDACTED:191— getComponentInfo has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (7 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 14). Most of this is not in the body itself: 3 of the 28 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 198, 234). 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.
cli.extractAndRun (cognitive 27) REDACTED:126— cli.extractAndRun has cognitive complexity 27 (threshold 15). Drivers by points: error handling 5 (10 pts), ternaries 3 (9 pts), if/else 7 (8 pts) (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.
InputField.InputField (cognitive 27) packages/ui/src/components/InputField.tsx:22— InputField.InputField has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 8, ternaries 3 (5 pts) (nesting depth added 5). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (getBorderClass, handleKeyDown, a function literal at line 47, …). 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.
useUiPreferencesStore.useUiPreferencesStore (cognitive 27) packages/web-core/src/shared/stores/useUiPreferencesStore.ts:448— useUiPreferencesStore.useUiPreferencesStore has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16, boolean chains 5, ternaries 4 (5 pts), error handling 1 (nesting depth added 1). None of this is in the body itself: all 27 points belong to 13 function literals inside it that branch (lines 551, 770, 525, …). 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.
AppNavigation.resolveRemoteDestinationFromPath (cognitive 26) packages/remote-web/src/app/navigation/AppNavigation.ts:19— AppNavigation.resolveRemoteDestinationFromPath has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 6, if/else 1, match/switch 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.
CodeBlockEscapePlugin.CodeBlockEscapePlugin (cognitive 26) packages/ui/src/components/CodeBlockEscapePlugin.tsx:23— CodeBlockEscapePlugin.CodeBlockEscapePlugin has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13, boolean chains 11, ternaries 2. None of this is in the body itself: all 26 points belong to 3 function literals inside it that branch (lines 29, 81, 63). 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.
IssueWorkspaceCard.IssueWorkspaceCard (cognitive 26) packages/ui/src/components/IssueWorkspaceCard.tsx:110— IssueWorkspaceCard.IssueWorkspaceCard has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 18, ternaries 4 (8 pts) (nesting depth added 4). Of this number, 21 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.
SessionChatBox.SessionChatBox::renderActionButtons (cognitive 26) packages/ui/src/components/SessionChatBox.tsx:380— SessionChatBox.SessionChatBox::renderActionButtons has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 7 (10 pts), boolean chains 3, match/switch 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. This shape REPEATS in the file: one other method here (SessionChatBox.SessionChatBox) 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.
ChangesPanelContainer.DiffFileItem (cognitive 26) packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx:321— ChangesPanelContainer.DiffFileItem has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10 (11 pts), boolean chains 9, if/else 6 (nesting depth added 1). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 440, 550, 372, …). 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.
GitPanelContainer.GitPanelContainer (cognitive 26) packages/web-core/src/pages/workspaces/GitPanelContainer.tsx:23— GitPanelContainer.GitPanelContainer has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 10, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 26 points belong to 11 function literals inside it that branch (lines 61, 139, 37, …). 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.
ResolveConflictsDialog.ResolveConflictsDialogImpl (cognitive 26) packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:47— ResolveConflictsDialog.ResolveConflictsDialogImpl has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11, boolean chains 10, ternaries 3 (4 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 141, a function literal at line 99, a function literal at line 69, …). 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.
PlainTextLogProcessor::process (cognitive 26) crates/executors/src/logs/plain_text_processor.rs:194— PlainTextLogProcessor::process has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 2 (3 pts), match/switch 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.
GitHubOAuthProvider::validate_token (cognitive 26) crates/remote/src/auth/provider.rs:275— GitHubOAuthProvider::validate_token has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (19 pts), match/switch 2 (4 pts), boolean chains 2, loops 1 (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.
GoogleOAuthProvider::validate_token (cognitive 26) crates/remote/src/auth/provider.rs:608— GoogleOAuthProvider::validate_token has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (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.
AppBar.AppBar (cognitive 25) packages/ui/src/components/AppBar.tsx:198— AppBar.AppBar has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 5 (8 pts), boolean chains 6, match/switch 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 9 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.
attachment-node.createAttachmentNode.AttachmentComponent (cognitive 25) packages/ui/src/components/attachment-node.tsx:156— attachment-node.createAttachmentNode.AttachmentComponent has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Of this number, 20 points are the body's own statements and 5 belong to 3 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.
component-info-node.ComponentInfoComponent (cognitive 25) REDACTED:49— component-info-node.ComponentInfoComponent has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 7, if/else 4 (7 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.
useJsonPatchWsStream.useJsonPatchWsStream (cognitive 25) packages/web-core/src/shared/hooks/useJsonPatchWsStream.ts:33— useJsonPatchWsStream.useJsonPatchWsStream has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, error handling 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 65, a function literal at line 103, a function literal at line 208, …). 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.
utils::diff::extract_unified_diff_hunks (cognitive 25) crates/utils/src/diff.rs:79— utils::diff::extract_unified_diff_hunks has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (23 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.
SettingsDialog.SettingsDialogContent (cognitive 24) packages/web-core/src/shared/dialogs/settings/SettingsDialog.tsx:155— SettingsDialog.SettingsDialogContent has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 8 (9 pts), boolean chains 5 (nesting depth added 7). Of this number, 12 points are the body's own statements and 12 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.
usePreviewNavigation.usePreviewNavigation.handleMessage (cognitive 24) packages/web-core/src/shared/hooks/usePreviewNavigation.ts:21— usePreviewNavigation.usePreviewNavigation.handleMessage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (22 pts), boolean chains 1, match/switch 1 (nesting depth added 14). 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.
aggregateEntries.aggregateConsecutiveEntries (cognitive 24) packages/web-core/src/shared/lib/aggregateEntries.ts:178— aggregateEntries.aggregateConsecutiveEntries has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (23 pts), loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 6 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.
review::claude_session::extract_session_metadata (cognitive 24) crates/review/src/claude_session.rs:199— review::claude_session::extract_session_metadata has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 3, match/switch 2 (3 pts), 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.
SlashCommandTypeaheadPlugin.SlashCommandTypeaheadPlugin (cognitive 23) packages/ui/src/components/SlashCommandTypeaheadPlugin.tsx:46— SlashCommandTypeaheadPlugin.SlashCommandTypeaheadPlugin has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10, boolean chains 9, ternaries 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 129, 83, 69, …). 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.
WorkspaceSummary.WorkspaceSummary (cognitive 23) packages/ui/src/components/WorkspaceSummary.tsx:53— WorkspaceSummary.WorkspaceSummary has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 19, ternaries 3, if/else 1. Of this number, 21 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.
SearchableTagDropdownContainer.SearchableTagDropdownContainer (cognitive 23) packages/web-core/src/shared/components/SearchableTagDropdownContainer.tsx:19— SearchableTagDropdownContainer.SearchableTagDropdownContainer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 99, 37, 64, …). 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.
CommandBarDialog.CommandBarContent (cognitive 23) packages/web-core/src/shared/dialogs/command-bar/CommandBarDialog.tsx:38— CommandBarDialog.CommandBarContent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 4, ternaries 3 (nesting depth added 4). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 105, 67, 88, …). 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.
PrMonitorService::sync_pending_to_remote (cognitive 23) crates/services/src/services/pr_monitor.rs:214— PrMonitorService::sync_pending_to_remote has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 3 (5 pts), 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.
hosts.$hostId.workspaces.MobileWorkspacesList (cognitive 22) packages/remote-web/src/routes/hosts.$hostId.workspaces.tsx:46— hosts.$hostId.workspaces.MobileWorkspacesList has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, ternaries 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 104). 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.
ContextUsageGauge.ContextUsageGauge (cognitive 22) packages/ui/src/components/ContextUsageGauge.tsx:20— ContextUsageGauge.ContextUsageGauge has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 7, boolean chains 1 (nesting depth added 7). Of this number, 12 points are the body's own statements and 10 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.
DataTable.DataTable (cognitive 22) packages/ui/src/components/DataTable.tsx:31— DataTable.DataTable has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (16 pts), if/else 1 (4 pts), boolean chains 2 (nesting depth added 12). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 66, 70). 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.
IssueWorkspacesSectionContainer.IssueWorkspacesSectionContainer (cognitive 22) packages/web-core/src/pages/kanban/IssueWorkspacesSectionContainer.tsx:34— IssueWorkspacesSectionContainer.IssueWorkspacesSectionContainer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9, ternaries 3 (6 pts), error handling 2 (3 pts), boolean chains 2, loops 2 (nesting depth added 4). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 210, 239, 54, …). 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.
CreateModeRepoPickerBar.CreateModeRepoPickerBar (cognitive 22) packages/web-core/src/shared/components/CreateModeRepoPickerBar.tsx:73— CreateModeRepoPickerBar.CreateModeRepoPickerBar has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 5 (6 pts), error handling 1 (nesting depth added 1). Of this number, 11 points are the body's own statements and 11 belong to 6 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.
StartReviewDialog.StartReviewDialogImpl (cognitive 22) packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:37— StartReviewDialog.StartReviewDialogImpl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 3 (4 pts), error handling 1 (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 5 function items inside it that branch (a function literal at line 83, a function literal at line 57, handleNewSessionChange, …). 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.
RemoteProjectsSettingsSection.StatusRow (cognitive 22) packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:155— RemoteProjectsSettingsSection.StatusRow has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 6 (7 pts), boolean chains 6 (nesting depth added 2). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 207, handleNameKeyDown, handleNameBlur, …). 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.
usePreviewUrl.detectPreviewUrl (cognitive 22) REDACTED:151— usePreviewUrl.detectPreviewUrl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (5 pts), boolean chains 3, error handling 1 (2 pts), 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.
useIssueShortcuts.useIssueShortcuts (cognitive 22) packages/web-core/src/shared/keyboard/useIssueShortcuts.ts:23— useIssueShortcuts.useIssueShortcuts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 1, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 22 points belong to 10 function literals inside it that branch (lines 82, 215, 70, …). 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.
SshSessionHandler::spawn_stdio_session (cognitive 22) crates/embedded-ssh/src/handler.rs:48— SshSessionHandler::spawn_stdio_session has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 5 (7 pts), loops 4 (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.
Codex::handle_app_server_slash_command (cognitive 22) crates/executors/src/executors/codex/slash_commands.rs:142— Codex::handle_app_server_slash_command has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 9). 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.
Server::run (cognitive 22) crates/remote/src/app.rs:33— Server::run has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15, match/switch 4 (5 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.
PierreConversationDiff.useDiffData (cognitive 21) packages/ui/src/components/PierreConversationDiff.tsx:168— PierreConversationDiff.useDiffData has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 9). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 172). 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.
ExportChooseProjects.ExportChooseProjects (cognitive 21) packages/web-core/src/features/export/ui/ExportChooseProjects.tsx:28— ExportChooseProjects.ExportChooseProjects has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 6, boolean chains 3 (nesting depth added 7). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 50, handleSelectAll, handleContinue, …). 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.
bridge.installVSCodeIframeKeyboardBridge::onKeyDown (cognitive 21) REDACTED:353— bridge.installVSCodeIframeKeyboardBridge::onKeyDown has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), error handling 2 (4 pts) (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.
RebaseDialog.RebaseDialogContent::handleConfirm (cognitive 21) packages/web-core/src/shared/dialogs/command-bar/RebaseDialog.tsx:171— RebaseDialog.RebaseDialogContent::handleConfirm has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, ternaries 1 (2 pts), error handling 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.
McpSettingsSection.McpSettingsSection (cognitive 21) packages/web-core/src/shared/dialogs/settings/settings/McpSettingsSection.tsx:26— McpSettingsSection.McpSettingsSection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 19 (27 pts), ternaries 13 (23 pts), boolean chains 16, error handling 5 (7 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: one other method here (McpSettingsSection.McpSettingsSection::handleApplyMcpServers) 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.
TagEditDialog.TagEditDialogImpl (cognitive 21) packages/web-core/src/shared/dialogs/shared/TagEditDialog.tsx:27— TagEditDialog.TagEditDialogImpl has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 8, ternaries 3, error handling 1. Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (handleSave, a function literal at line 40, a function literal at line 135, …). 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.
useLogStream.useLogStream (cognitive 21) packages/web-core/src/shared/hooks/useLogStream.ts:12— useLogStream.useLogStream has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 7, error handling 1 (nesting depth added 2). None of this is in the body itself: all 21 points belong to 9 function literals inside it that branch (lines 47, 83, 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.
McpServer::list_issues (cognitive 21) crates/mcp/src/task_server/tools/remote_issues.rs:322— McpServer::list_issues has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 11 (15 pts), if/else 3 (4 pts), boolean chains 1, loops 1 (nesting depth added 5). 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.
ChatAggregatedToolEntries.ChatAggregatedToolEntries (cognitive 20) packages/ui/src/components/ChatAggregatedToolEntries.tsx:28— ChatAggregatedToolEntries.ChatAggregatedToolEntries has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 5 (7 pts), if/else 4 (nesting depth added 2). Of this number, 15 points are the body's own statements and 5 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.
ModelList.ModelList (cognitive 20) packages/ui/src/components/ModelList.tsx:122— ModelList.ModelList has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 9 (nesting depth added 4). Of this number, 10 points are the body's own statements and 10 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.
useTodos.useTodos (cognitive 20) packages/web-core/src/features/workspace-chat/model/hooks/useTodos.ts:16— useTodos.useTodos has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 3 (9 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 17, 38). 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.
FileTreeContainer.FileTreeContainer (cognitive 20) packages/web-core/src/pages/workspaces/FileTreeContainer.tsx:33— FileTreeContainer.FileTreeContainer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, boolean chains 5, ternaries 2. None of this is in the body itself: all 20 points belong to 11 function literals inside it that branch (lines 159, 59, 66, …). 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.
McpSettingsSection.McpSettingsSection::handleApplyMcpServers (cognitive 20) packages/web-core/src/shared/dialogs/settings/settings/McpSettingsSection.tsx:133— McpSettingsSection.McpSettingsSection::handleApplyMcpServers has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (6 pts), error handling 2 (3 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. This shape REPEATS in the file: one other method here (McpSettingsSection.McpSettingsSection) 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.
CursorToolCall::to_action_and_content (cognitive 20) crates/executors/src/executors/cursor.rs:904— CursorToolCall::to_action_and_content has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1, match/switch 1 (nesting depth added 8). 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.
getComponentInfo (cognitive 20) REDACTED:542— getComponentInfo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, loops 1 (3 pts), ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 554). 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.
devtools_script.ensureCurrentInStack (cognitive 19) REDACTED:108— devtools_script.ensureCurrentInStack has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, loops 1 (2 pts) (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.
ClickedElementsProvider.pruneValue (cognitive 19) packages/local-web/src/app/providers/ClickedElementsProvider.tsx:169— ClickedElementsProvider.pruneValue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 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.
RemoteNavbarContainer.RemoteNavbarContainer (cognitive 19) packages/remote-web/src/app/layout/RemoteNavbarContainer.tsx:106— RemoteNavbarContainer.RemoteNavbarContainer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 192, 154, 174, …). 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.
HomePage.HomePage (cognitive 19) packages/remote-web/src/pages/HomePage.tsx:38— HomePage.HomePage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5 (7 pts), boolean chains 3, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 100, 59, 66, …). 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.
FileTreeNode.FileTreeNode (cognitive 19) packages/ui/src/components/FileTreeNode.tsx:46— FileTreeNode.FileTreeNode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 2, ternaries 2. 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, 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.
KanbanFilterBar.KanbanFilterBar (cognitive 19) packages/ui/src/components/KanbanFilterBar.tsx:109— KanbanFilterBar.KanbanFilterBar has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (15 pts), boolean chains 4 (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.
CreateOrganizationDialog.CreateOrganizationDialogImpl (cognitive 19) packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:24— CreateOrganizationDialog.CreateOrganizationDialogImpl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 4, ternaries 2. Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (validateSlug, validateName, a function literal at line 56, …). 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.
notificationMessage.getGroupedNotificationSegments (cognitive 19) packages/web-core/src/shared/lib/notificationMessage.ts:71— notificationMessage.getGroupedNotificationSegments has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, match/switch 2 (3 pts), ternaries 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.
ActionsProvider.ActionsProvider (cognitive 19) packages/web-core/src/shared/providers/ActionsProvider.tsx:42— ActionsProvider.ActionsProvider has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 267, 97, 228, …). 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.
useIssueSelectionStore.useIssueSelectionStore (cognitive 19) packages/web-core/src/shared/stores/useIssueSelectionStore.ts:28— useIssueSelectionStore.useIssueSelectionStore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5 (6 pts), boolean chains 4 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 93, 34, 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.
conversation-row-model.classifyRowFamily (cognitive 18) packages/web-core/src/features/workspace-chat/model/conversation-row-model.ts:108— conversation-row-model.classifyRowFamily has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1, match/switch 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.
deriveConversationEntries.deriveConversationEntries.entries (cognitive 18) packages/web-core/src/features/workspace-chat/model/deriveConversationEntries.ts:166— deriveConversationEntries.deriveConversationEntries.entries has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2 (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.
useScrollCommandExecutor.executeIntent (cognitive 18) packages/web-core/src/features/workspace-chat/model/useScrollCommandExecutor.ts:236— useScrollCommandExecutor.executeIntent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 1, match/switch 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.
RetryEditorInline.RetryEditorInline (cognitive 18) packages/web-core/src/shared/components/NormalizedConversation/RetryEditorInline.tsx:19— RetryEditorInline.RetryEditorInline has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 5, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 99, 70, 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.
useGitOperations.useGitOperations (cognitive 18) packages/web-core/src/shared/hooks/useGitOperations.ts:11— useGitOperations.useGitOperations has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (6 pts), ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 61, 21, 37, …). 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.
hooks.useShape (cognitive 18) packages/web-core/src/shared/integrations/electric/hooks.ts:86— hooks.useShape has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, ternaries 2, loops 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 125, 233, 149, …). 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.
SequenceTracker.SequenceTrackerProvider (cognitive 18) packages/web-core/src/shared/keyboard/SequenceTracker.tsx:51— SequenceTracker.SequenceTrackerProvider has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 2, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 95, 147, 67, …). 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.
Opencode::discover_options (cognitive 18) crates/executors/src/executors/opencode.rs:527— Opencode::discover_options has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 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.
NotificationService::play_sound_notification (cognitive 18) crates/services/src/services/notification.rs:95— NotificationService::play_sound_notification has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, match/switch 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.
KeyboardDialog.Dialog (cognitive 17) packages/ui/src/components/KeyboardDialog.tsx:29— KeyboardDialog.Dialog has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 1. Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 89, 61, 42, …). 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.
ChatEntryContainer.ChatEntryContainer (cognitive 17) packages/ui/src/components/ChatEntryContainer.tsx:64— ChatEntryContainer.ChatEntryContainer has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, ternaries 4, if/else 2. Of this number, 13 points are the body's own statements and 4 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.
IssueSubIssuesSection.IssueSubIssuesSection (cognitive 17) packages/ui/src/components/IssueSubIssuesSection.tsx:35— IssueSubIssuesSection.IssueSubIssuesSection has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (15 pts), boolean chains 2 (nesting depth added 9). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 57, 77). 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.
BranchSelector.BranchSelector (cognitive 17) packages/web-core/src/shared/components/tasks/BranchSelector.tsx:103— BranchSelector.BranchSelector has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 3, ternaries 2 (3 pts), loops 1, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 161, 184, 147, …). 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.
CreateRemoteProjectDialog.CreateRemoteProjectDialogImpl (cognitive 17) packages/web-core/src/shared/dialogs/org/CreateRemoteProjectDialog.tsx:36— CreateRemoteProjectDialog.CreateRemoteProjectDialogImpl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 4, ternaries 2 (3 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (handleCreate, validateName, a function literal at line 63, …). 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.
terminalTheme.hslToHex (cognitive 17) packages/web-core/src/shared/lib/terminalTheme.ts:6— terminalTheme.hslToHex has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (hue2rgb, toHex). 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.
AppServerClient::on_notification (cognitive 17) crates/executors/src/executors/codex/client.rs:852— AppServerClient::on_notification has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 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.
AzCli::parse_pr_url (cognitive 17) crates/git-host/src/azure/cli.rs:407— AzCli::parse_pr_url has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1 (2 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.
buildStackEntries (cognitive 17) REDACTED:124— buildStackEntries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 6, loops 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.
AppNavigation.destinationToLocalTarget (cognitive 16) packages/local-web/src/app/navigation/AppNavigation.ts:175— AppNavigation.destinationToLocalTarget has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 1, ternaries 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.
LoginPage.LoginPage (cognitive 16) packages/remote-web/src/pages/LoginPage.tsx:20— LoginPage.LoginPage has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 2 (4 pts), error handling 2, if/else 1 (nesting depth added 2). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (handleLogin, handleLocalLogin). 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.
DataChannelWebSocket.handleFrame (cognitive 16) packages/remote-web/src/shared/lib/webrtc/dataChannelWebSocket.ts:138— DataChannelWebSocket.handleFrame has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (6 pts), 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.
KanbanCardContent.KanbanCardContent (cognitive 16) packages/ui/src/components/KanbanCardContent.tsx:143— KanbanCardContent.KanbanCardContent has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, ternaries 3, if/else 1. Of this number, 14 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.
migrate-remote-web-structure.run (cognitive 16) scripts/migrate-remote-web-structure.mjs:166— migrate-remote-web-structure.run has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (6 pts), loops 2 (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.
GitCli::get_worktree_status (cognitive 16) crates/git/src/cli.rs:231— GitCli::get_worktree_status has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 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.
local_deployment::copy::copy_project_files_impl (cognitive 16) crates/local-deployment/src/copy.rs:18— local_deployment::copy::copy_project_files_impl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), match/switch 1 (2 pts) (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.
Cross-context type AppBarHostStatus (ui → web-core) packages/web-core/src/shared/hooks/useRemoteCloudHosts.ts:9— AppBarHostStatus (context ui) is exposed in web-core's public surface via RemoteCloudHostStatus.RemoteCloudHostStatus — couples the contexts.
Cross-context type RepoAction (ui → web-core) packages/web-core/src/shared/stores/useUiPreferencesStore.ts:848— RepoAction (context ui) is exposed in web-core's public surface via useUiPreferencesStore.useRepoAction — couples the contexts.
D4 · Code Duplication· Near-duplicate member family (4 members, 23 shared lines) · ×1
Near-duplicate member family (4 members, 23 shared lines) crates/executors/src/executors/amp.rs:53— crates/executors/src/executors/amp.rs:53-82 | crates/executors/src/executors/amp.rs:91-125 | crates/executors/src/executors/cursor.rs:191-222 | crates/executors/src/executors/cursor.rs:231-263 — These 4 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 19 shared lines) · ×1
Near-duplicate member family (4 members, 19 shared lines) crates/executors/src/executors/amp.rs:53— crates/executors/src/executors/amp.rs:53-82 | crates/executors/src/executors/cursor.rs:191-222 | crates/executors/src/executors/cursor.rs:231-263 | crates/executors/src/executors/droid.rs:116-141 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Near-duplicate member pair (61 shared lines) crates/remote/src/routes/organization_members.rs:367— crates/remote/src/routes/organization_members.rs:367-463 | crates/remote/src/routes/organization_members.rs:470-581 — These two members are variants of one another: 61 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (48 shared lines) crates/executors/src/executors/claude.rs:409— crates/executors/src/executors/claude.rs:409-565 | crates/executors/src/executors/opencode.rs:531-754 — These two members are variants of one another: 48 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (44 shared lines) crates/server/src/routes/workspaces/codex_setup.rs:24— crates/server/src/routes/workspaces/codex_setup.rs:24-77 | crates/server/src/routes/workspaces/cursor_setup.rs:24-75 — These two members are variants of one another: 44 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) crates/server/src/middleware/relay_request_signature.rs:135— crates/server/src/middleware/relay_request_signature.rs:135-178 | crates/server/src/middleware/relay_request_signature.rs:183-257 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) crates/db/src/models/merge.rs:113— crates/db/src/models/merge.rs:113-150 | crates/db/src/models/merge.rs:157-195 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) crates/remote/src/routes/issues.rs:348— crates/remote/src/routes/issues.rs:348-399 | crates/remote/src/routes/issues.rs:495-584 | crates/remote/src/routes/notifications.rs:128-170 | crates/remote/src/routes/notifications.rs:181-223 | crates/remote/src/routes/notifications.rs:234-311 | crates/remote/src/routes/project_statuses.rs:243-349 | crates/remote/src/routes/projects.rs:187-270 | crates/remote/src/routes/pull_request_issues.rs:107-187 | crates/remote/src/routes/pull_request_issues.rs:198-239 | crates/remote/src/routes/pull_requests.rs:99-170 | crates/remote/src/routes/pull_requests.rs:181-257 | crates/remote/src/routes/pull_requests.rs:268-369 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) crates/executors/src/executors/opencode/sdk.rs:815— crates/executors/src/executors/opencode/sdk.rs:815-830 | crates/executors/src/executors/opencode/sdk.rs:836-851 | crates/executors/src/executors/opencode/sdk.rs:857-872 | crates/executors/src/executors/opencode/sdk.rs:878-893 | crates/executors/src/executors/opencode/sdk.rs:899-914 | crates/executors/src/executors/opencode/sdk.rs:920-935 | crates/executors/src/executors/opencode/sdk.rs:941-956 | crates/executors/src/executors/opencode/sdk.rs:962-977 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/server/src/routes/execution_processes.rs:171— crates/server/src/routes/execution_processes.rs:171-201 | crates/server/src/routes/execution_processes.rs:239-274 | crates/server/src/routes/scratch.rs:121-155 | crates/server/src/routes/workspaces/streams.rs:60-98 | crates/server/src/routes/workspaces/streams.rs:105-141 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (35 lines × 2) crates/remote/src/routes/organization_members.rs:375— crates/remote/src/routes/organization_members.rs:375-409 | crates/remote/src/routes/organization_members.rs:478-512 — 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 (30–31 lines × 2) crates/executors/src/executors/copilot.rs:197— crates/executors/src/executors/copilot.rs:197-226 | crates/executors/src/executors/droid.rs:238-268 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (29–30 lines × 2) crates/server/src/routes/workspaces/execution.rs:179— crates/server/src/routes/workspaces/execution.rs:179-208 | crates/server/src/routes/workspaces/execution.rs:245-273 — 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 (28 lines × 2) crates/remote/src/routes/issue_comments.rs:169— crates/remote/src/routes/issue_comments.rs:169-196 | crates/remote/src/routes/issue_comments.rs:222-249 — 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 (27 lines × 2) crates/server/src/middleware/relay_request_signature.rs:141— crates/server/src/middleware/relay_request_signature.rs:141-167 | crates/server/src/middleware/relay_request_signature.rs:213-239 — 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 (25 lines × 2) crates/server/src/routes/workspaces/streams.rs:74— crates/server/src/routes/workspaces/streams.rs:74-98 | crates/server/src/routes/workspaces/streams.rs:117-141 — 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 (24 lines × 2) crates/executors/src/executors/acp/harness.rs:93— crates/executors/src/executors/acp/harness.rs:93-116 | crates/executors/src/executors/acp/harness.rs:146-169 — 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 (23–24 lines × 2) crates/server/src/routes/workspaces/cursor_setup.rs:121— crates/server/src/routes/workspaces/cursor_setup.rs:121-144 | crates/server/src/routes/workspaces/gh_cli_setup.rs:110-132 — before extracting anything, compare `crates/server/src/routes/workspaces/cursor_setup.rs` and `crates/server/src/routes/workspaces/gh_cli_setup.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–22 lines × 2) crates/executors/src/mcp_config.rs:246— crates/executors/src/mcp_config.rs:246-263 | crates/executors/src/mcp_config.rs:293-314 — 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 (21 lines × 2) crates/relay-tunnel/src/server_bin/auth.rs:140— crates/relay-tunnel/src/server_bin/auth.rs:140-160 | crates/remote/src/auth/middleware.rs:74-94 — before extracting anything, compare `crates/relay-tunnel/src/server_bin/auth.rs` and `crates/remote/src/auth/middleware.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 3) crates/server/src/routes/workspaces/codex_setup.rs:58— crates/server/src/routes/workspaces/codex_setup.rs:58-77 | crates/server/src/routes/workspaces/cursor_setup.rs:56-75 | crates/server/src/routes/workspaces/gh_cli_setup.rs:51-70 — before extracting anything, compare `crates/server/src/routes/workspaces/codex_setup.rs` and `crates/server/src/routes/workspaces/cursor_setup.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17–18 lines × 3) crates/executors/src/executors/amp.rs:59— crates/executors/src/executors/amp.rs:59-76 | crates/executors/src/executors/cursor.rs:200-216 | crates/executors/src/executors/cursor.rs:241-257 — before extracting anything, compare `crates/executors/src/executors/amp.rs` and `crates/executors/src/executors/cursor.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16–17 lines × 2) crates/db/src/models/merge.rs:134— crates/db/src/models/merge.rs:134-150 | crates/db/src/models/merge.rs:180-195 — 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 (15–17 lines × 2) crates/executors/src/executors/opencode/sdk.rs:635— crates/executors/src/executors/opencode/sdk.rs:635-651 | crates/executors/src/executors/opencode/sdk.rs:721-735 — 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 (15–16 lines × 3) crates/remote/src/routes/github_app.rs:259— crates/remote/src/routes/github_app.rs:259-273 | crates/remote/src/routes/github_app.rs:292-307 | crates/remote/src/routes/github_app.rs:423-437 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 3) crates/remote/src/routes/notifications.rs:98— crates/remote/src/routes/notifications.rs:98-113 | crates/remote/src/routes/notifications.rs:135-150 | crates/remote/src/routes/notifications.rs:188-203 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–16 lines × 2) crates/remote/src/routes/github_app.rs:195— crates/remote/src/routes/github_app.rs:195-206 | crates/remote/src/routes/github_app.rs:351-366 — 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 (15–16 lines × 2) crates/server/src/routes/workspaces/execution.rs:162— crates/server/src/routes/workspaces/execution.rs:162-177 | crates/server/src/routes/workspaces/execution.rs:229-243 — 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 (15 lines × 4) crates/server/src/routes/execution_processes.rs:174— crates/server/src/routes/execution_processes.rs:174-188 | crates/server/src/routes/execution_processes.rs:248-262 | crates/server/src/routes/workspaces/streams.rs:72-86 | crates/server/src/routes/workspaces/streams.rs:115-129 — before extracting anything, compare `crates/server/src/routes/execution_processes.rs` and `crates/server/src/routes/workspaces/streams.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 3) crates/server/src/routes/workspaces/codex_setup.rs:43— crates/server/src/routes/workspaces/codex_setup.rs:43-56 | crates/server/src/routes/workspaces/cursor_setup.rs:42-54 | crates/server/src/routes/workspaces/gh_cli_setup.rs:37-49 — before extracting anything, compare `crates/server/src/routes/workspaces/codex_setup.rs` and `crates/server/src/routes/workspaces/cursor_setup.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–14 lines × 2) crates/mcp/src/task_server/mod.rs:196— crates/mcp/src/task_server/mod.rs:196-209 | crates/mcp/src/task_server/mod.rs:229-239 — 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 (13–14 lines × 2) crates/preview-proxy/src/api.rs:45— crates/preview-proxy/src/api.rs:45-57 | crates/preview-proxy/src/lib.rs:494-507 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 6) crates/git-host/src/github/mod.rs:76— crates/git-host/src/github/mod.rs:76-88 | crates/git-host/src/github/mod.rs:117-129 | crates/git-host/src/github/mod.rs:209-221 | crates/git-host/src/github/mod.rs:243-255 | crates/git-host/src/github/mod.rs:286-298 | crates/git-host/src/github/mod.rs:382-394 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 2) crates/executors/src/executors/claude.rs:1315— crates/executors/src/executors/claude.rs:1315-1326 | crates/executors/src/executors/claude.rs:1611-1623 — 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 (11–12 lines × 5) crates/executors/src/executors/amp.rs:71— crates/executors/src/executors/amp.rs:71-82 | crates/executors/src/executors/amp.rs:114-125 | crates/executors/src/executors/cursor.rs:212-222 | crates/executors/src/executors/cursor.rs:253-263 | crates/executors/src/executors/droid.rs:131-141 — before extracting anything, compare `crates/executors/src/executors/amp.rs` and `crates/executors/src/executors/cursor.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) crates/executors/src/executors/amp.rs:55— crates/executors/src/executors/amp.rs:55-66 | crates/executors/src/executors/amp.rs:98-109 | crates/executors/src/executors/cursor.rs:196-207 | crates/executors/src/executors/cursor.rs:237-248 — before extracting anything, compare `crates/executors/src/executors/amp.rs` and `crates/executors/src/executors/cursor.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–12 lines × 2) crates/executors/src/actions/coding_agent_follow_up.rs:67— crates/executors/src/actions/coding_agent_follow_up.rs:67-78 | crates/executors/src/actions/coding_agent_initial.rs:60-67 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11–12 lines × 2) crates/preview-proxy/src/lib.rs:621— crates/preview-proxy/src/lib.rs:621-632 | crates/preview-proxy/src/lib.rs:692-702 — 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 (10–12 lines × 2) crates/relay-tunnel/src/server_bin/routes/auth_code.rs:28— crates/relay-tunnel/src/server_bin/routes/auth_code.rs:28-37 | crates/relay-tunnel/src/server_bin/routes/path_routes.rs:107-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–12 lines × 2) crates/remote/src/github_app/pr_review.rs:205— crates/remote/src/github_app/pr_review.rs:205-213 | crates/review/src/archive.rs:11-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–11 lines × 3) crates/executors/src/actions/coding_agent_follow_up.rs:73— crates/executors/src/actions/coding_agent_follow_up.rs:73-83 | crates/executors/src/actions/coding_agent_initial.rs:62-70 | crates/executors/src/actions/review.rs:61-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (9–10 lines × 3) crates/remote/src/routes/github_app.rs:303— crates/remote/src/routes/github_app.rs:303-312 | crates/remote/src/routes/github_app.rs:359-368 | crates/remote/src/routes/github_app.rs:434-442 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–10 lines × 2) crates/remote/src/db/issues.rs:436— crates/remote/src/db/issues.rs:436-443 | crates/remote/src/db/workspaces.rs:255-264 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–9 lines × 12) crates/remote/src/routes/issues.rs:386— crates/remote/src/routes/issues.rs:386-394 | crates/remote/src/routes/issues.rs:566-573 | crates/remote/src/routes/notifications.rs:159-167 | crates/remote/src/routes/notifications.rs:212-220 | crates/remote/src/routes/notifications.rs:297-305 | crates/remote/src/routes/project_statuses.rs:336-343 | crates/remote/src/routes/projects.rs:257-264 | crates/remote/src/routes/pull_request_issues.rs:176-184 | crates/remote/src/routes/pull_request_issues.rs:228-236 | crates/remote/src/routes/pull_requests.rs:159-167 | crates/remote/src/routes/pull_requests.rs:246-254 | crates/remote/src/routes/pull_requests.rs:358-366 — before extracting anything, compare `crates/remote/src/routes/project_statuses.rs` and `crates/remote/src/routes/projects.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) crates/executors/src/executors/amp.rs:63— crates/executors/src/executors/amp.rs:63-71 | crates/executors/src/executors/claude.rs:634-642 | crates/executors/src/executors/cursor.rs:204-212 | crates/executors/src/executors/cursor.rs:245-253 — before extracting anything, compare `crates/executors/src/executors/amp.rs` and `crates/executors/src/executors/cursor.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7–9 lines × 2) crates/mcp/src/task_server/tools/mod.rs:131— crates/mcp/src/task_server/tools/mod.rs:131-139 | crates/mcp/src/task_server/tools/mod.rs:166-172 — 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 (7–8 lines × 2) crates/review/src/github.rs:113— crates/review/src/github.rs:113-119 | crates/review/src/github.rs:161-168 — 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 (7 lines × 6) crates/services/src/services/config/versions/v2.rs:58— crates/services/src/services/config/versions/v2.rs:58-64 | crates/services/src/services/config/versions/v3.rs:27-33 | crates/services/src/services/config/versions/v4.rs:49-55 | crates/services/src/services/config/versions/v5.rs:29-35 | crates/services/src/services/config/versions/v6.rs:49-55 | crates/services/src/services/config/versions/v7.rs:59-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
Duplicated block (7 lines × 4) crates/mcp/src/task_server/tools/sessions.rs:154— crates/mcp/src/task_server/tools/sessions.rs:154-160 | crates/mcp/src/task_server/tools/sessions.rs:198-204 | crates/mcp/src/task_server/tools/workspaces.rs:181-187 | crates/mcp/src/task_server/tools/workspaces.rs:221-227 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5–7 lines × 2) crates/remote/src/routes/issue_comment_reactions.rs:103— crates/remote/src/routes/issue_comment_reactions.rs:103-109 | crates/remote/src/routes/issue_comment_reactions.rs:292-296 — 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 (6 lines × 8) crates/executors/src/executors/opencode/sdk.rs:818— crates/executors/src/executors/opencode/sdk.rs:818-823 | crates/executors/src/executors/opencode/sdk.rs:839-844 | crates/executors/src/executors/opencode/sdk.rs:860-865 | crates/executors/src/executors/opencode/sdk.rs:881-886 | crates/executors/src/executors/opencode/sdk.rs:902-907 | crates/executors/src/executors/opencode/sdk.rs:923-928 | crates/executors/src/executors/opencode/sdk.rs:944-949 | crates/executors/src/executors/opencode/sdk.rs:965-970 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 6) crates/executors/src/executors/claude.rs:422— crates/executors/src/executors/claude.rs:422-426 | crates/executors/src/executors/claude.rs:461-465 | crates/executors/src/executors/claude.rs:488-492 | crates/executors/src/executors/opencode.rs:544-548 | crates/executors/src/executors/opencode.rs:571-575 | crates/executors/src/executors/opencode.rs:586-590 — before extracting anything, compare `crates/executors/src/executors/claude.rs` and `crates/executors/src/executors/opencode.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) crates/remote/src/routes/issues.rs:516— crates/remote/src/routes/issues.rs:516-520 | crates/remote/src/routes/project_statuses.rs:264-268 | crates/remote/src/routes/projects.rs:207-211 — before extracting anything, compare `crates/remote/src/routes/project_statuses.rs` and `crates/remote/src/routes/projects.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 5) crates/server/src/routes/organizations.rs:63— crates/server/src/routes/organizations.rs:63-69 | crates/server/src/routes/remote/issues.rs:47-51 | crates/server/src/routes/remote/projects.rs:37-41 | crates/server/src/routes/remote/tags.rs:37-41 | crates/server/src/routes/remote/workspaces.rs:23-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (5 lines × 8) crates/server/src/routes/remote/issue_assignees.rs:36— crates/server/src/routes/remote/issue_assignees.rs:36-40 | crates/server/src/routes/remote/issue_relationships.rs:31-35 | crates/server/src/routes/remote/issue_tags.rs:31-35 | crates/server/src/routes/remote/issues.rs:29-33 | crates/server/src/routes/remote/project_statuses.rs:26-30 | crates/server/src/routes/remote/projects.rs:28-32 | crates/server/src/routes/remote/pull_requests.rs:25-29 | crates/server/src/routes/remote/tags.rs:28-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 8 call sites, so a change lands once.
Duplicated block (10 lines × 6) crates/remote/src/routes/github_app.rs:138— crates/remote/src/routes/github_app.rs:138-147 | crates/remote/src/routes/github_app.rs:262-271 | crates/remote/src/routes/github_app.rs:295-304 | crates/remote/src/routes/github_app.rs:426-435 | crates/remote/src/routes/organization_members.rs:248-257 | crates/remote/src/routes/organizations.rs:155-164 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 10) crates/remote/src/db/issue_assignees.rs:119— crates/remote/src/db/issue_assignees.rs:119-125 | crates/remote/src/db/issue_comment_reactions.rs:139-145 | crates/remote/src/db/issue_comments.rs:125-131 | crates/remote/src/db/issue_followers.rs:114-120 | crates/remote/src/db/issue_relationships.rs:124-130 | crates/remote/src/db/issue_tags.rs:110-116 | crates/remote/src/db/issues.rs:510-518 | crates/remote/src/db/project_statuses.rs:177-183 | crates/remote/src/db/projects.rs:202-208 | crates/remote/src/db/tags.rs:121-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 10 call sites, so a change lands once.
Fake-async — async method never awaits REDACTED:308— `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×1
Markup wires an event to an empty handler packages/remote-web/src/app/layout/RemoteAppShell.tsx:269— `onProjectsDragEnd` 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.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×1
Guard cannot change the result — returns what the code already falls through to REDACTED:77— 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.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 4 sibling directories (58 clone groups) packages/remote-web/src/app/layout/RemoteAppShell.tsx:151— 58 duplicated blocks under packages/ have copies in at least two of the sibling directories local-web, remote-web, ui, web-core — 41 of them are reported below, and 17 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 58 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 58 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 58 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 (41 clone groups) packages/web-core/src/features/workspace/model/hooks/usePreviewDevServer.ts:2— 41 duplicated blocks under packages/web-core/src/ have copies in at least two of the sibling directories features, integrations, pages, shared — 15 of them are reported below, and 26 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 41 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 41 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 41 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 (17 clone groups) packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:55— 17 duplicated blocks under packages/web-core/src/shared/dialogs/ have copies in at least two of the sibling directories auth, command-bar, org, scripts, settings, shared (+1 more sibling(s) not listed) — 12 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 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 7 sibling directories (12 clone groups) packages/web-core/src/shared/hooks/useUserSystemController.ts:159— 12 duplicated blocks under packages/web-core/src/shared/ have copies in at least two of the sibling directories components, dialogs, hooks, lib, providers, stores (+1 more sibling(s) not listed) — 4 of them are reported below, and 8 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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 (213 matched lines × 2 locations) · ×1
Duplicated block with local edits (213 matched lines × 2 locations) packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:63— packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:63 · packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:124 — the two spans are one implementation copied and then locally edited — 1177 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 (183 matched lines × 2 locations) · ×1
Duplicated block with local edits (183 matched lines × 2 locations) packages/remote-web/src/app/layout/RemoteAppShell.tsx:151— packages/remote-web/src/app/layout/RemoteAppShell.tsx:151 · packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:272 — the two spans are one implementation copied and then locally edited — 740 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 (155 matched lines × 2 locations) · ×1
Duplicated block with local edits (155 matched lines × 2 locations) packages/ui/src/components/attachment-node.tsx:54— packages/ui/src/components/attachment-node.tsx:54 · packages/ui/src/components/image-node.tsx:75 — the two spans are one implementation copied and then locally edited — 878 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 (149 matched lines × 2 locations) · ×1
Duplicated block with local edits (149 matched lines × 2 locations) packages/ui/src/components/Dropdown.tsx:13— packages/ui/src/components/Dropdown.tsx:13 · packages/ui/src/components/DropdownMenu.tsx:7 — the two spans are one implementation copied and then locally edited — 812 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 (125 matched lines × 2 locations) · ×1
Duplicated block with local edits (125 matched lines × 2 locations) packages/local-web/src/app/navigation/AppNavigation.ts:45— packages/local-web/src/app/navigation/AppNavigation.ts:45 · packages/remote-web/src/app/navigation/AppNavigation.ts:30 — the two spans are one implementation copied and then locally edited — 619 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) packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:55— packages/web-core/src/shared/dialogs/command-bar/StartReviewDialog.tsx:55 · packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:97 — the two spans are one implementation copied and then locally edited — 604 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 (107 matched lines × 2 locations) · ×1
Duplicated block with local edits (107 matched lines × 2 locations) packages/ui/src/components/RenameSessionDialog.tsx:27— packages/ui/src/components/RenameSessionDialog.tsx:27 · packages/ui/src/components/RenameWorkspaceDialog.tsx:27 — the two spans are one implementation copied and then locally edited — 431 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) packages/web-core/src/pages/workspaces/VSCodeWorkspacePage.tsx:38— packages/web-core/src/pages/workspaces/VSCodeWorkspacePage.tsx:38 · packages/web-core/src/pages/workspaces/WorkspacesMainContainer.tsx:44 — the two spans are one implementation copied and then locally edited — 526 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 (90 matched lines × 2 locations) · ×1
Duplicated block with local edits (90 matched lines × 2 locations) packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:254— packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:254 · packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:510 — the two spans are one implementation copied and then locally edited — 523 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 (83 matched lines × 2 locations) · ×1
Duplicated block with local edits (83 matched lines × 2 locations) packages/remote-web/src/shared/lib/relay/ws.ts:48— packages/remote-web/src/shared/lib/relay/ws.ts:48 · packages/remote-web/src/shared/lib/webrtc/dataChannelWebSocket.ts:17 — the two spans are one implementation copied and then locally edited — 452 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 (69 matched lines × 2 locations) · ×1
Duplicated block with local edits (69 matched lines × 2 locations) packages/remote-web/src/pages/InvitationCompletePage.tsx:22— packages/remote-web/src/pages/InvitationCompletePage.tsx:22 · packages/remote-web/src/pages/LoginCompletePage.tsx:27 — the two spans are one implementation copied and then locally edited — 275 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 (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) packages/web-core/src/shared/components/tasks/AgentSelector.tsx:21— packages/web-core/src/shared/components/tasks/AgentSelector.tsx:21 · packages/web-core/src/shared/components/tasks/ConfigSelector.tsx:22 — the two spans are one implementation copied and then locally edited — 173 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 (63 matched lines × 2 locations) · ×1
Duplicated block with local edits (63 matched lines × 2 locations) packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:130— packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:130 · packages/web-core/src/shared/dialogs/org/InviteMemberDialog.tsx:108 — the two spans are one implementation copied and then locally edited — 320 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) packages/web-core/src/shared/components/tasks/BranchSelector.tsx:113— packages/web-core/src/shared/components/tasks/BranchSelector.tsx:113 · packages/web-core/src/shared/components/ui-new/containers/SearchableDropdownContainer.tsx:53 — the two spans are one implementation copied and then locally edited — 366 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 (58 identical lines × 2 files) packages/web-core/src/features/workspace/model/hooks/usePreviewDevServer.ts:2— packages/web-core/src/features/workspace/model/hooks/usePreviewDevServer.ts:2 · packages/web-core/src/shared/hooks/useDevServer.ts:2 — these 2 files are line-for-line copies of one another — 58 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.
Duplicated block (57 lines × 2 locations) packages/web-core/src/features/workspace-chat/model/hooks/useMessageEditRetry.ts:15— packages/web-core/src/features/workspace-chat/model/hooks/useMessageEditRetry.ts:15 · packages/web-core/src/shared/hooks/useRetryProcess.ts:16 — 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 (54 lines × 2 locations) packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx:29— packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx:29 · packages/web-core/src/shared/components/ui-new/containers/NavbarContainer.tsx:46 — 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 (53 lines × 2 locations) packages/ui/src/components/ChatFileEntry.tsx:100— packages/ui/src/components/ChatFileEntry.tsx:100 · packages/ui/src/components/ChatFileEntry.tsx:168 — 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.
R10 · Code Duplication· Duplicated block with local edits (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:37— packages/web-core/src/shared/dialogs/org/CreateOrganizationDialog.tsx:37 · packages/web-core/src/shared/dialogs/org/InviteMemberDialog.tsx:45 — the two spans are one implementation copied and then locally edited — 233 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 (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) packages/remote-web/src/routes/hosts.$hostId.workspaces.tsx:142— packages/remote-web/src/routes/hosts.$hostId.workspaces.tsx:142 · packages/ui/src/components/WorkspaceSummary.tsx:126 — the two spans are one implementation copied and then locally edited — 133 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 (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) packages/ui/src/components/ChatTodoList.tsx:14— packages/ui/src/components/ChatTodoList.tsx:14 · packages/ui/src/components/TodoProgressPopup.tsx:16 — the two spans are one implementation copied and then locally edited — 280 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) packages/web-core/src/shared/providers/WorkspaceProvider.tsx:199— packages/web-core/src/shared/providers/WorkspaceProvider.tsx:199 · packages/web-core/src/shared/providers/remote/ProjectProvider.tsx:281 — 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 (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) packages/ui/src/components/ChatAggregatedDiffEntries.tsx:228— packages/ui/src/components/ChatAggregatedDiffEntries.tsx:228 · packages/ui/src/components/ChatAggregatedToolEntries.tsx:70 — the two spans are one implementation copied and then locally edited — 199 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 (38 matched lines × 2 locations) · ×1
Duplicated block with local edits (38 matched lines × 2 locations) packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:560— packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:560 · packages/web-core/src/pages/kanban/IssueWorkspacesSectionContainer.tsx:52 — the two spans are one implementation copied and then locally edited — 216 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 (38 lines × 2 locations) packages/web-core/src/shared/hooks/useProfiles.ts:38— packages/web-core/src/shared/hooks/useProfiles.ts:38 · packages/web-core/src/shared/hooks/useProfiles.ts:111 — 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 (37 lines × 2 locations) packages/web-core/src/shared/lib/relayBackendApi.ts:124— packages/web-core/src/shared/lib/relayBackendApi.ts:124 · packages/web-core/src/shared/lib/remoteApi.ts:55 — 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 (36 lines × 2 locations) packages/web-core/src/features/onboarding/ui/LandingPage.tsx:380— packages/web-core/src/features/onboarding/ui/LandingPage.tsx:380 · packages/web-core/src/features/onboarding/ui/LandingPage.tsx:417 — 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 (35 lines × 2 locations) packages/ui/src/components/PreviewBrowser.tsx:264— packages/ui/src/components/PreviewBrowser.tsx:264 · packages/ui/src/components/PreviewBrowser.tsx:438 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Boundary violation [package:third-party-deep-import] packages/web-core/src/shared/components/VirtualizedProcessLogs.tsx:11— packages/web-core/src/shared/components/VirtualizedProcessLogs.tsx:11 imports @phosphor-icons/react/dist/ssr, 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.
Complex function SessionChatBox (cyclomatic 71, cognitive 56) packages/ui/src/components/SessionChatBox.tsx:223— SessionChatBox has cyclomatic complexity 71 and cognitive complexity 56; 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 PreviewBrowser (cyclomatic 61, cognitive 56) packages/ui/src/components/PreviewBrowser.tsx:94— PreviewBrowser has cyclomatic complexity 61 and cognitive complexity 56; 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 53, cognitive 47) packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:44— (anonymous) has cyclomatic complexity 53 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 ModelSelectorContainer (cyclomatic 52, cognitive 43) packages/web-core/src/shared/components/ModelSelectorContainer.tsx:60— ModelSelectorContainer has cyclomatic complexity 52 and cognitive complexity 43; 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 resolveLocalDestinationFromPath (cyclomatic 52, cognitive 39) packages/local-web/src/app/navigation/AppNavigation.ts:28— resolveLocalDestinationFromPath has cyclomatic complexity 52 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 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 ImageComponent (cyclomatic 51, cognitive 68) packages/ui/src/components/image-node.tsx:189— ImageComponent has cyclomatic complexity 51 and cognitive complexity 68; 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 KanbanIssuePanel (cyclomatic 49, cognitive 33) packages/ui/src/components/KanbanIssuePanel.tsx:159— KanbanIssuePanel has cyclomatic complexity 49 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 ChatFileEntry (cyclomatic 46, cognitive 40) packages/ui/src/components/ChatFileEntry.tsx:48— ChatFileEntry has cyclomatic complexity 46 and cognitive complexity 40; 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 LinkPrToIssueContent (cyclomatic 46, cognitive 37) packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:39— LinkPrToIssueContent has cyclomatic complexity 46 and cognitive complexity 37; 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 GitOperations (cyclomatic 41, cognitive 28) packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:42— GitOperations has cyclomatic complexity 41 and cognitive complexity 28; 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 GeneralSettingsSection (cyclomatic 40, cognitive 35) packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:57— GeneralSettingsSection has cyclomatic complexity 40 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 SessionChatBoxContainer (cyclomatic 40, cognitive 33) packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:143— SessionChatBoxContainer has cyclomatic complexity 40 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 IssueWorkspaceCard (cyclomatic 35, cognitive 28) packages/ui/src/components/IssueWorkspaceCard.tsx:110— IssueWorkspaceCard has cyclomatic complexity 35 and cognitive complexity 28; 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 OrganizationsSettingsSection (cyclomatic 35, cognitive 28) packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:45— OrganizationsSettingsSection has cyclomatic complexity 35 and cognitive complexity 28; 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 WorkspacesLayout (cyclomatic 34, cognitive 31) packages/web-core/src/pages/workspaces/WorkspacesLayout.tsx:47— WorkspacesLayout has cyclomatic complexity 34 and cognitive complexity 31; 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 OnboardingSignInPage (cyclomatic 34, cognitive 28) packages/web-core/src/features/onboarding/ui/OnboardingSignInPage.tsx:74— OnboardingSignInPage has cyclomatic complexity 34 and cognitive complexity 28; 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 resolveRemoteDestinationFromPath (cyclomatic 33, cognitive 26) packages/remote-web/src/app/navigation/AppNavigation.ts:19— resolveRemoteDestinationFromPath has cyclomatic complexity 33 and cognitive complexity 26; 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 ElectricTestPage (cyclomatic 32, cognitive 26) packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:887— ElectricTestPage has cyclomatic complexity 32 and cognitive complexity 26; 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 32, cognitive 25) packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:34— (anonymous) has cyclomatic complexity 32 and cognitive complexity 25; 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 RemoteAppShell (cyclomatic 31, cognitive 28) packages/remote-web/src/app/layout/RemoteAppShell.tsx:54— RemoteAppShell has cyclomatic complexity 31 and cognitive complexity 28; 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.
R3 · Large Files· packages/web-core/src/shared/lib/api.ts · ×1
packages/web-core/src/shared/lib/api.ts: 1537 lines of code packages/web-core/src/shared/lib/api.ts:1— packages/web-core/src/shared/lib/api.ts has 1537 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· packages/web-core/src/shared/actions/index.ts · ×1
packages/web-core/src/shared/actions/index.ts: 1465 lines of code packages/web-core/src/shared/actions/index.ts:1— packages/web-core/src/shared/actions/index.ts has 1465 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· packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx · ×1
packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx: 1409 lines of code packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx:1— packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.tsx has 1409 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· packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx · ×1
packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx: 1294 lines of code packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx:1— packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.tsx has 1294 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· packages/web-core/src/pages/workspaces/ElectricTestPage.tsx · ×1
packages/web-core/src/pages/workspaces/ElectricTestPage.tsx: 1054 lines of code packages/web-core/src/pages/workspaces/ElectricTestPage.tsx:1— packages/web-core/src/pages/workspaces/ElectricTestPage.tsx has 1054 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· packages/web-core/src/features/kanban/ui/KanbanContainer.tsx · ×1
packages/web-core/src/features/kanban/ui/KanbanContainer.tsx: 1051 lines of code packages/web-core/src/features/kanban/ui/KanbanContainer.tsx:1— packages/web-core/src/features/kanban/ui/KanbanContainer.tsx has 1051 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· packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx · ×1
packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx: 1035 lines of code packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:1— packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx has 1035 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· packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx · ×1
packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx: 1017 lines of code packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx:1— packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx has 1017 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· packages/web-core/src/shared/stores/useUiPreferencesStore.ts · ×1
packages/web-core/src/shared/stores/useUiPreferencesStore.ts: 887 lines of code packages/web-core/src/shared/stores/useUiPreferencesStore.ts:1— packages/web-core/src/shared/stores/useUiPreferencesStore.ts has 887 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· packages/ui/src/components/SessionChatBox.tsx · ×1
packages/ui/src/components/SessionChatBox.tsx: 876 lines of code packages/ui/src/components/SessionChatBox.tsx:1— packages/ui/src/components/SessionChatBox.tsx has 876 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: 854 lines of code REDACTED:1— REDACTED has 854 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· packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx · ×1
packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx: 798 lines of code packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx:1— packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx has 798 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· packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx · ×1
packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx: 776 lines of code packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx:1— packages/web-core/src/pages/workspaces/ChangesPanelContainer.tsx has 776 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· packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx · ×1
packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx: 771 lines of code packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx:1— packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx has 771 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: 711 lines of code REDACTED:1— REDACTED has 711 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· packages/web-core/src/shared/lib/electric/collections.ts · ×1
packages/web-core/src/shared/lib/electric/collections.ts: 691 lines of code packages/web-core/src/shared/lib/electric/collections.ts:1— packages/web-core/src/shared/lib/electric/collections.ts has 691 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· packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx · ×1
packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx: 645 lines of code packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx:1— packages/web-core/src/shared/dialogs/settings/settings/ReposSettingsSection.tsx has 645 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· packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx · ×1
packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx: 639 lines of code packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx:1— packages/web-core/src/pages/workspaces/WorkspacesSidebarContainer.tsx has 639 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· packages/web-core/src/shared/components/WYSIWYGEditor.tsx · ×1
packages/web-core/src/shared/components/WYSIWYGEditor.tsx: 638 lines of code packages/web-core/src/shared/components/WYSIWYGEditor.tsx:1— packages/web-core/src/shared/components/WYSIWYGEditor.tsx has 638 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· packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx · ×1
packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx: 626 lines of code packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx:1— packages/web-core/src/shared/dialogs/settings/settings/RelaySettingsSection.tsx has 626 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· packages/ui/src/components/PreviewBrowser.tsx · ×1
packages/ui/src/components/PreviewBrowser.tsx: 610 lines of code packages/ui/src/components/PreviewBrowser.tsx:1— packages/ui/src/components/PreviewBrowser.tsx has 610 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· packages/web-core/src/features/create-mode/model/useCreateModeState.ts · ×1
packages/web-core/src/features/create-mode/model/useCreateModeState.ts: 583 lines of code packages/web-core/src/features/create-mode/model/useCreateModeState.ts:1— packages/web-core/src/features/create-mode/model/useCreateModeState.ts has 583 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· packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx · ×1
packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx: 578 lines of code packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx:1— packages/web-core/src/shared/dialogs/tasks/RestoreLogsDialog.tsx has 578 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· packages/ui/src/components/AppBar.tsx · ×1
packages/ui/src/components/AppBar.tsx: 558 lines of code packages/ui/src/components/AppBar.tsx:1— packages/ui/src/components/AppBar.tsx has 558 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· packages/local-web/src/routeTree.gen.ts · ×1
packages/local-web/src/routeTree.gen.ts: 544 lines of code packages/local-web/src/routeTree.gen.ts:1— packages/local-web/src/routeTree.gen.ts has 544 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· packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx · ×1
packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx: 539 lines of code packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx:1— packages/web-core/src/shared/dialogs/settings/settings/AgentsSettingsSection.tsx has 539 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· packages/web-core/src/features/onboarding/ui/LandingPage.tsx · ×1
packages/web-core/src/features/onboarding/ui/LandingPage.tsx: 538 lines of code packages/web-core/src/features/onboarding/ui/LandingPage.tsx:1— packages/web-core/src/features/onboarding/ui/LandingPage.tsx has 538 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· packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx · ×1
packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx: 534 lines of code packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx:1— packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.tsx has 534 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· packages/web-core/src/shared/keyboard/registry.ts · ×1
packages/web-core/src/shared/keyboard/registry.ts: 534 lines of code packages/web-core/src/shared/keyboard/registry.ts:1— packages/web-core/src/shared/keyboard/registry.ts has 534 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· packages/ui/src/components/FileTagTypeaheadPlugin.tsx · ×1
packages/ui/src/components/FileTagTypeaheadPlugin.tsx: 530 lines of code packages/ui/src/components/FileTagTypeaheadPlugin.tsx:1— packages/ui/src/components/FileTagTypeaheadPlugin.tsx has 530 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· packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx · ×1
packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx: 514 lines of code packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx:1— packages/web-core/src/pages/kanban/ProjectRightSidebarContainer.tsx has 514 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· packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx · ×1
packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx: 514 lines of code packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:1— packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx has 514 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· packages/ui/src/components/KanbanIssuePanel.tsx · ×1
packages/ui/src/components/KanbanIssuePanel.tsx: 512 lines of code packages/ui/src/components/KanbanIssuePanel.tsx:1— packages/ui/src/components/KanbanIssuePanel.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· packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx · ×1
packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx: 507 lines of code packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx:1— packages/web-core/src/shared/dialogs/settings/settings/OrganizationsSettingsSection.tsx 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· packages/ui/src/components/image-node.tsx · ×1
packages/ui/src/components/image-node.tsx: 503 lines of code packages/ui/src/components/image-node.tsx:1— packages/ui/src/components/image-node.tsx has 503 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· packages/web-core/src/shared/components/ModelSelectorContainer.tsx · ×1
packages/web-core/src/shared/components/ModelSelectorContainer.tsx: 502 lines of code packages/web-core/src/shared/components/ModelSelectorContainer.tsx:1— packages/web-core/src/shared/components/ModelSelectorContainer.tsx has 502 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· packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx · ×1
packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx: 488 lines of code packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx:1— packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx has 488 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· packages/ui/src/components/WorkspacesSidebar.tsx · ×1
packages/ui/src/components/WorkspacesSidebar.tsx: 482 lines of code packages/ui/src/components/WorkspacesSidebar.tsx:1— packages/ui/src/components/WorkspacesSidebar.tsx has 482 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· packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts · ×1
packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts: 477 lines of code packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts:1— packages/web-core/src/features/workspace-chat/model/hooks/useConversationHistory.ts has 477 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· packages/remote-web/src/routeTree.gen.ts · ×1
packages/remote-web/src/routeTree.gen.ts: 458 lines of code packages/remote-web/src/routeTree.gen.ts:1— packages/remote-web/src/routeTree.gen.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency '@codemirror/lang-json' — Declared in packages/local-web/package.json 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.
Unused dependency '@codemirror/language' — Declared in packages/local-web/package.json 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.
Unused dependency '@codemirror/lint' — Declared in packages/local-web/package.json 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped packages/web-core/src/shared/components/MermaidDiagram.tsx:84— `svg` 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.
Orphaned file crates/embedded-ssh/src/handler.rs: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 crates/review/src/claude_session.rs: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 packages/ui/src/components/image-node.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 crates/relay-webrtc/src/peer.rs: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 crates/services/src/services/events/streams.rs: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 crates/remote/src/azure_blob.rs: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 crates/remote/src/db/github_app.rs: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 packages/web-core/src/features/workspace-chat/model/conversation-row-model.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 packages/web-core/src/shared/dialogs/global/OAuthDialog.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 packages/web-core/src/pages/kanban/IssueCommentsSectionContainer.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 crates/remote/src/routes/export.rs: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 packages/web-core/src/shared/dialogs/settings/settings/RemoteCloudHostsSettingsCard.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 crates/server/src/routes/workspaces/create.rs: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 packages/web-core/src/features/workspace-chat/model/useConversationVirtualizer.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 packages/ui/src/components/IssueCommentsSection.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 crates/embedded-ssh/src/sftp.rs: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 crates/executors/src/executors/claude/slash_commands.rs: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 packages/web-core/src/shared/hooks/useAzureAttachments.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 crates/relay-webrtc/src/proxy.rs: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 packages/ui/src/components/PierreConversationDiff.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 crates/db/src/models/pull_request.rs: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 packages/remote-web/src/app/navigation/AppNavigation.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 crates/relay-control/src/signing.rs: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 packages/remote-web/src/shared/lib/relay/ws.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 crates/executors/src/executors/codex/jsonrpc.rs: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.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:109— `trace!` at line 109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:114— `info!` at line 114 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:128— `info!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:235— `debug!` at line 235 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:241— `debug!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:246— `debug!` at line 246 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:251— `debug!` at line 251 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:260— `debug!` at line 260 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:263— `debug!` at line 263 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:292— `debug!` at line 292 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:324— `info!` at line 324 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:331— `warn!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:355— `info!` at line 355 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:379— `debug!` at line 379 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:393— `debug!` at line 393 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:396— `error!` at line 396 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:429— `debug!` at line 429 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:479— `info!` at line 479 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/worktree-manager/src/worktree_manager.rs:531— `debug!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/workspace-manager/src/workspace_manager.rs:233— `warn!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/workspace-manager/src/workspace_manager.rs:241— `info!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/workspace-manager/src/workspace_manager.rs:248— `error!` at line 248 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/workspace-manager/src/workspace_manager.rs:255— `info!` at line 255 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/workspace-manager/src/workspace_manager.rs:267— `info!` at line 267 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/workspace-manager/src/workspace_manager.rs:270— `warn!` at line 270 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Duplicated predicate packages/ui/src/components/CodeBlockEscapePlugin.tsx:34— `!$isRangeSelection(selection) || !selection.isCollapsed()` appears character-identically in 2 files — packages/ui/src/components/CodeBlockEscapePlugin.tsx, packages/ui/src/components/InlineCodeBoundaryPlugin.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 packages/web-core/src/pages/workspaces/VSCodeWorkspacePage.tsx:139— `!container || typeof ResizeObserver === 'undefined'` appears character-identically in 2 files — packages/web-core/src/pages/workspaces/VSCodeWorkspacePage.tsx, packages/web-core/src/pages/workspaces/WorkspacesMainContainer.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 packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx:218— `!destination || source.index === destination.index` appears character-identically in 2 files — packages/web-core/src/shared/components/ui-new/containers/SharedAppLayout.tsx, packages/web-core/src/shared/dialogs/settings/settings/RemoteProjectsSettingsSection.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 packages/web-core/src/features/workspace-chat/model/hooks/useMessageEditRetry.ts:52— `!modalResult || modalResult.action !== 'confirmed'` appears character-identically in 3 files — packages/web-core/src/features/workspace-chat/model/hooks/useMessageEditRetry.ts, packages/web-core/src/features/workspace-chat/model/hooks/useResetProcessMutation.ts, packages/web-core/src/shared/hooks/useRetryProcess.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 packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx:30— `"type" in item && item.type === "divider"` appears character-identically in 2 files — packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx, packages/remote-web/src/app/layout/RemoteNavbarContainer.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 packages/web-core/src/pages/workspaces/ContextBarContainer.tsx:34— `'type' in item && item.type === 'divider'` appears character-identically in 2 files — packages/web-core/src/pages/workspaces/ContextBarContainer.tsx, packages/web-core/src/shared/components/ui-new/containers/NavbarContainer.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 packages/ui/src/components/KanbanIssuePanel.tsx:249— `(e.metaKey || e.ctrlKey) && e.key === 'Enter'` appears character-identically in 2 files — packages/ui/src/components/KanbanIssuePanel.tsx, packages/ui/src/components/MultiSelectCommandBar.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 packages/remote-web/src/shared/lib/relay/routing.ts:59— `/^https?:\/\//i.test(pathOrUrl) || /^wss?:\/\//i.test(pathOrUrl)` appears character-identically in 2 files — packages/remote-web/src/shared/lib/relay/routing.ts, packages/web-core/src/shared/lib/localApiTransport.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 packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:319— `String(pr.number).includes(query) || pr.title.toLowerCase().includes(query)` appears character-identically in 2 files — packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx, packages/web-core/src/shared/dialogs/command-bar/LinkPrToIssueDialog.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 packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx:122— `action.requiresTarget && selectedWorkspace?.id` appears character-identically in 3 files — packages/remote-web/src/app/layout/RemoteDesktopNavbar.tsx, packages/remote-web/src/app/layout/RemoteNavbarContainer.tsx, packages/web-core/src/shared/components/ui-new/containers/NavbarContainer.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 packages/web-core/src/shared/lib/relayBackendApi.ts:173— `body.error || body.message || fallbackMessage` appears character-identically in 2 files — packages/web-core/src/shared/lib/relayBackendApi.ts, packages/web-core/src/shared/lib/remoteApi.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 packages/ui/src/components/ChatAggregatedDiffEntries.tsx:77— `change.action === 'edit' && change.unified_diff` appears character-identically in 2 files — packages/ui/src/components/ChatAggregatedDiffEntries.tsx, packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.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 packages/ui/src/components/ChatAggregatedDiffEntries.tsx:85— `change.action === 'write' && change.content` appears character-identically in 2 files — packages/ui/src/components/ChatAggregatedDiffEntries.tsx, packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.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 packages/ui/src/components/ColorPicker.tsx:41— `e.key === 'ArrowLeft' || e.key === 'ArrowUp'` appears character-identically in 2 files — packages/ui/src/components/ColorPicker.tsx, packages/web-core/src/shared/components/ui-new/containers/ColorPickerContainer.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 packages/ui/src/components/ColorPicker.tsx:47— `e.key === 'ArrowRight' || e.key === 'ArrowDown'` appears character-identically in 2 files — packages/ui/src/components/ColorPicker.tsx, packages/web-core/src/shared/components/ui-new/containers/ColorPickerContainer.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 packages/ui/src/components/ChangeTargetDialog.tsx:57— `err && typeof err === 'object' && 'message' in err` appears character-identically in 3 files — packages/ui/src/components/ChangeTargetDialog.tsx, packages/web-core/src/shared/dialogs/command-bar/ForcePushDialog.tsx, packages/web-core/src/shared/hooks/useGitOperations.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 packages/ui/src/components/ChatEntryContainer.tsx:84— `event.key !== 'Enter' && event.key !== ' '` appears character-identically in 3 files — packages/ui/src/components/ChatEntryContainer.tsx, packages/ui/src/components/ChatFileEntry.tsx, packages/ui/src/components/ChatSubagentEntry.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 packages/ui/src/components/CodeBlockEscapePlugin.tsx:31— `event.shiftKey || event.metaKey || event.ctrlKey` appears character-identically in 2 files — packages/ui/src/components/CodeBlockEscapePlugin.tsx, packages/ui/src/components/KeyboardCommandsPlugin.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 packages/ui/src/components/ChatErrorMessage.tsx:30— `expanded && 'whitespace-pre-wrap break-all'` appears character-identically in 3 files — packages/ui/src/components/ChatErrorMessage.tsx, packages/ui/src/components/ChatSystemMessage.tsx, packages/ui/src/components/ChatToolSummary.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 packages/ui/src/components/ChatEntryContainer.tsx:96— `isGreyed && 'opacity-50 pointer-events-none'` appears character-identically in 2 files — packages/ui/src/components/ChatEntryContainer.tsx, packages/web-core/src/features/workspace-chat/ui/DisplayConversationEntry.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 packages/ui/src/components/attachment-node.tsx:174— `isPendingAttachment || src.startsWith('attachment://')` appears character-identically in 2 files — packages/ui/src/components/attachment-node.tsx, packages/ui/src/components/image-node.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 packages/ui/src/components/PierreConversationDiff.tsx:159— `line.startsWith('+') && !line.startsWith('+++')` appears character-identically in 3 files — packages/ui/src/components/PierreConversationDiff.tsx, packages/ui/src/components/pr-comment-card.tsx, packages/web-core/src/shared/lib/diffStatsParser.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 packages/ui/src/components/PierreConversationDiff.tsx:160— `line.startsWith('-') && !line.startsWith('---')` appears character-identically in 3 files — packages/ui/src/components/PierreConversationDiff.tsx, packages/ui/src/components/pr-comment-card.tsx, packages/web-core/src/shared/lib/diffStatsParser.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 packages/web-core/src/pages/workspaces/GitPanelContainer.tsx:73— `m.type === 'pr' && m.pr_info.status === 'merged'` appears character-identically in 2 files — packages/web-core/src/pages/workspaces/GitPanelContainer.tsx, packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.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 packages/web-core/src/pages/workspaces/GitPanelContainer.tsx:70— `m.type === 'pr' && m.pr_info.status === 'open'` appears character-identically in 4 files — packages/web-core/src/pages/workspaces/GitPanelContainer.tsx, packages/web-core/src/shared/actions/index.ts, packages/web-core/src/shared/components/tasks/Toolbar/GitOperations.tsx, packages/web-core/src/shared/hooks/useActionVisibilityContext.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.
IC1 · Incompleteness & stubs· Empty method body · ×17
Empty method body packages/web-core/src/shared/hooks/useChangesView.ts:29— `selectFile` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useChangesView.ts:30— `scrollToFile` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useChangesView.ts:31— `viewFileInChanges` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useChangesView.ts:34— `registerScrollToFile` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useChangesView.ts:38— `viewFileInChanges` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:41— `setLogSearchQuery` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:42— `setLogMatchIndices` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:43— `handleLogPrevMatch` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:44— `handleLogNextMatch` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:45— `viewProcessInPanel` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:46— `viewToolContentInPanel` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:47— `expandTerminal` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:48— `collapseTerminal` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:53— `viewProcessInPanel` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:54— `viewToolContentInPanel` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:55— `expandTerminal` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/web-core/src/shared/hooks/useLogsPanel.ts:56— `collapseTerminal` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Silent fallback default on Err crates/executors/src/executors/opencode.rs:821— `merge_compaction_config` turns every `Err` into `r#"{"compaction":{"auto":true}}"#.to_string()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/mcp/src/task_server/tools/remote_issues.rs:724— `fetch_issue_tags_resolved` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/mcp/src/task_server/tools/remote_issues.rs:761— `fetch_issue_relationships_resolved` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/mcp/src/task_server/tools/remote_issues.rs:816— `fetch_sub_issues` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/review/src/config.rs:29— `load` turns every `Err` into `Self::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/server/src/middleware/origin.rs:144— `allowed_origins` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Blanket warning suppression packages/local-web/src/routeTree.gen.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/local-web/src/routeTree.gen.ts:3— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/remote-web/src/routeTree.gen.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/remote-web/src/routeTree.gen.ts:3— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 20 significant file(s) lose their only recent owner: packages/web-core/src/features/kanban/ui/KanbanContainer.tsx, crates/remote/src/github_app/service.rs, packages/ui/src/components/ModelSelectorPopover.tsx, packages/web-core/src/shared/dialogs/command-bar/selections/ProjectSelectionDialog.tsx, packages/web-core/src/shared/dialogs/kanban/AssigneeSelectionDialog.tsx, packages/web-core/src/pages/kanban/IssueSubIssuesSectionContainer.tsx, packages/ui/src/components/SubIssueRow.tsx, packages/web-core/src/pages/kanban/kanban-issue-panel-state.ts (+12 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: crates/remote/src/auth/handoff.rs, crates/remote/src/db/auth.rs, crates/remote/src/auth/oauth_token_validator.rs, crates/db/src/lib.rs, crates/executors/src/logs/utils/shell_command_parsing.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/local-deployment/src/copy.rs, crates/relay-tunnel-core/src/server.rs, crates/server/src/routes/filesystem.rs. Pair on, review, or document these before any departure.
Silent fallback default in catch packages/web-core/src/shared/components/WYSIWYGEditor.tsx:336— `WYSIWYGEditor` 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 packages/web-core/src/shared/dialogs/settings/settings/SettingsHostContext.tsx:118— `queryFn` (in `SettingsHostProvider`) 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.
Fat interface: ProjectContextValue (31 required operations) packages/web-core/src/shared/hooks/useProjectContext.ts:44— `ProjectContextValue` declares 31 required operations: `retry`, `insertIssue`, `updateIssue`, `removeIssue`, `insertStatus`, `updateStatus`, `removeStatus`, `insertTag`, `updateTag`, `removeTag`, `insertIssueAssignee`, `removeIssueAssignee`, `insertIssueFollower`, `removeIssueFollower`, `insertIssueTag`, `removeIssueTag`, `insertIssueRelationship`, `removeIssueRelationship`, `insertPullRequestIssue`, `removePullRequestIssue`, `getIssue`, `getIssuesForStatus`, `getAssigneesForIssue`, `getFollowersForIssue`, `getTagsForIssue`, `getTagObjectsForIssue`, `getRelationshipsForIssue`, `getStatus`, `getTag`, `getPullRequestsForIssue`, `getWorkspacesForIssue`. 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.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 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 (32 single-owned of 660 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 660 of the 1115 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/web-core/src/shared/dialogs/command-bar/RebaseDialog.tsx, packages/web-core/src/shared/lib/notificationMessage.ts, packages/ui/src/components/ContextBar.tsx, packages/ui/src/lib/imeComposition.ts.
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 — 6 of 38 project(s) overshoot their size bounds, lowering Project Cohesion to 7.0/10. The most over is `packages/web-core` (66479 LoC, 661 module-visible types across 59 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.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 273 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: crates/embedded-ssh/src/handler.rs, crates/review/src/claude_session.rs, packages/ui/src/components/image-node.tsx, crates/relay-webrtc/src/peer.rs, crates/services/src/services/events/streams.rs, crates/remote/src/azure_blob.rs, crates/remote/src/db/github_app.rs, packages/web-core/src/features/workspace-chat/model/conversation-row-model.ts (and 265 more) (278 orphaned of 660 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 660 of the 1115 production source files in this repository met that bar). 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.
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.
Logging is not universal — Only 20/22 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `npx-cli`.
R7 · Dead Code· Unused export 'useClickedElements' · ×1
Unused export 'useClickedElements' packages/local-web/src/app/providers/ClickedElementsProvider.tsx:34— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'closeWebRtcConnection' · ×1
Unused export 'closeWebRtcConnection' packages/remote-web/src/shared/lib/webrtc/connectionManager.ts:37— Nothing imports this binding — it is safe to review for removal.
Security headers incomplete — Set: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−0.5 on this card.) The server: `axum::serve(` (crates/server/src/main.rs:130).
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/20 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.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 5/7 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~0.6 `!` null assertions per 1k TypeScript source lines — 66 assertion(s) across the 107681 source line(s) of the 680 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: packages/web-core/src/shared/dialogs/settings/settings/GeneralSettingsSection.tsx (11), packages/remote-web/src/shared/lib/webrtc/dataChannelWebSocket.ts (4), packages/web-core/src/features/create-mode/model/createModeBootstrap.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Subsumed condition operand crates/git-host/src/detection.rs:52— `url_lower.contains("github.com")` can never decide this `||` — every value satisfying `url_lower.contains("github.com")` also satisfies `url_lower.contains("github.")`, 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: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/db/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: arboard — `arboard` is locked at 3.6.1 but 3.7.0 is the current stable release on crates.io, and it already satisfies the `"3.6.1"` requirement declared in crates/tauri-app/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p arboard` and commit the updated REDACTED.
Outdated: async-trait — `async-trait` is locked at 0.1.89 but 0.1.92 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/deployment/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-trait` and commit the updated REDACTED.
Outdated: axum — `axum` is locked at 0.8.8 but 0.8.9 is the current stable release on crates.io, and it already satisfies the `"0.8.4"` requirement declared in crates/deployment/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p axum` and commit the updated REDACTED.
Outdated: bon — `bon` is locked at 3.9.1 but 3.10.3 is the current stable release on crates.io, and it already satisfies the `"3.6"` requirement declared in crates/executors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bon` and commit the updated REDACTED.
Outdated: bytes — `bytes` is locked at 1.11.1 but 1.12.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/relay-hosts/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes` and commit the updated REDACTED.
Outdated: chrono — `chrono` is locked at 0.4.44 but 0.4.45 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in crates/api-types/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p chrono` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.0 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/review/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: dashmap — `dashmap` is locked at 6.1.0 but 6.2.1 is the current stable release on crates.io, and it already satisfies the `"6.1"` requirement declared in crates/services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p dashmap` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.9 but 1.1.10 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/remote/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.32"` requirement declared in crates/db/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: futures-io — `futures-io` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.31"` requirement declared in crates/executors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-io` and commit the updated REDACTED.
Outdated: futures-util — `futures-util` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/relay-hosts/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-util` and commit the updated REDACTED.
Outdated: http — `http` is locked at 1.4.0 but 1.5.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/preview-proxy/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p http` and commit the updated REDACTED.
Outdated: hyper — `hyper` is locked at 1.8.1 but 1.12.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/relay-tunnel-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p hyper` and commit the updated REDACTED.
Outdated: hyper-util — `hyper-util` is locked at 0.1.20 but 0.1.21 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/relay-tunnel-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p hyper-util` and commit the updated REDACTED.
Outdated: ignore — `ignore` is locked at 0.4.25 but 0.4.33 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in crates/services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ignore` and commit the updated REDACTED.
Outdated: moka — `moka` is locked at 0.12.15 but 0.12.16 is the current stable release on crates.io, and it already satisfies the `"0.12"` requirement declared in crates/services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p moka` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.1 is the current stable release on crates.io, and it already satisfies the `"8.2.0"` requirement declared in crates/services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: notify-rust — `notify-rust` is locked at 4.12.0 but 4.18.2 is the current stable release on crates.io, and it already satisfies the `"4.11"` requirement declared in crates/services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify-rust` and commit the updated REDACTED.
Outdated: objc2 — `objc2` is locked at 0.6.4 but 0.6.5 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in crates/tauri-app/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: open — `open` is locked at 5.3.3 but 5.4.5 is the current stable release on crates.io, and it already satisfies the `"5.3.2"` requirement declared in crates/utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p open` and commit the updated REDACTED.
Outdated: openssl — `openssl` is locked at 0.10.77 but 0.10.81 is the current stable release on crates.io, and it already satisfies the `"0.10"` requirement declared in crates/executors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p openssl` and commit the updated REDACTED.
Outdated: os_info — `os_info` is locked at 3.14.0 but 3.15.0 is the current stable release on crates.io, and it already satisfies the `"3.12.0"` requirement declared in crates/relay-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p os_info` and commit the updated REDACTED.
Outdated: regex — `regex` is locked at 1.12.3 but 1.13.1 is the current stable release on crates.io, and it already satisfies the `"1.11.1"` requirement declared in crates/executors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p regex` and commit the updated REDACTED.
+ 22 more in this group — see findings.md.
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 5 file(s) — `packages/web-core/src/features/workspace-chat/model/conversation-row-model.ts`, `packages/web-core/src/features/workspace-chat/model/deriveConversationEntries.ts`, `packages/web-core/src/features/workspace-chat/model/deriveConversationSemanticTimeline.ts`, `packages/web-core/src/shared/actions/index.ts`, `packages/web-core/src/shared/dialogs/command-bar/commandBar/useResolvedPage.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1760d-a598-7c1d-b4cb-f2f9205e8278 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 205 · Warnings: 1214 · Recommendations: 390 · Info: 47 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 02:32 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.