Public report of stoneforge-ai/stoneforge, published 9 November 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.11.2). Assert 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, 9 November 2026, 09:23 UTC · Survey ID cd_54526e3e260c4c2dbaf2b861e58f0c2d
stoneforge-ai/stoneforge
Measured 9 November 2026, 09:21 UTC, at code version 0a7052a
CAI scoreAt riskUp 3 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: 313,797 lines of product code in 14 projects, tests not counted · Estimated rebuild effort: about 3.0 person-years · Weakest lens: Production Readiness, 40
Findings by how serious they are
173 critical3224 serious1596 minor
9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
9 November 2026, 09:21 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer 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. We work 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 ▸
85of 85 dimensions measured by tools.
4913of 4993 findings point to an exact file and line, so you can open each one in the code. The other 80 concern the repository as a whole, such as missing documentation.
85dimensions across 7 lenses, read from 313,797 lines of product code in 14 projects.
stoneforge-ai/stoneforge is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies, and it has packages under a licence on your banned list. It scores 45 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 40, is the weakest lens and counts most in the score. The best first step is fixing the nine packages used at two incompatible versions, worth about 4 points. Replacing the 14 packages under a banned licence would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 70 would lift the score to about 49.
Fifty-seven known security holes in the packages the code depends on can be used by attackers. Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and thirty-seven controls can't be used without a mouse. Updating the vulnerable packages, pinning each tool to an exact version and making the controls work with a keyboard would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and passing outside input through environment variables would deal with the two pipeline steps that put outside input straight into a shell command. The 15 form fields without a label need a label.
The product code is 313,797 lines, about €430,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 40 to 70, the lowest score rated Strong, the score would rise from 45 to about 49.
Code composition: what the lines of code are
Product code 64%Tests 36%
New since the last survey: 123 findings
These 123 critical or serious findings weren't in the previous survey, on 22 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare 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: 3795 findings
These 3795 critical or serious findings were in the previous survey, on 22 October 2026, and are gone from this one. The first 100 are listed here.
€140,000 to €720,000, for 2,391 to 7,585 hours of work, about 3.0 person-years for 1 to 6 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 45. 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: 313,797 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: We price 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 9 One package at two majors across the workspace finding(s) in Dependency Hygiene.
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 €430,000 to build again, about 3.0 person-years of work. Its weakest lens is Production Readiness, at 40 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 9 One package at two majors across the workspace finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 9 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 737,315 lines over the last 90 days, which is about 2,990,222 lines a year. At that pace, the extra work comes to an estimated 623 to 3737.8 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 our 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 · 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 1420 dependencies between them. Every module uses only modules listed above it, so there are no loops.
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.
apps.smithy-next.src.components uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break apps.smithy-next.src.components, while a change to apps.smithy-next.src.components can't break apps.quarry-web.src.App.
Position
Below the diagonal: apps.smithy-next.src.components uses a module listed above it, which is the healthy direction.
apps.smithy-next.src.components.overlays uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break apps.smithy-next.src.components.overlays, while a change to apps.smithy-next.src.components.overlays can't break apps.quarry-web.src.App.
Position
Below the diagonal: apps.smithy-next.src.components.overlays uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.smithy-next.src.components.overlays.sessions uses a type in apps.smithy-next.src.components.overlays.sessions.session-types.
apps.smithy-next.src.components.overlays.sessions uses apps.smithy-next.src.components.overlays.sessions.session-types, so a change to apps.smithy-next.src.components.overlays.sessions.session-types can break apps.smithy-next.src.components.overlays.sessions, while a change to apps.smithy-next.src.components.overlays.sessions can't break apps.smithy-next.src.components.overlays.sessions.session-types.
Position
Below the diagonal: apps.smithy-next.src.components.overlays.sessions uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.types uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break apps.smithy-web.src.api.types, while a change to apps.smithy-web.src.api.types can't break apps.quarry-web.src.App.
Position
Below the diagonal: apps.smithy-web.src.api.types uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.types uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break apps.smithy-web.src.api.types, while a change to apps.smithy-web.src.api.types can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: apps.smithy-web.src.api.types uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.types uses apps.quarry-web.src.routes.timeline.types, so a change to apps.quarry-web.src.routes.timeline.types can break apps.smithy-web.src.api.types, while a change to apps.smithy-web.src.api.types can't break apps.quarry-web.src.routes.timeline.types.
Position
Below the diagonal: apps.smithy-web.src.api.types uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.types uses apps.smithy-next.src.components.overlays.sessions.session-types, so a change to apps.smithy-next.src.components.overlays.sessions.session-types can break apps.smithy-web.src.api.types, while a change to apps.smithy-web.src.api.types can't break apps.smithy-next.src.components.overlays.sessions.session-types.
Position
Below the diagonal: apps.smithy-web.src.api.types uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.components.editor uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break apps.smithy-web.src.components.editor, while a change to apps.smithy-web.src.components.editor can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: apps.smithy-web.src.components.editor uses a module listed above it, which is the healthy direction.
packages.quarry.src.services.inbox uses packages.storage.src.backend, so a change to packages.storage.src.backend can break packages.quarry.src.services.inbox, while a change to packages.quarry.src.services.inbox can't break packages.storage.src.backend.
Position
Below the diagonal: packages.quarry.src.services.inbox uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.hooks uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break apps.smithy-web.src.api.hooks, while a change to apps.smithy-web.src.api.hooks can't break apps.quarry-web.src.App.
Position
Below the diagonal: apps.smithy-web.src.api.hooks uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.hooks uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break apps.smithy-web.src.api.hooks, while a change to apps.smithy-web.src.api.hooks can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: apps.smithy-web.src.api.hooks uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.hooks uses apps.smithy-next.src.components.overlays.sessions.session-types, so a change to apps.smithy-next.src.components.overlays.sessions.session-types can break apps.smithy-web.src.api.hooks, while a change to apps.smithy-web.src.api.hooks can't break apps.smithy-next.src.components.overlays.sessions.session-types.
Position
Below the diagonal: apps.smithy-web.src.api.hooks uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.hooks uses packages.shared-routes.src.ws.types, so a change to packages.shared-routes.src.ws.types can break apps.smithy-web.src.api.hooks, while a change to apps.smithy-web.src.api.hooks can't break packages.shared-routes.src.ws.types.
Position
Below the diagonal: apps.smithy-web.src.api.hooks uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.api.hooks uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break apps.smithy-web.src.api.hooks, while a change to apps.smithy-web.src.api.hooks can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: apps.smithy-web.src.api.hooks uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.components.agent uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break apps.smithy-web.src.components.agent, while a change to apps.smithy-web.src.components.agent can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: apps.smithy-web.src.components.agent uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.components.task uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break apps.smithy-web.src.components.task, while a change to apps.smithy-web.src.components.task can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: apps.smithy-web.src.components.task uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.hooks uses apps.quarry-web.src.lib.task-constants, so a change to apps.quarry-web.src.lib.task-constants can break apps.smithy-web.src.hooks, while a change to apps.smithy-web.src.hooks can't break apps.quarry-web.src.lib.task-constants.
Position
Below the diagonal: apps.smithy-web.src.hooks uses a module listed above it, which is the healthy direction.
apps.smithy-web.src.hooks uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break apps.smithy-web.src.hooks, while a change to apps.smithy-web.src.hooks can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: apps.smithy-web.src.hooks uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.types uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.quarry.src.api.types, while a change to packages.quarry.src.api.types can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.quarry.src.api.types uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.types uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.quarry.src.api.types, while a change to packages.quarry.src.api.types can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.quarry.src.api.types uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.types uses apps.quarry-web.src.lib.task-constants, so a change to apps.quarry-web.src.lib.task-constants can break packages.quarry.src.api.types, while a change to packages.quarry.src.api.types can't break apps.quarry-web.src.lib.task-constants.
Position
Below the diagonal: packages.quarry.src.api.types uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.types uses apps.quarry-web.src.routes.plans.types, so a change to apps.quarry-web.src.routes.plans.types can break packages.quarry.src.api.types, while a change to packages.quarry.src.api.types can't break apps.quarry-web.src.routes.plans.types.
Position
Below the diagonal: packages.quarry.src.api.types uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.types uses apps.quarry-web.src.routes.timeline.types, so a change to apps.quarry-web.src.routes.timeline.types can break packages.quarry.src.api.types, while a change to packages.quarry.src.api.types can't break apps.quarry-web.src.routes.timeline.types.
Position
Below the diagonal: packages.quarry.src.api.types uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.types uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.quarry.src.api.types, while a change to packages.quarry.src.api.types can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.quarry.src.api.types uses a module listed above it, which is the healthy direction.
packages.ui.src.workflows.components uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.ui.src.workflows.components, while a change to packages.ui.src.workflows.components can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.ui.src.workflows.components uses a module listed above it, which is the healthy direction.
packages.core.src.types.external-sync uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.core.src.types.external-sync, while a change to packages.core.src.types.external-sync can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.core.src.types.external-sync uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.quarry-api uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.quarry-api uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.quarry-api uses apps.quarry-web.src.routes.plans.types, so a change to apps.quarry-web.src.routes.plans.types can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break apps.quarry-web.src.routes.plans.types.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.quarry-api uses packages.storage.src.backend, so a change to packages.storage.src.backend can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break packages.storage.src.backend.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.quarry-api uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
packages.quarry.src.api.quarry-api uses packages.quarry.src.services.inbox, so a change to packages.quarry.src.services.inbox can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break packages.quarry.src.services.inbox.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in packages.quarry.src.api.quarry-api uses a type in packages.quarry.src.api.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
packages.quarry.src.api.quarry-api uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.quarry.src.api.quarry-api, while a change to packages.quarry.src.api.quarry-api can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.quarry.src.api.quarry-api uses a module listed above it, which is the healthy direction.
packages.core.src.types uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.core.src.types, while a change to packages.core.src.types can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.core.src.types uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.core.src.types, while a change to packages.core.src.types can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.core.src.types uses apps.quarry-web.src.routes.plans.types, so a change to apps.quarry-web.src.routes.plans.types can break packages.core.src.types, while a change to packages.core.src.types can't break apps.quarry-web.src.routes.plans.types.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.core.src.types uses apps.quarry-web.src.routes.timeline.types, so a change to apps.quarry-web.src.routes.timeline.types can break packages.core.src.types, while a change to packages.core.src.types can't break apps.quarry-web.src.routes.timeline.types.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.core.src.types uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.core.src.types, while a change to packages.core.src.types can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.core.src.types uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.core.src.types, while a change to packages.core.src.types can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.core.src.types uses packages.core.src.types.external-sync, so a change to packages.core.src.types.external-sync can break packages.core.src.types, while a change to packages.core.src.types can't break packages.core.src.types.external-sync.
Position
Below the diagonal: packages.core.src.types uses a module listed above it, which is the healthy direction.
packages.quarry.src.cli.commands uses packages.storage.src.backend, so a change to packages.storage.src.backend can break packages.quarry.src.cli.commands, while a change to packages.quarry.src.cli.commands can't break packages.storage.src.backend.
Position
Below the diagonal: packages.quarry.src.cli.commands uses a module listed above it, which is the healthy direction.
packages.quarry.src.cli.commands uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.quarry.src.cli.commands, while a change to packages.quarry.src.cli.commands can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.quarry.src.cli.commands uses a module listed above it, which is the healthy direction.
packages.quarry.src.cli.commands uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.quarry.src.cli.commands, while a change to packages.quarry.src.cli.commands can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.quarry.src.cli.commands uses a module listed above it, which is the healthy direction.
packages.quarry.src.cli.commands uses packages.core.src.types.external-sync, so a change to packages.core.src.types.external-sync can break packages.quarry.src.cli.commands, while a change to packages.quarry.src.cli.commands can't break packages.core.src.types.external-sync.
Position
Below the diagonal: packages.quarry.src.cli.commands uses a module listed above it, which is the healthy direction.
packages.smithy.src.api.orchestrator-api uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.smithy.src.api.orchestrator-api, while a change to packages.smithy.src.api.orchestrator-api can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.smithy.src.api.orchestrator-api uses a module listed above it, which is the healthy direction.
packages.smithy.src.api.orchestrator-api uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.smithy.src.api.orchestrator-api, while a change to packages.smithy.src.api.orchestrator-api can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.smithy.src.api.orchestrator-api uses a module listed above it, which is the healthy direction.
packages.smithy.src.api.orchestrator-api uses packages.storage.src.backend, so a change to packages.storage.src.backend can break packages.smithy.src.api.orchestrator-api, while a change to packages.smithy.src.api.orchestrator-api can't break packages.storage.src.backend.
Position
Below the diagonal: packages.smithy.src.api.orchestrator-api uses a module listed above it, which is the healthy direction.
packages.smithy.src.api.orchestrator-api uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.api.orchestrator-api, while a change to packages.smithy.src.api.orchestrator-api can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.api.orchestrator-api uses a module listed above it, which is the healthy direction.
packages.smithy.src.api.orchestrator-api uses packages.quarry.src.api.quarry-api, so a change to packages.quarry.src.api.quarry-api can break packages.smithy.src.api.orchestrator-api, while a change to packages.smithy.src.api.orchestrator-api can't break packages.quarry.src.api.quarry-api.
Position
Below the diagonal: packages.smithy.src.api.orchestrator-api uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.agent-registry uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.smithy.src.services.agent-registry, while a change to packages.smithy.src.services.agent-registry can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.smithy.src.services.agent-registry uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.agent-registry uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.services.agent-registry, while a change to packages.smithy.src.services.agent-registry can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.agent-registry uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.agent-registry uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.services.agent-registry, while a change to packages.smithy.src.services.agent-registry can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.agent-registry uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.agent-registry uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.services.agent-registry, while a change to packages.smithy.src.services.agent-registry can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.services.agent-registry uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.smithy.src.runtime.session-manager uses a type in apps.smithy-next.src.components.overlays.sessions.session-types.
packages.smithy.src.runtime.session-manager uses apps.smithy-next.src.components.overlays.sessions.session-types, so a change to apps.smithy-next.src.components.overlays.sessions.session-types can break packages.smithy.src.runtime.session-manager, while a change to packages.smithy.src.runtime.session-manager can't break apps.smithy-next.src.components.overlays.sessions.session-types.
Position
Below the diagonal: packages.smithy.src.runtime.session-manager uses a module listed above it, which is the healthy direction.
packages.smithy.src.runtime.session-manager uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.runtime.session-manager, while a change to packages.smithy.src.runtime.session-manager can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.runtime.session-manager uses a module listed above it, which is the healthy direction.
packages.smithy.src.runtime.session-manager uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.runtime.session-manager, while a change to packages.smithy.src.runtime.session-manager can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.runtime.session-manager uses a module listed above it, which is the healthy direction.
packages.smithy.src.runtime.session-manager uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.runtime.session-manager, while a change to packages.smithy.src.runtime.session-manager can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.runtime.session-manager uses a module listed above it, which is the healthy direction.
packages.smithy.src.runtime.session-manager uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.runtime.session-manager, while a change to packages.smithy.src.runtime.session-manager can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.runtime.session-manager uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-service uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.smithy.src.services.dispatch-service, while a change to packages.smithy.src.services.dispatch-service can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.smithy.src.services.dispatch-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-service uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.smithy.src.services.dispatch-service, while a change to packages.smithy.src.services.dispatch-service can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.smithy.src.services.dispatch-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-service uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.services.dispatch-service, while a change to packages.smithy.src.services.dispatch-service can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.dispatch-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-service uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.services.dispatch-service, while a change to packages.smithy.src.services.dispatch-service can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.services.dispatch-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-service uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.services.dispatch-service, while a change to packages.smithy.src.services.dispatch-service can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.services.dispatch-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.merge-steward-service uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.smithy.src.services.merge-steward-service, while a change to packages.smithy.src.services.merge-steward-service can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.smithy.src.services.merge-steward-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.merge-steward-service uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.services.merge-steward-service, while a change to packages.smithy.src.services.merge-steward-service can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.merge-steward-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.merge-steward-service uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.services.merge-steward-service, while a change to packages.smithy.src.services.merge-steward-service can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.merge-steward-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.merge-steward-service uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.services.merge-steward-service, while a change to packages.smithy.src.services.merge-steward-service can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.services.merge-steward-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.merge-steward-service uses packages.smithy.src.services.dispatch-service, so a change to packages.smithy.src.services.dispatch-service can break packages.smithy.src.services.merge-steward-service, while a change to packages.smithy.src.services.merge-steward-service can't break packages.smithy.src.services.dispatch-service.
Position
Below the diagonal: packages.smithy.src.services.merge-steward-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses packages.smithy.src.runtime.session-manager, so a change to packages.smithy.src.runtime.session-manager can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break packages.smithy.src.runtime.session-manager.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.worker-task-service uses packages.smithy.src.services.dispatch-service, so a change to packages.smithy.src.services.dispatch-service can break packages.smithy.src.services.worker-task-service, while a change to packages.smithy.src.services.worker-task-service can't break packages.smithy.src.services.dispatch-service.
Position
Below the diagonal: packages.smithy.src.services.worker-task-service uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.steward-scheduler uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.services.steward-scheduler, while a change to packages.smithy.src.services.steward-scheduler can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.steward-scheduler uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.steward-scheduler uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.services.steward-scheduler, while a change to packages.smithy.src.services.steward-scheduler can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.services.steward-scheduler uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.steward-scheduler uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.services.steward-scheduler, while a change to packages.smithy.src.services.steward-scheduler can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.services.steward-scheduler uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.steward-scheduler uses packages.smithy.src.runtime.session-manager, so a change to packages.smithy.src.runtime.session-manager can break packages.smithy.src.services.steward-scheduler, while a change to packages.smithy.src.services.steward-scheduler can't break packages.smithy.src.runtime.session-manager.
Position
Below the diagonal: packages.smithy.src.services.steward-scheduler uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.steward-scheduler uses packages.smithy.src.services.merge-steward-service, so a change to packages.smithy.src.services.merge-steward-service can break packages.smithy.src.services.steward-scheduler, while a change to packages.smithy.src.services.steward-scheduler can't break packages.smithy.src.services.merge-steward-service.
Position
Below the diagonal: packages.smithy.src.services.steward-scheduler uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.storage.src.backend, so a change to packages.storage.src.backend can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.storage.src.backend.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.quarry.src.services.inbox, so a change to packages.quarry.src.services.inbox can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.quarry.src.services.inbox.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.quarry.src.api.types.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.runtime.session-manager, so a change to packages.smithy.src.runtime.session-manager can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.runtime.session-manager.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.services.dispatch-service, so a change to packages.smithy.src.services.dispatch-service can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.services.dispatch-service.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.services.merge-steward-service, so a change to packages.smithy.src.services.merge-steward-service can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.services.merge-steward-service.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.services.worker-task-service, so a change to packages.smithy.src.services.worker-task-service can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.services.worker-task-service.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
apps.smithy-server.src.services uses packages.smithy.src.services.steward-scheduler, so a change to packages.smithy.src.services.steward-scheduler can break apps.smithy-server.src.services, while a change to apps.smithy-server.src.services can't break packages.smithy.src.services.steward-scheduler.
Position
Below the diagonal: apps.smithy-server.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.storage.src.backend, so a change to packages.storage.src.backend can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.storage.src.backend.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.quarry.src.services.inbox, so a change to packages.quarry.src.services.inbox can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.quarry.src.services.inbox.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.runtime.session-manager, so a change to packages.smithy.src.runtime.session-manager can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.runtime.session-manager.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.services.dispatch-service, so a change to packages.smithy.src.services.dispatch-service can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.services.dispatch-service.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.services.merge-steward-service, so a change to packages.smithy.src.services.merge-steward-service can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.services.merge-steward-service.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.services.worker-task-service, so a change to packages.smithy.src.services.worker-task-service can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.services.worker-task-service.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.server.services uses packages.smithy.src.services.steward-scheduler, so a change to packages.smithy.src.services.steward-scheduler can break packages.smithy.src.server.services, while a change to packages.smithy.src.server.services can't break packages.smithy.src.services.steward-scheduler.
Position
Below the diagonal: packages.smithy.src.server.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses apps.quarry-web.src.api.hooks.useAllElements, so a change to apps.quarry-web.src.api.hooks.useAllElements can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break apps.quarry-web.src.api.hooks.useAllElements.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.quarry.src.services.inbox, so a change to packages.quarry.src.services.inbox can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.quarry.src.services.inbox.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.smithy.src.runtime.session-manager, so a change to packages.smithy.src.runtime.session-manager can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.smithy.src.runtime.session-manager.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.smithy.src.services.dispatch-service, so a change to packages.smithy.src.services.dispatch-service can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.smithy.src.services.dispatch-service.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.services.dispatch-daemon uses packages.smithy.src.services.steward-scheduler, so a change to packages.smithy.src.services.steward-scheduler can break packages.smithy.src.services.dispatch-daemon, while a change to packages.smithy.src.services.dispatch-daemon can't break packages.smithy.src.services.steward-scheduler.
Position
Below the diagonal: packages.smithy.src.services.dispatch-daemon uses a module listed above it, which is the healthy direction.
packages.smithy.src.server uses apps.quarry-web.src.App, so a change to apps.quarry-web.src.App can break packages.smithy.src.server, while a change to packages.smithy.src.server can't break apps.quarry-web.src.App.
Position
Below the diagonal: packages.smithy.src.server uses a module listed above it, which is the healthy direction.
packages.smithy.src.server uses packages.shared-routes.src.ws.types, so a change to packages.shared-routes.src.ws.types can break packages.smithy.src.server, while a change to packages.smithy.src.server can't break packages.shared-routes.src.ws.types.
Position
Below the diagonal: packages.smithy.src.server uses a module listed above it, which is the healthy direction.
packages.smithy.src.server uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.server, while a change to packages.smithy.src.server can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.server uses a module listed above it, which is the healthy direction.
packages.smithy.src.server uses packages.smithy.src.services.steward-scheduler, so a change to packages.smithy.src.services.steward-scheduler can break packages.smithy.src.server, while a change to packages.smithy.src.server can't break packages.smithy.src.services.steward-scheduler.
Position
Below the diagonal: packages.smithy.src.server uses a module listed above it, which is the healthy direction.
packages.smithy.src.server uses apps.smithy-server.src.services, so a change to apps.smithy-server.src.services can break packages.smithy.src.server, while a change to packages.smithy.src.server can't break apps.smithy-server.src.services.
Position
Below the diagonal: packages.smithy.src.server uses a module listed above it, which is the healthy direction.
packages.smithy.src.server uses packages.smithy.src.server.services, so a change to packages.smithy.src.server.services can break packages.smithy.src.server, while a change to packages.smithy.src.server can't break packages.smithy.src.server.services.
Position
Below the diagonal: packages.smithy.src.server uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses apps.quarry-web.src.routes.timeline.types, so a change to apps.quarry-web.src.routes.timeline.types can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break apps.quarry-web.src.routes.timeline.types.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.storage.src.backend, so a change to packages.storage.src.backend can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.storage.src.backend.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses apps.smithy-web.src.api.types, so a change to apps.smithy-web.src.api.types can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break apps.smithy-web.src.api.types.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.quarry.src.services.inbox, so a change to packages.quarry.src.services.inbox can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.quarry.src.services.inbox.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.quarry.src.api.types, so a change to packages.quarry.src.api.types can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.quarry.src.api.types.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.core.src.types.external-sync, so a change to packages.core.src.types.external-sync can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.core.src.types.external-sync.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.api.orchestrator-api, so a change to packages.smithy.src.api.orchestrator-api can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.api.orchestrator-api.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.services.agent-registry, so a change to packages.smithy.src.services.agent-registry can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.services.agent-registry.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.runtime.session-manager, so a change to packages.smithy.src.runtime.session-manager can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.runtime.session-manager.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.services.dispatch-service, so a change to packages.smithy.src.services.dispatch-service can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.services.dispatch-service.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.services.merge-steward-service, so a change to packages.smithy.src.services.merge-steward-service can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.services.merge-steward-service.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.services.worker-task-service, so a change to packages.smithy.src.services.worker-task-service can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.services.worker-task-service.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.services.steward-scheduler, so a change to packages.smithy.src.services.steward-scheduler can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.services.steward-scheduler.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
packages.smithy.src.services uses packages.smithy.src.services.dispatch-daemon, so a change to packages.smithy.src.services.dispatch-daemon can break packages.smithy.src.services, while a change to packages.smithy.src.services can't break packages.smithy.src.services.dispatch-daemon.
Position
Below the diagonal: packages.smithy.src.services uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 42% · Weak · gated by D1, D2, R3 ·
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
A03:2025 — Software Supply Chain Failures
76
High / Critical
A05:2025 — Injection
58
High / Critical
Roadmap
Top priorities: Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14); Resolve the 9 One package at two majors across the workspace finding(s) in Dependency Hygiene; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 9 One package at two majors across the workspace finding(s) in Dependency Hygiene.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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 — 173
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 — 3224
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 — 1596
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
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
This survey 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. All 85 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 85 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, 4913 of 4993 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 or a scanner, 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 — We 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: the JavaScript/TypeScript half could not be measured — the dependency install for apps/smithy-server/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for apps/smithy-server/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in apps/smithy-server/ was NOT MEASURED: the dependency install for apps/smithy-server/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in packages/core/ was NOT MEASURED: the dependency install for packages/core/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in packages/quarry/ was NOT MEASURED: the dependency install for packages/quarry/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in packages/smithy/ was NOT MEASURED: the dependency install for packages/smithy/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in packages/storage/ was NOT MEASURED: the dependency install for packages/storage/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in packages/ui/ was NOT MEASURED: the dependency install for packages/ui/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 829 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 3 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 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.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We 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.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx`, `apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.tsx`, `apps/smithy-next/src/components/overlays/ci/CIRunDetailView.tsx`, `apps/smithy-server/src/routes/events.ts`, `apps/smithy-server/src/routes/sessions.ts`, … (+14 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — We 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 Dockerfile) is simply not read here yet.
AC1 Text alternatives — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 builds user interface as HTML STRINGS — 7 script file(s) building 33 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages/ui/src/message/MessageRichComposer.tsx, REDACTED, REDACTED) — that this run could NOT read, and the accessibility cards beside it were measured over the 555 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 builds user interface as HTML STRINGS — 7 script file(s) building 33 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages/ui/src/message/MessageRichComposer.tsx, REDACTED, REDACTED) — that this run could NOT read, and the accessibility cards beside it were measured over the 555 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 629 further occurrence(s) are not listed individually; the score already reflects all 669.
AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 builds user interface as HTML STRINGS — 7 script file(s) building 33 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages/ui/src/message/MessageRichComposer.tsx, REDACTED, REDACTED) — that this run could NOT read, and the accessibility cards beside it were measured over the 555 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 builds user interface as HTML STRINGS — 7 script file(s) building 33 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages/ui/src/message/MessageRichComposer.tsx, REDACTED, REDACTED) — that this run could NOT read, and the accessibility cards beside it were measured over the 555 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 222 further occurrence(s) are not listed individually; the score already reflects all 262.
AC5 ARIA correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 builds user interface as HTML STRINGS — 7 script file(s) building 33 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages/ui/src/message/MessageRichComposer.tsx, REDACTED, REDACTED) — that this run could NOT read, and the accessibility cards beside it were measured over the 555 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 builds user interface as HTML STRINGS — 7 script file(s) building 33 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages/ui/src/message/MessageRichComposer.tsx, REDACTED, REDACTED) — that this run could NOT read, and the accessibility cards beside it were measured over the 555 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 160 further occurrence(s) are not listed individually; the score already reflects all 200.
AX1 Captive dependencies — not measured this run — We 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 reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/smithy/src/providers/registry.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We 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. The dev server exited, and its output does not match a cause we recognise. (rule: unrecognised-exit). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "https://turborepo.dev/docs/telemetry / • turbo 2.11.10 / • Packages in scope: @stoneforge/core, @stoneforge/docs, @stoneforge/quarry, @stoneforge/quarry-server, @stoneforge/quarry-web, @stoneforge/shared-routes, @stoneforge/smithy, @stoneforge/smithy-next, @stoneforge/smithy-server, @stoneforge/smithy-web, @stoneforge/storage, @stoneforge/ui, @stoneforge/website / • Running dev in 13 packages / • Remote caching disabled / x Unable to find package manager binary: cannot find binary path / `-> cannot find binary path" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "https://turborepo.dev/docs/telemetry / • turbo 2.11.10 / • Packages in scope: @stoneforge/core, @stoneforge/docs, @stoneforge/quarry, @stoneforge/quarry-server, @stoneforge/quarry-web, @stoneforge/shared-routes, @stoneforge/smithy, @stoneforge/smithy-next, @stoneforge/smithy-server, @stoneforge/smithy-web, @stoneforge/storage, @stoneforge/ui, @stoneforge/website / • Running dev in 13 packages / • Remote caching disabled / x Unable to find package manager binary: cannot find binary path / `-> cannot find binary path" No runtime evidence was gathered.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 1019 further occurrence(s) are not listed individually; the score already reflects all 1059.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we 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), and artefact counts an order of magnitude off. 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.
PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 1447 further occurrence(s) are not listed individually; the score already reflects all 1487.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 200 further occurrence(s) are not listed individually; the score already reflects all 240.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 200 further occurrence(s) are not listed individually; the score already reflects all 240.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 251 further occurrence(s) are not listed individually; the score already reflects all 291.
X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 141 further occurrence(s) are not listed individually; the score already reflects all 181.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 200 further occurrence(s) are not listed individually; the score already reflects all 240.
X4 Structured logging — not measured this run — We 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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".
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.
541 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.createQuarryApp at 561. A further 10 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 merge.configurationsEqual at 28 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/ui/src/workflows/components/WorkflowProgressDashboard.tsx (WorkflowProgressDashboard.FunctionStepListItem at 19), apps/smithy-server/src/formatters.ts (formatters.generateActivitySummary at 18), packages/smithy/src/server/formatters.ts (formatters.generateActivitySummary at 18), apps/smithy-next/src/components/overlays/sessions/SessionEventDetail.tsx (SessionEventDetail.SessionEventDetail 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.
+ 500 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 48 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with index.createQuarryApp (cyclomatic 561), documents.createDocumentRoutes (cyclomatic 252), index.FileEditorPage (cyclomatic 210). — 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 48 together lifts Cyclomatic Complexity from 2.0 to about 3.2/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.
+ 535 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 65 bodies over 60 down to 60 or less in Cognitive Complexity — start with index.createQuarryApp (cognitive 619), documents.createDocumentRoutes (cognitive 280), index.FileEditorPage (cognitive 229). — 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 65 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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 Classes4.4 / 10Weak✓ 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 383 FunctionTooLong finding(s) in God Classes — start with index.tsx (28), TaskDetailPanel.tsx (13), KanbanBoard.tsx (8). — One of this dimension's main actionable groups (383 warning-level).
Resolve the 85 FileTooLong finding(s) in God Classes — start with index.tsx (8), KanbanBoard.tsx (3), TaskDetailPanel.tsx (2). — One of this dimension's main actionable groups (85 warning-level).
Resolve the 27 ClassTooLong finding(s) in God Classes — start with DirectorPanel.tsx (2), quarry-api.ts, dispatch-daemon.ts. — One of this dimension's main actionable groups (27 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.4 / 10Stronggated by 1 serious finding✓ 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.
13 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
Off the main sequence: @stoneforge/core
What to do
Resolve the 1 Off the main sequence 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.
12888 test methods: 12888 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 12888 `it`/`test` case(s) across 342 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality8.4 / 10Adequategated by 1 critical finding✓ 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.
1012 skipped (4 with a documented reason), 24 zero-assertion, 14 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 12888 tests.
No assertions (empty test): off() removes callbackpackages/core/src/types/playbook-yaml.bun.test.ts:876
Skipped test: continues polling after errors · ×1008packages/smithy/src/services/dispatch-daemon.bun.test.ts:387
No assertions: handles heartbeat event · ×23packages/ui/src/api/sse-client.test.ts:260
Fixed-sleep synchronisation: resumes predecessor session with correct options · ×14packages/smithy/src/runtime/predecessor-query.bun.test.ts:304
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with playbook-yaml.bun.test.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1008 Skipped test finding(s) in Test Quality — start with teams.spec.ts (53), entities.spec.ts (51), dependency-graph.spec.ts (41). — One of this dimension's main actionable groups (1008 warning-level).
Resolve the 23 No assertions finding(s) in Test Quality — start with progress.bun.test.ts (5), websocket.test.ts (4), session-manager.bun.test.ts (2). — One of this dimension's main actionable groups (23 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
57 outdated direct production npm dependency(ies) of 73 graded, 9 pinning defect(s), across 15 package.json (13 of them the product) and 5 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
One package at two majors across the workspace: @tiptap/core · ×9
Resolve the 9 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
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.
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.
14 of 789 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 789 package(s) this repository's committed lockfile installs for a consumer — its 76 production, optional and peer dependency(ies), across 13 product package.json manifest(s), and everything those install in turn. Its 109 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 3 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: REDACTED (5×561=2805); packages/smithy/src/services/dispatch-daemon.ts (56×42=2352); apps/smithy-web/src/components/layout/AppShell.tsx (22×83=1826) Repeated repair below the complexity floor: packages/smithy/src/providers/opencode/server-manager.ts (5 of 6 changes were fixes); packages/smithy/src/providers/claude/interactive.ts (3 of 5 changes were fixes); packages/smithy/src/providers/opencode/interactive.ts (3 of 5 changes were fixes)
Resolve the 56 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.tsx (4), REDACTED (2), agents.ts (2). — One of this dimension's main actionable groups (56 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with interactive.ts (2), server-manager.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_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.
10 deducted task-comment markers across 312232 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 10 TodoComment finding(s) in Explicit Debt — start with DocumentDetailPanel.tsx (3), handoff.ts, local-provider.ts. — One of this dimension's main actionable groups (10 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.
2 of 2 documentation facets pass in full. 45 document(s) read across 15 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: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. 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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×10packages/core/src/errors/codes.ts:22
What to do
Resolve the 571 redundant comment finding(s) in Comment Value — start with index.tsx (15), REDACTED (14), usePaginatedData.ts (6). — One of this dimension's main actionable groups (571 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
7 of 14 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
9 % of calls cross a namespace and 1 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
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).
58 finding(s): 0 critical, 25 high, 33 medium, 0 low. 16 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 28 file(s) — `apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx` (line 525, line 878, line 879, …), `apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.tsx` (line 21), `apps/smithy-next/src/components/overlays/ci/CIRunDetailView.tsx` (line 325), `apps/smithy-server/src/routes/events.ts` (line 169), `apps/smithy-server/src/routes/sessions.ts` (line 22, line 173), … (+23 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 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
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 16 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (16 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 51 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (32), REDACTED (19). — One of this dimension's main actionable groups (51 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 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.
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.
817 of 817 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 817 of the 1076 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 814 Orphaned file finding(s) in Knowledge Freshness — start with index.tsx (23), types.ts (16), REDACTED (13). — One of this dimension's main actionable groups (814 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED, mock-data.ts, dispatch-daemon.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase 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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 alternatives6.7 / 10Adequate✓ Tool-verified
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.
Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). — apps/website/src/components/sections/DemoSection.astro:35
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels4.7 / 10Weak✓ 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.
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. (×15) — apps/quarry-web/src/components/document/CreateDocumentModal.tsx:270, apps/quarry-web/src/components/document/CreateLibraryModal.tsx:226, apps/quarry-web/src/components/editor/ImageUploadModal.tsx:438, …
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. (×4) — apps/quarry-web/src/components/document/CreateDocumentModal.tsx:273, apps/quarry-web/src/components/document/CreateLibraryModal.tsx:229, apps/quarry-web/src/components/task/CreateTaskModal.tsx:340, …
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). (×3) — apps/quarry-web/src/components/editor/CommentsPanel.tsx:97, apps/quarry-web/src/components/navigation/CommandPalette.tsx:525, apps/quarry-web/src/components/task/BulkActionMenu.tsx:191
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. (×10) — apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:212, apps/quarry-web/src/components/editor/ImageUploadModal.tsx:441, apps/quarry-web/src/components/editor/ImageUploadModal.tsx:471, …
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. (×3) — apps/quarry-web/src/components/shared/ContributionChart.tsx:302, apps/quarry-web/src/components/task/TaskDetailPanel.tsx:416, apps/quarry-web/src/components/task/TaskDetailPanel.tsx:634
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×5) — apps/quarry-web/src/components/task/FilterBar.tsx:126, apps/quarry-web/src/components/task/KanbanBoard.tsx:492, apps/quarry-web/src/components/task/KanbanBoard.tsx:555, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure7.5 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×8) — apps/quarry-web/src/routes/workflows/index.tsx:355, apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:317, REDACTED:437, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×22) — apps/quarry-web/src/components/editor/CommentsPanel.tsx:54, apps/quarry-web/src/components/editor/ImageUploadModal.tsx:401, apps/quarry-web/src/components/editor/ImageUploadModal.tsx:503, …
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — apps/quarry-web/src/components/navigation/CommandPalette.tsx:330, apps/quarry-web/src/components/navigation/CommandPalette.tsx:509
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}. (×12) — apps/quarry-web/src/components/task/TaskDetailPanel.tsx:416, apps/quarry-web/src/components/task/TaskDetailPanel.tsx:634, apps/quarry-web/src/components/task/TaskDetailPanel.tsx:942, …
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:369
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. (×3) — apps/smithy-next/src/components/BottomPanel.tsx:89, apps/smithy-next/src/components/DirectorPanel.tsx:287, apps/smithy-next/src/components/DirectorPanel.tsx:728
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.
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.
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×32) — apps/quarry-web/src/components/editor/BlockEditor.tsx:111, apps/quarry-web/src/components/editor/BubbleMenu.tsx:49, apps/quarry-web/src/components/editor/ImageUploadModal.tsx:526, …
<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). (×2) — apps/quarry-web/src/components/navigation/CommandPalette.tsx:353, apps/quarry-web/src/components/navigation/CommandPalette.tsx:538
<div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×3) — apps/quarry-web/src/components/shared/DataPreloader.tsx:34, apps/quarry-web/src/components/shared/VirtualizedChatList.tsx:277, apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx:122
<select> 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). (×2) — apps/quarry-web/src/routes/inbox.tsx:1177, apps/quarry-web/src/routes/inbox.tsx:1192
<span> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — apps/quarry-web/src/routes/timeline/index.tsx:349
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
Accessibility checks run in tests (Verified) but aren't gated in CI — run the suite that holds those checks in your pipeline so an accessibility regression blocks the merge (Prevented). What was searched, so you can tell an absence from a miss: the 555 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. — apps/smithy-web/package.json:68
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then run the suite that already asserts accessibility in CI so a regression blocks the merge.
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.
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.
`WorkspaceActions` declares 21 required operations: `addPane`, `removePane`, `setActivePane`, `updatePaneStatus`, `setLayoutPreset`, `reorderPanes`, `setPaneWeight`, `saveLayout`, `loadLayout`, `clearPanes`, `startDrag`, `updateDragTarget`, `endDrag`, `cancelDrag`, `movePaneToPosition`, `swapPanes`, `movePaneUp`, `movePaneDown`, `rotateLayout`, `swapGridSections`, `swap2x2Rows`. 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. — apps/smithy-web/src/components/workspace/types.ts:85
`QuarryAPI` declares 68 required operations: `getIdGeneratorConfig`, `get`, `list`, `listPaginated`, `create`, `update`, `delete`, `lookupEntityByName`, `setEntityManager`, `clearEntityManager`, `getDirectReports`, `getManagementChain`, `getOrgChart`, `addTaskToPlan`, `removeTaskFromPlan`, `getTasksInPlan`, `getPlanProgress`, `createTaskInPlan`, `bulkClosePlanTasks`, `bulkDeferPlanTasks`, `bulkReassignPlanTasks`, `bulkTagPlanTasks`, `ready`, `backlog`, `blocked`, `addDependency`, `removeDependency`, `getDependencies`, `getDependents`, `getDependencyTree`, `satisfyGate`, `recordApproval`, `removeApproval`, `search`, `searchDocumentsFTS`, `archiveDocument`, `unarchiveDocument`, `registerEmbeddingService`, `reindexAllDocumentsFTS`, `getEvents`, and 28 more. 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/quarry/src/api/types.ts:748
`QuarryLikeAPI` declares 22 required operations: `get`, `list`, `listPaginated`, `create`, `update`, `delete`, `search`, `searchDocumentsFTS`, `getDependencies`, `getDependents`, `addDependency`, `removeDependency`, `addChannelMember`, `removeChannelMember`, `leaveChannel`, `mergeChannels`, `getDocumentHistory`, `getDocumentVersion`, `getPlanProgress`, `getTasksInPlan`, `addTaskToPlan`, `removeTaskFromPlan`. 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/shared-routes/src/types.ts:33
`OrchestratorAPI` declares 17 required operations: `registerDirector`, `registerWorker`, `registerSteward`, `getAgent`, `getAgentByName`, `listAgents`, `getAgentsByRole`, `getAvailableWorkers`, `getStewards`, `getDirector`, `updateAgentSession`, `getAgentChannel`, `setTaskOrchestratorMeta`, `updateTaskOrchestratorMeta`, `getTaskOrchestratorMeta`, `assignTaskToAgent`, `updateAgentMetadata`. 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/smithy/src/api/orchestrator-api.ts:118
`AgentRegistry` declares 20 required operations: `registerAgent`, `registerDirector`, `registerWorker`, `registerSteward`, `getAgent`, `getAgentByName`, `listAgents`, `getAgentsByRole`, `getAvailableWorkers`, `getStewards`, `getDirector`, `getDirectors`, `getAvailableDirector`, `updateAgentSession`, `updateAgentMetadata`, `updateAgent`, `deleteAgent`, `getAgentChannel`, `getAgentChannelId`, `ensureAgentChannel`. 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/smithy/src/services/agent-registry.ts:118
`SessionManager` declares 20 required operations: `startSession`, `resumeSession`, `stopSession`, `suspendSession`, `interruptSession`, `getSession`, `getActiveSession`, `listSessions`, `getMostRecentResumableSession`, `getSessionHistory`, `getSessionHistoryByRole`, `getPreviousSession`, `messageSession`, `getEventEmitter`, `recordUserInput`, `getSessionUserIdleMs`, `persistSession`, `loadSessionState`, `reconcileOnStartup`, `setOperationLog`. 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/smithy/src/runtime/session-manager.ts:251
`WorktreeManager` declares 17 required operations: `initWorkspace`, `isInitialized`, `getWorkspaceRoot`, `createWorktree`, `createReadOnlyWorktree`, `removeWorktree`, `suspendWorktree`, `resumeWorktree`, `listWorktrees`, `getWorktree`, `getWorktreePath`, `getWorktreesForAgent`, `worktreeExists`, `ensureWorktreeRemote`, `getCurrentBranch`, `getDefaultBranch`, `branchExists`. 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. — REDACTED:206
`StewardScheduler` declares 20 required operations: `start`, `stop`, `isRunning`, `registerSteward`, `unregisterSteward`, `refreshSteward`, `registerAllStewards`, `executeSteward`, `publishEvent`, `getScheduledJobs`, `getEventSubscriptions`, `getExecutionHistory`, `getLastExecution`, `getStats`, `on`, `on`, `on`, `on`, `on`, `off`. 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. Those 20 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — REDACTED:184
`DispatchDaemon` declares 26 required operations: `start`, `stop`, `isRunning`, `pollWorkerAvailability`, `pollInboxes`, `pollStewardTriggers`, `pollWorkflowTasks`, `recoverOrphanedAssignments`, `reconcileClosedUnmergedTasks`, `recoverStuckMergeTasks`, `pollPlanAutoComplete`, `pollWorkflowAutoTransition`, `handleRateLimitDetected`, `getRateLimitStatus`, `sleepUntil`, `wake`, `getConfig`, `updateConfig`, `on`, `on`, `on`, `on`, `on`, `on`, `on`, `off`. 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. Those 26 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/smithy/src/services/dispatch-daemon.ts:355
`StorageBackend` declares 21 required operations: `close`, `exec`, `query`, `queryOne`, `run`, `prepare`, `transaction`, `getSchemaVersion`, `setSchemaVersion`, `migrate`, `markDirty`, `getDirtyElements`, `clearDirty`, `clearDirtyElements`, `getNextChildNumber`, `getChildCounter`, `resetChildCounter`, `getElementCount`, `checkIntegrity`, `optimize`, `getStats`. 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/storage/src/backend.ts:37
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
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.
Here who may pass is decided by the 'role' form field (if(!body.role||!body.name)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. (×2) — apps/smithy-server/src/routes/agents.ts:52, packages/smithy/src/server/routes/agents.ts:54
Here who is asking is taken from the 'actor' query parameter (const actor = url.searchParams.get('actor')as EntityId|null) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. (×2) — apps/smithy-server/src/routes/events.ts:54, packages/smithy/src/server/routes/events.ts:55
Here who is asking is taken from the 'actor' form field (const actor = (body.actor as EntityId)||('el-0000'as EntityId)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. (×2) — packages/shared-routes/src/documents.ts:893, packages/shared-routes/src/libraries.ts:293
Here who is asking is taken from the 'authorId' form field (const event = createEvent({elementId:documentId, eventType:'comment_added'as EventType,…) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. — packages/shared-routes/src/documents.ts:1167
Here who is asking is taken from the 'author_id' form field (const event = createEvent({elementId:documentId, eventType:'comment_updated'as EventTyp…) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. — packages/shared-routes/src/documents.ts:1251
Here who is asking is taken from the 'actor' form field (const actorEntity = await api.get(body.actor as ElementId)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. — packages/shared-routes/src/documents.ts:1365
Here who is asking is taken from the 'actor' form field (const event = createEvent({elementId:documentId, eventType:eventType as EventType, acto…) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed. — packages/shared-routes/src/documents.ts:1398
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — apps/smithy-web/src/components/activity/ActiveAgentCard.tsx:50
What to do
Keep who is signed in on the server: give the browser only a long random session id (express-session, iron-session, a sessions table), or sign the cookie (cookie-parser with a secret and req.signedCookies, a verified JWT), and look the user up from that — never from an id, role or token claim the browser sends unchecked.
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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.
`onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×9) — apps/quarry-web/src/components/task/KanbanBoard.tsx:1085, apps/smithy-next/src/components/DirectorPanel.tsx:835, apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:372, …
`onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:337, apps/smithy-web/src/routes/documents/components/DocumentLinkComponents.tsx:337
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×15) — apps/quarry-web/src/routes/entities/components/InboxComponents.tsx:389, apps/quarry-web/src/routes/inbox.tsx:664, apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:458, …
`onCreateSession` 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. — apps/smithy-next/src/App.tsx:1091
`onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×3) — apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:605, apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:611, apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1615
`onToggleViewed` 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. — apps/smithy-next/src/components/overlays/mr/MRCommitsTab.tsx:70
`onDragStart` 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. — apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:506
`onDragEnd` 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. — apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:508
`onSelectEvent` 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. — apps/smithy-next/src/components/overlays/sessions/canvas/SessionNode.tsx:290
`commandExists` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/smithy-server/src/services/lsp-manager.ts:63
`onSelect` 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. — apps/smithy-web/src/components/editor/EditorTabBar.tsx:612
`onClose` 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. — apps/smithy-web/src/components/editor/EditorTabBar.tsx:613
The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — apps/smithy-web/src/components/terminal/XTerminal.tsx:688
`stop` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/smithy-web/src/lib/monaco-lsp/lightweight-client.ts:353
`onDismiss` 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. — apps/smithy-web/src/routes/activity/index.tsx:69
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a README to the 8 of 14 project(s) that lack one — worth up to 1.1 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/smithy-next`, `packages/quarry`, `packages/shared-routes`.
`packages/core/src/types/playbook-yaml.ts` reports through `console.*` at line 1233 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/types/playbook-yaml.ts:1233
`packages/core/src/id/generator.ts` reports through `console.*` at line 222 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:222
`packages/core/src/id/generator.ts` reports through `console.*` at line 348 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:348
`packages/core/src/id/generator.ts` reports through `console.*` at line 350 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:350
`packages/core/src/id/generator.ts` reports through `console.*` at line 355 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:355
`packages/core/src/id/generator.ts` reports through `console.*` at line 357 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:357
`packages/core/src/id/generator.ts` reports through `console.*` at line 362 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:362
`packages/core/src/id/generator.ts` reports through `console.*` at line 364 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:364
`packages/core/src/id/generator.ts` reports through `console.*` at line 369 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:369
`packages/core/src/id/generator.ts` reports through `console.*` at line 371 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/id/generator.ts:371
`packages/smithy/src/testing/test-context.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/testing/test-context.ts:171
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 588 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:588
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1469 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1469
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1482 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1482
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1502 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1502
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1511 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1511
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1513 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1513
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1520 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1520
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1528 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1528
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1543 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1543
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1546 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1546
`packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1573 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/session-manager.ts:1573
`packages/smithy/src/runtime/spawner.ts` reports through `console.*` at line 857 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/runtime/spawner.ts:857
`packages/smithy/src/git/merge.ts` reports through `console.*` at line 576 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/git/merge.ts:576
`packages/smithy/src/git/merge.ts` reports through `console.*` at line 594 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/git/merge.ts:594
`packages/smithy/src/git/merge.ts` reports through `console.*` at line 635 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/smithy/src/git/merge.ts:635
`REDACTED` reports through `console.*` at line 722 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:722
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 7984 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:29
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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.
`fetch(` 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. (×8) — packages/quarry/src/cli/commands/reset.ts:52, packages/quarry/src/external-sync/providers/github/github-api.ts:422, packages/quarry/src/external-sync/providers/github/github-api.ts:481, …
`ky(` 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. — packages/quarry/web/assets/editor-vendor-BxraAWts.js:6
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`mkdirSync` in `globalSetup` 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) — apps/quarry-web/tests/global-setup.ts:14, apps/smithy-web/tests/global-setup.ts:24
`rmSync` in `globalTeardown` 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) — apps/quarry-web/tests/global-teardown.ts:11, apps/smithy-web/tests/global-teardown.ts:11
`execSync` in `commandExists` 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. — apps/smithy-server/src/services/lsp-manager.ts:65
`existsSync` in `isAvailable` 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. (×4) — apps/smithy-server/src/services/lsp-manager.ts:94, apps/smithy-server/src/services/lsp-manager.ts:130, apps/smithy-server/src/services/lsp-manager.ts:139, …
`existsSync` in `doctorHandler` 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. — packages/quarry/src/cli/commands/admin.ts:66
`existsSync` in `migrateHandler` 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. — packages/quarry/src/cli/commands/admin.ts:807
`existsSync` in `configEditHandler` 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) — packages/quarry/src/cli/commands/config.ts:198, packages/quarry/src/cli/commands/config.ts:200
`mkdirSync` in `configEditHandler` 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. — packages/quarry/src/cli/commands/config.ts:201
`writeFileSync` in `configEditHandler` 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. — packages/quarry/src/cli/commands/config.ts:203
`spawnSync` in `configEditHandler` 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. — packages/quarry/src/cli/commands/config.ts:213
`existsSync` in `docCreateHandler` 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. — packages/quarry/src/cli/commands/document.ts:116
`readFileSync` in `docCreateHandler` 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. — packages/quarry/src/cli/commands/document.ts:119
`existsSync` in `docUpdateHandler` 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. — packages/quarry/src/cli/commands/document.ts:691
`readFileSync` in `docUpdateHandler` 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. — packages/quarry/src/cli/commands/document.ts:694
`existsSync` in `embeddingsInstallHandler` 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. — packages/quarry/src/cli/commands/embeddings.ts:65
`mkdirSync` in `embeddingsInstallHandler` 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. — packages/quarry/src/cli/commands/embeddings.ts:71
`existsSync` in `embeddingsStatusHandler` 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. — packages/quarry/src/cli/commands/embeddings.ts:114
`readFileSync` in `signHandler` 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. — packages/quarry/src/cli/commands/identity.ts:361
`readFileSync` in `verifyHandler` 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. — packages/quarry/src/cli/commands/identity.ts:556
`readFileSync` in `hashHandler` 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. — packages/quarry/src/cli/commands/identity.ts:743
`existsSync` in `initHandler` 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. (×7) — packages/quarry/src/cli/commands/init.ts:546, packages/quarry/src/cli/commands/init.ts:547, packages/quarry/src/cli/commands/init.ts:586, …
`mkdirSync` in `initHandler` 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) — packages/quarry/src/cli/commands/init.ts:563, packages/quarry/src/cli/commands/init.ts:616
`writeFileSync` in `initHandler` 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) — packages/quarry/src/cli/commands/init.ts:598, packages/quarry/src/cli/commands/init.ts:610, packages/quarry/src/cli/commands/init.ts:624
`existsSync` in `msgSendHandler` 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. — packages/quarry/src/cli/commands/message.ts:226
`readFileSync` in `msgSendHandler` 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. — packages/quarry/src/cli/commands/message.ts:229
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 Safety10.0 / 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.
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.
190 duplicated blocks under apps/ have copies in at least two of the sibling directories quarry-web, smithy-next, smithy-web — 149 of them are reported below, and 41 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 190 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 190 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 190 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. — apps/quarry-web/src/routes/inbox.tsx:8
180 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages — 128 of them are reported below, and 52 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 180 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 180 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 180 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. — apps/smithy-server/src/routes/tasks.ts:7
148 duplicated blocks under apps/smithy-next/src/components/overlays/ have copies in at least two of the sibling directories agents, automations, ci, documents, editor, messages (+7 more sibling(s) not listed) — 89 of them are reported below, and 59 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 148 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 148 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 148 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. — apps/smithy-next/src/components/overlays/documents/DocListView.tsx:358
103 duplicated blocks under packages/ have copies in at least two of the sibling directories core, quarry, shared-routes, smithy, ui — 77 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 103 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 103 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 103 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. — REDACTED:1781
37 duplicated blocks under apps/smithy-web/src/components/ have copies in at least two of the sibling directories activity, agent, agent-graph, command, document, editor (+10 more sibling(s) not listed) — 23 of them are reported below, and 14 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 37 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 37 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 37 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. — apps/smithy-web/src/components/command/FileContentSearch.tsx:59
22 duplicated blocks under apps/quarry-web/src/routes/ have copies in at least two of the sibling directories dashboard, dependency-graph, entities, plans, settings, tasks (+2 more sibling(s) not listed) — 12 of them are reported below, and 10 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — apps/quarry-web/src/routes/entities/hooks.ts:242
22 duplicated blocks under apps/smithy-next/src/components/ have copies in at least two of the sibling directories dropdowns, onboarding, overlays — 9 of them are reported below, and 13 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — apps/smithy-next/src/components/onboarding/WorkerEnvironmentStep.tsx:140
16 duplicated blocks under packages/smithy/src/ have copies in at least two of the sibling directories api, cli, permissions, runtime, server, services (+2 more sibling(s) not listed) — 10 of them are reported below, and 6 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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/smithy/src/api/orchestrator-api.ts:447
12 duplicated blocks under apps/smithy-web/src/ have copies in at least two of the sibling directories api, components, hooks, routes — 6 of them are reported below, and 6 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. — apps/smithy-web/src/components/task/CreateTaskModal.tsx:308
12 duplicated blocks under packages/quarry/src/external-sync/providers/ have copies in at least two of the sibling directories folder, github, linear, notion — 6 of them are reported below, and 6 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/quarry/src/external-sync/providers/linear/linear-provider.ts:47
11 duplicated blocks under apps/quarry-web/src/ have copies in at least two of the sibling directories api, components, hooks, lib, routes — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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. — apps/quarry-web/src/components/team/CreateTeamModal.tsx:108
10 duplicated blocks under apps/smithy-web/src/routes/ have copies in at least two of the sibling directories activity, agents, merge-requests, metrics, settings, tasks — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/smithy-web/src/routes/merge-requests/index.tsx:259
10 duplicated blocks under packages/quarry/src/ have copies in at least two of the sibling directories api, cli, config, external-sync, server, services (+2 more sibling(s) not listed) — 4 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/quarry/src/api/quarry-api.ts:156
10 of the duplicated blocks reported below have copies in at least two of the sibling directories claude, codex, opencode under packages/smithy/src/providers/. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/smithy/src/providers/codex/interactive.ts:28
apps/quarry-web/src/routes/inbox.tsx:8 · apps/smithy-web/src/routes/inbox/index.tsx:8 — these 2 files are line-for-line copies of one another — 925 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. — apps/quarry-web/src/routes/inbox.tsx:8
apps/smithy-server/src/routes/tasks.ts:7 · packages/smithy/src/server/routes/tasks.ts:7 — these 2 files are line-for-line copies of one another — 702 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. — apps/smithy-server/src/routes/tasks.ts:7
apps/smithy-server/src/routes/sessions.ts:7 · packages/smithy/src/server/routes/sessions.ts:7 — these 2 files are line-for-line copies of one another — 566 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. — apps/smithy-server/src/routes/sessions.ts:7
apps/quarry-web/src/api/hooks/useAllElements.ts:8 · apps/smithy-web/src/api/hooks/useAllElements.ts:8 — these 2 files are line-for-line copies of one another — 413 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. — apps/quarry-web/src/api/hooks/useAllElements.ts:8
packages/core/src/types/task.ts:47 · packages/core/src/types/workflow.ts:57 — the two spans are one implementation copied and then locally edited — 2355 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/core/src/types/task.ts:47
apps/smithy-server/src/routes/workflows.ts:7 · packages/smithy/src/server/routes/workflows.ts:7 — these 2 files are line-for-line copies of one another — 356 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. — apps/smithy-server/src/routes/workflows.ts:7
apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:5 · apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:5 — these 2 files are line-for-line copies of one another — 349 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. — apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:5
apps/quarry-web/src/components/editor/ImageUploadModal.tsx:60 · packages/ui/src/message/MessageImageAttachment.tsx:54 — the two spans are one implementation copied and then locally edited — 1859 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. — apps/quarry-web/src/components/editor/ImageUploadModal.tsx:60
REDACTED:8 · REDACTED:8 — these 2 files are line-for-line copies of one another — 329 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. — REDACTED:8
apps/smithy-server/src/routes/agents.ts:17 · packages/smithy/src/server/routes/agents.ts:17 — the two spans are one implementation copied and then locally edited — 2923 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. — apps/smithy-server/src/routes/agents.ts:17
apps/quarry-web/src/routes/messages/components/ChannelView.tsx:5 · apps/smithy-web/src/routes/messages/components/ChannelView.tsx:5 — these 2 files are line-for-line copies of one another — 318 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. — apps/quarry-web/src/routes/messages/components/ChannelView.tsx:5
apps/smithy-web/src/components/command/FileContentSearch.tsx:59 · apps/smithy-web/src/components/editor/EditorSearchPanel.tsx:65 — the two spans are one implementation copied and then locally edited — 1547 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. — apps/smithy-web/src/components/command/FileContentSearch.tsx:59
apps/quarry-web/src/routes/workflows/index.tsx:11 · apps/smithy-web/src/routes/workflows/index.tsx:10 — these 2 files are line-for-line copies of one another — 274 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. — apps/quarry-web/src/routes/workflows/index.tsx:11
apps/quarry-web/src/lib/task-utils.tsx:38 · apps/smithy-web/src/lib/task-utils.tsx:39 — the two spans are one implementation copied and then locally edited — 1990 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. — apps/quarry-web/src/lib/task-utils.tsx:38
apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:5 · apps/smithy-web/src/routes/messages/components/MessageBubble.tsx:5 — these 2 files are line-for-line copies of one another — 241 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. — apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:5
apps/quarry-web/src/components/editor/MentionAutocomplete.tsx:17 · apps/smithy-web/src/components/editor/MentionAutocomplete.tsx:17 · packages/ui/src/message/MentionAutocomplete.tsx:17 — these 3 files are line-for-line copies of one another — 239 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. — apps/quarry-web/src/components/editor/MentionAutocomplete.tsx:17
apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:8 · apps/smithy-web/src/routes/documents/components/DocumentLinkComponents.tsx:8 — these 2 files are line-for-line copies of one another — 235 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. — apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:8
apps/quarry-web/src/components/document/CreateDocumentModal.tsx:1 · apps/smithy-web/src/components/document/CreateDocumentModal.tsx:1 — these 2 files are line-for-line copies of one another — 231 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. — apps/quarry-web/src/components/document/CreateDocumentModal.tsx:1
apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:366 · apps/smithy-web/src/routes/documents/components/DocumentDetailPanel.tsx:225 — the two spans are one implementation copied and then locally edited — 1072 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. — apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:366
apps/quarry-web/src/routes/documents/components/LibraryView.tsx:5 · apps/smithy-web/src/routes/documents/components/LibraryView.tsx:5 — these 2 files are line-for-line copies of one another — 218 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. — apps/quarry-web/src/routes/documents/components/LibraryView.tsx:5
packages/storage/src/bun-backend.ts:9 · packages/storage/src/node-backend.ts:11 — these 2 files are line-for-line copies of one another — 217 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/storage/src/bun-backend.ts:9
apps/smithy-web/src/components/pool/CreatePoolDialog.tsx:100 · apps/smithy-web/src/components/pool/EditPoolDialog.tsx:131 — the two spans are one implementation copied and then locally edited — 1149 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. — apps/smithy-web/src/components/pool/CreatePoolDialog.tsx:100
REDACTED:40 · REDACTED:56 — the two spans are one implementation copied and then locally edited — 1675 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. — REDACTED:40
apps/quarry-web/src/routes/plans/components/RoadmapView.tsx:5 · packages/ui/src/plans/components/RoadmapView.tsx:5 — these 2 files are line-for-line copies of one another — 195 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. — apps/quarry-web/src/routes/plans/components/RoadmapView.tsx:5
apps/quarry-web/src/hooks/usePaginatedData.ts:14 · apps/smithy-web/src/hooks/usePaginatedData.ts:14 — these 2 files are line-for-line copies of one another — 190 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. — apps/quarry-web/src/hooks/usePaginatedData.ts:14
apps/smithy-server/src/routes/events.ts:7 · packages/smithy/src/server/routes/events.ts:7 — these 2 files are line-for-line copies of one another — 190 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. — apps/smithy-server/src/routes/events.ts:7
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/quarry/src/cli/commands/auto-link-helper.ts:60 imports @stoneforge/smithy/services, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/quarry/src/cli/commands/auto-link-helper.ts:60
packages/quarry/src/cli/commands/external-sync.ts:104 imports @stoneforge/smithy/services, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/quarry/src/cli/commands/external-sync.ts:104
packages/quarry/src/cli/commands/external-sync.ts:1855 imports @stoneforge/smithy/services, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/quarry/src/cli/commands/external-sync.ts:1855
packages/quarry/src/cli/commands/install.ts:51 imports @stoneforge/smithy/package.json, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/quarry/src/cli/commands/install.ts:51
REDACTED:396 imports @stoneforge/smithy/server, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:396
REDACTED:513 imports @stoneforge/smithy/server, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:513
What to do
Fix the listed violations: declare the workspace packages these files import in the importing package's own package.json dependencies (6 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.
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.
TaskDetailOverlay has cyclomatic complexity 75 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 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. — apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:36
DocumentDetailPanel has cyclomatic complexity 74 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 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. — apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:59
DocumentDetailPanel has cyclomatic complexity 64 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — apps/smithy-web/src/routes/documents/components/DocumentDetailPanel.tsx:49
FileEditorPage has cyclomatic complexity 63 and cognitive complexity 62; 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. — apps/smithy-web/src/routes/editor/index.tsx:219
Oi has cyclomatic complexity 62 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. — REDACTED:1
linkAllDocumentsHandler has cyclomatic complexity 58 and cognitive complexity 77; 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/quarry/src/cli/commands/external-sync.ts:2089
parseUrl has cyclomatic complexity 56 and cognitive complexity 75; 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. — apps/smithy-next/src/App.tsx:108
updateHandler has cyclomatic complexity 55 and cognitive complexity 82; 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/quarry/src/cli/commands/crud.ts:820
(anonymous) has cyclomatic complexity 54 and cognitive complexity 77; 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/workflows/components/WorkflowEditorModal.tsx:1160
linkAllHandler has cyclomatic complexity 54 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/quarry/src/cli/commands/external-sync.ts:2392
DirectorPanel has cyclomatic complexity 54 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/smithy-next/src/components/DirectorPanel.tsx:112
playbookValidateHandler has cyclomatic complexity 52 and cognitive complexity 90; 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/quarry/src/cli/commands/playbook.ts:326
saveSessionEvent has cyclomatic complexity 52 and cognitive complexity 79; 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. (×2) — apps/smithy-server/src/routes/sessions.ts:30, packages/smithy/src/server/routes/sessions.ts:36
validateYamlStep has cyclomatic complexity 52 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 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/core/src/types/playbook-yaml.ts:651
WorkspacePane has cyclomatic complexity 52 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/smithy-web/src/components/workspace/WorkspacePane.tsx:66
(anonymous) has cyclomatic complexity 51 and cognitive complexity 72; 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/smithy/src/server/routes/agents.ts:306
ImageUploadModal has cyclomatic complexity 51 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/quarry-web/src/components/editor/ImageUploadModal.tsx:53
validateConfiguration has cyclomatic complexity 51 and cognitive complexity 55; 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/quarry/src/config/validation.ts:321
buildUrl has cyclomatic complexity 50 and cognitive complexity 69; 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. — apps/smithy-next/src/App.tsx:269
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files0.9 / 10Critical✓ 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/quarry/src/api/quarry-api.ts has 4852 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/quarry/src/api/quarry-api.ts:1
packages/smithy/src/services/dispatch-daemon.ts has 3807 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/smithy/src/services/dispatch-daemon.ts:1
REDACTED has 3350 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/core/src/types/entity.ts has 2993 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/core/src/types/entity.ts:1
packages/quarry/src/cli/commands/external-sync.ts has 2723 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/quarry/src/cli/commands/external-sync.ts:1
apps/smithy-web/src/components/task/TaskDetailPanel.tsx has 2441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1
apps/smithy-next/src/mock-data.ts has 2307 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-next/src/mock-data.ts:1
packages/core/src/types/playbook.ts has 2085 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/core/src/types/playbook.ts:1
apps/smithy-next/src/components/overlays/SettingsOverlay.tsx has 2065 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1
apps/quarry-web/src/components/task/TaskDetailPanel.tsx has 2003 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/quarry-web/src/components/task/TaskDetailPanel.tsx:1
packages/quarry/src/api/types.ts has 1721 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/quarry/src/api/types.ts:1
packages/ui/src/workflows/components/WorkflowEditorModal.tsx has 1578 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/workflows/components/WorkflowEditorModal.tsx:1
packages/smithy/src/runtime/session-manager.ts has 1523 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/smithy/src/runtime/session-manager.ts:1
apps/smithy-next/src/components/DirectorPanel.tsx has 1515 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-next/src/components/DirectorPanel.tsx:1
REDACTED has 1473 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
apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx has 1459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:1
packages/quarry/src/external-sync/sync-engine.ts has 1441 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/quarry/src/external-sync/sync-engine.ts:1
packages/core/src/types/playbook-yaml.ts has 1415 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/core/src/types/playbook-yaml.ts:1
packages/quarry/src/cli/commands/task.ts has 1345 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/quarry/src/cli/commands/task.ts:1
apps/smithy-web/src/components/layout/AppShell.tsx has 1338 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/components/layout/AppShell.tsx:1
packages/smithy/src/services/merge-steward-service.ts has 1333 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/smithy/src/services/merge-steward-service.ts:1
apps/smithy-web/src/routes/inbox/index.tsx has 1324 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/routes/inbox/index.tsx:1
apps/quarry-web/src/routes/inbox.tsx has 1311 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/quarry-web/src/routes/inbox.tsx:1
apps/smithy-web/src/routes/editor/index.tsx has 1299 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/routes/editor/index.tsx:1
apps/smithy-web/src/routes/tasks/index.tsx has 1283 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/routes/tasks/index.tsx:1
packages/smithy/src/runtime/spawner.ts has 1264 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/smithy/src/runtime/spawner.ts:1
packages/shared-routes/src/documents.ts has 1256 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/shared-routes/src/documents.ts:1
apps/smithy-next/src/App.tsx has 1252 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-next/src/App.tsx:1
packages/smithy/src/testing/orchestration-tests.ts has 1225 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/smithy/src/testing/orchestration-tests.ts:1
packages/smithy/src/cli/commands/task.ts has 1210 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/smithy/src/cli/commands/task.ts:1
packages/quarry/src/systems/identity.ts has 1190 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/quarry/src/systems/identity.ts:1
REDACTED has 1187 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
apps/smithy-web/src/routes/metrics/index.tsx has 1168 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/routes/metrics/index.tsx:1
apps/smithy-web/src/components/workspace/StreamViewer.tsx has 1143 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-web/src/components/workspace/StreamViewer.tsx:1
packages/quarry/src/cli/commands/document.ts has 1142 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/quarry/src/cli/commands/document.ts:1
apps/smithy-next/src/components/KanbanBoard.tsx has 1111 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/smithy-next/src/components/KanbanBoard.tsx:1
packages/smithy/src/cli/commands/agent.ts has 1065 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/smithy/src/cli/commands/agent.ts:1
packages/smithy/src/server/routes/tasks.ts has 1046 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/smithy/src/server/routes/tasks.ts:1
packages/quarry/src/cli/commands/crud.ts has 1038 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/quarry/src/cli/commands/crud.ts:1
packages/core/src/types/dependency.ts has 1020 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/core/src/types/dependency.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 Coverage7.4 / 10Strong✓ 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.
packages/quarry/src/cli/commands/plan.bun.test.ts:1023 imports '../../types/element.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/quarry/src/cli/commands/plan.bun.test.ts:1023
tests/node/cross-runtime.test.ts:11 imports '../../src/storage/node-backend.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — tests/node/cross-runtime.test.ts:11
tests/node/node-backend.test.ts:10 imports '../../src/storage/node-backend.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — tests/node/node-backend.test.ts:10
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. (×37) — apps/smithy-next/src/mock-data.ts:1, apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1, apps/smithy-next/src/components/DirectorPanel.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.
42 outdated package(s); JS/npm CVEs scored in D30
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each 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.
This repository declares test tooling, and the ✓ above records that declaration — but packages/quarry/src/cli/commands/plan.bun.test.ts and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/quarry/src/cli/commands/plan.bun.test.ts:1023
Do you agree with this assessment?
R7 · Dead Code7.2 / 10Strong✓ 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.
Unreachable from the 187 application, 21 tooling and 349 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×11) — apps/smithy-server/src/routes/tasks.ts, apps/smithy-server/src/routes/workflows.ts, REDACTED, …
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-next/src/components/overlays/RuntimesOverlay.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — apps/smithy-next/src/components/overlays/runtimes/RuntimeListView.tsx, apps/smithy-next/src/components/overlays/runtimes/RuntimeCreateView.tsx, apps/smithy-next/src/components/overlays/runtimes/RuntimeDetailView.tsx
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×14) — apps/smithy-next/src/components/overlays/WorkspacesOverlay.tsx, apps/smithy-web/src/components/editor/MentionAutocomplete.tsx, apps/quarry-web/src/App.tsx, …
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/RoadmapView.tsx, apps/quarry-web/src/routes/plans/components/MobilePlanCard.tsx, …
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/quarry-web/src/routes/plans/components/MobilePlanCard.tsx, apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/PlanListItem.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/quarry-web/src/components/shared/ProgressRing.tsx
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/PlanListItem.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/quarry-web/src/routes/plans/utils.ts
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx, apps/quarry-web/src/routes/plans/components/TaskPickerModal.tsx, apps/quarry-web/src/routes/plans/components/TaskStatusSummary.tsx
no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx, apps/quarry-web/src/routes/plans/components/RoadmapView.tsx, apps/quarry-web/src/routes/plans/components/StatusBadge.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/quarry-web/src/routes/plans/constants.tsx
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 the root 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.
Declared in apps/smithy-server/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. (×2)
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.
apps/quarry-web/src/components/entity/CreateEntityModal.tsx → apps/quarry-web/src/hooks/index.ts → apps/quarry-web/src/hooks/useGlobalQuickActions.tsx → apps/quarry-web/src/components/entity/CreateEntityModal.tsx (one verified cycle inside a mutually-dependent group of 5 files) — apps/quarry-web/src/components/entity/CreateEntityModal.tsx:11
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://plausible.io/js/script.tagged-events.outbound-links.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — apps/website/src/layouts/BaseLayout.astro:106
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
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 document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`isValidCLIPlugin` is exported, takes a document from its caller (line 149) and hands it to `isValidCommand`, which calls itself at line 224 (`isValidCommand`) with a piece of `obj` — and nowhere in `isValidCommand` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isValidCommand` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/quarry/src/cli/plugin-types.ts:224
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 14/194 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) 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.
`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 })`. (×28) — packages/ui/src/plans/hooks/usePlanApi.ts:17, packages/ui/src/plans/hooks/usePlanApi.ts:38, packages/ui/src/plans/hooks/usePlanApi.ts:57, …
`uploadFile` 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/ui/src/message/MessageImageAttachment.tsx:109
`serverRequest` 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/smithy/src/cli/commands/daemon.ts:36
`executeRequest` 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/quarry/src/external-sync/providers/notion/notion-api.ts:557
`testConnection` 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/quarry/src/external-sync/providers/notion/notion-provider.ts:83, packages/quarry/src/external-sync/providers/github/github-provider.ts:73
`graphql` 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/quarry/src/external-sync/providers/linear/linear-api.ts:273
`request` 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/quarry/src/external-sync/providers/github/github-api.ts:407
`paginatedRequest` 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/quarry/src/external-sync/providers/github/github-api.ts:455
`tryStopDaemon` 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/quarry/src/cli/commands/reset.ts:50
`uploadImageFile` 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 })`. — apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:237
`downloadVsix` 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 })`. — apps/smithy-web/src/lib/openvsx/client.ts:350
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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
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.
`debug` at line 4235 is called with an argument built by `conflicts.join(', ')` (line 4235), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/smithy/src/services/dispatch-daemon.ts:4235
`debug` at line 107 is called with an argument built by `channels.join(', ')` (line 107), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. (×2) — packages/smithy/src/server/events-websocket.ts:107, apps/smithy-server/src/events-websocket.ts:107
`debug` at line 116 is called with an argument built by `channels.join(', ')` (line 116), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. (×2) — packages/smithy/src/server/events-websocket.ts:116, apps/smithy-server/src/events-websocket.ts:116
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.4 / 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.
`content` 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. (×2) — REDACTED:61, REDACTED:80
`html||' '` 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. — apps/smithy-next/src/components/overlays/mr/RichTextEditor.tsx:76
`html` 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. (×2) — REDACTED:120, REDACTED:144
`htmlContent as string` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:163
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?
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 element7.6 / 10Strong✓ Tool-verified
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.
This loop runs once per element of `layoutConfig.rows`, and the statement it guards acts on the element it is on — `rowIndex`. The test deciding whether that statement runs does not: `is2x2Grid && onSwap2x2Rows` reads `layoutConfig.rows[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 763, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — apps/smithy-web/src/components/workspace/WorkspaceGrid.tsx:782
What to do
Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
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) — packages/ui/src/message/ChannelMembersPanel.tsx:346, packages/ui/src/message/ChannelMembersPanel.tsx:432, packages/ui/src/message/ChannelMembersPanel.tsx:448, …
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 strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.9 `!` null assertions per 1k TypeScript source lines — 322 assertion(s) across the 341886 source line(s) of the 1051 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/quarry/src/cli/commands/external-sync.ts (22), packages/quarry/src/api/quarry-api.ts (19), apps/smithy-next/src/components/KanbanBoard.tsx (9). 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.
X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 34 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 43 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 analysed — these correctness checks read a source model 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
AX2 Stateful singletons — Not applicable: 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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "https://turborepo.dev/docs/telemetry / • turbo 2.11.10 / • Packages in scope: @stoneforge/core, @stoneforge/docs, @stoneforge/quarry, @stoneforge/quarry-server, @stoneforge/quarry-web, @stoneforge/shared-routes, @stoneforge/smithy, @stoneforge/smithy-next, @stoneforge/smithy-server, @stoneforge/smithy-web, @stoneforge/storage, @stoneforge/ui, @stoneforge/website / • Running dev in 13 packages / • Remote caching disabled / x Unable to find package manager binary: cannot find binary path / `-> cannot find binary path" No runtime evidence was gathered. 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.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 19 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.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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 measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (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, 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
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. 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.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. 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.
X4 Structured logging — not analysed — these correctness checks read a source model 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
X9 Subsumed condition operand — 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> · ×31
Click handler on a non-interactive <div> apps/quarry-web/src/components/editor/CommentsPanel.tsx:54— 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> apps/quarry-web/src/components/editor/ImageUploadModal.tsx:401— 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> apps/quarry-web/src/components/editor/ImageUploadModal.tsx:503— 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> apps/quarry-web/src/components/editor/ImageUploadModal.tsx:726— 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> apps/quarry-web/src/components/editor/ImageUploadModal.tsx:837— 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> apps/quarry-web/src/components/shared/ContributionChart.tsx:252— 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> apps/quarry-web/src/components/shared/ContributionChart.tsx:302— 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> apps/quarry-web/src/components/task/KanbanBoard.tsx:309— 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> apps/quarry-web/src/components/task/MobileTaskCard.tsx:142— 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> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:416— 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}.
Click handler on a non-interactive <div> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:634— 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}.
Click handler on a non-interactive <div> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:942— 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}.
Click handler on a non-interactive <div> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:1344— 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}.
Click handler on a non-interactive <div> apps/quarry-web/src/components/task/TaskListView.tsx:65— 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> apps/quarry-web/src/components/team/MobileTeamCard.tsx:115— 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> apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.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> apps/quarry-web/src/routes/documents/components/DocumentListItem.tsx:20— 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> apps/quarry-web/src/routes/documents/components/LibraryTree.tsx:44— 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> apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:77— 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> apps/quarry-web/src/routes/plans/components/MobilePlanCard.tsx:126— 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> apps/quarry-web/src/routes/plans/components/PlanListItem.tsx:33— 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> apps/quarry-web/src/routes/teams/components/DeleteTeamConfirmModal.tsx:24— 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> apps/quarry-web/src/routes/teams/components/TeamCard.tsx:20— 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> apps/smithy-next/src/App.tsx:1150— 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> apps/smithy-next/src/App.tsx:1284— 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· <label> that labels no control · ×15
<label> that labels no control apps/quarry-web/src/components/document/CreateDocumentModal.tsx:270— 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 apps/quarry-web/src/components/document/CreateLibraryModal.tsx:226— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:438— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:582— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:763— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:956— 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 apps/quarry-web/src/components/entity/CreateEntityModal.tsx:195— 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 apps/quarry-web/src/components/task/CreateTaskModal.tsx:337— 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 apps/quarry-web/src/components/task/CreateTaskModal.tsx:511— 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 apps/quarry-web/src/components/task/FilterBar.tsx:83— 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 apps/quarry-web/src/components/task/FilterBar.tsx:104— 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 apps/quarry-web/src/components/task/FilterBar.tsx:125— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:554— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:578— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:603— 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.
Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:2530— `@img/sharp-libvips-darwin-arm64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-darwin-x64 REDACTED:2545— `@img/sharp-libvips-darwin-x64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm REDACTED:2575— `@img/sharp-libvips-linux-arm` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm64 REDACTED:2560— `@img/sharp-libvips-linux-arm64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:2583— `@img/sharp-libvips-linux-ppc64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:2591— `@img/sharp-libvips-linux-riscv64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-s390x REDACTED:2606— `@img/sharp-libvips-linux-s390x` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-x64 REDACTED:2621— `@img/sharp-libvips-linux-x64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:2636— `@img/sharp-libvips-linuxmusl-arm64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:2651— `@img/sharp-libvips-linuxmusl-x64` 1.2.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-wasm32 REDACTED:2816— `@img/sharp-wasm32` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-arm64 REDACTED:2826— `@img/sharp-win32-arm64` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-ia32 REDACTED:2843— `@img/sharp-win32-ia32` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-x64 REDACTED:2860— `@img/sharp-win32-x64` 0.34.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
AC2 · Forms & labels· <input> without a programmatic label · ×10
<input> without a programmatic label apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:212— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:441— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:471— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:585— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:767— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:800— 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 apps/quarry-web/src/components/editor/ImageUploadModal.tsx:959— 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 apps/quarry-web/src/components/editor/TaskPickerModal.tsx:220— 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 apps/quarry-web/src/components/navigation/CommandPalette.tsx:353— 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 apps/quarry-web/src/components/navigation/CommandPalette.tsx:538— 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· <select> without a programmatic label · ×5
<select> without a programmatic label apps/quarry-web/src/components/task/FilterBar.tsx:126— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:492— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:555— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:579— 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 apps/quarry-web/src/components/task/KanbanBoard.tsx:604— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×3
<button> with no accessible text apps/quarry-web/src/components/editor/CommentsPanel.tsx:97— 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 apps/quarry-web/src/components/navigation/CommandPalette.tsx:525— 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 apps/quarry-web/src/components/task/BulkActionMenu.tsx:191— 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· Custom control with no accessible name on <div> · ×3
Custom control with no accessible name on <div> apps/quarry-web/src/components/shared/ContributionChart.tsx:302— 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> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:416— 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> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:634— 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.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×3
Hover-only interaction on <div> apps/smithy-next/src/components/BottomPanel.tsx:89— 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> apps/smithy-next/src/components/DirectorPanel.tsx:287— 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> apps/smithy-next/src/components/DirectorPanel.tsx:728— 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.
Import cycle (2 files) packages/quarry/src/cli/commands/alias.ts:10— packages/quarry/src/cli/commands/alias.ts → packages/quarry/src/cli/runner.ts → packages/quarry/src/cli/commands/alias.ts (one verified cycle inside a mutually-dependent group of 43 files)
AC4 · Keyboard semantics· Click handler on a non-interactive <h2> · ×1
Click handler on a non-interactive <h2> apps/quarry-web/src/components/task/TaskDetailPanel.tsx:1516— 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}.
AC4 · Keyboard semantics· Click handler on a non-interactive <img> · ×1
Click handler on a non-interactive <img> REDACTED:288— 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> apps/smithy-next/src/components/CommandPalette.tsx:198— 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}.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): off() removes callback packages/core/src/types/playbook-yaml.bun.test.ts:876— Test method has an empty body — it asserts nothing and exercises no code.
FunctionTooLong: index.createQuarryApp REDACTED:129— FunctionTooLong — createQuarryApp runs 2099 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1999 over it, 20.99× 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: index.FileEditorPage apps/smithy-web/src/routes/editor/index.tsx:219— FunctionTooLong — FileEditorPage runs 866 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 766 over it, 8.66× 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: ImageUploadModal.ImageUploadModal apps/quarry-web/src/components/editor/ImageUploadModal.tsx:53— FunctionTooLong — ImageUploadModal runs 812 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 712 over it, 8.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: utils-vendor-CfYKiENT.kn REDACTED:6— FunctionTooLong — kn runs 808 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 708 over it, 8.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: documents.createDocumentRoutes packages/shared-routes/src/documents.ts:30— FunctionTooLong — createDocumentRoutes runs 807 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 707 over it, 8.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: utils-vendor-CfYKiENT.Ui REDACTED:11— FunctionTooLong — Ui runs 803 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 703 over it, 8.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: utils-vendor-CfYKiENT.Gi REDACTED:16— FunctionTooLong — Gi runs 798 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 698 over it, 7.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: utils-vendor-CfYKiENT.qa REDACTED:21— FunctionTooLong — qa runs 793 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 693 over it, 7.93× 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: utils-vendor-CfYKiENT.Hi REDACTED:31— FunctionTooLong — Hi runs 783 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 683 over it, 7.83× 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: utils-vendor-CfYKiENT._i REDACTED:36— FunctionTooLong — _i runs 778 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 678 over it, 7.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: utils-vendor-CfYKiENT.g REDACTED:41— FunctionTooLong — g runs 773 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 673 over it, 7.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tasks.createTaskRoutes packages/smithy/src/server/routes/tasks.ts:46— FunctionTooLong — createTaskRoutes runs 728 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 628 over it, 7.28× 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: tasks.createTaskRoutes apps/smithy-server/src/routes/tasks.ts:43— FunctionTooLong — createTaskRoutes runs 700 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 600 over it, 7.00× 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: CreateAgentDialog.CreateAgentDialog REDACTED:195— FunctionTooLong — CreateAgentDialog runs 672 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 572 over it, 6.72× 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: DirectorPanel.DirectorPanel apps/smithy-next/src/components/DirectorPanel.tsx:112— FunctionTooLong — DirectorPanel runs 647 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 547 over it, 6.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: App.App apps/smithy-next/src/App.tsx:371— FunctionTooLong — App runs 631 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 531 over it, 6.31× 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: index.TasksPage apps/smithy-web/src/routes/tasks/index.tsx:89— FunctionTooLong — TasksPage runs 622 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 522 over it, 6.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.
FunctionTooLong: DirectorPanel.DirectorPanel apps/smithy-web/src/components/layout/DirectorPanel.tsx:303— FunctionTooLong — DirectorPanel runs 612 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 512 over it, 6.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: WorkflowEditorModal.WorkflowEditorModal packages/ui/src/workflows/components/WorkflowEditorModal.tsx:980— FunctionTooLong — WorkflowEditorModal runs 592 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 492 over it, 5.92× 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: StreamViewer.StreamViewer apps/smithy-web/src/components/workspace/StreamViewer.tsx:335— FunctionTooLong — StreamViewer runs 585 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 485 over it, 5.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: index.MetricsPage apps/smithy-web/src/routes/metrics/index.tsx:576— FunctionTooLong — MetricsPage runs 570 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 470 over it, 5.70× 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: RoleDefinitionDetailView.RoleDefinitionDetailView apps/smithy-next/src/components/overlays/agents/RoleDefinitionDetailView.tsx:277— FunctionTooLong — RoleDefinitionDetailView runs 565 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 465 over it, 5.65× 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: CanvasView.CanvasView apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:36— FunctionTooLong — CanvasView runs 558 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 458 over it, 5.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AppShell.AppShell apps/smithy-web/src/components/layout/AppShell.tsx:663— FunctionTooLong — AppShell runs 545 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 445 over it, 5.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: index.TasksPage apps/quarry-web/src/routes/tasks/index.tsx:90— FunctionTooLong — TasksPage runs 541 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 441 over it, 5.41× 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: api/quarry-api.ts packages/quarry/src/api/quarry-api.ts— FileTooLong — 3217 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: QuarryAPIImpl (555-5505). The bar is 500 significant lines; this is 2717 over it, 6.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: REDACTED REDACTED— FileTooLong — 2293 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: createQuarryApp (129-3666). The bar is 500 significant lines; this is 1793 over it, 4.59× 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/dispatch-daemon.ts packages/smithy/src/services/dispatch-daemon.ts— FileTooLong — 2244 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: DispatchDaemonImpl (517-4264). The bar is 500 significant lines; this is 1744 over it, 4.49× 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: task/TaskDetailPanel.tsx apps/smithy-web/src/components/task/TaskDetailPanel.tsx— FileTooLong — 2107 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1607 over it, 4.21× 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: commands/external-sync.ts packages/quarry/src/cli/commands/external-sync.ts— FileTooLong — 1973 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1473 over it, 3.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/mock-data.ts apps/smithy-next/src/mock-data.ts— FileTooLong — 1837 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1337 over it, 3.67× 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: overlays/SettingsOverlay.tsx apps/smithy-next/src/components/overlays/SettingsOverlay.tsx— FileTooLong — 1835 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1335 over it, 3.67× 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: task/TaskDetailPanel.tsx apps/quarry-web/src/components/task/TaskDetailPanel.tsx— FileTooLong — 1686 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1186 over it, 3.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: components/WorkflowEditorModal.tsx packages/ui/src/workflows/components/WorkflowEditorModal.tsx— FileTooLong — 1386 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 886 over it, 2.77× 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/DirectorPanel.tsx apps/smithy-next/src/components/DirectorPanel.tsx— FileTooLong — 1337 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 837 over it, 2.67× 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: types/entity.ts packages/core/src/types/entity.ts— FileTooLong — 1329 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 829 over it, 2.66× 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/EntityDetailPanel.tsx apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx— FileTooLong — 1315 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 815 over it, 2.63× 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: inbox/index.tsx apps/smithy-web/src/routes/inbox/index.tsx— FileTooLong — 1130 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 630 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: routes/inbox.tsx apps/quarry-web/src/routes/inbox.tsx— FileTooLong — 1124 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 624 over it, 2.25× 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: tasks/index.tsx apps/smithy-web/src/routes/tasks/index.tsx— FileTooLong — 1096 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 596 over it, 2.19× 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: types/playbook.ts packages/core/src/types/playbook.ts— FileTooLong — 1087 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 587 over it, 2.17× 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/App.tsx apps/smithy-next/src/App.tsx— FileTooLong — 1065 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 565 over it, 2.13× 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: layout/AppShell.tsx apps/smithy-web/src/components/layout/AppShell.tsx— FileTooLong — 1027 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 527 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: editor/index.tsx apps/smithy-web/src/routes/editor/index.tsx— FileTooLong — 1006 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: FileEditorPage (219-1424). The bar is 500 significant lines; this is 506 over it, 2.01× 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: metrics/index.tsx apps/smithy-web/src/routes/metrics/index.tsx— FileTooLong — 1005 significant lines (blank, comment-only and punctuation-only lines excluded). 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: commands/task.ts packages/quarry/src/cli/commands/task.ts— FileTooLong — 990 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 490 over it, 1.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: components/KanbanBoard.tsx apps/smithy-next/src/components/KanbanBoard.tsx— FileTooLong — 945 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 445 over it, 1.89× 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: commands/task.ts packages/smithy/src/cli/commands/task.ts— FileTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 401 over it, 1.80× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 349 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: editor/ImageUploadModal.tsx apps/quarry-web/src/components/editor/ImageUploadModal.tsx— FileTooLong — 842 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ImageUploadModal (53-1025). The bar is 500 significant lines; this is 342 over it, 1.68× 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.
Hotspot: REDACTED REDACTED:129— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 561 in index.createQuarryApp at line 129. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/smithy/src/services/dispatch-daemon.ts packages/smithy/src/services/dispatch-daemon.ts:1203— packages/smithy/src/services/dispatch-daemon.ts changed 56 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in DispatchDaemonImpl.recoverOrphanedAssignments at line 1203. 15 of those changes were fix/bug commits, and the other 41 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/services/dispatch-daemon.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-web/src/components/layout/AppShell.tsx apps/smithy-web/src/components/layout/AppShell.tsx:663— apps/smithy-web/src/components/layout/AppShell.tsx changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 83 in AppShell.AppShell at line 663. 7 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-web/src/components/layout/AppShell.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/cli/commands/external-sync.ts packages/quarry/src/cli/commands/external-sync.ts:2089— packages/quarry/src/cli/commands/external-sync.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in external-sync.linkAllDocumentsHandler at line 2089. 8 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/cli/commands/external-sync.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/smithy/src/server/routes/agents.ts packages/smithy/src/server/routes/agents.ts:16— packages/smithy/src/server/routes/agents.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 116 in agents.createAgentRoutes at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/server/routes/agents.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/smithy/src/server/services.ts packages/smithy/src/server/services.ts:111— packages/smithy/src/server/services.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in services.initializeServices at line 111. 3 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/server/services.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-web/src/components/layout/DirectorPanel.tsx apps/smithy-web/src/components/layout/DirectorPanel.tsx:303— apps/smithy-web/src/components/layout/DirectorPanel.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 81 in DirectorPanel.DirectorPanel at line 303. 3 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-web/src/components/layout/DirectorPanel.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/smithy/src/server/routes/tasks.ts packages/smithy/src/server/routes/tasks.ts:46— packages/smithy/src/server/routes/tasks.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 158 in tasks.createTaskRoutes at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/server/routes/tasks.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-web/src/components/workspace/StreamViewer.tsx apps/smithy-web/src/components/workspace/StreamViewer.tsx:335— apps/smithy-web/src/components/workspace/StreamViewer.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 155 in StreamViewer.StreamViewer at line 335. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-web/src/components/workspace/StreamViewer.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:195— REDACTED changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in CreateAgentDialog.CreateAgentDialog at line 195. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-server/src/routes/tasks.ts apps/smithy-server/src/routes/tasks.ts:43— apps/smithy-server/src/routes/tasks.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 152 in tasks.createTaskRoutes at line 43. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-server/src/routes/tasks.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/cli/commands/init.ts packages/quarry/src/cli/commands/init.ts:538— packages/quarry/src/cli/commands/init.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in init.initHandler at line 538. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/cli/commands/init.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:1442— REDACTED changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in steward-scheduler.createStewardExecutor.<returned closure> at line 1442. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/config/validation.ts packages/quarry/src/config/validation.ts:321— packages/quarry/src/config/validation.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in validation.validateConfiguration at line 321. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/config/validation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-server/src/routes/agents.ts apps/smithy-server/src/routes/agents.ts:16— apps/smithy-server/src/routes/agents.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in agents.createAgentRoutes at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-server/src/routes/agents.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/smithy/src/server/routes/sessions.ts packages/smithy/src/server/routes/sessions.ts:213— packages/smithy/src/server/routes/sessions.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 93 in sessions.createSessionRoutes at line 213. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/server/routes/sessions.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/config/file.ts packages/quarry/src/config/file.ts:189— packages/quarry/src/config/file.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in file.convertYamlToConfig at line 189. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/config/file.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/smithy/src/cli/commands/task.ts packages/smithy/src/cli/commands/task.ts:386— packages/smithy/src/cli/commands/task.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in task.taskMergeHandler at line 386. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/cli/commands/task.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:381— REDACTED changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in serve.startSmithy at line 381. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-web/src/components/terminal/XTerminal.tsx apps/smithy-web/src/components/terminal/XTerminal.tsx:125— apps/smithy-web/src/components/terminal/XTerminal.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 105 in XTerminal.XTerminal at line 125. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-web/src/components/terminal/XTerminal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/external-sync/sync-engine.ts packages/quarry/src/external-sync/sync-engine.ts:745— packages/quarry/src/external-sync/sync-engine.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SyncEngine.pullItem at line 745. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/external-sync/sync-engine.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/config/merge.ts packages/quarry/src/config/merge.ts:225— packages/quarry/src/config/merge.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in merge.diffConfigurations at line 225. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/config/merge.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-web/src/routes/agents/index.tsx apps/smithy-web/src/routes/agents/index.tsx:23— apps/smithy-web/src/routes/agents/index.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in index.AgentsPage at line 23. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-web/src/routes/agents/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/smithy-web/src/components/workspace/WorkspacePane.tsx apps/smithy-web/src/components/workspace/WorkspacePane.tsx:66— apps/smithy-web/src/components/workspace/WorkspacePane.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in WorkspacePane.WorkspacePane at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- apps/smithy-web/src/components/workspace/WorkspacePane.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/quarry/src/config/config.ts packages/quarry/src/config/config.ts:366— packages/quarry/src/config/config.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in config.mergeTrackedConfig at line 366. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/quarry/src/config/config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Sync-over-async blocking apps/quarry-web/tests/global-setup.ts:14— `mkdirSync` in `globalSetup` 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 apps/quarry-web/tests/global-teardown.ts:11— `rmSync` in `globalTeardown` 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 apps/smithy-server/src/services/lsp-manager.ts:65— `execSync` in `commandExists` 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 apps/smithy-server/src/services/lsp-manager.ts:94— `existsSync` in `isAvailable` 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 apps/smithy-server/src/services/lsp-manager.ts:130— `existsSync` in `isAvailable` 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 apps/smithy-server/src/services/lsp-manager.ts:139— `existsSync` in `isAvailable` 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 apps/smithy-server/src/services/lsp-manager.ts:148— `existsSync` in `isAvailable` 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 apps/smithy-web/tests/global-setup.ts:24— `mkdirSync` in `globalSetup` 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 apps/smithy-web/tests/global-teardown.ts:11— `rmSync` in `globalTeardown` 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 packages/quarry/src/cli/commands/admin.ts:66— `existsSync` in `doctorHandler` 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 packages/quarry/src/cli/commands/admin.ts:807— `existsSync` in `migrateHandler` 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 packages/quarry/src/cli/commands/config.ts:198— `existsSync` in `configEditHandler` 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 packages/quarry/src/cli/commands/config.ts:200— `existsSync` in `configEditHandler` 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 packages/quarry/src/cli/commands/config.ts:201— `mkdirSync` in `configEditHandler` 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 packages/quarry/src/cli/commands/config.ts:203— `writeFileSync` in `configEditHandler` 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 packages/quarry/src/cli/commands/config.ts:213— `spawnSync` in `configEditHandler` 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 packages/quarry/src/cli/commands/document.ts:116— `existsSync` in `docCreateHandler` 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 packages/quarry/src/cli/commands/document.ts:119— `readFileSync` in `docCreateHandler` 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 packages/quarry/src/cli/commands/document.ts:691— `existsSync` in `docUpdateHandler` 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 packages/quarry/src/cli/commands/document.ts:694— `readFileSync` in `docUpdateHandler` 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 packages/quarry/src/cli/commands/embeddings.ts:65— `existsSync` in `embeddingsInstallHandler` 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 packages/quarry/src/cli/commands/embeddings.ts:71— `mkdirSync` in `embeddingsInstallHandler` 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 packages/quarry/src/cli/commands/embeddings.ts:114— `existsSync` in `embeddingsStatusHandler` 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 packages/quarry/src/cli/commands/identity.ts:361— `readFileSync` in `signHandler` 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 packages/quarry/src/cli/commands/identity.ts:556— `readFileSync` in `verifyHandler` 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.
Swallowed exception (empty catch) packages/ui/src/message/ChannelMembersPanel.tsx:346— 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/ui/src/message/ChannelMembersPanel.tsx:432— 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/ui/src/message/ChannelMembersPanel.tsx:448— 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/ui/src/message/ChannelMembersPanel.tsx:462— 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/ui/src/message/CreateChannelModal.tsx:157— 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/ui/src/api/api-client.ts:164— 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:168— 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:636— 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:928— 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:940— 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/storage/src/bun-backend.ts:290— 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/storage/src/bun-backend.ts:545— 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/storage/src/node-backend.ts:293— 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/storage/src/node-backend.ts:548— 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/smithy/src/services/agent-registry.ts:578— 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/smithy/src/services/agent-registry.ts:693— 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/smithy/src/services/agent-registry.ts:702— 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/smithy/src/services/agent-registry.ts:703— 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/smithy/src/services/dispatch-daemon.ts:708— 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/smithy/src/services/dispatch-daemon.ts:1716— 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/smithy/src/services/dispatch-daemon.ts:2848— 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/smithy/src/services/dispatch-daemon.ts:3981— 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/smithy/src/services/dispatch-daemon.ts:4007— 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/smithy/src/services/dispatch-daemon.ts:4043— 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:429— 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.
+ 15 more in this group — see findings.md.
X2 · Cancellation propagation· Async function without AbortSignal · ×39
Async function without AbortSignal: queryFn packages/ui/src/plans/hooks/usePlanApi.ts:17— `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: queryFn packages/ui/src/plans/hooks/usePlanApi.ts:38— `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: queryFn packages/ui/src/plans/hooks/usePlanApi.ts:57— `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: queryFn packages/ui/src/plans/hooks/usePlanApi.ts:76— `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: queryFn packages/ui/src/plans/hooks/usePlanApi.ts:170— `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: queryFn packages/ui/src/plans/components/CreatePlanModal.tsx:81— `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: queryFn packages/ui/src/message/ChannelMembersPanel.tsx:62— `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: queryFn packages/ui/src/message/ChannelMembersPanel.tsx:75— `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: queryFn packages/ui/src/message/CreateChannelModal.tsx:43— `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: queryFn packages/ui/src/message/EntityLink.tsx:65— `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: queryFn packages/ui/src/message/MessageEmbedCard.tsx:64— `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: queryFn packages/ui/src/message/MessageEmbedCard.tsx:146— `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: uploadFile packages/ui/src/message/MessageImageAttachment.tsx:109— `uploadFile` 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/domain/EntityLink.tsx:131— `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: queryFn packages/ui/src/domain/EntityLink.tsx:162— `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: serverRequest packages/smithy/src/cli/commands/daemon.ts:36— `serverRequest` 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: executeRequest packages/quarry/src/external-sync/providers/notion/notion-api.ts:557— `executeRequest` 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: testConnection packages/quarry/src/external-sync/providers/notion/notion-provider.ts:83— `testConnection` 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: graphql packages/quarry/src/external-sync/providers/linear/linear-api.ts:273— `graphql` 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: request packages/quarry/src/external-sync/providers/github/github-api.ts:407— `request` 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: paginatedRequest packages/quarry/src/external-sync/providers/github/github-api.ts:455— `paginatedRequest` 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: testConnection packages/quarry/src/external-sync/providers/github/github-provider.ts:73— `testConnection` 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: tryStopDaemon packages/quarry/src/cli/commands/reset.ts:50— `tryStopDaemon` 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: uploadImageFile apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:237— `uploadImageFile` 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 apps/smithy-web/src/routes/inbox/index.tsx:154— `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 })`.
+ 14 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×37
No test reaches this file apps/smithy-next/src/mock-data.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 apps/smithy-next/src/components/overlays/SettingsOverlay.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 apps/smithy-next/src/components/DirectorPanel.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 apps/smithy-next/src/App.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 apps/smithy-next/src/components/KanbanBoard.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 apps/smithy-server/src/routes/tasks.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 apps/smithy-next/src/components/overlays/agents/RoleDefinitionDetailView.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 apps/smithy-next/src/components/overlays/editor/editor-mock-data.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 apps/smithy-next/src/components/overlays/TaskDetailOverlay.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 apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.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 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 tools/seo/search-console.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 apps/smithy-next/src/components/overlays/agents/RuntimeDetailView.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 apps/smithy-web/src/api/types.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 apps/smithy-next/src/components/overlays/documents/DocEditorView.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 apps/smithy-server/src/routes/workflows.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 apps/smithy-next/src/components/ActivityRail.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 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 apps/smithy-next/src/components/overlays/documents/doc-mock-data.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 apps/smithy-next/src/components/overlays/runtimes/RuntimeListView.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 apps/smithy-next/src/components/overlays/documents/DocListView.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 apps/smithy-next/src/components/overlays/sessions/SessionListView.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 apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.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 apps/smithy-next/src/components/overlays/ci/CIRunListView.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 apps/smithy-next/src/components/onboarding/IntegrationsStep.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.
ClassTooLong: QuarryAPIImpl packages/quarry/src/api/quarry-api.ts:555— ClassTooLong — 2840 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 400 significant lines; this is 2440 over it, 7.10× 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: DispatchDaemonImpl packages/smithy/src/services/dispatch-daemon.ts:517— ClassTooLong — 2079 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 400 significant lines; this is 1679 over it, 5.20× 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: ImageUploadModal apps/quarry-web/src/components/editor/ImageUploadModal.tsx:1— ClassTooLong — 812 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 412 over it, 2.03× 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: SessionManagerImpl packages/smithy/src/runtime/session-manager.ts:492— ClassTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 292 over it, 1.73× 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: SyncEngine packages/quarry/src/external-sync/sync-engine.ts:249— ClassTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 283 over it, 1.71× 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: MergeStewardServiceImpl packages/smithy/src/services/merge-steward-service.ts:393— ClassTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 275 over it, 1.69× 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: CreateAgentDialog REDACTED:1— ClassTooLong — 672 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 272 over it, 1.68× 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: DirectorPanel apps/smithy-next/src/components/DirectorPanel.tsx:1— ClassTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 247 over it, 1.62× 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: App apps/smithy-next/src/App.tsx:1— ClassTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 231 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: DirectorPanel apps/smithy-web/src/components/layout/DirectorPanel.tsx:1— ClassTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 212 over it, 1.53× 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: WorkflowEditorModal packages/ui/src/workflows/components/WorkflowEditorModal.tsx:1— ClassTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 192 over it, 1.48× 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: StreamViewer apps/smithy-web/src/components/workspace/StreamViewer.tsx:1— ClassTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 185 over it, 1.46× 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: RoleDefinitionDetailView apps/smithy-next/src/components/overlays/agents/RoleDefinitionDetailView.tsx:1— ClassTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 165 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: CanvasView apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:1— ClassTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 158 over it, 1.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: AppShell apps/smithy-web/src/components/layout/AppShell.tsx:1— ClassTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 145 over it, 1.36× 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: WorktreeManagerImpl REDACTED:355— ClassTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 142 over it, 1.36× 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: SpawnerServiceImpl packages/smithy/src/runtime/spawner.ts:498— ClassTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 140 over it, 1.35× 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: CommandPalette apps/quarry-web/src/components/navigation/CommandPalette.tsx:1— ClassTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 106 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: TaskDetailOverlay apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:1— ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 100 over it, 1.25× 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: DocumentDetailPanel apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:1— ClassTooLong — 481 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 81 over it, 1.20× 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: ActivityRail apps/smithy-next/src/components/ActivityRail.tsx:1— ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 77 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: XTerminal apps/smithy-web/src/components/terminal/XTerminal.tsx:1— ClassTooLong — 456 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 56 over it, 1.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: HorizontalTimeline apps/quarry-web/src/routes/timeline/components/HorizontalTimeline.tsx:1— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 40 over it, 1.10× 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: BlockedCacheService packages/quarry/src/services/blocked-cache.ts:125— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 37 over it, 1.09× 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: BlockEditor apps/quarry-web/src/components/editor/BlockEditor.tsx:1— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. 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.
No assertions: handles heartbeat event packages/ui/src/api/sse-client.test.ts:260— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: handles subscribed message packages/ui/src/api/websocket.test.ts:267— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: handles pong message packages/ui/src/api/websocket.test.ts:280— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: handles error message packages/ui/src/api/websocket.test.ts:290— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: handles malformed messages gracefully packages/ui/src/api/websocket.test.ts:304— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: cancel does nothing for non-existent query packages/smithy/src/runtime/predecessor-query.bun.test.ts:754— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does nothing for non-existent session packages/smithy/src/runtime/session-manager.bun.test.ts:888— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does nothing for non-existent agent packages/smithy/src/runtime/session-manager.bun.test.ts:895— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is a no-op for main branch packages/smithy/src/git/merge.bun.test.ts:829— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is a no-op for master branch packages/smithy/src/git/merge.bun.test.ts:839— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should handle verbose logging option packages/quarry/src/cli/plugin-loader.bun.test.ts:81— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nullProgressBar.update and finish are no-ops packages/quarry/src/cli/utils/progress.bun.test.ts:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createProgressBar.update does not throw packages/quarry/src/cli/utils/progress.bun.test.ts:22— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createProgressBar.finish does not throw packages/quarry/src/cli/utils/progress.bun.test.ts:30— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createProgressBar handles zero total packages/quarry/src/cli/utils/progress.bun.test.ts:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createProgressBar clamps current to total packages/quarry/src/cli/utils/progress.bun.test.ts:41— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: on() returns unsubscribe function packages/core/src/types/playbook-yaml.bun.test.ts:867— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: log method accepts all log levels packages/core/src/id/generator.bun.test.ts:979— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: log method accepts data parameter packages/core/src/id/generator.bun.test.ts:989— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: boundary: 767px is mobile, 768px is tablet apps/smithy-web/tests/responsive-breakpoints.spec.ts:121— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: contribution chart shows loading state initially apps/quarry-web/tests/tb108-entity-contribution-chart.spec.ts:136— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: all buttons have accessible names apps/quarry-web/tests/tb119-accessibility.spec.ts:212— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: all links have accessible names apps/quarry-web/tests/tb119-accessibility.spec.ts:238— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×22
Markup wires an event to an empty handler apps/quarry-web/src/components/task/KanbanBoard.tsx:1085— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:337— `onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/App.tsx:1091— `onCreateSession` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/DirectorPanel.tsx:835— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:605— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:611— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1615— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:372— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:373— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:374— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:375— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:440— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:559— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/mr/MRCommitsTab.tsx:70— `onToggleViewed` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:506— `onDragStart` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:508— `onDragEnd` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-next/src/components/overlays/sessions/canvas/SessionNode.tsx:290— `onSelectEvent` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-web/src/components/editor/EditorTabBar.tsx:612— `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-web/src/components/editor/EditorTabBar.tsx:613— `onClose` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-web/src/components/task/KanbanBoard.tsx:1075— `onClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-web/src/routes/activity/index.tsx:69— `onDismiss` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler apps/smithy-web/src/routes/documents/components/DocumentLinkComponents.tsx:337— `onRemove` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
IC1 · Incompleteness & stubs· Both branches are identical · ×16
Both branches are identical — the condition decides nothing apps/quarry-web/src/routes/entities/components/InboxComponents.tsx:389— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/quarry-web/src/routes/inbox.tsx:664— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:458— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:460— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:472— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-next/src/components/overlays/ci/CIFilterPanel.tsx:120— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-next/src/components/overlays/editor/EditorFolderView.tsx:118— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-next/src/components/overlays/mr/MRTimelineEvent.tsx:57— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-next/src/components/overlays/mr/RichTextEditor.tsx:28— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-next/src/components/overlays/preview/DesignModeOverlay.tsx:181— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-next/src/components/shared/FilesChangedView.tsx:34— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-web/src/components/layout/DaemonToggle.tsx:84— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-web/src/components/terminal/XTerminal.tsx:688— The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing apps/smithy-web/src/routes/inbox/index.tsx:664— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:458— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:460— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
D10 · Test Quality· Fixed-sleep synchronisation · ×14
Fixed-sleep synchronisation: resumes predecessor session with correct options packages/smithy/src/runtime/predecessor-query.bun.test.ts:304— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: includes context in prompt when provided packages/smithy/src/runtime/predecessor-query.bun.test.ts:351— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: captures response from predecessor packages/smithy/src/runtime/predecessor-query.bun.test.ts:394— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: suspends predecessor after response by default packages/smithy/src/runtime/predecessor-query.bun.test.ts:438— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: does not suspend predecessor when suspendAfterResponse is false packages/smithy/src/runtime/predecessor-query.bun.test.ts:477— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: returns predecessor info in result packages/smithy/src/runtime/predecessor-query.bun.test.ts:516— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: handles error events from predecessor packages/smithy/src/runtime/predecessor-query.bun.test.ts:554— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: handles session exit with accumulated response packages/smithy/src/runtime/predecessor-query.bun.test.ts:585— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: handles session exit without response packages/smithy/src/runtime/predecessor-query.bun.test.ts:619— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: lists active queries packages/smithy/src/runtime/predecessor-query.bun.test.ts:649— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: gets active query by ID packages/smithy/src/runtime/predecessor-query.bun.test.ts:684— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: cancels active query packages/smithy/src/runtime/predecessor-query.bun.test.ts:720— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: tracks query status through lifecycle packages/smithy/src/runtime/predecessor-query.bun.test.ts:790— This test starts work it did not wait for (`queryPromise`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 100))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should reject updates with stale timestamps even in parallel packages/quarry/src/api/concurrent-update.integration.bun.test.ts:295— This test starts work it did not wait for (`originalUpdatedAt`, still running when the sleep starts) and then orders itself against it with `sleep(2)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:526— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:866— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/components/shared/VirtualizedChatList.tsx:328— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/documents/index.tsx:324— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:399— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:489— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/messages/components/ThreadPanel.tsx:154— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/messages/index.tsx:190— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx:102— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/settings/components/NotificationsSection.tsx:149— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/settings/components/OptionCard.tsx:37— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/settings/components/SyncSection.tsx:234— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) apps/quarry-web/src/routes/settings/components/ThemeSection.tsx:41— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:597— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:974— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/editor/blocks/DocumentEmbedBlock.tsx:49— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/editor/blocks/DocumentEmbedBlock.tsx:63— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/editor/blocks/TaskEmbedBlock.tsx:54— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/editor/blocks/TaskEmbedBlock.tsx:68— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/entity/CreateEntityModal.tsx:266— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/task/CreateTaskModal.tsx:215— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/components/team/CreateTeamModal.tsx:345— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:467— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/routes/entities/components/HistoryEventItem.tsx:195— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/routes/teams/components/DeleteTeamConfirmModal.tsx:32— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) apps/quarry-web/src/routes/teams/components/TeamDetailPanel.tsx:252— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
C2 · Access Controls· Anyone can act as another user by changing what their browser sends · ×10
Anyone can act as another user by changing what their browser sends apps/smithy-server/src/routes/agents.ts:52— Here who may pass is decided by the 'role' form field (if(!body.role||!body.name)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends apps/smithy-server/src/routes/events.ts:54— Here who is asking is taken from the 'actor' query parameter (const actor = url.searchParams.get('actor')as EntityId|null) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/shared-routes/src/documents.ts:893— Here who is asking is taken from the 'actor' form field (const actor = (body.actor as EntityId)||('el-0000'as EntityId)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/shared-routes/src/documents.ts:1167— Here who is asking is taken from the 'authorId' form field (const event = createEvent({elementId:documentId, eventType:'comment_added'as EventType,…) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/shared-routes/src/documents.ts:1251— Here who is asking is taken from the 'author_id' form field (const event = createEvent({elementId:documentId, eventType:'comment_updated'as EventTyp…) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/shared-routes/src/documents.ts:1365— Here who is asking is taken from the 'actor' form field (const actorEntity = await api.get(body.actor as ElementId)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/shared-routes/src/documents.ts:1398— Here who is asking is taken from the 'actor' form field (const event = createEvent({elementId:documentId, eventType:eventType as EventType, acto…) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/shared-routes/src/libraries.ts:293— Here who is asking is taken from the 'actor' form field (const actor = (body.actor as EntityId)||('el-0000'as EntityId)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/smithy/src/server/routes/agents.ts:54— Here who may pass is decided by the 'role' form field (if(!body.role||!body.name)) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
Anyone can act as another user by changing what their browser sends packages/smithy/src/server/routes/events.ts:55— Here who is asking is taken from the 'actor' query parameter (const actor = url.searchParams.get('actor')as EntityId|null) and nothing checks it: no signature, no server-side session, no verified token. Cookies, headers and form or address values come from the visitor's browser and they can change them, so anyone can put another person's id there and be treated as that person — no password needed.
TodoComment packages/smithy/src/runtime/handoff.ts:469— // TODO: If options.triggerTarget !== false and target agent is idle, — 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/quarry/src/services/embeddings/local-provider.ts:60— // TODO: Initialize ONNX runtime session — 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/quarry/src/cli/commands/embeddings.ts:73— // TODO: Download actual ONNX model files — 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/quarry/src/cli/commands/workflow.ts:107— // TODO: When playbook instantiation is implemented, look up playbook and create workflow — 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/quarry/src/api/quarry-api.ts:2663— // TODO: Check for cycles (for blocking dependency types) — 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 apps/smithy-web/src/components/task/TaskCard.tsx:55— // TODO: Open menu — 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 apps/smithy-next/src/components/overlays/editor/editor-mock-data.ts:436— // TODO: Replace with actual database query — 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 apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:175— // TODO: Use actual current user ID — 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 apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:636— // TODO: Use actual current user ID — 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 apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:195— // TODO: Scroll to position in editor — 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×10
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D12 · Dependency Hygiene· One package at two majors across the workspace · ×9
One package at two majors across the workspace: @tiptap/core — `@tiptap/core` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/extension-code-block-lowlight — `@tiptap/extension-code-block-lowlight` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/extension-placeholder — `@tiptap/extension-placeholder` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/extension-underline — `@tiptap/extension-underline` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/pm — `@tiptap/pm` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/react — `@tiptap/react` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/starter-kit — `@tiptap/starter-kit` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @tiptap/suggestion — `@tiptap/suggestion` is maintained at 2 different major versions inside this one repository — major 2 in apps/smithy-web/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: recharts — `recharts` is maintained at 2 different major versions inside this one repository — major 2 in packages/ui/package.json; major 3 in apps/quarry-web/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
Outbound HTTP without resilience packages/quarry/src/cli/commands/reset.ts:52— `fetch(` 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 packages/quarry/src/external-sync/providers/github/github-api.ts:422— `fetch(` 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 packages/quarry/src/external-sync/providers/github/github-api.ts:481— `fetch(` 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 packages/quarry/src/external-sync/providers/github/github-provider.ts:81— `fetch(` 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 packages/quarry/src/external-sync/providers/linear/linear-api.ts:276— `fetch(` 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 packages/quarry/src/external-sync/providers/notion/notion-api.ts:571— `fetch(` 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 packages/quarry/src/external-sync/providers/notion/notion-provider.ts:89— `fetch(` 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 packages/quarry/web/assets/editor-vendor-BxraAWts.js:6— `ky(` 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 packages/smithy/src/cli/commands/daemon.ts:42— `fetch(` 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.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×8
Heading level jumps from h1 to h3 apps/quarry-web/src/routes/workflows/index.tsx:355— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:317— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 REDACTED:437— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 apps/smithy-web/src/routes/agents/index.tsx:455— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 apps/smithy-web/src/routes/merge-requests/index.tsx:267— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 apps/smithy-web/src/routes/metrics/index.tsx:1221— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 apps/smithy-web/src/routes/tasks/index.tsx:833— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 apps/smithy-web/src/routes/workflows/index.tsx:357— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
MethodTooLong: QuarryAPIImpl.create packages/quarry/src/api/quarry-api.ts:892— MethodTooLong — create runs 237 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 137 over it, 2.37× 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: DispatchDaemonImpl.recoverOrphanedAssignments packages/smithy/src/services/dispatch-daemon.ts:1203— MethodTooLong — recoverOrphanedAssignments runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× 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: QuarryAPIImpl.update packages/quarry/src/api/quarry-api.ts:1286— MethodTooLong — update runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: DispatchDaemonImpl.spawnRecoveryStewardForTask packages/smithy/src/services/dispatch-daemon.ts:3393— MethodTooLong — spawnRecoveryStewardForTask runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: DispatchDaemonImpl.assignTaskToWorker packages/smithy/src/services/dispatch-daemon.ts:2711— MethodTooLong — assignTaskToWorker runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: QuarryAPIImpl.listPaginated packages/quarry/src/api/quarry-api.ts:711— MethodTooLong — listPaginated runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: MergeStewardServiceImpl.createApprovalPR packages/smithy/src/services/merge-steward-service.ts:1197— MethodTooLong — createApprovalPR runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.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: DispatchDaemonImpl.recoverOrphanedTask packages/smithy/src/services/dispatch-daemon.ts:2259— MethodTooLong — recoverOrphanedTask runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
Boundary violation [package:undeclared-workspace-dep] packages/quarry/src/cli/commands/auto-link-helper.ts:60— packages/quarry/src/cli/commands/auto-link-helper.ts:60 imports @stoneforge/smithy/services, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/quarry/src/cli/commands/external-sync.ts:104— packages/quarry/src/cli/commands/external-sync.ts:104 imports @stoneforge/smithy/services, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/quarry/src/cli/commands/external-sync.ts:1855— packages/quarry/src/cli/commands/external-sync.ts:1855 imports @stoneforge/smithy/services, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/quarry/src/cli/commands/install.ts:51— packages/quarry/src/cli/commands/install.ts:51 imports @stoneforge/smithy/package.json, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:396— REDACTED:396 imports @stoneforge/smithy/server, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:513— REDACTED:513 imports @stoneforge/smithy/server, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×6
Untrusted text written into markup unescaped REDACTED:61— `content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped apps/smithy-next/src/components/overlays/mr/RichTextEditor.tsx:76— `html||' '` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:120— `html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:144— `html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:163— `htmlContent as string` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:80— `content` 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.
TooManyMethods: QuarryAPIImpl packages/quarry/src/api/quarry-api.ts:555— TooManyMethods — 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. Most of these members implement types.QuarryAPI (68 of 84 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: DispatchDaemonImpl packages/smithy/src/services/dispatch-daemon.ts:517— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: SessionManagerImpl packages/smithy/src/runtime/session-manager.ts:492— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 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.
TooManyMethods: BrowserStorageBackend REDACTED:347— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 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.
TooManyMethods: WorktreeManagerImpl REDACTED:355— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
AC2 · Forms & labels· <TagInput> field component without a label · ×4
<TagInput> field component without a label apps/quarry-web/src/components/document/CreateDocumentModal.tsx:273— 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.
<TagInput> field component without a label apps/quarry-web/src/components/document/CreateLibraryModal.tsx:229— 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.
<TagInput> field component without a label apps/quarry-web/src/components/task/CreateTaskModal.tsx:340— 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.
<TagInput> field component without a label apps/quarry-web/src/components/task/CreateTaskModal.tsx:514— 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.
Focus outline removed inline apps/quarry-web/src/components/navigation/CommandPalette.tsx:353— <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 apps/quarry-web/src/components/navigation/CommandPalette.tsx:538— <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 apps/quarry-web/src/routes/inbox.tsx:1177— <select> 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 apps/quarry-web/src/routes/inbox.tsx:1192— <select> 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).
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard apps/quarry-web/src/components/shared/DataPreloader.tsx:34— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard apps/quarry-web/src/components/shared/VirtualizedChatList.tsx:277— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx:122— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard apps/quarry-web/src/routes/timeline/index.tsx:349— <span> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×3
Modal dialog does not manage focus apps/quarry-web/src/components/navigation/CommandPalette.tsx:330— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus apps/quarry-web/src/components/navigation/CommandPalette.tsx:509— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:369— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Repeated repair: packages/smithy/src/providers/opencode/server-manager.ts packages/smithy/src/providers/opencode/server-manager.ts:179— packages/smithy/src/providers/opencode/server-manager.ts changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is OpenCodeServerManager.listModels at line 179), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix opencode spawn ENOENT on Windows (el-1kv8)”; “Fix OpenCode session creation error handling and directory param (el-3v22)”; “Fix opencode provider: remove invalid wd config key (el-3n4p)”; “Fix opencode provider: spawn process with cwd directly (el-g9we)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/providers/opencode/server-manager.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/smithy/src/providers/claude/interactive.ts packages/smithy/src/providers/claude/interactive.ts:35— packages/smithy/src/providers/claude/interactive.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is interactive.ensureSpawnHelperPermissions at line 35), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(smithy): Windows spawn failures in provider layer (#51)”; “fix: set CLAUDE_CODE_DISABLE_1M_CONTEXT=1 on all spawned agent sessions”; “Fix posix_spawnp for bun: ensure spawn-helper permissions at runtime”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/providers/claude/interactive.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/smithy/src/providers/opencode/interactive.ts packages/smithy/src/providers/opencode/interactive.ts:91— packages/smithy/src/providers/opencode/interactive.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is OpenCodeInteractiveProvider.spawn at line 91), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(smithy): Windows spawn failures in provider layer (#51)”; “Fix OpenCode interactive session resume to use --session flag”; “Fix OpenCode interactive provider: pass initial prompt via --prompt flag (el-4x6f)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-02-03..2026-05-04, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-03 17:45:00 -10:00' --until='2026-05-04 17:45:00 -10:00' --full-history --no-merges -- packages/smithy/src/providers/opencode/interactive.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
R4 · Test Coverage· This test file cannot be loaded · ×3
This test file cannot be loaded packages/quarry/src/cli/commands/plan.bun.test.ts:1023— packages/quarry/src/cli/commands/plan.bun.test.ts:1023 imports '../../types/element.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded tests/node/cross-runtime.test.ts:11— tests/node/cross-runtime.test.ts:11 imports '../../src/storage/node-backend.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded tests/node/node-backend.test.ts:10— tests/node/node-backend.test.ts:10 imports '../../src/storage/node-backend.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
Low contrast Tailwind colour pair (4.1:1) apps/quarry-web/src/components/editor/BubbleMenu.tsx:49— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.1:1) apps/quarry-web/src/routes/inbox.tsx:795— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
ChannelView.ChannelView (cyclomatic 58) apps/quarry-web/src/routes/messages/components/ChannelView.tsx:49— ChannelView.ChannelView has cyclomatic complexity 58 (threshold 15). Of this number, 27 points are the body's own statements and 31 belong to 14 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.
ChannelView.ChannelView (cyclomatic 58) apps/smithy-web/src/routes/messages/components/ChannelView.tsx:50— ChannelView.ChannelView has cyclomatic complexity 58 (threshold 15). Of this number, 27 points are the body's own statements and 31 belong to 14 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.
MessageComposer.MessageComposer (cyclomatic 53) apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:157— MessageComposer.MessageComposer has cyclomatic complexity 53 (threshold 15). Of this number, 29 points are the body's own statements and 24 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.
MessageComposer.MessageComposer (cyclomatic 53) apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:157— MessageComposer.MessageComposer has cyclomatic complexity 53 (threshold 15). Of this number, 29 points are the body's own statements and 24 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.
sessions.saveSessionEvent (cyclomatic 52) apps/smithy-server/src/routes/sessions.ts:30— sessions.saveSessionEvent has cyclomatic complexity 52 (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.
sessions.saveSessionEvent (cyclomatic 52) packages/smithy/src/server/routes/sessions.ts:36— sessions.saveSessionEvent has cyclomatic complexity 52 (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.
MessageBubble.MessageBubble (cyclomatic 48) apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:63— MessageBubble.MessageBubble has cyclomatic complexity 48 (threshold 15). Of this number, 34 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MessageBubble.MessageBubble (cyclomatic 48) apps/smithy-web/src/routes/messages/components/MessageBubble.tsx:62— MessageBubble.MessageBubble has cyclomatic complexity 48 (threshold 15). Of this number, 34 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
events.createEventRoutes (cyclomatic 47) apps/smithy-server/src/routes/events.ts:43— events.createEventRoutes has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 261, 48, 80, …). 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.
events.createEventRoutes (cyclomatic 47) packages/smithy/src/server/routes/events.ts:44— events.createEventRoutes has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 262, 49, 81, …). 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.
index.WorkflowsPage (cyclomatic 45) apps/quarry-web/src/routes/workflows/index.tsx:41— index.WorkflowsPage has cyclomatic complexity 45 (threshold 15). Of this number, 37 points are the body's own statements and 8 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.WorkflowsPage (cyclomatic 45) apps/smithy-web/src/routes/workflows/index.tsx:43— index.WorkflowsPage has cyclomatic complexity 45 (threshold 15). Of this number, 37 points are the body's own statements and 8 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
workspace-files.createWorkspaceFilesRoutes (cyclomatic 44) REDACTED:353— workspace-files.createWorkspaceFilesRoutes has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 358, 395, 524, …). 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.
workspace-files.createWorkspaceFilesRoutes (cyclomatic 44) REDACTED:354— workspace-files.createWorkspaceFilesRoutes has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 359, 396, 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.
CreateDocumentModal.CreateDocumentModal (cyclomatic 39) apps/quarry-web/src/components/document/CreateDocumentModal.tsx:75— CreateDocumentModal.CreateDocumentModal has cyclomatic complexity 39 (threshold 15). Of this number, 28 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CreateDocumentModal.CreateDocumentModal (cyclomatic 39) apps/smithy-web/src/components/document/CreateDocumentModal.tsx:75— CreateDocumentModal.CreateDocumentModal has cyclomatic complexity 39 (threshold 15). Of this number, 28 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LibraryView.LibraryView (cyclomatic 34) apps/quarry-web/src/routes/documents/components/LibraryView.tsx:40— LibraryView.LibraryView has cyclomatic complexity 34 (threshold 15). Of this number, 30 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, 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.
LibraryView.LibraryView (cyclomatic 34) apps/smithy-web/src/routes/documents/components/LibraryView.tsx:40— LibraryView.LibraryView has cyclomatic complexity 34 (threshold 15). Of this number, 30 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, 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.
Oi::onPointerMove (cyclomatic 30) REDACTED:1— Oi::onPointerMove 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.
Oi::onPointerUp (cyclomatic 17) REDACTED:1— Oi::onPointerUp has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: _n (cyclomatic 23) 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.
DocumentPickerModal.DocumentPickerModal (cyclomatic 29) apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:80— DocumentPickerModal.DocumentPickerModal has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 11 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 243, 138, 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.
DocumentPickerModal.DocumentPickerModal (cyclomatic 29) apps/smithy-web/src/components/editor/DocumentPickerModal.tsx:80— DocumentPickerModal.DocumentPickerModal has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 11 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 243, 138, 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.
TaskPickerModal.TaskPickerModal (cyclomatic 28) apps/quarry-web/src/components/editor/TaskPickerModal.tsx:88— TaskPickerModal.TaskPickerModal has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 146, 249, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TaskPickerModal.TaskPickerModal (cyclomatic 28) apps/smithy-web/src/components/editor/TaskPickerModal.tsx:88— TaskPickerModal.TaskPickerModal has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 146, 249, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
daemon.createDaemonRoutes (cyclomatic 27) apps/smithy-server/src/routes/daemon.ts:27— daemon.createDaemonRoutes has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 237, 144, 61, …). 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.
daemon.createDaemonRoutes (cyclomatic 27) packages/smithy/src/server/routes/daemon.ts:28— daemon.createDaemonRoutes has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 238, 145, 62, …). 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.
VirtualizedChatList.VirtualizedChatList (cyclomatic 26) apps/quarry-web/src/components/shared/VirtualizedChatList.tsx:112— VirtualizedChatList.VirtualizedChatList has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 223, 182, 188, …). 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.
VirtualizedChatList.VirtualizedChatList (cyclomatic 26) apps/smithy-web/src/components/shared/VirtualizedChatList.tsx:112— VirtualizedChatList.VirtualizedChatList has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 223, 182, 188, …). 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.
ChannelList.ChannelList (cyclomatic 26) apps/quarry-web/src/routes/messages/components/ChannelList.tsx:89— ChannelList.ChannelList has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ChannelList.ChannelList (cyclomatic 26) apps/smithy-web/src/routes/messages/components/ChannelList.tsx:89— ChannelList.ChannelList has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocumentSearchBar.DocumentSearchBar (cyclomatic 26) apps/quarry-web/src/routes/documents/components/DocumentSearchBar.tsx:14— DocumentSearchBar.DocumentSearchBar has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 4 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.
DocumentSearchBar.DocumentSearchBar (cyclomatic 26) apps/smithy-web/src/routes/documents/components/DocumentSearchBar.tsx:14— DocumentSearchBar.DocumentSearchBar has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 4 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.
AllDocumentsView.AllDocumentsView (cyclomatic 25) apps/quarry-web/src/routes/documents/components/AllDocumentsView.tsx:37— AllDocumentsView.AllDocumentsView has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 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.
AllDocumentsView.AllDocumentsView (cyclomatic 25) apps/smithy-web/src/routes/documents/components/AllDocumentsView.tsx:37— AllDocumentsView.AllDocumentsView has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 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.
extensions.createExtensionsRoutes (cyclomatic 25) apps/smithy-server/src/routes/extensions.ts:49— extensions.createExtensionsRoutes has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 157, 62, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
extensions.createExtensionsRoutes (cyclomatic 25) packages/smithy/src/server/routes/extensions.ts:49— extensions.createExtensionsRoutes has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 157, 62, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VirtualizedList.VirtualizedList (cyclomatic 24) apps/quarry-web/src/components/shared/VirtualizedList.tsx:91— VirtualizedList.VirtualizedList has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 123, 137, 148, …). 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.
VirtualizedList.VirtualizedList (cyclomatic 24) apps/smithy-web/src/components/shared/VirtualizedList.tsx:91— VirtualizedList.VirtualizedList has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 123, 137, 148, …). 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.
FilterBar.FilterBar (cyclomatic 23) apps/quarry-web/src/components/task/FilterBar.tsx:23— FilterBar.FilterBar has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FilterBar.FilterBar (cyclomatic 23) apps/smithy-web/src/components/task/FilterBar.tsx:22— FilterBar.FilterBar has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SortByDropdown.SortByDropdown (cyclomatic 23) apps/quarry-web/src/components/task/SortByDropdown.tsx:25— SortByDropdown.SortByDropdown has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SortByDropdown.SortByDropdown (cyclomatic 23) apps/smithy-web/src/components/task/SortByDropdown.tsx:25— SortByDropdown.SortByDropdown has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PageHeader.PageHeader (cyclomatic 22) apps/quarry-web/src/components/shared/PageHeader.tsx:51— PageHeader.PageHeader has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 89, renderCount, renderActions). 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.
PageHeader.PageHeader (cyclomatic 22) apps/smithy-web/src/components/shared/PageHeader.tsx:51— PageHeader.PageHeader has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 89, renderCount, renderActions). 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.
index.MessagesPage (cyclomatic 22) apps/quarry-web/src/routes/messages/index.tsx:32— index.MessagesPage has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 52, 98, 87). 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.
index.MessagesPage (cyclomatic 22) apps/smithy-web/src/routes/messages/index.tsx:32— index.MessagesPage has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 52, 98, 87). 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.
VersionHistorySidebar.VersionHistorySidebar (cyclomatic 21) apps/quarry-web/src/routes/documents/components/VersionHistorySidebar.tsx:17— VersionHistorySidebar.VersionHistorySidebar has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 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.
VersionHistorySidebar.VersionHistorySidebar (cyclomatic 21) apps/smithy-web/src/routes/documents/components/VersionHistorySidebar.tsx:17— VersionHistorySidebar.VersionHistorySidebar has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 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.
RoadmapView.RoadmapView (cyclomatic 21) apps/quarry-web/src/routes/plans/components/RoadmapView.tsx:73— RoadmapView.RoadmapView has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 96, 125, 275, …). 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.
RoadmapView.RoadmapView (cyclomatic 21) packages/ui/src/plans/components/RoadmapView.tsx:73— RoadmapView.RoadmapView has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 96, 125, 275, …). 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.
MobileDetailSheet.MobileDetailSheet (cyclomatic 20) apps/quarry-web/src/components/shared/MobileDetailSheet.tsx:26— MobileDetailSheet.MobileDetailSheet has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchMove, handleTouchEnd, 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.
MobileDetailSheet.MobileDetailSheet (cyclomatic 20) apps/smithy-web/src/components/shared/MobileDetailSheet.tsx:26— MobileDetailSheet.MobileDetailSheet has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchMove, handleTouchEnd, 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.
PlanTaskList.PlanTaskList (cyclomatic 20) apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx:18— PlanTaskList.PlanTaskList has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 69, handleRemoveClick). 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.
PlanTaskList.PlanTaskList (cyclomatic 20) packages/ui/src/plans/components/PlanTaskList.tsx:21— PlanTaskList.PlanTaskList has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 74, handleRemoveClick). 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.
websocket.handleWSMessage (cyclomatic 20) apps/smithy-server/src/websocket.ts:86— websocket.handleWSMessage 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.
websocket.handleWSMessage (cyclomatic 20) packages/smithy/src/server/websocket.ts:87— websocket.handleWSMessage 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.
Sidebar.Sidebar::renderNavItem (cyclomatic 19) apps/quarry-web/src/components/layout/Sidebar.tsx:150— Sidebar.Sidebar::renderNavItem has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (Sidebar.Sidebar) 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.
Sidebar.Sidebar::renderNavItem (cyclomatic 18) packages/ui/src/layout/Sidebar.tsx:150— Sidebar.Sidebar::renderNavItem has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (Sidebar.Sidebar) 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.
CreateLibraryModal.CreateLibraryModal (cyclomatic 18) apps/quarry-web/src/components/document/CreateLibraryModal.tsx:65— CreateLibraryModal.CreateLibraryModal 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 5 function items inside it that branch (handleSubmit, a function literal at line 81, a function literal at line 88, …). 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.
CreateLibraryModal.CreateLibraryModal (cyclomatic 18) apps/smithy-web/src/components/document/CreateLibraryModal.tsx:65— CreateLibraryModal.CreateLibraryModal 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 5 function items inside it that branch (handleSubmit, a function literal at line 81, a function literal at line 88, …). 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.
KanbanBoard.applyFiltersAndSort (cyclomatic 17) apps/quarry-web/src/components/task/KanbanBoard.tsx:150— KanbanBoard.applyFiltersAndSort has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 179). 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.
KanbanBoard.applyFiltersAndSort (cyclomatic 17) apps/smithy-web/src/components/task/KanbanBoard.tsx:189— KanbanBoard.applyFiltersAndSort has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 218). 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.
DocumentLinkComponents.LinkedDocumentsSection (cyclomatic 17) apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:244— DocumentLinkComponents.LinkedDocumentsSection has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DocumentLinkComponents.LinkedDocumentsSection (cyclomatic 17) apps/smithy-web/src/routes/documents/components/DocumentLinkComponents.tsx:244— DocumentLinkComponents.LinkedDocumentsSection has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
workspace-files.searchDirectory (cyclomatic 17) REDACTED:215— workspace-files.searchDirectory 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.
workspace-files.searchDirectory (cyclomatic 17) REDACTED:216— workspace-files.searchDirectory 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.
ChannelView.ChannelView (cognitive 67) apps/quarry-web/src/routes/messages/components/ChannelView.tsx:49— ChannelView.ChannelView has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 14 (29 pts), boolean chains 23, if/else 10 (14 pts), error handling 1 (nesting depth added 19). Of this number, 22 points are the body's own statements and 45 belong to 14 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.
ChannelView.ChannelView (cognitive 67) apps/smithy-web/src/routes/messages/components/ChannelView.tsx:50— ChannelView.ChannelView has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 14 (29 pts), boolean chains 23, if/else 10 (14 pts), error handling 1 (nesting depth added 19). Of this number, 22 points are the body's own statements and 45 belong to 14 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.
sessions.saveSessionEvent (cognitive 66) apps/smithy-server/src/routes/sessions.ts:30— sessions.saveSessionEvent has cognitive complexity 66 (threshold 15). Drivers by points: if/else 16 (40 pts), boolean chains 17, loops 2 (5 pts), error handling 1 (2 pts), ternaries 2 (nesting depth added 28). 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.
sessions.saveSessionEvent (cognitive 66) packages/smithy/src/server/routes/sessions.ts:36— sessions.saveSessionEvent has cognitive complexity 66 (threshold 15). Drivers by points: if/else 16 (40 pts), boolean chains 17, loops 2 (5 pts), error handling 1 (2 pts), ternaries 2 (nesting depth added 28). 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.
events.createEventRoutes (cognitive 48) apps/smithy-server/src/routes/events.ts:43— events.createEventRoutes has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 13, error handling 8 (9 pts), ternaries 3, loops 2 (nesting depth added 5). None of this is in the body itself: all 48 points belong to 9 function literals inside it that branch (lines 80, 261, 48, …). 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.
events.createEventRoutes (cognitive 48) packages/smithy/src/server/routes/events.ts:44— events.createEventRoutes has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 13, error handling 8 (9 pts), ternaries 3, loops 2 (nesting depth added 5). None of this is in the body itself: all 48 points belong to 9 function literals inside it that branch (lines 81, 262, 49, …). 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.
LibraryView.LibraryView (cognitive 47) apps/quarry-web/src/routes/documents/components/LibraryView.tsx:40— LibraryView.LibraryView has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 17 (36 pts), boolean chains 11 (nesting depth added 19). Of this number, 45 points are the body's own statements and 2 belong to 3 function literals 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.
LibraryView.LibraryView (cognitive 47) apps/smithy-web/src/routes/documents/components/LibraryView.tsx:40— LibraryView.LibraryView has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 17 (36 pts), boolean chains 11 (nesting depth added 19). Of this number, 45 points are the body's own statements and 2 belong to 3 function literals 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.
MessageComposer.MessageComposer (cognitive 43) apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:157— MessageComposer.MessageComposer has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 15, ternaries 13 (15 pts), if/else 10 (11 pts), error handling 2 (nesting depth added 3). Of this number, 25 points are the body's own statements and 18 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.
MessageComposer.MessageComposer (cognitive 43) apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:157— MessageComposer.MessageComposer has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 15, ternaries 13 (15 pts), if/else 10 (11 pts), error handling 2 (nesting depth added 3). Of this number, 25 points are the body's own statements and 18 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.
workspace-files.createWorkspaceFilesRoutes (cognitive 43) REDACTED:353— workspace-files.createWorkspaceFilesRoutes has cognitive complexity 43 (threshold 15). Drivers by points: if/else 24, error handling 13, boolean chains 4, ternaries 2. None of this is in the body itself: all 43 points belong to 7 function literals inside it that branch (lines 358, 395, 524, …). 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.
workspace-files.createWorkspaceFilesRoutes (cognitive 43) REDACTED:354— workspace-files.createWorkspaceFilesRoutes has cognitive complexity 43 (threshold 15). Drivers by points: if/else 24, error handling 13, boolean chains 4, ternaries 2. None of this is in the body itself: all 43 points belong to 7 function literals inside it that branch (lines 359, 396, 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.
CreateDocumentModal.CreateDocumentModal (cognitive 39) apps/quarry-web/src/components/document/CreateDocumentModal.tsx:75— CreateDocumentModal.CreateDocumentModal has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 19 (22 pts), if/else 9, boolean chains 7, error handling 1 (nesting depth added 3). Of this number, 28 points are the body's own statements and 11 belong to 5 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.
CreateDocumentModal.CreateDocumentModal (cognitive 39) apps/smithy-web/src/components/document/CreateDocumentModal.tsx:75— CreateDocumentModal.CreateDocumentModal has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 19 (22 pts), if/else 9, boolean chains 7, error handling 1 (nesting depth added 3). Of this number, 28 points are the body's own statements and 11 belong to 5 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.
DocumentPickerModal.DocumentPickerModal (cognitive 38) apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:80— DocumentPickerModal.DocumentPickerModal has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 10 (20 pts), boolean chains 9, if/else 8 (9 pts) (nesting depth added 11). Most of this is not in the body itself: 15 of the 38 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 138, 243, 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.
DocumentPickerModal.DocumentPickerModal (cognitive 38) apps/smithy-web/src/components/editor/DocumentPickerModal.tsx:80— DocumentPickerModal.DocumentPickerModal has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 10 (20 pts), boolean chains 9, if/else 8 (9 pts) (nesting depth added 11). Most of this is not in the body itself: 15 of the 38 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 138, 243, 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.
Oi::onPointerMove (cognitive 38) REDACTED:1— Oi::onPointerMove has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 17, if/else 8 (12 pts), ternaries 5 (9 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.
Oi::onPointerUp (cognitive 20) REDACTED:1— Oi::onPointerUp has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (10 pts), boolean chains 7, if/else 3 (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.
TaskPickerModal.TaskPickerModal (cognitive 37) apps/quarry-web/src/components/editor/TaskPickerModal.tsx:88— TaskPickerModal.TaskPickerModal has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 8 (9 pts), boolean chains 8 (nesting depth added 11). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 146, 249, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TaskPickerModal.TaskPickerModal (cognitive 37) apps/smithy-web/src/components/editor/TaskPickerModal.tsx:88— TaskPickerModal.TaskPickerModal has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 8 (9 pts), boolean chains 8 (nesting depth added 11). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 146, 249, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AllDocumentsView.AllDocumentsView (cognitive 34) apps/quarry-web/src/routes/documents/components/AllDocumentsView.tsx:37— AllDocumentsView.AllDocumentsView has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 16 (26 pts), boolean chains 6, if/else 2 (nesting depth added 10). Of this number, 30 points are the body's own statements and 4 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.
AllDocumentsView.AllDocumentsView (cognitive 34) apps/smithy-web/src/routes/documents/components/AllDocumentsView.tsx:37— AllDocumentsView.AllDocumentsView has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 16 (26 pts), boolean chains 6, if/else 2 (nesting depth added 10). Of this number, 30 points are the body's own statements and 4 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.
index.WorkflowsPage (cognitive 34) apps/quarry-web/src/routes/workflows/index.tsx:41— index.WorkflowsPage has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 19, ternaries 7, if/else 6, error handling 2. Of this number, 26 points are the body's own statements and 8 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.WorkflowsPage (cognitive 34) apps/smithy-web/src/routes/workflows/index.tsx:43— index.WorkflowsPage has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 19, ternaries 7, if/else 6, error handling 2. Of this number, 26 points are the body's own statements and 8 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
workspace-files.searchDirectory (cognitive 33) REDACTED:215— workspace-files.searchDirectory has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (26 pts), error handling 2 (4 pts), boolean chains 2, loops 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.
workspace-files.searchDirectory (cognitive 33) REDACTED:216— workspace-files.searchDirectory has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (26 pts), error handling 2 (4 pts), boolean chains 2, loops 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.
ChannelList.ChannelList (cognitive 29) apps/quarry-web/src/routes/messages/components/ChannelList.tsx:89— ChannelList.ChannelList has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 18 (24 pts), if/else 3, boolean chains 2 (nesting depth added 6). Of this number, 23 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ChannelList.ChannelList (cognitive 29) apps/smithy-web/src/routes/messages/components/ChannelList.tsx:89— ChannelList.ChannelList has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 18 (24 pts), if/else 3, boolean chains 2 (nesting depth added 6). Of this number, 23 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MessageBubble.MessageBubble (cognitive 28) apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:63— MessageBubble.MessageBubble has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 11, ternaries 11, if/else 5, error handling 1. Of this number, 20 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MessageBubble.MessageBubble (cognitive 28) apps/smithy-web/src/routes/messages/components/MessageBubble.tsx:62— MessageBubble.MessageBubble has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 11, ternaries 11, if/else 5, error handling 1. Of this number, 20 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
daemon.createDaemonRoutes (cognitive 27) apps/smithy-server/src/routes/daemon.ts:27— daemon.createDaemonRoutes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (16 pts), error handling 6, ternaries 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 3). None of this is in the body itself: all 27 points belong to 7 function literals inside it that branch (lines 237, 61, 103, …). 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.
daemon.createDaemonRoutes (cognitive 27) packages/smithy/src/server/routes/daemon.ts:28— daemon.createDaemonRoutes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (16 pts), error handling 6, ternaries 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 3). None of this is in the body itself: all 27 points belong to 7 function literals inside it that branch (lines 238, 62, 104, …). 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.
extensions.createExtensionsRoutes (cognitive 27) apps/smithy-server/src/routes/extensions.ts:49— extensions.createExtensionsRoutes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 3, error handling 3, loops 1, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 27 points belong to 4 function literals inside it that branch (lines 157, 62, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
extensions.createExtensionsRoutes (cognitive 27) packages/smithy/src/server/routes/extensions.ts:49— extensions.createExtensionsRoutes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 3, error handling 3, loops 1, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 27 points belong to 4 function literals inside it that branch (lines 157, 62, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VirtualizedChatList.VirtualizedChatList (cognitive 26) apps/quarry-web/src/components/shared/VirtualizedChatList.tsx:112— VirtualizedChatList.VirtualizedChatList has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 223, 182, 212, …). 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.
VirtualizedChatList.VirtualizedChatList (cognitive 26) apps/smithy-web/src/components/shared/VirtualizedChatList.tsx:112— VirtualizedChatList.VirtualizedChatList has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 223, 182, 212, …). 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.
VirtualizedList.VirtualizedList (cognitive 23) apps/quarry-web/src/components/shared/VirtualizedList.tsx:91— VirtualizedList.VirtualizedList has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 6 (8 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 123, 137, 148, …). 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.
VirtualizedList.VirtualizedList (cognitive 23) apps/smithy-web/src/components/shared/VirtualizedList.tsx:91— VirtualizedList.VirtualizedList has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 6 (8 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 123, 137, 148, …). 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.
(anonymous)::(anonymous)::setState (cognitive 23) REDACTED:811— (anonymous)::(anonymous)::setState has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (8 pts), boolean chains 4, other 1 (nesting depth added 11). 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.
(anonymous)::pe (cognitive 18) REDACTED:811— (anonymous)::pe has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 2 (4 pts), loops 3 (4 pts), boolean chains 2 (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.
websocket.handleWSMessage (cognitive 22) apps/smithy-server/src/websocket.ts:86— websocket.handleWSMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, error handling 1, 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.
websocket.handleWSMessage (cognitive 22) packages/smithy/src/server/websocket.ts:87— websocket.handleWSMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, error handling 1, 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.
TaskDetailPanel.DocumentPickerModal (cognitive 21) apps/quarry-web/src/components/task/TaskDetailPanel.tsx:897— TaskDetailPanel.DocumentPickerModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (10 pts), boolean chains 6, if/else 4 (5 pts) (nesting depth added 7). Of this number, 12 points are the body's own statements and 9 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.
TaskDetailPanel.DocumentPickerModal (cognitive 21) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:2099— TaskDetailPanel.DocumentPickerModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (10 pts), boolean chains 6, if/else 4 (5 pts) (nesting depth added 7). Of this number, 12 points are the body's own statements and 9 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.
MessageSearch.MessageSearchDropdown (cognitive 21) apps/quarry-web/src/routes/messages/components/MessageSearch.tsx:22— MessageSearch.MessageSearchDropdown has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (9 pts), boolean chains 1 (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 4 function items inside it that branch (a function literal at line 40, a function literal at line 64, formatTime, …). 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.
MessageSearch.MessageSearchDropdown (cognitive 21) apps/smithy-web/src/routes/messages/components/MessageSearch.tsx:115— MessageSearch.MessageSearchDropdown has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (9 pts), boolean chains 1 (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 4 function items inside it that branch (a function literal at line 133, a function literal at line 157, formatTime, …). 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.
index.MessagesPage (cognitive 21) apps/quarry-web/src/routes/messages/index.tsx:32— index.MessagesPage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 52, 98, 87). 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.
index.MessagesPage (cognitive 21) apps/smithy-web/src/routes/messages/index.tsx:32— index.MessagesPage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 52, 98, 87). 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.
DocumentSearchBar.DocumentSearchBar (cognitive 21) apps/quarry-web/src/routes/documents/components/DocumentSearchBar.tsx:14— DocumentSearchBar.DocumentSearchBar has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 15, if/else 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 35, 24, 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.
DocumentSearchBar.DocumentSearchBar (cognitive 21) apps/smithy-web/src/routes/documents/components/DocumentSearchBar.tsx:14— DocumentSearchBar.DocumentSearchBar has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 15, if/else 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 35, 24, 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.
TaskPickerModal.TaskPickerModal (cognitive 21) apps/quarry-web/src/routes/plans/components/TaskPickerModal.tsx:17— TaskPickerModal.TaskPickerModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (18 pts), boolean chains 2, if/else 1 (nesting depth added 12). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 84, 32, 43). 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.
TaskPickerModal.TaskPickerModal (cognitive 21) packages/ui/src/plans/components/TaskPickerModal.tsx:18— TaskPickerModal.TaskPickerModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (18 pts), boolean chains 2, if/else 1 (nesting depth added 12). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85, 33, 44). 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.
RoadmapView.RoadmapView (cognitive 21) apps/quarry-web/src/routes/plans/components/RoadmapView.tsx:73— RoadmapView.RoadmapView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 8, boolean chains 3, loops 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 96, 125, 275, …). 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.
RoadmapView.RoadmapView (cognitive 21) packages/ui/src/plans/components/RoadmapView.tsx:73— RoadmapView.RoadmapView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 8, boolean chains 3, loops 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 96, 125, 275, …). 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.
MobileDetailSheet.MobileDetailSheet (cognitive 19) apps/quarry-web/src/components/shared/MobileDetailSheet.tsx:26— MobileDetailSheet.MobileDetailSheet has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 4, ternaries 1. Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchMove, handleTouchEnd, 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.
MobileDetailSheet.MobileDetailSheet (cognitive 19) apps/smithy-web/src/components/shared/MobileDetailSheet.tsx:26— MobileDetailSheet.MobileDetailSheet has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 4, ternaries 1. Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchMove, handleTouchEnd, 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.
KanbanBoard.VirtualizedKanbanColumn (cognitive 19) apps/quarry-web/src/components/task/KanbanBoard.tsx:654— KanbanBoard.VirtualizedKanbanColumn has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (8 pts), ternaries 2 (nesting depth added 2). 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 701, 714, 725, …). 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.
KanbanBoard.VirtualizedKanbanColumn (cognitive 19) apps/smithy-web/src/components/task/KanbanBoard.tsx:644— KanbanBoard.VirtualizedKanbanColumn has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 3). 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 686, 698, 708, …). 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.
PageHeader.PageHeader (cognitive 18) apps/quarry-web/src/components/shared/PageHeader.tsx:51— PageHeader.PageHeader has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (5 pts), if/else 3 (nesting depth added 1). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 89, renderCount, renderActions). 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.
PageHeader.PageHeader (cognitive 18) apps/smithy-web/src/components/shared/PageHeader.tsx:51— PageHeader.PageHeader has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (5 pts), if/else 3 (nesting depth added 1). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 89, renderCount, renderActions). 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.
MessageComposer.MessageAttachmentPicker (cognitive 18) apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:40— MessageComposer.MessageAttachmentPicker has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 7). Of this number, 12 points are the body's own statements and 6 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.
MessageComposer.MessageAttachmentPicker (cognitive 18) apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:40— MessageComposer.MessageAttachmentPicker has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 7). Of this number, 12 points are the body's own statements and 6 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.
FilterBar.FilterBar (cognitive 17) apps/quarry-web/src/components/task/FilterBar.tsx:23— FilterBar.FilterBar has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 14, ternaries 3. Of this number, 15 points are the body's own statements and 2 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FilterBar.FilterBar (cognitive 17) apps/smithy-web/src/components/task/FilterBar.tsx:22— FilterBar.FilterBar has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 14, ternaries 3. Of this number, 15 points are the body's own statements and 2 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CreateLibraryModal.CreateLibraryModal (cognitive 16) apps/quarry-web/src/components/document/CreateLibraryModal.tsx:65— CreateLibraryModal.CreateLibraryModal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 6, error handling 1, ternaries 1. Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 81, a function literal at line 88, …). 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.
CreateLibraryModal.CreateLibraryModal (cognitive 16) apps/smithy-web/src/components/document/CreateLibraryModal.tsx:65— CreateLibraryModal.CreateLibraryModal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 6, error handling 1, ternaries 1. Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 81, a function literal at line 88, …). 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.
SortByDropdown.SortByDropdown (cognitive 16) apps/quarry-web/src/components/task/SortByDropdown.tsx:25— SortByDropdown.SortByDropdown has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 7, if/else 1. Of this number, 13 points are the body's own statements and 3 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.
SortByDropdown.SortByDropdown (cognitive 16) apps/smithy-web/src/components/task/SortByDropdown.tsx:25— SortByDropdown.SortByDropdown has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 7, if/else 1. Of this number, 13 points are the body's own statements and 3 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.
Fake-async — async method never awaits apps/smithy-server/src/services/lsp-manager.ts:63— `commandExists` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits apps/smithy-web/src/lib/monaco-lsp/lightweight-client.ts:353— `stop` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplication concentrated across 4 sibling directories (12 clone groups) apps/smithy-web/src/components/task/CreateTaskModal.tsx:308— 12 duplicated blocks under apps/smithy-web/src/ have copies in at least two of the sibling directories api, components, hooks, routes — 6 of them are reported below, and 6 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.
Duplication concentrated across 4 sibling directories (12 clone groups) packages/quarry/src/external-sync/providers/linear/linear-provider.ts:47— 12 duplicated blocks under packages/quarry/src/external-sync/providers/ have copies in at least two of the sibling directories folder, github, linear, notion — 6 of them are reported below, and 6 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.
Wholesale file copy (190 identical lines × 2 files) apps/quarry-web/src/hooks/usePaginatedData.ts:14— apps/quarry-web/src/hooks/usePaginatedData.ts:14 · apps/smithy-web/src/hooks/usePaginatedData.ts:14 — these 2 files are line-for-line copies of one another — 190 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.
Wholesale file copy (190 identical lines × 2 files) apps/smithy-server/src/routes/events.ts:7— apps/smithy-server/src/routes/events.ts:7 · packages/smithy/src/server/routes/events.ts:7 — these 2 files are line-for-line copies of one another — 190 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.
Complex function saveSessionEvent (cyclomatic 52, cognitive 79) apps/smithy-server/src/routes/sessions.ts:30— saveSessionEvent has cyclomatic complexity 52 and cognitive complexity 79; 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 saveSessionEvent (cyclomatic 52, cognitive 79) packages/smithy/src/server/routes/sessions.ts:36— saveSessionEvent has cyclomatic complexity 52 and cognitive complexity 79; 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.
Dead file (~417 LoC) apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~417 LoC) apps/smithy-next/src/components/overlays/runtimes/RuntimeCreateView.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-next/src/components/overlays/RuntimesOverlay.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~191 LoC) apps/quarry-web/src/components/shared/ResponsiveSortDropdown.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~191 LoC) apps/smithy-server/src/routes/scheduler.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~78 LoC) apps/quarry-web/src/routes/plans/constants.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx, apps/quarry-web/src/routes/plans/components/RoadmapView.tsx, apps/quarry-web/src/routes/plans/components/StatusBadge.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~78 LoC) apps/smithy-next/src/components/dropdowns/DropdownPortal.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~52 LoC) apps/quarry-web/src/routes/plans/components/TaskStatusSummary.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~52 LoC) apps/smithy-server/src/routes/upload.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
AC1 · Text alternatives· <video> without a captions track · ×1
<video> without a captions track apps/website/src/components/sections/DemoSection.astro:35— Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
Low contrast Tailwind colour pair (4.2:1) apps/quarry-web/src/components/editor/BlockEditor.tsx:111— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.3:1) apps/quarry-web/src/components/editor/MentionAutocomplete.tsx:285— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.4:1) apps/quarry-web/src/routes/dependency-graph/components/GraphToolbar.tsx:177— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.1:1) apps/quarry-web/src/routes/entities/components/HistoryEventItem.tsx:201— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
index.createQuarryApp (cyclomatic 561) REDACTED:129— index.createQuarryApp has cyclomatic complexity 561 (threshold 15). Most of this is not in the body itself: 8 of the 561 points are its own statements and the rest belongs to 92 function items inside it that branch (a function literal at line 2494, a function literal at line 3017, a function literal at line 535, …). 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.
documents.createDocumentRoutes (cyclomatic 252) packages/shared-routes/src/documents.ts:30— documents.createDocumentRoutes has cyclomatic complexity 252 (threshold 15). Most of this is not in the body itself: 1 of the 252 points is its own statement and the rest belongs to 28 function literals inside it that branch (lines 35, 261, 159, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.FileEditorPage (cyclomatic 210) apps/smithy-web/src/routes/editor/index.tsx:219— index.FileEditorPage has cyclomatic complexity 210 (threshold 15). Of this number, 63 points are the body's own statements and 147 belong to 45 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.
tasks.createTaskRoutes (cyclomatic 158) packages/smithy/src/server/routes/tasks.ts:46— tasks.createTaskRoutes has cyclomatic complexity 158 (threshold 15). Most of this is not in the body itself: 1 of the 158 points is its own statement and the rest belongs to 31 function literals inside it that branch (lines 262, 133, 602, …). 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.
StreamViewer.StreamViewer (cyclomatic 155) apps/smithy-web/src/components/workspace/StreamViewer.tsx:335— StreamViewer.StreamViewer has cyclomatic complexity 155 (threshold 15). Most of this is not in the body itself: 13 of the 155 points are its own statements and the rest belongs to 32 function items inside it that branch (a function literal at line 674, a function literal at line 637, a function literal at line 1003, …). 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.
tasks.createTaskRoutes (cyclomatic 152) apps/smithy-server/src/routes/tasks.ts:43— tasks.createTaskRoutes has cyclomatic complexity 152 (threshold 15). Most of this is not in the body itself: 1 of the 152 points is its own statement and the rest belongs to 31 function literals inside it that branch (lines 205, 543, 108, …). 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.
utils-vendor-CfYKiENT.Oi (cyclomatic 144) REDACTED:1— utils-vendor-CfYKiENT.Oi has cyclomatic complexity 144 (threshold 15). Of this number, 69 points are the body's own statements and 75 belong to 17 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.
DirectorPanel.DirectorPanel (cyclomatic 141) apps/smithy-next/src/components/DirectorPanel.tsx:112— DirectorPanel.DirectorPanel has cyclomatic complexity 141 (threshold 15). Of this number, 66 points are the body's own statements and 75 belong to 38 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.
TaskDetailOverlay.TaskDetailOverlay (cyclomatic 138) apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:36— TaskDetailOverlay.TaskDetailOverlay has cyclomatic complexity 138 (threshold 15). Of this number, 84 points are the body's own statements and 54 belong to 26 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.
WorkflowEditorModal.WorkflowEditorModal (cyclomatic 123) packages/ui/src/workflows/components/WorkflowEditorModal.tsx:980— WorkflowEditorModal.WorkflowEditorModal has cyclomatic complexity 123 (threshold 15). Of this number, 37 points are the body's own statements and 86 belong to 13 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.
agents.createAgentRoutes (cyclomatic 116) packages/smithy/src/server/routes/agents.ts:16— agents.createAgentRoutes has cyclomatic complexity 116 (threshold 15). Most of this is not in the body itself: 1 of the 116 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 306, 211, 34, …). 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.
XTerminal.XTerminal (cyclomatic 105) apps/smithy-web/src/components/terminal/XTerminal.tsx:125— XTerminal.XTerminal has cyclomatic complexity 105 (threshold 15). Most of this is not in the body itself: 4 of the 105 points are its own statements and the rest belongs to 24 function literals inside it that branch (lines 314, 439, 665, …). 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.
DocumentDetailPanel.DocumentDetailPanel (cyclomatic 102) apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:59— DocumentDetailPanel.DocumentDetailPanel has cyclomatic complexity 102 (threshold 15). Of this number, 74 points are the body's own statements and 28 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.
plans.createPlanRoutes (cyclomatic 98) packages/shared-routes/src/plans.ts:22— plans.createPlanRoutes has cyclomatic complexity 98 (threshold 15). Most of this is not in the body itself: 1 of the 98 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 348, 196, 513, …). 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.
ImageUploadModal.ImageUploadModal (cyclomatic 97) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:53— ImageUploadModal.ImageUploadModal has cyclomatic complexity 97 (threshold 15). Of this number, 55 points are the body's own statements and 42 belong to 16 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.
sessions.createSessionRoutes (cyclomatic 94) apps/smithy-server/src/routes/sessions.ts:207— sessions.createSessionRoutes has cyclomatic complexity 94 (threshold 15). Most of this is not in the body itself: 1 of the 94 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 215, 896, 538, …). 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.
libraries.createLibraryRoutes (cyclomatic 93) packages/shared-routes/src/libraries.ts:12— libraries.createLibraryRoutes has cyclomatic complexity 93 (threshold 15). Most of this is not in the body itself: 1 of the 93 points is its own statement and the rest belongs to 12 function items inside it that branch (a function literal at line 382, a function literal at line 277, a function literal at line 469, …). 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.
sessions.createSessionRoutes (cyclomatic 93) packages/smithy/src/server/routes/sessions.ts:213— sessions.createSessionRoutes has cyclomatic complexity 93 (threshold 15). Most of this is not in the body itself: 1 of the 93 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 221, 908, 836, …). 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.
channels.createChannelRoutes (cyclomatic 92) packages/shared-routes/src/channels.ts:13— channels.createChannelRoutes has cyclomatic complexity 92 (threshold 15). Most of this is not in the body itself: 1 of the 92 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 112, 327, 18, …). 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.
inbox.createInboxRoutes (cyclomatic 92) packages/shared-routes/src/inbox.ts:13— inbox.createInboxRoutes has cyclomatic complexity 92 (threshold 15). Most of this is not in the body itself: 1 of the 92 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 28, 276, 350, …). 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.
RoleDefinitionDetailView.RoleDefinitionDetailView (cyclomatic 91) apps/smithy-next/src/components/overlays/agents/RoleDefinitionDetailView.tsx:277— RoleDefinitionDetailView.RoleDefinitionDetailView has cyclomatic complexity 91 (threshold 15). Of this number, 46 points are the body's own statements and 45 belong to 17 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.
utils-vendor-CfYKiENT.zn (cyclomatic 87) REDACTED:811— utils-vendor-CfYKiENT.zn has cyclomatic complexity 87 (threshold 15). Most of this is not in the body itself: 1 of the 87 points is its own statement and the rest belongs to 24 function items inside it that branch (a function literal at line 811, a function literal at line 811, pe, …). 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.
RuntimeDetailView.EditMode (cyclomatic 84) apps/smithy-next/src/components/overlays/agents/RuntimeDetailView.tsx:275— RuntimeDetailView.EditMode has cyclomatic complexity 84 (threshold 15). Of this number, 42 points are the body's own statements and 42 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.
CanvasView.CanvasView (cyclomatic 83) apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:36— CanvasView.CanvasView has cyclomatic complexity 83 (threshold 15). Of this number, 19 points are the body's own statements and 64 belong to 34 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.
AppShell.AppShell (cyclomatic 83) apps/smithy-web/src/components/layout/AppShell.tsx:663— AppShell.AppShell has cyclomatic complexity 83 (threshold 15). Of this number, 26 points are the body's own statements and 57 belong to 19 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.
KanbanBoard.KanbanBoard (cyclomatic 81) apps/smithy-next/src/components/KanbanBoard.tsx:40— KanbanBoard.KanbanBoard has cyclomatic complexity 81 (threshold 15). Of this number, 20 points are the body's own statements and 61 belong to 25 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.
MRDiffViewer.MRDiffViewer (cyclomatic 81) apps/smithy-next/src/components/overlays/mr/MRDiffViewer.tsx:30— MRDiffViewer.MRDiffViewer has cyclomatic complexity 81 (threshold 15). Most of this is not in the body itself: 1 of the 81 points is its own statement and the rest belongs to 17 function items inside it that branch (a function literal at line 218, a function literal at line 144, isLineSelected, …). 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.
DirectorPanel.DirectorPanel (cyclomatic 81) apps/smithy-web/src/components/layout/DirectorPanel.tsx:303— DirectorPanel.DirectorPanel has cyclomatic complexity 81 (threshold 15). Of this number, 27 points are the body's own statements and 54 belong to 24 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.
index.DocumentsPage (cyclomatic 81) apps/smithy-web/src/routes/documents/index.tsx:53— index.DocumentsPage has cyclomatic complexity 81 (threshold 15). Of this number, 34 points are the body's own statements and 47 belong to 19 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.
DocumentDetailPanel.DocumentDetailPanel (cyclomatic 80) apps/smithy-web/src/routes/documents/components/DocumentDetailPanel.tsx:49— DocumentDetailPanel.DocumentDetailPanel has cyclomatic complexity 80 (threshold 15). Of this number, 64 points are the body's own statements and 16 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.
index.TasksPage (cyclomatic 78) apps/quarry-web/src/routes/tasks/index.tsx:90— index.TasksPage has cyclomatic complexity 78 (threshold 15). Of this number, 40 points are the body's own statements and 38 belong to 19 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.
ActiveAgentsStrip.ActiveAgentsStrip (cyclomatic 77) apps/smithy-next/src/components/ActiveAgentsStrip.tsx:22— ActiveAgentsStrip.ActiveAgentsStrip has cyclomatic complexity 77 (threshold 15). Of this number, 30 points are the body's own statements and 47 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.
agents.createAgentRoutes (cyclomatic 76) apps/smithy-server/src/routes/agents.ts:16— agents.createAgentRoutes has cyclomatic complexity 76 (threshold 15). Most of this is not in the body itself: 1 of the 76 points is its own statement and the rest belongs to 12 function literals inside it that branch (lines 196, 283, 34, …). 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.
index.InboxPage (cyclomatic 75) apps/smithy-web/src/routes/inbox/index.tsx:853— index.InboxPage has cyclomatic complexity 75 (threshold 15). Of this number, 38 points are the body's own statements and 37 belong to 12 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.
messages.createMessageRoutes (cyclomatic 73) packages/shared-routes/src/messages.ts:12— messages.createMessageRoutes has cyclomatic complexity 73 (threshold 15). Most of this is not in the body itself: 1 of the 73 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 17, 256, 373, …). 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.
EditorOverlayNew.EditorOverlayNew (cyclomatic 72) apps/smithy-next/src/components/overlays/editor/EditorOverlayNew.tsx:36— EditorOverlayNew.EditorOverlayNew has cyclomatic complexity 72 (threshold 15). Of this number, 29 points are the body's own statements and 43 belong to 15 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.
WorkspacesOverlay.WorkspacesOverlay (cyclomatic 72) apps/smithy-next/src/components/overlays/WorkspacesOverlay.tsx:46— WorkspacesOverlay.WorkspacesOverlay has cyclomatic complexity 72 (threshold 15). Of this number, 18 points are the body's own statements and 54 belong to 29 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.
inbox.InboxPage (cyclomatic 69) apps/quarry-web/src/routes/inbox.tsx:853— inbox.InboxPage has cyclomatic complexity 69 (threshold 15). Of this number, 38 points are the body's own statements and 31 belong to 11 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.
WorkspaceGrid.WorkspaceGrid (cyclomatic 69) apps/smithy-web/src/components/workspace/WorkspaceGrid.tsx:347— WorkspaceGrid.WorkspaceGrid has cyclomatic complexity 69 (threshold 15). Of this number, 28 points are the body's own statements and 41 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.
ActivityRail.ActivityRail (cyclomatic 68) apps/smithy-next/src/components/ActivityRail.tsx:79— ActivityRail.ActivityRail has cyclomatic complexity 68 (threshold 15). Of this number, 38 points are the body's own statements and 30 belong to 15 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.
index.TimelinePage (cyclomatic 66) apps/quarry-web/src/routes/timeline/index.tsx:32— index.TimelinePage has cyclomatic complexity 66 (threshold 15). Of this number, 37 points are the body's own statements and 29 belong to 13 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.
RuntimeListView.RuntimeListView (cyclomatic 65) apps/smithy-next/src/components/overlays/runtimes/RuntimeListView.tsx:30— RuntimeListView.RuntimeListView has cyclomatic complexity 65 (threshold 15). Of this number, 28 points are the body's own statements and 37 belong to 16 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.
WorkspacePane.WorkspacePane (cyclomatic 64) apps/smithy-web/src/components/workspace/WorkspacePane.tsx:66— WorkspacePane.WorkspacePane has cyclomatic complexity 64 (threshold 15). Of this number, 51 points are the body's own statements and 13 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KanbanBoard.TaskCard (cyclomatic 63) apps/smithy-next/src/components/KanbanBoard.tsx:456— KanbanBoard.TaskCard has cyclomatic complexity 63 (threshold 15). Of this number, 46 points are the body's own statements and 17 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.TasksPage (cyclomatic 63) apps/smithy-web/src/routes/tasks/index.tsx:89— index.TasksPage has cyclomatic complexity 63 (threshold 15). Of this number, 16 points are the body's own statements and 47 belong to 19 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.
workflows.createWorkflowRoutes (cyclomatic 63) packages/smithy/src/server/routes/workflows.ts:143— workflows.createWorkflowRoutes has cyclomatic complexity 63 (threshold 15). Most of this is not in the body itself: 1 of the 63 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 660, 154, 238, …). 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.
PreviewOverlay.PreviewOverlay (cyclomatic 62) apps/smithy-next/src/components/overlays/PreviewOverlay.tsx:41— PreviewOverlay.PreviewOverlay has cyclomatic complexity 62 (threshold 15). Of this number, 41 points are the body's own statements and 21 belong to 14 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.
KanbanBoard.ListRow (cyclomatic 60) apps/smithy-next/src/components/KanbanBoard.tsx:585— KanbanBoard.ListRow has cyclomatic complexity 60 (threshold 15). Of this number, 42 points are the body's own statements and 18 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RuntimeCreateView.RuntimeCreateView (cyclomatic 58) apps/smithy-next/src/components/overlays/runtimes/RuntimeCreateView.tsx:25— RuntimeCreateView.RuntimeCreateView has cyclomatic complexity 58 (threshold 15). Of this number, 28 points are the body's own statements and 30 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.
TeamDetailPanel.TeamDetailPanel (cyclomatic 57) apps/quarry-web/src/routes/teams/components/TeamDetailPanel.tsx:25— TeamDetailPanel.TeamDetailPanel has cyclomatic complexity 57 (threshold 15). Of this number, 37 points are the body's own statements and 20 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.
EntityDetailPanel.OverviewTabContent (cyclomatic 56) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:592— EntityDetailPanel.OverviewTabContent has cyclomatic complexity 56 (threshold 15). Of this number, 45 points are the body's own statements and 11 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.
inbox.InboxMessageContent (cyclomatic 56) apps/quarry-web/src/routes/inbox.tsx:402— inbox.InboxMessageContent has cyclomatic complexity 56 (threshold 15). Of this number, 29 points are the body's own statements and 27 belong to 9 function items 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.
ChannelListView.ChannelListView (cyclomatic 56) apps/smithy-next/src/components/overlays/messages/ChannelListView.tsx:19— ChannelListView.ChannelListView has cyclomatic complexity 56 (threshold 15). Of this number, 23 points are the body's own statements and 33 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.
App.parseUrl (cyclomatic 56) apps/smithy-next/src/App.tsx:108— App.parseUrl has cyclomatic complexity 56 (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.
EditorExtensionsPanel.EditorExtensionsPanel (cyclomatic 56) apps/smithy-web/src/components/editor/EditorExtensionsPanel.tsx:83— EditorExtensionsPanel.EditorExtensionsPanel has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 10 of the 56 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 352, 505, 486, …). 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.
index.InboxMessageContent (cyclomatic 56) apps/smithy-web/src/routes/inbox/index.tsx:402— index.InboxMessageContent has cyclomatic complexity 56 (threshold 15). Of this number, 29 points are the body's own statements and 27 belong to 9 function items 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.
external-sync.linkAllDocumentsHandler (cyclomatic 56) packages/quarry/src/cli/commands/external-sync.ts:2089— external-sync.linkAllDocumentsHandler has cyclomatic complexity 56 (threshold 15). Of this number, 53 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HistoryEventItem.HistoryEventItem (cyclomatic 55) apps/quarry-web/src/routes/entities/components/HistoryEventItem.tsx:15— HistoryEventItem.HistoryEventItem has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 11 of the 55 points are its own statements and the rest belongs to 9 function items inside it that branch (getMessage, formatValue, getChangedFields, …). 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.
DesignModeOverlay.DesignModeOverlay (cyclomatic 55) apps/smithy-next/src/components/overlays/preview/DesignModeOverlay.tsx:20— DesignModeOverlay.DesignModeOverlay has cyclomatic complexity 55 (threshold 15). Of this number, 20 points are the body's own statements and 35 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.
index.DocumentsPage (cyclomatic 54) apps/quarry-web/src/routes/documents/index.tsx:34— index.DocumentsPage has cyclomatic complexity 54 (threshold 15). Of this number, 28 points are the body's own statements and 26 belong to 13 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.
index.PlansPage (cyclomatic 54) apps/quarry-web/src/routes/plans/index.tsx:49— index.PlansPage has cyclomatic complexity 54 (threshold 15). Of this number, 40 points are the body's own statements and 14 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.
EntityDetailPanel.EntityDetailPanel (cyclomatic 54) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:95— EntityDetailPanel.EntityDetailPanel has cyclomatic complexity 54 (threshold 15). Of this number, 18 points are the body's own statements and 36 belong to 11 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.
SessionListView.SessionListView (cyclomatic 54) apps/smithy-next/src/components/overlays/sessions/SessionListView.tsx:62— SessionListView.SessionListView has cyclomatic complexity 54 (threshold 15). Of this number, 16 points are the body's own statements and 38 belong to 15 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.
workflows.createWorkflowRoutes (cyclomatic 54) apps/smithy-server/src/routes/workflows.ts:98— workflows.createWorkflowRoutes has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 1 of the 54 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 109, 193, 443, …). 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.
CronScheduleBuilder.describeCron (cyclomatic 54) apps/smithy-web/src/components/agent/CronScheduleBuilder.tsx:174— CronScheduleBuilder.describeCron has cyclomatic complexity 54 (threshold 15). Of this number, 49 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.
LspMonacoEditor.LspMonacoEditorComponent (cyclomatic 54) apps/smithy-web/src/components/editor/LspMonacoEditor.tsx:176— LspMonacoEditor.LspMonacoEditorComponent has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 5 of the 54 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 326, 373, 397, …). 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.
crud.updateHandler (cyclomatic 53) packages/quarry/src/cli/commands/crud.ts:820— crud.updateHandler has cyclomatic complexity 53 (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.
playbook-yaml.validateYamlStep (cyclomatic 52) packages/core/src/types/playbook-yaml.ts:651— playbook-yaml.validateYamlStep has cyclomatic complexity 52 (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.
external-sync.linkAllHandler (cyclomatic 52) packages/quarry/src/cli/commands/external-sync.ts:2392— external-sync.linkAllHandler has cyclomatic complexity 52 (threshold 15). Of this number, 49 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
playbook.playbookValidateHandler (cyclomatic 52) packages/quarry/src/cli/commands/playbook.ts:326— playbook.playbookValidateHandler has cyclomatic complexity 52 (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.
CIRunListView.CIRunListView (cyclomatic 51) apps/smithy-next/src/components/overlays/ci/CIRunListView.tsx:31— CIRunListView.CIRunListView has cyclomatic complexity 51 (threshold 15). Of this number, 19 points are the body's own statements and 32 belong to 14 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.
TaskDetailPanel.TaskDetailPanel (cyclomatic 51) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:99— TaskDetailPanel.TaskDetailPanel has cyclomatic complexity 51 (threshold 15). Of this number, 40 points are the body's own statements and 11 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
validation.validateConfiguration (cyclomatic 51) packages/quarry/src/config/validation.ts:321— validation.validateConfiguration has cyclomatic complexity 51 (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.
EntityDetailPanel.InboxTabContent (cyclomatic 50) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:1087— EntityDetailPanel.InboxTabContent has cyclomatic complexity 50 (threshold 15). Of this number, 29 points are the body's own statements and 21 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.
SessionsOverlay.SessionsOverlay (cyclomatic 50) apps/smithy-next/src/components/overlays/SessionsOverlay.tsx:47— SessionsOverlay.SessionsOverlay has cyclomatic complexity 50 (threshold 15). Of this number, 17 points are the body's own statements and 33 belong to 19 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.
App.buildUrl (cyclomatic 50) apps/smithy-next/src/App.tsx:269— App.buildUrl has cyclomatic complexity 50 (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.
QuarryAPIImpl.create (cyclomatic 50) packages/quarry/src/api/quarry-api.ts:892— QuarryAPIImpl.create has cyclomatic complexity 50 (threshold 15). Of this number, 46 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WorkflowListView.WorkflowListView (cyclomatic 49) apps/smithy-next/src/components/overlays/automations/WorkflowListView.tsx:47— WorkflowListView.WorkflowListView has cyclomatic complexity 49 (threshold 15). Of this number, 16 points are the body's own statements and 33 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.
HorizontalTimeline.HorizontalTimeline (cyclomatic 48) apps/quarry-web/src/routes/timeline/components/HorizontalTimeline.tsx:32— HorizontalTimeline.HorizontalTimeline has cyclomatic complexity 48 (threshold 15). Of this number, 24 points are the body's own statements and 24 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.
ExtensionDetailPage.ExtensionDetailPage (cyclomatic 48) REDACTED:172— ExtensionDetailPage.ExtensionDetailPage has cyclomatic complexity 48 (threshold 15). Of this number, 38 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
init.initHandler (cyclomatic 48) packages/quarry/src/cli/commands/init.ts:538— init.initHandler has cyclomatic complexity 48 (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.
WorkflowRunPage.WorkflowRunPage (cyclomatic 47) apps/smithy-next/src/components/overlays/automations/WorkflowRunPage.tsx:46— WorkflowRunPage.WorkflowRunPage has cyclomatic complexity 47 (threshold 15). Of this number, 43 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.
ChannelDetailView.ChannelDetailView (cyclomatic 47) apps/smithy-next/src/components/overlays/messages/ChannelDetailView.tsx:121— ChannelDetailView.ChannelDetailView has cyclomatic complexity 47 (threshold 15). Of this number, 24 points are the body's own statements and 23 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.
DocListView.DocListView (cyclomatic 47) apps/smithy-next/src/components/overlays/documents/DocListView.tsx:358— DocListView.DocListView has cyclomatic complexity 47 (threshold 15). Of this number, 17 points are the body's own statements and 30 belong to 6 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.
utils-vendor-CfYKiENT.Oc (cyclomatic 47) REDACTED:1— utils-vendor-CfYKiENT.Oc has cyclomatic complexity 47 (threshold 15). Of this number, 24 points are the body's own statements and 23 belong to 14 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.
services.initializeServices (cyclomatic 47) packages/smithy/src/server/services.ts:111— services.initializeServices has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 10 of the 47 points are its own statements and the rest belongs to 11 function items inside it that branch (onSessionStarted::onResultEvent, a function literal at line 237, onSessionStarted::resolveTaskId, …). 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.
(anonymous) (cyclomatic 47) REDACTED:1— (anonymous) has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 5 of the 47 points are its own statements and the rest belongs to 42 function items inside it that branch (a function literal at line 1, (anonymous)::y, a function literal at line 1, …). 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.
PlanDetailView.PlanDetailView (cyclomatic 46) apps/smithy-next/src/components/overlays/plans/PlanDetailView.tsx:40— PlanDetailView.PlanDetailView has cyclomatic complexity 46 (threshold 15). Of this number, 27 points are the body's own statements and 19 belong to 7 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.
crud.createHandler (cyclomatic 46) packages/quarry/src/cli/commands/crud.ts:100— crud.createHandler has cyclomatic complexity 46 (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.
MRListView.MRListView (cyclomatic 45) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:19— MRListView.MRListView has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 15 of the 45 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 32, 85, 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.
WorkflowCreateView.WorkflowCreateView (cyclomatic 45) apps/smithy-next/src/components/overlays/automations/WorkflowCreateView.tsx:75— WorkflowCreateView.WorkflowCreateView has cyclomatic complexity 45 (threshold 15). Of this number, 25 points are the body's own statements and 20 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
file.convertYamlToConfig (cyclomatic 45) packages/quarry/src/config/file.ts:189— file.convertYamlToConfig has cyclomatic complexity 45 (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.
message.msgSendHandler (cyclomatic 45) packages/quarry/src/cli/commands/message.ts:110— message.msgSendHandler has cyclomatic complexity 45 (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.
RuntimeDetailView.RuntimeDetailView (cyclomatic 44) apps/smithy-next/src/components/overlays/runtimes/RuntimeDetailView.tsx:30— RuntimeDetailView.RuntimeDetailView has cyclomatic complexity 44 (threshold 15). Of this number, 34 points are the body's own statements and 10 belong to 4 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.
EditorFileTree.EditorFileTree (cyclomatic 44) apps/smithy-web/src/components/editor/EditorFileTree.tsx:733— EditorFileTree.EditorFileTree has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 6 of the 44 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 926, 973, 837, …). 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.
admin.doctorHandler (cyclomatic 44) packages/quarry/src/cli/commands/admin.ts:57— admin.doctorHandler has cyclomatic complexity 44 (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.
pools.createPoolRoutes (cyclomatic 43) packages/smithy/src/server/routes/pools.ts:16— pools.createPoolRoutes has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 127, 51, 167, …). 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.
constructor (cyclomatic 43) REDACTED:1— constructor has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 1 of the 43 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 1, promise, create, …). 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.
EditorCodeView.EditorCodeView (cyclomatic 42) apps/smithy-next/src/components/overlays/editor/EditorCodeView.tsx:20— EditorCodeView.EditorCodeView has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 11 of the 42 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 217, a function literal at line 55, a function literal at line 43, …). 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.
AgentListView.AgentListView (cyclomatic 42) apps/smithy-next/src/components/overlays/agents/AgentListView.tsx:51— AgentListView.AgentListView has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 12 of the 42 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 71, 112, 93, …). 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.
CronScheduleBuilder.cronToBuilder (cyclomatic 42) apps/smithy-web/src/components/agent/CronScheduleBuilder.tsx:115— CronScheduleBuilder.cronToBuilder has cyclomatic complexity 42 (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.
task-utils.groupTasks (cyclomatic 42) apps/smithy-web/src/lib/task-utils.tsx:190— task-utils.groupTasks has cyclomatic complexity 42 (threshold 15). Of this number, 32 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QuarryAPIImpl.update (cyclomatic 42) packages/quarry/src/api/quarry-api.ts:1286— QuarryAPIImpl.update has cyclomatic complexity 42 (threshold 15). Of this number, 20 points are the body's own statements and 22 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
validation.validatePartialConfiguration (cyclomatic 42) packages/quarry/src/config/validation.ts:640— validation.validatePartialConfiguration has cyclomatic complexity 42 (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.
DispatchDaemonImpl.recoverOrphanedAssignments (cyclomatic 42) packages/smithy/src/services/dispatch-daemon.ts:1203— DispatchDaemonImpl.recoverOrphanedAssignments has cyclomatic complexity 42 (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.
MessageImageAttachment.MessageImageAttachment (cyclomatic 42) packages/ui/src/message/MessageImageAttachment.tsx:45— MessageImageAttachment.MessageImageAttachment has cyclomatic complexity 42 (threshold 15). Of this number, 19 points are the body's own statements and 23 belong to 11 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.
file.convertConfigToYaml (cyclomatic 41) packages/quarry/src/config/file.ts:423— file.convertConfigToYaml has cyclomatic complexity 41 (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.
KanbanBoard.KanbanBoard (cyclomatic 40) apps/smithy-web/src/components/task/KanbanBoard.tsx:814— KanbanBoard.KanbanBoard has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 2 of the 40 points are its own statements and the rest belongs to 14 function items inside it that branch (handleDragEnd, a function literal at line 848, a function literal at line 826, …). 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.
task.isTask (cyclomatic 40) packages/core/src/types/task.ts:464— task.isTask has cyclomatic complexity 40 (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.
MessageRichComposer.MessageRichComposer (cyclomatic 40) packages/ui/src/message/MessageRichComposer.tsx:134— MessageRichComposer.MessageRichComposer has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 9 of the 40 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 238, 270, 304, …). 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.
DocEditorView.DocEditorView (cyclomatic 39) apps/smithy-next/src/components/overlays/documents/DocEditorView.tsx:371— DocEditorView.DocEditorView has cyclomatic complexity 39 (threshold 15). Of this number, 20 points are the body's own statements and 19 belong to 8 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.
dependency.isValidAwaitsMetadata (cyclomatic 39) packages/core/src/types/dependency.ts:386— dependency.isValidAwaitsMetadata has cyclomatic complexity 39 (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.
external-sync.unlinkAllHandler (cyclomatic 39) packages/quarry/src/cli/commands/external-sync.ts:766— external-sync.unlinkAllHandler has cyclomatic complexity 39 (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.
ContributionChart.ContributionChart (cyclomatic 38) apps/quarry-web/src/components/shared/ContributionChart.tsx:101— ContributionChart.ContributionChart has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 7 of the 38 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 118, a function literal at line 273, a function literal at line 293, …). 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.
task-utils.groupTasks (cyclomatic 38) apps/quarry-web/src/lib/task-utils.tsx:187— task-utils.groupTasks has cyclomatic complexity 38 (threshold 15). Of this number, 32 points are the body's own statements and 6 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.
PlanListView.PlanListView (cyclomatic 38) apps/smithy-next/src/components/overlays/plans/PlanListView.tsx:27— PlanListView.PlanListView has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 11 of the 38 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 50, 89, 74, …). 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.
InfiniteCanvas.InfiniteCanvas (cyclomatic 38) apps/smithy-next/src/components/overlays/sessions/canvas/InfiniteCanvas.tsx:26— InfiniteCanvas.InfiniteCanvas 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 63, 105, 139, …). 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.
SessionDetailView.SessionDetailView (cyclomatic 37) apps/smithy-next/src/components/overlays/sessions/SessionDetailView.tsx:39— SessionDetailView.SessionDetailView has cyclomatic complexity 37 (threshold 15). Of this number, 25 points are the body's own statements and 12 belong to 8 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.
App._unused_TaskDetail (cyclomatic 37) apps/smithy-next/src/App.tsx:1145— App._unused_TaskDetail has cyclomatic complexity 37 (threshold 15). Of this number, 31 points are the body's own statements and 6 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.
index.AgentsPage (cyclomatic 37) apps/smithy-web/src/routes/agents/index.tsx:23— index.AgentsPage has cyclomatic complexity 37 (threshold 15). Of this number, 21 points are the body's own statements and 16 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.
steward-scheduler.createStewardExecutor.<returned closure> (cyclomatic 37) REDACTED:1442— steward-scheduler.createStewardExecutor.<returned closure> 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.
WorkflowDetailView.WorkflowDetailView (cyclomatic 36) apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.tsx:49— WorkflowDetailView.WorkflowDetailView has cyclomatic complexity 36 (threshold 15). Of this number, 22 points are the body's own statements and 14 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentOverviewTab.AgentOverviewTab (cyclomatic 36) apps/smithy-next/src/components/overlays/agents/AgentOverviewTab.tsx:22— AgentOverviewTab.AgentOverviewTab has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 10 of the 36 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 166, 130, 96, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
OnboardingTour.OnboardingTour (cyclomatic 36) apps/smithy-web/src/components/onboarding/OnboardingTour.tsx:545— OnboardingTour.OnboardingTour has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 5 of the 36 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 607, 622, 586, …). 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.
index.MetricsPage (cyclomatic 36) apps/smithy-web/src/routes/metrics/index.tsx:576— index.MetricsPage has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 8 of the 36 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 749, 680, 721, …). 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.
SyncSection.SyncSection (cyclomatic 35) apps/quarry-web/src/routes/settings/components/SyncSection.tsx:17— SyncSection.SyncSection has cyclomatic complexity 35 (threshold 15). Of this number, 23 points are the body's own statements and 12 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ActivityFeedItem.ActivityFeedItem (cyclomatic 35) apps/quarry-web/src/routes/entities/components/ActivityFeedItem.tsx:23— ActivityFeedItem.ActivityFeedItem 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 4 function items inside it that branch (getDescription, getEventIcon, getIconBg, …). 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.
DirectorPanel.CrossWorkspaceThreadsView (cyclomatic 35) apps/smithy-next/src/components/DirectorPanel.tsx:1115— DirectorPanel.CrossWorkspaceThreadsView has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 12 of the 35 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1196, 1237, 1159, …). 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.
MRReviewSidebar.MRReviewSidebar (cyclomatic 35) apps/smithy-next/src/components/overlays/mr/MRReviewSidebar.tsx:31— MRReviewSidebar.MRReviewSidebar has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 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.
CILogViewer.CILogViewer (cyclomatic 35) apps/smithy-next/src/components/overlays/ci/CILogViewer.tsx:10— CILogViewer.CILogViewer has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 5 of the 35 points are its own statements and the rest belongs to 8 function items inside it that branch (getLineColor, a function literal at line 103, a function literal at line 33, …). 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.
SettingsOverlay.OrganizationSection (cyclomatic 35) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:619— SettingsOverlay.OrganizationSection has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 10 of the 35 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 827, commitRename, a function literal at line 791, …). 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.
pools.createPoolRoutes (cyclomatic 35) apps/smithy-server/src/routes/pools.ts:15— pools.createPoolRoutes has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 117, 50, 148, …). 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.
AgentCard.AgentCard (cyclomatic 35) apps/smithy-web/src/components/agent/AgentCard.tsx:34— AgentCard.AgentCard has cyclomatic complexity 35 (threshold 15). Of this number, 32 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dependency.validateAwaitsMetadata (cyclomatic 35) packages/core/src/types/dependency.ts:559— dependency.validateAwaitsMetadata 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.
merge.diffConfigurations (cyclomatic 35) packages/quarry/src/config/merge.ts:225— merge.diffConfigurations has cyclomatic complexity 35 (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.
EditorExplorerPanel.TreeItem (cyclomatic 34) apps/smithy-next/src/components/overlays/editor/EditorExplorerPanel.tsx:250— EditorExplorerPanel.TreeItem has cyclomatic complexity 34 (threshold 15). Of this number, 20 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EditorSearchPanel.EditorSearchPanel (cyclomatic 34) apps/smithy-next/src/components/overlays/editor/EditorSearchPanel.tsx:17— EditorSearchPanel.EditorSearchPanel has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 24, 220, 71, …). 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.
CreateAgentView.CreateAgentView (cyclomatic 34) apps/smithy-next/src/components/overlays/agents/CreateAgentView.tsx:26— CreateAgentView.CreateAgentView has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 10 of the 34 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 93, a function literal at line 155, a function literal at line 131, …). 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.
CreateAgentDialog.CreateAgentDialog (cyclomatic 34) REDACTED:195— CreateAgentDialog.CreateAgentDialog has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (CreateAgentDialog.CreateAgentDialog::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StartAgentDialog.StartAgentDialog (cyclomatic 34) apps/smithy-web/src/components/agent/StartAgentDialog.tsx:43— StartAgentDialog.StartAgentDialog has cyclomatic complexity 34 (threshold 15). Of this number, 20 points are the body's own statements and 14 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.
LibraryTree.LibraryTree (cyclomatic 34) apps/smithy-web/src/routes/documents/components/LibraryTree.tsx:176— LibraryTree.LibraryTree has cyclomatic complexity 34 (threshold 15). Of this number, 19 points are the body's own statements and 15 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.
playbook-yaml.validateYamlPlaybook (cyclomatic 34) packages/core/src/types/playbook-yaml.ts:409— playbook-yaml.validateYamlPlaybook 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.
PlanDetailPanel.PlanDetailPanel (cyclomatic 34) packages/ui/src/plans/components/PlanDetailPanel.tsx:76— PlanDetailPanel.PlanDetailPanel has cyclomatic complexity 34 (threshold 15). Of this number, 17 points are the body's own statements and 17 belong to 9 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.
CreateChannelModal.CreateChannelModal (cyclomatic 34) packages/ui/src/message/CreateChannelModal.tsx:80— CreateChannelModal.CreateChannelModal has cyclomatic complexity 34 (threshold 15). Of this number, 19 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.
KanbanBoard.FilterPanel (cyclomatic 33) apps/smithy-next/src/components/KanbanBoard.tsx:831— KanbanBoard.FilterPanel has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 2 of the 33 points are its own statements and the rest belongs to 13 function items inside it that branch (getCounts, a function literal at line 857, getDisplayName, …). 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.
CIRunDetailView.CIRunDetailView (cyclomatic 33) apps/smithy-next/src/components/overlays/ci/CIRunDetailView.tsx:29— CIRunDetailView.CIRunDetailView has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 12 of the 33 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 112, 45, 47, …). 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.
CronScheduleBuilder.CronScheduleBuilder (cyclomatic 33) apps/smithy-web/src/components/agent/CronScheduleBuilder.tsx:271— CronScheduleBuilder.CronScheduleBuilder has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 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.
Sidebar.Sidebar (cyclomatic 33) apps/smithy-web/src/components/layout/Sidebar.tsx:108— Sidebar.Sidebar has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
playbook.isValidPlaybookStep (cyclomatic 33) packages/core/src/types/playbook.ts:640— playbook.isValidPlaybookStep 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.
parser.parseArgs (cyclomatic 33) packages/quarry/src/cli/parser.ts:92— parser.parseArgs 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.
crud.listHandler (cyclomatic 33) packages/quarry/src/cli/commands/crud.ts:397— crud.listHandler has cyclomatic complexity 33 (threshold 15). Of this number, 27 points are the body's own statements and 6 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.
external-sync.pushHandler (cyclomatic 33) packages/quarry/src/cli/commands/external-sync.ts:960— external-sync.pushHandler has cyclomatic complexity 33 (threshold 15). Of this number, 30 points are the body's own statements and 3 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.
UserSelector.UserSelector (cyclomatic 33) packages/ui/src/domain/UserSelector.tsx:22— UserSelector.UserSelector has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 7 of the 33 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 96, 68, 55, …). 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.
CreateTeamModal.CreateTeamModal (cyclomatic 32) apps/quarry-web/src/components/team/CreateTeamModal.tsx:92— CreateTeamModal.CreateTeamModal has cyclomatic complexity 32 (threshold 15). Of this number, 19 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CommandPalette.CommandPalette (cyclomatic 32) apps/quarry-web/src/components/navigation/CommandPalette.tsx:95— CommandPalette.CommandPalette has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 13 of the 32 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 280, a function literal at line 362, a function literal at line 547, …). 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.
FileContentSearch.FileContentSearch (cyclomatic 32) apps/smithy-web/src/components/command/FileContentSearch.tsx:235— FileContentSearch.FileContentSearch has cyclomatic complexity 32 (threshold 15). Of this number, 26 points are the body's own statements and 6 belong to 4 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.
task.taskMergeHandler (cyclomatic 32) packages/smithy/src/cli/commands/task.ts:386— task.taskMergeHandler has cyclomatic complexity 32 (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.
Pagination.Pagination (cyclomatic 31) apps/quarry-web/src/components/shared/Pagination.tsx:28— Pagination.Pagination has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 15 of the 31 points are its own statements and the rest belongs to 3 function items inside it that branch (getPageNumbers, a function literal at line 139, a function literal at line 240). 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.
InboxComponents.InboxMessageContent (cyclomatic 31) apps/quarry-web/src/routes/entities/components/InboxComponents.tsx:152— InboxComponents.InboxMessageContent has cyclomatic complexity 31 (threshold 15). Of this number, 22 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DirectorTabContent.DirectorTabContent (cyclomatic 31) apps/smithy-web/src/components/layout/DirectorTabContent.tsx:29— DirectorTabContent.DirectorTabContent has cyclomatic complexity 31 (threshold 15). Of this number, 19 points are the body's own statements and 12 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EditPoolDialog.EditPoolDialog (cyclomatic 31) apps/smithy-web/src/components/pool/EditPoolDialog.tsx:75— EditPoolDialog.EditPoolDialog has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 10 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (handleSubmit, a function literal at line 145, a function literal at line 83, …). 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.
CreateWorkflowModal.CreateWorkflowModal (cyclomatic 31) packages/ui/src/workflows/components/CreateWorkflowModal.tsx:228— CreateWorkflowModal.CreateWorkflowModal has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 290, a function literal at line 261, …). 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.
BottomPanel.BottomPanel (cyclomatic 30) apps/smithy-next/src/components/BottomPanel.tsx:21— BottomPanel.BottomPanel 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 12 function items inside it that branch (a function literal at line 143, a function literal at line 69, consoleColorForLevel, …). 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.
MRChecksTab.JobRow (cyclomatic 30) apps/smithy-next/src/components/overlays/mr/MRChecksTab.tsx:98— MRChecksTab.JobRow has cyclomatic complexity 30 (threshold 15). Of this number, 18 points are the body's own statements and 12 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkflowStepCard.WorkflowStepCard (cyclomatic 30) apps/smithy-next/src/components/overlays/automations/WorkflowStepCard.tsx:20— WorkflowStepCard.WorkflowStepCard has cyclomatic complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentSettingsTab.AgentSettingsTab (cyclomatic 30) apps/smithy-next/src/components/overlays/agents/AgentSettingsTab.tsx:28— AgentSettingsTab.AgentSettingsTab has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 69, 149, 61, …). 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.
terminal.PopoutTerminalPage (cyclomatic 30) apps/smithy-web/src/routes/popout/terminal.tsx:32— terminal.PopoutTerminalPage has cyclomatic complexity 30 (threshold 15). Of this number, 23 points are the body's own statements and 7 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.
StatusPieChart.StatusPieChart (cyclomatic 30) packages/ui/src/visualizations/StatusPieChart.tsx:68— StatusPieChart.StatusPieChart has cyclomatic complexity 30 (threshold 15). Of this number, 18 points are the body's own statements and 12 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
utils.generateChangesPreview (cyclomatic 29) apps/quarry-web/src/routes/timeline/utils.ts:67— utils.generateChangesPreview has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MRListView.MRFilterPanel (cyclomatic 29) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:246— MRListView.MRFilterPanel 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 18 function items inside it that branch (getItems, a function literal at line 305, a function literal at line 253, …). 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.
CreateActionDialog.parseYaml (cyclomatic 29) apps/smithy-next/src/components/overlays/ci/CreateActionDialog.tsx:65— CreateActionDialog.parseYaml has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
task-utils.taskSortCompareFn (cyclomatic 29) apps/smithy-web/src/lib/task-utils.tsx:126— task-utils.taskSortCompareFn has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QuickFileOpen.QuickFileOpen (cyclomatic 29) apps/smithy-web/src/components/command/QuickFileOpen.tsx:128— QuickFileOpen.QuickFileOpen has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EditorSearchPanel.EditorSearchPanel (cyclomatic 29) apps/smithy-web/src/components/editor/EditorSearchPanel.tsx:227— EditorSearchPanel.EditorSearchPanel has cyclomatic complexity 29 (threshold 15). Of this number, 26 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
NotificationSidebar.NotificationSidebar (cyclomatic 29) apps/smithy-web/src/components/notification/NotificationSidebar.tsx:209— NotificationSidebar.NotificationSidebar has cyclomatic complexity 29 (threshold 15). Of this number, 25 points are the body's own statements and 4 belong to 4 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.
index.MergeRequestsPage (cyclomatic 29) apps/smithy-web/src/routes/merge-requests/index.tsx:35— index.MergeRequestsPage has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 90, 78, 73, …). 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.
QuarryAPIImpl.listPaginated (cyclomatic 29) packages/quarry/src/api/quarry-api.ts:711— QuarryAPIImpl.listPaginated has cyclomatic complexity 29 (threshold 15). Of this number, 26 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
merge.mergeConfiguration (cyclomatic 29) packages/quarry/src/config/merge.ts:72— merge.mergeConfiguration has cyclomatic complexity 29 (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.
config.mergeTrackedConfig (cyclomatic 29) packages/quarry/src/config/config.ts:366— config.mergeTrackedConfig has cyclomatic complexity 29 (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.
serve.startSmithy (cyclomatic 29) REDACTED:381— serve.startSmithy has cyclomatic complexity 29 (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.
pool.poolUpdateHandler (cyclomatic 29) packages/smithy/src/cli/commands/pool.ts:550— pool.poolUpdateHandler has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ResponsiveModal.ResponsiveModal (cyclomatic 29) packages/ui/src/layout/ResponsiveModal.tsx:47— ResponsiveModal.ResponsiveModal has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 10 function items inside it that branch (handleTouchMove, handleTouchEnd, a function literal at line 90, …). 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.
CreateActionDialog.CreateActionDialog (cyclomatic 28) apps/smithy-next/src/components/overlays/ci/CreateActionDialog.tsx:132— CreateActionDialog.CreateActionDialog has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 279, handleSubmit, addTrigger, …). 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.
SessionDetailHeader.SessionDetailHeader (cyclomatic 28) apps/smithy-next/src/components/overlays/sessions/SessionDetailHeader.tsx:51— SessionDetailHeader.SessionDetailHeader has cyclomatic complexity 28 (threshold 15). Of this number, 18 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CIJobPanel.JobRow (cyclomatic 28) apps/smithy-next/src/components/overlays/ci/CIJobPanel.tsx:44— CIJobPanel.JobRow has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 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.
MergeRequestActions.MergeRequestActions (cyclomatic 28) apps/smithy-web/src/components/merge-request/MergeRequestActions.tsx:42— MergeRequestActions.MergeRequestActions has cyclomatic complexity 28 (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.
CreatePoolDialog.CreatePoolDialog (cyclomatic 28) apps/smithy-web/src/components/pool/CreatePoolDialog.tsx:49— CreatePoolDialog.CreatePoolDialog has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSubmit, a function literal at line 114, a function literal at line 77). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SessionHistoryModal.SessionHistoryModal (cyclomatic 28) apps/smithy-web/src/components/workspace/SessionHistoryModal.tsx:335— SessionHistoryModal.SessionHistoryModal has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 395, a function literal at line 358, a function literal at line 420, …). 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.
log.logHandler (cyclomatic 28) packages/quarry/src/cli/commands/log.ts:163— log.logHandler has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DispatchDaemonImpl.assignTaskToWorker (cyclomatic 28) packages/smithy/src/services/dispatch-daemon.ts:2711— DispatchDaemonImpl.assignTaskToWorker has cyclomatic complexity 28 (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.
ShortcutsSection.ShortcutEditModal (cyclomatic 28) packages/ui/src/settings/shortcuts/ShortcutsSection.tsx:33— ShortcutsSection.ShortcutEditModal has cyclomatic complexity 28 (threshold 15). Of this number, 15 points are the body's own statements and 13 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WorkflowEditorModal.generateYaml (cyclomatic 28) packages/ui/src/workflows/components/WorkflowEditorModal.tsx:205— WorkflowEditorModal.generateYaml has cyclomatic complexity 28 (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.
KanbanBoard.KanbanBoard (cyclomatic 27) apps/quarry-web/src/components/task/KanbanBoard.tsx:844— KanbanBoard.KanbanBoard 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 8 function items inside it that branch (handleDragEnd, a function literal at line 884, a function literal at line 852, …). 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.
PreviewConfigDialog.PreviewConfigDialog (cyclomatic 27) apps/smithy-next/src/components/overlays/PreviewConfigDialog.tsx:11— PreviewConfigDialog.PreviewConfigDialog has cyclomatic complexity 27 (threshold 15). Of this number, 16 points are the body's own statements and 11 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.
SettingsOverlay.IntegrationSyncGroup (cyclomatic 27) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1718— SettingsOverlay.IntegrationSyncGroup has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1752, 1779, 1780). 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.
ExtensionCard.ExtensionCard (cyclomatic 27) apps/smithy-web/src/components/editor/ExtensionCard.tsx:59— ExtensionCard.ExtensionCard has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 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.
MergeRequestDetailPanel.MergeRequestDetailPanel (cyclomatic 27) apps/smithy-web/src/components/merge-request/MergeRequestDetailPanel.tsx:42— MergeRequestDetailPanel.MergeRequestDetailPanel has cyclomatic complexity 27 (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.
index.PlansPage (cyclomatic 27) apps/smithy-web/src/routes/plans/index.tsx:42— index.PlansPage has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to 5 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.
workflow.isWorkflow (cyclomatic 27) packages/core/src/types/workflow.ts:357— workflow.isWorkflow has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
crud.showHandler (cyclomatic 27) packages/quarry/src/cli/commands/crud.ts:585— crud.showHandler has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
task.describeHandler (cyclomatic 27) packages/quarry/src/cli/commands/task.ts:1016— task.describeHandler 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.
document.docUpdateHandler (cyclomatic 27) packages/quarry/src/cli/commands/document.ts:624— document.docUpdateHandler has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
task.taskSyncHandler (cyclomatic 27) packages/smithy/src/cli/commands/task.ts:746— task.taskSyncHandler 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.
server.startNodeServer (cyclomatic 27) REDACTED:146— server.startNodeServer 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 8 function literals inside it that branch (lines 154, 293, 258, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DemoModeSection.DemoModeSection (cyclomatic 26) apps/quarry-web/src/routes/settings/components/DemoModeSection.tsx:31— DemoModeSection.DemoModeSection has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.EntitiesPage (cyclomatic 26) apps/quarry-web/src/routes/entities/index.tsx:27— index.EntitiesPage has cyclomatic complexity 26 (threshold 15). Of this number, 19 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RichTextEditor.RichTextEditor (cyclomatic 26) apps/smithy-next/src/components/overlays/mr/RichTextEditor.tsx:13— RichTextEditor.RichTextEditor has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 51, a function literal at line 145, insertMarkdown, …). 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.
CIRunHeader.CIRunHeader (cyclomatic 26) apps/smithy-next/src/components/overlays/ci/CIRunHeader.tsx:31— CIRunHeader.CIRunHeader has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkflowPipelineViz.WorkflowPipelineViz (cyclomatic 26) apps/smithy-next/src/components/overlays/automations/WorkflowPipelineViz.tsx:15— WorkflowPipelineViz.WorkflowPipelineViz has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 97, a function literal at line 129, getDepth, …). 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.
WorkflowStepCard.AgentStepContent (cyclomatic 26) apps/smithy-next/src/components/overlays/automations/WorkflowStepCard.tsx:174— WorkflowStepCard.AgentStepContent has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentDetailView.AgentDetailView (cyclomatic 26) apps/smithy-next/src/components/overlays/agents/AgentDetailView.tsx:39— AgentDetailView.AgentDetailView has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 4 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.
CreateTaskDialog.CreateTaskDialog (cyclomatic 26) apps/smithy-next/src/components/CreateTaskDialog.tsx:15— CreateTaskDialog.CreateTaskDialog has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 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.
language-detection.detectLanguageFromContentType (cyclomatic 26) apps/smithy-web/src/lib/language-detection.ts:345— language-detection.detectLanguageFromContentType has cyclomatic complexity 26 (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.
event.isValidEventFilter (cyclomatic 26) packages/core/src/types/event.ts:411— event.isValidEventFilter has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
playbook.isPlaybook (cyclomatic 26) packages/core/src/types/playbook.ts:1251— playbook.isPlaybook has cyclomatic complexity 26 (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.
formatter.formatChanges (cyclomatic 26) packages/quarry/src/cli/formatter.ts:540— formatter.formatChanges 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.
dep.depListHandler (cyclomatic 26) packages/quarry/src/cli/commands/dep.ts:325— dep.depListHandler has cyclomatic complexity 26 (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.
playbook.playbookCreateHandler (cyclomatic 26) packages/quarry/src/cli/commands/playbook.ts:696— playbook.playbookCreateHandler 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.
MobileDocumentFilter.MobileDocumentFilter (cyclomatic 26) packages/ui/src/documents/components/MobileDocumentFilter.tsx:20— MobileDocumentFilter.MobileDocumentFilter has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 13 function items inside it that branch (handleTouchMove, handleTouchEnd, 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.
TaskCard.TaskCard (cyclomatic 26) packages/ui/src/domain/TaskCard.tsx:62— TaskCard.TaskCard has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 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.
WorkflowDetailPanel.WorkflowDetailPanel (cyclomatic 26) packages/ui/src/workflows/components/WorkflowDetailPanel.tsx:76— WorkflowDetailPanel.WorkflowDetailPanel has cyclomatic complexity 26 (threshold 15). Of this number, 14 points are the body's own statements and 12 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BlockEditor.BlockEditor (cyclomatic 25) apps/quarry-web/src/components/editor/BlockEditor.tsx:161— BlockEditor.BlockEditor has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 267, 279, 350, …). 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.
task-utils.taskSortCompareFn (cyclomatic 25) apps/quarry-web/src/lib/task-utils.tsx:125— task-utils.taskSortCompareFn 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.
PlanDetailPanel.PlanDetailPanel (cyclomatic 25) apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx:64— PlanDetailPanel.PlanDetailPanel has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NotificationInbox.NotificationInbox (cyclomatic 25) apps/smithy-next/src/components/NotificationInbox.tsx:40— NotificationInbox.NotificationInbox has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WorkflowRunDetail.WorkflowRunDetail (cyclomatic 25) apps/smithy-next/src/components/overlays/automations/WorkflowRunDetail.tsx:33— WorkflowRunDetail.WorkflowRunDetail has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
CreateDocumentDialog.CreateDocumentDialog (cyclomatic 25) apps/smithy-next/src/components/overlays/documents/CreateDocumentDialog.tsx:34— CreateDocumentDialog.CreateDocumentDialog has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (handleTagKeyDown, handleCreate, a function literal at line 169, …). 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.
CommandPalette.CommandPalette (cyclomatic 25) apps/smithy-next/src/components/CommandPalette.tsx:39— CommandPalette.CommandPalette has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 234, 114, 76, …). 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.
WorkspacesOverlay.WorkspaceCard (cyclomatic 25) apps/smithy-next/src/components/overlays/WorkspacesOverlay.tsx:437— WorkspacesOverlay.WorkspaceCard has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoolCard.PoolCard (cyclomatic 25) apps/smithy-web/src/components/pool/PoolCard.tsx:16— PoolCard.PoolCard has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 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.
event.applyEventToState (cyclomatic 25) packages/core/src/types/event.ts:835— event.applyEventToState 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.
notion-blocks.markdownToNotionBlocks (cyclomatic 25) packages/quarry/src/external-sync/providers/notion/notion-blocks.ts:207— notion-blocks.markdownToNotionBlocks 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.
merge.mergeHandler (cyclomatic 25) packages/smithy/src/cli/commands/merge.ts:78— merge.mergeHandler 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.
MergeStewardServiceImpl.processTask (cyclomatic 25) packages/smithy/src/services/merge-steward-service.ts:439— MergeStewardServiceImpl.processTask 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.
task.taskMergeStatusHandler (cyclomatic 25) packages/smithy/src/cli/commands/task.ts:1102— task.taskMergeStatusHandler 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.
settings.createSettingsRoutes (cyclomatic 25) packages/smithy/src/server/routes/settings.ts:23— settings.createSettingsRoutes has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 39, 194, 111, …). 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.
CreateTaskModal.CreateTaskModal (cyclomatic 24) apps/quarry-web/src/components/task/CreateTaskModal.tsx:102— CreateTaskModal.CreateTaskModal has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 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.
Tooltip.Tooltip (cyclomatic 24) apps/smithy-next/src/components/Tooltip.tsx:15— Tooltip.Tooltip has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 22, 79). 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.
IntegrationsStep.InstallFlowBlock (cyclomatic 24) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:285— IntegrationsStep.InstallFlowBlock has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
App.App::renderMainContent (cyclomatic 24) apps/smithy-next/src/App.tsx:864— App.App::renderMainContent has cyclomatic complexity 24 (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 shape REPEATS in the file: one other method here (App.App) 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.
server.startNodeServer (cyclomatic 24) REDACTED:111— server.startNodeServer has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 115, 253, 218, …). 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.
useActiveAgentOutputs.useActiveAgentOutputs (cyclomatic 24) apps/smithy-web/src/api/hooks/useActiveAgentOutputs.ts:106— useActiveAgentOutputs.useActiveAgentOutputs has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 150, 113, 140). 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.
KanbanBoard.FilterSortDropdown (cyclomatic 24) apps/smithy-web/src/components/task/KanbanBoard.tsx:398— KanbanBoard.FilterSortDropdown has cyclomatic complexity 24 (threshold 15). Of this number, 18 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MergeRequestManageDropdown.MergeRequestManageDropdown (cyclomatic 24) apps/smithy-web/src/components/merge-request/MergeRequestManageDropdown.tsx:37— MergeRequestManageDropdown.MergeRequestManageDropdown has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 8 function items inside it that branch (getStatusIcon, a function literal at line 54, a function literal at line 199, …). 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.
generator.generateId (cyclomatic 24) packages/core/src/id/generator.ts:626— generator.generateId 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.
SpawnerServiceImpl.processProviderMessages (cyclomatic 24) packages/smithy/src/runtime/spawner.ts:966— SpawnerServiceImpl.processProviderMessages 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.
pool.parseAgentTypeConfig (cyclomatic 24) packages/smithy/src/cli/commands/pool.ts:75— pool.parseAgentTypeConfig 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.
KanbanBoard.FilterSortDropdown (cyclomatic 23) apps/quarry-web/src/components/task/KanbanBoard.tsx:398— KanbanBoard.FilterSortDropdown has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
KanbanBoard.VirtualizedKanbanColumn (cyclomatic 23) apps/quarry-web/src/components/task/KanbanBoard.tsx:654— KanbanBoard.VirtualizedKanbanColumn has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 701, 714, 725, …). 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.
TaskDetailPanel.AssigneeDropdown (cyclomatic 23) apps/quarry-web/src/components/task/TaskDetailPanel.tsx:1758— TaskDetailPanel.AssigneeDropdown has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1774, 1784, 1791, …). 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.
CreateMRDialog.CreateMRDialog (cyclomatic 23) apps/smithy-next/src/components/overlays/mr/CreateMRDialog.tsx:21— CreateMRDialog.CreateMRDialog has cyclomatic complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MRConversationTab.ActionRow (cyclomatic 23) apps/smithy-next/src/components/overlays/mr/MRConversationTab.tsx:231— MRConversationTab.ActionRow has cyclomatic complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RuntimeDetailView.ViewMode (cyclomatic 23) apps/smithy-next/src/components/overlays/agents/RuntimeDetailView.tsx:87— RuntimeDetailView.ViewMode has cyclomatic complexity 23 (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.
SettingsOverlay.SettingsOverlay (cyclomatic 23) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:74— SettingsOverlay.SettingsOverlay has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (renderContent, a function literal at line 128, a function literal at line 154, …). 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.
ActivityCard.ActivityCard (cyclomatic 23) apps/smithy-web/src/components/activity/ActivityCard.tsx:64— ActivityCard.ActivityCard has cyclomatic complexity 23 (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.
AgentNode.AgentNodeComponent (cyclomatic 23) apps/smithy-web/src/components/agent-graph/AgentNode.tsx:79— AgentNode.AgentNodeComponent has cyclomatic complexity 23 (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.
manager.installExtension (cyclomatic 23) apps/smithy-web/src/lib/extensions/manager.ts:146— manager.installExtension 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.
TaskDetailPanel.EditableDescription (cyclomatic 23) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1348— TaskDetailPanel.EditableDescription has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 1375, handleKeyDown, a function literal at line 1384, …). 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.
index.WorkspacesPage (cyclomatic 23) apps/smithy-web/src/routes/workspaces/index.tsx:40— index.WorkspacesPage has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
document.isDocument (cyclomatic 23) packages/core/src/types/document.ts:388— document.isDocument has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
event.validateEventFilter (cyclomatic 23) packages/core/src/types/event.ts:463— event.validateEventFilter has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
external-sync.pullHandler (cyclomatic 23) packages/quarry/src/cli/commands/external-sync.ts:1160— external-sync.pullHandler has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
channel.channelCreateHandler (cyclomatic 23) packages/quarry/src/cli/commands/channel.ts:97— channel.channelCreateHandler 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.
document.docCreateHandler (cyclomatic 23) packages/quarry/src/cli/commands/document.ts:89— document.docCreateHandler has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SpawnerServiceImpl.parseAndEmitEvent (cyclomatic 23) packages/smithy/src/runtime/spawner.ts:1231— SpawnerServiceImpl.parseAndEmitEvent 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.
DispatchDaemonImpl.spawnRecoveryStewardForTask (cyclomatic 23) packages/smithy/src/services/dispatch-daemon.ts:3393— DispatchDaemonImpl.spawnRecoveryStewardForTask 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.
ChannelMembersPanel.ChannelMembersPanel (cyclomatic 23) packages/ui/src/message/ChannelMembersPanel.tsx:403— ChannelMembersPanel.ChannelMembersPanel has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, 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.
useGlobalQuickActions.GlobalQuickActionsProvider (cyclomatic 22) apps/quarry-web/src/hooks/useGlobalQuickActions.tsx:57— useGlobalQuickActions.GlobalQuickActionsProvider has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 176, 177, 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.
ThemeSection.ThemeSection (cyclomatic 22) apps/quarry-web/src/routes/settings/components/ThemeSection.tsx:73— ThemeSection.ThemeSection has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.TeamsPage (cyclomatic 22) apps/quarry-web/src/routes/teams/index.tsx:27— index.TeamsPage has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 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.
SessionEventList.SessionEventList (cyclomatic 22) apps/smithy-next/src/components/overlays/sessions/SessionEventList.tsx:40— SessionEventList.SessionEventList 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 5 function literals inside it that branch (lines 57, 45, 65, …). 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.
CanvasLayoutPicker.CanvasLayoutPicker (cyclomatic 22) apps/smithy-next/src/components/overlays/sessions/canvas/CanvasLayoutPicker.tsx:19— CanvasLayoutPicker.CanvasLayoutPicker has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentsOverlay.AgentsOverlay::renderView (cyclomatic 22) apps/smithy-next/src/components/overlays/AgentsOverlay.tsx:204— AgentsOverlay.AgentsOverlay::renderView has cyclomatic complexity 22 (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.
EditorFileTree.getIconColor (cyclomatic 22) apps/smithy-web/src/components/editor/EditorFileTree.tsx:187— EditorFileTree.getIconColor has cyclomatic complexity 22 (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.
LightweightLspClient.registerProviders (cyclomatic 22) apps/smithy-web/src/lib/monaco-lsp/lightweight-client.ts:172— LightweightLspClient.registerProviders has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 277, 220, 231, …). 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. This is NOT this file's highest cyclomatic complexity: lightweight-client.toMonacoCompletionItemKind (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
use-lsp.useLsp (cyclomatic 22) apps/smithy-web/src/lib/monaco-lsp/use-lsp.ts:62— use-lsp.useLsp 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 5 function literals inside it that branch (lines 188, 158, 204, …). 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.
TaskCard.TaskCard (cyclomatic 22) apps/smithy-web/src/components/task/TaskCard.tsx:22— TaskCard.TaskCard has cyclomatic complexity 22 (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.
TaskDetailPanel.AssigneeDropdown (cyclomatic 22) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:816— TaskDetailPanel.AssigneeDropdown has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 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.
CreateTaskModal.CreateTaskModal (cyclomatic 22) apps/smithy-web/src/components/task/CreateTaskModal.tsx:48— CreateTaskModal.CreateTaskModal has cyclomatic complexity 22 (threshold 15). Of this number, 12 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.
WorkspaceGrid.CustomResizeHandle (cyclomatic 22) apps/smithy-web/src/components/workspace/WorkspaceGrid.tsx:52— WorkspaceGrid.CustomResizeHandle has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 103, 77, 129, …). 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.
task.taskListHandler (cyclomatic 22) packages/quarry/src/cli/commands/task.ts:1306— task.taskListHandler has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
external-sync.statusHandler (cyclomatic 22) packages/quarry/src/cli/commands/external-sync.ts:1461— external-sync.statusHandler 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.
gc.gcWorkflowsHandler (cyclomatic 22) packages/quarry/src/cli/commands/gc.ts:158— gc.gcWorkflowsHandler has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 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.
playbook.playbookShowHandler (cyclomatic 22) packages/quarry/src/cli/commands/playbook.ts:153— playbook.playbookShowHandler has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 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.
inbox.inboxListHandler (cyclomatic 22) packages/quarry/src/cli/commands/inbox.ts:118— inbox.inboxListHandler has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tasks.createTaskRoutes (cyclomatic 22) packages/shared-routes/src/tasks.ts:12— tasks.createTaskRoutes 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 2 function literals inside it that branch (lines 27, 100). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
agent.agentStartHandler (cyclomatic 22) packages/smithy/src/cli/commands/agent.ts:886— agent.agentStartHandler has cyclomatic complexity 22 (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.
WorktreeManagerImpl.createWorktree (cyclomatic 22) REDACTED:426— WorktreeManagerImpl.createWorktree has cyclomatic complexity 22 (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.
CreatePlanModal.CreatePlanModal (cyclomatic 22) packages/ui/src/plans/components/CreatePlanModal.tsx:39— CreatePlanModal.CreatePlanModal has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 81, handleSubmit, a function literal at line 58, …). 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.
CreateEntityModal.CreateEntityModal (cyclomatic 21) apps/quarry-web/src/components/entity/CreateEntityModal.tsx:68— CreateEntityModal.CreateEntityModal has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 199, a function literal at line 82, …). 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.
MRHeader.MRHeader (cyclomatic 21) apps/smithy-next/src/components/overlays/mr/MRHeader.tsx:19— MRHeader.MRHeader has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MRMergeFlow.MRMergeFlow (cyclomatic 21) apps/smithy-next/src/components/overlays/mr/MRMergeFlow.tsx:15— MRMergeFlow.MRMergeFlow has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 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.
EditorFuzzyFinder.EditorFuzzyFinder (cyclomatic 21) apps/smithy-next/src/components/overlays/editor/EditorFuzzyFinder.tsx:24— EditorFuzzyFinder.EditorFuzzyFinder has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, a function literal at line 37, a function literal at line 140, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
onboarding-types.onboardingReducer (cyclomatic 21) apps/smithy-next/src/components/onboarding/onboarding-types.ts:162— onboarding-types.onboardingReducer 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.
App.App (cyclomatic 21) apps/smithy-next/src/App.tsx:371— App.App has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (App.App::renderMainContent) 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.
vsix-parser.getContributedFilePaths (cyclomatic 21) apps/smithy-web/src/lib/openvsx/vsix-parser.ts:324— vsix-parser.getContributedFilePaths 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.
plan.isPlan (cyclomatic 21) packages/core/src/types/plan.ts:261— plan.isPlan 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.
types.isValidElementFilter (cyclomatic 21) packages/quarry/src/api/types.ts:1602— types.isValidElementFilter 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.
utils-vendor-CfYKiENT.sa (cyclomatic 21) REDACTED:811— utils-vendor-CfYKiENT.sa has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: utils-vendor-CfYKiENT._n (cyclomatic 23) 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.
HorizontalBarChart.HorizontalBarChart (cyclomatic 21) packages/ui/src/visualizations/HorizontalBarChart.tsx:54— HorizontalBarChart.HorizontalBarChart has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 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.
DashboardCharts.TasksByStatusChart (cyclomatic 20) apps/quarry-web/src/components/dashboard/DashboardCharts.tsx:243— DashboardCharts.TasksByStatusChart has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PlanListView.DisplayPanel (cyclomatic 20) apps/smithy-next/src/components/overlays/plans/PlanListView.tsx:420— PlanListView.DisplayPanel has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 454, 487, 462, …). 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.
CIManualTriggerDialog.CIManualTriggerDialog (cyclomatic 20) apps/smithy-next/src/components/overlays/ci/CIManualTriggerDialog.tsx:11— CIManualTriggerDialog.CIManualTriggerDialog has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CIRunListView.RunRow (cyclomatic 20) apps/smithy-next/src/components/overlays/ci/CIRunListView.tsx:384— CIRunListView.RunRow has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkflowListView.WorkflowRow (cyclomatic 20) apps/smithy-next/src/components/overlays/automations/WorkflowListView.tsx:303— WorkflowListView.WorkflowRow has cyclomatic complexity 20 (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.
WorkflowRunPage.StepDetail (cyclomatic 20) apps/smithy-next/src/components/overlays/automations/WorkflowRunPage.tsx:346— WorkflowRunPage.StepDetail has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SessionFilterPanel.SessionFilterPanel (cyclomatic 20) apps/smithy-next/src/components/overlays/sessions/SessionFilterPanel.tsx:23— SessionFilterPanel.SessionFilterPanel has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 95, 28, 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.
SessionListView.SessionDisplayPanel (cyclomatic 20) apps/smithy-next/src/components/overlays/sessions/SessionListView.tsx:493— SessionListView.SessionDisplayPanel 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 531, 564, 594, …). 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.
DocEditorView.renderMarkdown (cyclomatic 20) apps/smithy-next/src/components/overlays/documents/DocEditorView.tsx:44— DocEditorView.renderMarkdown 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.
IntegrationsStep.SyncOptionRow (cyclomatic 20) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:129— IntegrationsStep.SyncOptionRow has cyclomatic complexity 20 (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.
TaskRow.TaskRow (cyclomatic 20) apps/smithy-web/src/components/task/TaskRow.tsx:31— TaskRow.TaskRow 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.
MergeRequestCard.MergeRequestCard (cyclomatic 20) apps/smithy-web/src/components/merge-request/MergeRequestCard.tsx:26— MergeRequestCard.MergeRequestCard 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.
external-sync.linkHandler (cyclomatic 20) packages/quarry/src/cli/commands/external-sync.ts:530— external-sync.linkHandler 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.
history.historyHandler (cyclomatic 20) packages/quarry/src/cli/commands/history.ts:66— history.historyHandler has cyclomatic complexity 20 (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.
plan.planAutoCompleteHandler (cyclomatic 20) packages/quarry/src/cli/commands/plan.ts:859— plan.planAutoCompleteHandler 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.
settings-service.createSettingsService.getExternalSyncSettings (cyclomatic 20) packages/smithy/src/services/settings-service.ts:260— settings-service.createSettingsService.getExternalSyncSettings 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.
DocsStewardServiceImpl.verifyFilePaths (cyclomatic 20) REDACTED:277— DocsStewardServiceImpl.verifyFilePaths 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.
DispatchDaemonImpl.runPollCycle (cyclomatic 20) packages/smithy/src/services/dispatch-daemon.ts:2036— DispatchDaemonImpl.runPollCycle 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.
external-sync.createExternalSyncRoutes (cyclomatic 20) packages/smithy/src/server/routes/external-sync.ts:24— external-sync.createExternalSyncRoutes has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 145, 57, 112, …). 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.startBunServer (cyclomatic 20) REDACTED:44— server.startBunServer has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Sidebar.Sidebar (cyclomatic 20) packages/ui/src/layout/Sidebar.tsx:120— Sidebar.Sidebar 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. This shape REPEATS in the file: one other method here (Sidebar.Sidebar::renderNavItem) 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.
TrendLineChart.TrendLineChart (cyclomatic 20) packages/ui/src/visualizations/TrendLineChart.tsx:44— TrendLineChart.TrendLineChart has cyclomatic complexity 20 (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.
HashAutocomplete.HashAutocompleteMenu (cyclomatic 20) packages/ui/src/message/HashAutocomplete.tsx:55— HashAutocomplete.HashAutocompleteMenu has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 75, 146, 189, …). 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.
DashboardCharts.WorkloadByAgentChart (cyclomatic 19) apps/quarry-web/src/components/dashboard/DashboardCharts.tsx:444— DashboardCharts.WorkloadByAgentChart has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 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.
index.DependencyGraphPage (cyclomatic 19) apps/quarry-web/src/routes/dependency-graph/index.tsx:35— index.DependencyGraphPage 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 6 function literals inside it that branch (lines 103, 92, 128, …). 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.
EditorToolbar.EditorToolbar (cyclomatic 19) apps/smithy-next/src/components/overlays/editor/EditorToolbar.tsx:26— EditorToolbar.EditorToolbar has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
WorkflowRunTimeline.WorkflowRunTimeline (cyclomatic 19) apps/smithy-next/src/components/overlays/automations/WorkflowRunTimeline.tsx:33— WorkflowRunTimeline.WorkflowRunTimeline has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 119, 70, 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.
SessionChatView.SessionChatView (cyclomatic 19) apps/smithy-next/src/components/overlays/sessions/SessionChatView.tsx:24— SessionChatView.SessionChatView has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 64, 38, 30, …). 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.
MessageBubble.MessageBubble (cyclomatic 19) REDACTED:41— MessageBubble.MessageBubble 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.
MetricsQualityTab.MetricsQualityTab (cyclomatic 19) apps/smithy-next/src/components/overlays/metrics/MetricsQualityTab.tsx:22— MetricsQualityTab.MetricsQualityTab 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 5 function literals inside it that branch (lines 153, 103, 49, …). 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.
IntegrationsStep.MiniDropdown (cyclomatic 19) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:479— IntegrationsStep.MiniDropdown has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ChangeTriggerDialog.ChangeTriggerDialog (cyclomatic 19) apps/smithy-web/src/components/agent/ChangeTriggerDialog.tsx:22— ChangeTriggerDialog.ChangeTriggerDialog has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 34, a function literal at line 57, …). 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.
OnboardingTour.TourTooltip (cyclomatic 19) apps/smithy-web/src/components/onboarding/OnboardingTour.tsx:362— OnboardingTour.TourTooltip has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TaskDetailPanel.DeadlineInput (cyclomatic 19) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1073— TaskDetailPanel.DeadlineInput has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSave, handleKeyDown, a function literal at line 1086, …). 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.
KanbanBoard.VirtualizedKanbanColumn (cyclomatic 19) apps/smithy-web/src/components/task/KanbanBoard.tsx:644— KanbanBoard.VirtualizedKanbanColumn has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 686, 698, 708, …). 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.
Pagination.Pagination (cyclomatic 19) apps/smithy-web/src/components/shared/Pagination.tsx:27— Pagination.Pagination has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StreamViewer.StreamEventCard (cyclomatic 19) apps/smithy-web/src/components/workspace/StreamViewer.tsx:97— StreamViewer.StreamEventCard has cyclomatic complexity 19 (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.
document.validateDocument (cyclomatic 19) packages/core/src/types/document.ts:429— document.validateDocument 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.
event.generateEventSummary (cyclomatic 19) packages/core/src/types/event.ts:944— event.generateEventSummary 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.
BlockedCacheService.invalidateElement (cyclomatic 19) packages/quarry/src/services/blocked-cache.ts:491— BlockedCacheService.invalidateElement 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.
QuarryAPIImpl.getOrderedTasksInWorkflow (cyclomatic 19) packages/quarry/src/api/quarry-api.ts:4285— QuarryAPIImpl.getOrderedTasksInWorkflow 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.
LinearApiClient.graphql (cyclomatic 19) packages/quarry/src/external-sync/providers/linear/linear-api.ts:273— LinearApiClient.graphql 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.
SyncEngine.pullItem (cyclomatic 19) packages/quarry/src/external-sync/sync-engine.ts:745— SyncEngine.pullItem 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.
external-sync.syncHandler (cyclomatic 19) packages/quarry/src/cli/commands/external-sync.ts:1333— external-sync.syncHandler 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.
identity.verifyHandler (cyclomatic 19) packages/quarry/src/cli/commands/identity.ts:496— identity.verifyHandler 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.
workflow.workflowListHandler (cyclomatic 19) packages/quarry/src/cli/commands/workflow.ts:193— workflow.workflowListHandler has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 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.
workflow.workflowShowHandler (cyclomatic 19) packages/quarry/src/cli/commands/workflow.ts:304— workflow.workflowShowHandler 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.
docs.docsAddHandler (cyclomatic 19) packages/quarry/src/cli/commands/docs.ts:248— docs.docsAddHandler 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.
message.msgListHandler (cyclomatic 19) packages/quarry/src/cli/commands/message.ts:506— message.msgListHandler has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 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.
task-meta.isOrchestratorTaskMeta (cyclomatic 19) packages/smithy/src/types/task-meta.ts:346— task-meta.isOrchestratorTaskMeta has cyclomatic complexity 19 (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.
SessionManagerImpl.listSessions (cyclomatic 19) packages/smithy/src/runtime/session-manager.ts:895— SessionManagerImpl.listSessions has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SessionManagerImpl.setupSessionEventForwarding (cyclomatic 19) packages/smithy/src/runtime/session-manager.ts:1415— SessionManagerImpl.setupSessionEventForwarding 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 8 function items inside it that branch (onExit, onProviderSessionId, onEvent, …). 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.
agent.agentListHandler (cyclomatic 19) packages/smithy/src/cli/commands/agent.ts:175— agent.agentListHandler has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StewardSchedulerImpl.parseCronField (cyclomatic 19) REDACTED:1033— StewardSchedulerImpl.parseCronField 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.
DispatchDaemonImpl.pollInboxes (cyclomatic 19) packages/smithy/src/services/dispatch-daemon.ts:938— DispatchDaemonImpl.pollInboxes 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.
DispatchDaemonImpl.pollWorkflowTasks (cyclomatic 19) packages/smithy/src/services/dispatch-daemon.ts:1076— DispatchDaemonImpl.pollWorkflowTasks has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous)::onKeyDown (cyclomatic 19) REDACTED:811— (anonymous)::onKeyDown 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: _n (cyclomatic 23) 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.
EmojiAutocomplete.fuzzySearchEmoji (cyclomatic 18) apps/quarry-web/src/components/editor/EmojiAutocomplete.tsx:642— EmojiAutocomplete.fuzzySearchEmoji has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TopBar.TopBar (cyclomatic 18) apps/smithy-next/src/components/TopBar.tsx:49— TopBar.TopBar has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.
TaskDetailOverlay.getActivity (cyclomatic 18) apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:928— TaskDetailOverlay.getActivity 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.
MetricsOverlay.EventLogTab (cyclomatic 18) apps/smithy-next/src/components/overlays/MetricsOverlay.tsx:168— MetricsOverlay.EventLogTab has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 174, 229, 185, …). 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.
DocListView.FilterPanel (cyclomatic 18) apps/smithy-next/src/components/overlays/documents/DocListView.tsx:190— DocListView.FilterPanel has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 242, 202, 225, …). 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.
DocumentsOverlay.DocumentsOverlay (cyclomatic 18) apps/smithy-next/src/components/overlays/DocumentsOverlay.tsx:18— DocumentsOverlay.DocumentsOverlay has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
IntegrationsStep.FlowStep (cyclomatic 18) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:412— IntegrationsStep.FlowStep has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EditorFileTree.getFileIcon (cyclomatic 18) apps/smithy-web/src/components/editor/EditorFileTree.tsx:117— EditorFileTree.getFileIcon 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.
ApprovalRequestCard.ApprovalRequestCard (cyclomatic 18) apps/smithy-web/src/components/notification/ApprovalRequestCard.tsx:79— ApprovalRequestCard.ApprovalRequestCard has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TaskDetailPanel.OrchestratorMetadataSection (cyclomatic 18) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:488— TaskDetailPanel.OrchestratorMetadataSection has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SessionHistoryModal.extractSessionName (cyclomatic 18) apps/smithy-web/src/components/workspace/SessionHistoryModal.tsx:164— SessionHistoryModal.extractSessionName has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SyncService.importFromStrings (cyclomatic 18) packages/quarry/src/sync/service.ts:280— SyncService.importFromStrings has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
plugin-types.isValidCLIPlugin (cyclomatic 18) packages/quarry/src/cli/plugin-types.ts:149— plugin-types.isValidCLIPlugin has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
task.readyHandler (cyclomatic 18) packages/quarry/src/cli/commands/task.ts:86— task.readyHandler 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, 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.
dep.depAddHandler (cyclomatic 18) packages/quarry/src/cli/commands/dep.ts:50— dep.depAddHandler 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.
document.docSearchHandler (cyclomatic 18) packages/quarry/src/cli/commands/document.ts:1096— document.docSearchHandler 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.
agent-pool.isValidPoolAgentTypeConfig (cyclomatic 18) packages/smithy/src/types/agent-pool.ts:251— agent-pool.isValidPoolAgentTypeConfig 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.
agent.agentRegisterHandler (cyclomatic 18) packages/smithy/src/cli/commands/agent.ts:480— agent.agentRegisterHandler has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DispatchDaemonImpl.processInboxItem (cyclomatic 18) packages/smithy/src/services/dispatch-daemon.ts:3729— DispatchDaemonImpl.processInboxItem has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
pool.poolShowHandler (cyclomatic 18) packages/smithy/src/cli/commands/pool.ts:261— pool.poolShowHandler 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.
Input.Input (cyclomatic 18) packages/ui/src/components/Input.tsx:45— Input.Input 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.
DocumentFilterBar.DocumentFilterBar (cyclomatic 18) packages/ui/src/documents/components/DocumentFilterBar.tsx:18— DocumentFilterBar.DocumentFilterBar has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 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.
ChannelHeader.ChannelHeader (cyclomatic 18) packages/ui/src/domain/ChannelHeader.tsx:177— ChannelHeader.ChannelHeader has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EntityLink.EntityLink (cyclomatic 18) packages/ui/src/domain/EntityLink.tsx:172— EntityLink.EntityLink has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ResponsiveSortDropdown.ResponsiveSortDropdown (cyclomatic 17) apps/quarry-web/src/components/shared/ResponsiveSortDropdown.tsx:36— ResponsiveSortDropdown.ResponsiveSortDropdown has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
inbox.InboxMessageListItem (cyclomatic 17) apps/quarry-web/src/routes/inbox.tsx:312— inbox.InboxMessageListItem has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function items 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.
DirectorPanel.ChatMessageArea (cyclomatic 17) apps/smithy-next/src/components/DirectorPanel.tsx:860— DirectorPanel.ChatMessageArea has cyclomatic complexity 17 (threshold 15). 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 literals inside it that branch (lines 932, 874, 901, …). 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.
MRListView.MRDisplayPanel (cyclomatic 17) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:342— MRListView.MRDisplayPanel has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 370, 398, 349, …). 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.
MRDiffViewer.SplitDiffView (cyclomatic 17) apps/smithy-next/src/components/overlays/mr/MRDiffViewer.tsx:341— MRDiffViewer.SplitDiffView 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 3 function literals inside it that branch (lines 344, 383, 402). 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.
EditorFolderView.EditorFolderView (cyclomatic 17) apps/smithy-next/src/components/overlays/editor/EditorFolderView.tsx:24— EditorFolderView.EditorFolderView 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 4 function literals inside it that branch (lines 89, 26, 32, …). 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.
WorkflowRunDetail.StepRunRow (cyclomatic 17) apps/smithy-next/src/components/overlays/automations/WorkflowRunDetail.tsx:152— WorkflowRunDetail.StepRunRow has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentListView.AgentRow (cyclomatic 17) apps/smithy-next/src/components/overlays/agents/AgentListView.tsx:287— AgentListView.AgentRow has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RoleDefinitionListView.RoleDefinitionListView (cyclomatic 17) apps/smithy-next/src/components/overlays/agents/RoleDefinitionListView.tsx:24— RoleDefinitionListView.RoleDefinitionListView has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 32, 128, 87). 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.
SessionChatView.ToolBlock (cyclomatic 17) apps/smithy-next/src/components/overlays/sessions/SessionChatView.tsx:203— SessionChatView.ToolBlock has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, 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.
ChannelListView.ChannelDisplayPanel (cyclomatic 17) apps/smithy-next/src/components/overlays/messages/ChannelListView.tsx:454— ChannelListView.ChannelDisplayPanel has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 488, 521, 462, …). 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.
SessionSummaryCard.SessionSummaryCard (cyclomatic 17) apps/smithy-next/src/components/overlays/messages/SessionSummaryCard.tsx:23— SessionSummaryCard.SessionSummaryCard has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DocNavPanel.DocNavPanel (cyclomatic 17) apps/smithy-next/src/components/overlays/documents/DocNavPanel.tsx:153— DocNavPanel.DocNavPanel has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 254, 167, 209, …). 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.
DocVersionHistory.DocVersionHistory (cyclomatic 17) apps/smithy-next/src/components/overlays/documents/DocVersionHistory.tsx:23— DocVersionHistory.DocVersionHistory has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 61, 76, 79, …). 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.
OnboardingWizard.OnboardingWizard (cyclomatic 17) apps/smithy-next/src/components/onboarding/OnboardingWizard.tsx:16— OnboardingWizard.OnboardingWizard has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 79, renderStep, a function literal at line 19, …). 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.
useActivity.fetchActivity (cyclomatic 17) apps/smithy-web/src/api/hooks/useActivity.ts:37— useActivity.fetchActivity has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ActiveAgentsDashboard.ActiveAgentsDashboard (cyclomatic 17) apps/smithy-web/src/components/activity/ActiveAgentsDashboard.tsx:26— ActiveAgentsDashboard.ActiveAgentsDashboard has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 129, 58, 72, …). 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.
AgentInboxDrawer.AgentInboxDrawer (cyclomatic 17) apps/smithy-web/src/components/agent/AgentInboxDrawer.tsx:297— AgentInboxDrawer.AgentInboxDrawer has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CreateAgentDialog.CreateAgentDialog::handleSubmit (cyclomatic 17) REDACTED:300— CreateAgentDialog.CreateAgentDialog::handleSubmit 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. This shape REPEATS in the file: one other method here (CreateAgentDialog.CreateAgentDialog) 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.
EditorTabBar.EditorTabBar (cyclomatic 17) apps/smithy-web/src/components/editor/EditorTabBar.tsx:399— EditorTabBar.EditorTabBar has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (handleDragEnd, a function literal at line 467, a function literal at line 485, …). 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.
TaskDetailPanel.EditableTags (cyclomatic 17) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1170— TaskDetailPanel.EditableTags has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (handleKeyDown, a function literal at line 1186, handleAddTag, …). 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.
TaskDetailPanel.ReopenDialog (cyclomatic 17) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1619— TaskDetailPanel.ReopenDialog has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1642, 1649, 1669, …). 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.
BulkActionMenu.BulkActionMenu (cyclomatic 17) apps/smithy-web/src/components/task/BulkActionMenu.tsx:26— BulkActionMenu.BulkActionMenu has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.InboxMessageListItem (cyclomatic 17) apps/smithy-web/src/routes/inbox/index.tsx:312— index.InboxMessageListItem has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function items 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.
dependency.isDependency (cyclomatic 17) packages/core/src/types/dependency.ts:466— dependency.isDependency has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InboxService.buildFilterQuery (cyclomatic 17) packages/quarry/src/services/inbox.ts:467— InboxService.buildFilterQuery 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.
QuarryAPIImpl.getDependencyTree (cyclomatic 17) packages/quarry/src/api/quarry-api.ts:2843— QuarryAPIImpl.getDependencyTree has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (buildNode, countNodes, countDepth). 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.
plugin-registry.registerPluginCommands (cyclomatic 17) packages/quarry/src/cli/plugin-registry.ts:75— plugin-registry.registerPluginCommands 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.
reset.resetHandler (cyclomatic 17) packages/quarry/src/cli/commands/reset.ts:186— reset.resetHandler 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.
task.blockedHandler (cyclomatic 17) packages/quarry/src/cli/commands/task.ts:335— task.blockedHandler has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 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.
SyncEngine.pullDocumentItem (cyclomatic 17) packages/quarry/src/external-sync/sync-engine.ts:987— SyncEngine.pullDocumentItem 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.
plan.planListHandler (cyclomatic 17) packages/quarry/src/cli/commands/plan.ts:159— plan.planListHandler has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
document.docShowHandler (cyclomatic 17) packages/quarry/src/cli/commands/document.ts:771— document.docShowHandler 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.
message.msgThreadHandler (cyclomatic 17) packages/quarry/src/cli/commands/message.ts:356— message.msgThreadHandler has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
role-definition.isBaseRoleDefinition (cyclomatic 17) packages/smithy/src/types/role-definition.ts:346— role-definition.isBaseRoleDefinition has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClaudeHeadlessSession.createMessageIterator (cyclomatic 17) packages/smithy/src/providers/claude/headless.ts:138— ClaudeHeadlessSession.createMessageIterator 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.
ClaudeHeadlessSession.decomposeContentBlocks (cyclomatic 17) packages/smithy/src/providers/claude/headless.ts:233— ClaudeHeadlessSession.decomposeContentBlocks 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.
SpawnerServiceImpl.terminate (cyclomatic 17) packages/smithy/src/runtime/spawner.ts:572— SpawnerServiceImpl.terminate has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 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.
WorktreeManagerImpl.installDependencies (cyclomatic 17) REDACTED:1050— WorktreeManagerImpl.installDependencies has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
DocsStewardServiceImpl.verifyInternalLinks (cyclomatic 17) REDACTED:353— DocsStewardServiceImpl.verifyInternalLinks 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.
DispatchDaemonImpl.recoverStuckMergeTasks (cyclomatic 17) packages/smithy/src/services/dispatch-daemon.ts:1647— DispatchDaemonImpl.recoverStuckMergeTasks 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.
pool.poolCreateHandler (cyclomatic 17) packages/smithy/src/cli/commands/pool.ts:397— pool.poolCreateHandler has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useRealtimeEvents.defaultQueryKeyMapper (cyclomatic 17) packages/ui/src/hooks/useRealtimeEvents.ts:72— useRealtimeEvents.defaultQueryKeyMapper has cyclomatic complexity 17 (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.
MobileDrawer.MobileDrawer (cyclomatic 17) packages/ui/src/layout/MobileDrawer.tsx:46— MobileDrawer.MobileDrawer has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 124, handleTouchMove, a function literal at line 111, …). 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.
Sidebar.Sidebar (cyclomatic 16) apps/quarry-web/src/components/layout/Sidebar.tsx:117— Sidebar.Sidebar has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (Sidebar.Sidebar::renderNavItem) 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.
BulkActionMenu.BulkActionMenu (cyclomatic 16) apps/quarry-web/src/components/task/BulkActionMenu.tsx:25— BulkActionMenu.BulkActionMenu has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GraphToolbar.GraphToolbar (cyclomatic 16) apps/quarry-web/src/routes/dependency-graph/components/GraphToolbar.tsx:46— GraphToolbar.GraphToolbar has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 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.
PropertyDropdowns.DropdownWrapper (cyclomatic 16) apps/smithy-next/src/components/dropdowns/PropertyDropdowns.tsx:12— PropertyDropdowns.DropdownWrapper 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 3 function literals inside it that branch (lines 47, 18, 39). 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.
MRListView.MRRow (cyclomatic 16) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:426— MRListView.MRRow has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, 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.
CIWorkflowGraph.CIWorkflowGraph (cyclomatic 16) apps/smithy-next/src/components/overlays/ci/CIWorkflowGraph.tsx:23— CIWorkflowGraph.CIWorkflowGraph 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 5 function items inside it that branch (getDepth, a function literal at line 120, 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.
CIRunDetailView.StepSection (cyclomatic 16) apps/smithy-next/src/components/overlays/ci/CIRunDetailView.tsx:284— CIRunDetailView.StepSection has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkflowDetailView.OverviewTab (cyclomatic 16) apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.tsx:285— WorkflowDetailView.OverviewTab has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SessionNode.SessionNodeImpl (cyclomatic 16) apps/smithy-next/src/components/overlays/sessions/canvas/SessionNode.tsx:49— SessionNode.SessionNodeImpl has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
metrics-mock-data.mockMetricsTasks (cyclomatic 16) apps/smithy-next/src/components/overlays/metrics/metrics-mock-data.ts:56— metrics-mock-data.mockMetricsTasks has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetricsOverlay.MetricsOverlay (cyclomatic 16) apps/smithy-next/src/components/overlays/MetricsOverlay.tsx:33— MetricsOverlay.MetricsOverlay 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 8 function items inside it that branch (renderTab, a function literal at line 34, a function literal at line 45, …). 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.
DocListView.DocRow (cyclomatic 16) apps/smithy-next/src/components/overlays/documents/DocListView.tsx:67— DocListView.DocRow has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useAgentGraph.useAgentGraph (cyclomatic 16) apps/smithy-web/src/components/agent-graph/useAgentGraph.ts:34— useAgentGraph.useAgentGraph has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 53, 122, 159, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
language-detection.getExtension (cyclomatic 16) apps/smithy-web/src/lib/language-detection.ts:270— language-detection.getExtension has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useFileContentSearch.useFileContentSearch (cyclomatic 16) apps/smithy-web/src/hooks/useFileContentSearch.ts:221— useFileContentSearch.useFileContentSearch has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 312, 286, 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.
DaemonToggle.DaemonToggle (cyclomatic 16) apps/smithy-web/src/components/layout/DaemonToggle.tsx:12— DaemonToggle.DaemonToggle has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, 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.
TaskDependencySection.AddBlockerModal (cyclomatic 16) apps/smithy-web/src/components/task/TaskDependencySection.tsx:288— TaskDependencySection.AddBlockerModal has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 321, 293, 301, …). 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.
index.PlanProgressSection (cyclomatic 16) apps/smithy-web/src/routes/metrics/index.tsx:298— index.PlanProgressSection 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 373, 307, 311, …). 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.
message.isMessage (cyclomatic 16) packages/core/src/types/message.ts:302— message.isMessage has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
library.validateLibrary (cyclomatic 16) packages/core/src/types/library.ts:188— library.validateLibrary has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
team.validateTeam (cyclomatic 16) packages/core/src/types/team.ts:287— team.validateTeam has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
channel.isChannel (cyclomatic 16) packages/core/src/types/channel.ts:472— channel.isChannel has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BlockedCacheService.rebuild (cyclomatic 16) packages/quarry/src/services/blocked-cache.ts:882— BlockedCacheService.rebuild 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.
QuarryAPIImpl.getTasksInPlan (cyclomatic 16) packages/quarry/src/api/quarry-api.ts:1966— QuarryAPIImpl.getTasksInPlan has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (QuarryAPIImpl.getTasksInWorkflow) 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.
QuarryAPIImpl.ready (cyclomatic 16) packages/quarry/src/api/quarry-api.ts:2433— QuarryAPIImpl.ready has cyclomatic complexity 16 (threshold 15). Of this number, 9 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.
QuarryAPIImpl.getTasksInWorkflow (cyclomatic 16) packages/quarry/src/api/quarry-api.ts:4087— QuarryAPIImpl.getTasksInWorkflow has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (QuarryAPIImpl.getTasksInPlan) 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.
QuarryAPIImpl.hydrateMessages (cyclomatic 16) packages/quarry/src/api/quarry-api.ts:5385— QuarryAPIImpl.hydrateMessages has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, 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.
dep.depTreeHandler (cyclomatic 16) packages/quarry/src/cli/commands/dep.ts:517— dep.depTreeHandler has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SyncEngine.pullDocumentsFromProvider (cyclomatic 16) packages/quarry/src/external-sync/sync-engine.ts:889— SyncEngine.pullDocumentsFromProvider has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SyncEngine.findLinkedElements (cyclomatic 16) packages/quarry/src/external-sync/sync-engine.ts:1197— SyncEngine.findLinkedElements has cyclomatic complexity 16 (threshold 15). 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, 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.
entity.entityRegisterHandler (cyclomatic 16) packages/quarry/src/cli/commands/entity.ts:42— entity.entityRegisterHandler 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.
workflow.workflowTasksHandler (cyclomatic 16) packages/quarry/src/cli/commands/workflow.ts:431— workflow.workflowTasksHandler has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
channel.channelListHandler (cyclomatic 16) packages/quarry/src/cli/commands/channel.ts:392— channel.channelListHandler has cyclomatic complexity 16 (threshold 15). 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, 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.
document.docListHandler (cyclomatic 16) packages/quarry/src/cli/commands/document.ts:252— document.docListHandler has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
document.docHistoryHandler (cyclomatic 16) packages/quarry/src/cli/commands/document.ts:397— document.docHistoryHandler has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
runner.run (cyclomatic 16) packages/quarry/src/cli/runner.ts:118— runner.run 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.
MergeStewardServiceImpl.createApprovalPR (cyclomatic 16) packages/smithy/src/services/merge-steward-service.ts:1197— MergeStewardServiceImpl.createApprovalPR has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StewardSchedulerImpl.getNextCronTime (cyclomatic 16) REDACTED:975— StewardSchedulerImpl.getNextCronTime has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PluginExecutorImpl.validate (cyclomatic 16) packages/smithy/src/services/plugin-executor.ts:447— PluginExecutorImpl.validate 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.
DispatchDaemonImpl.reapStaleSessions (cyclomatic 16) packages/smithy/src/services/dispatch-daemon.ts:2203— DispatchDaemonImpl.reapStaleSessions 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.
DispatchDaemonImpl.attachRapidExitDetector (cyclomatic 16) packages/smithy/src/services/dispatch-daemon.ts:2455— DispatchDaemonImpl.attachRapidExitDetector 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 items inside it that branch (onExit, onEvent). 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.
DispatchDaemonImpl.buildStewardPrompt (cyclomatic 16) packages/smithy/src/services/dispatch-daemon.ts:3107— DispatchDaemonImpl.buildStewardPrompt has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pool.poolStatusHandler (cyclomatic 16) packages/smithy/src/cli/commands/pool.ts:767— pool.poolStatusHandler has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.startSmithyServer (cyclomatic 16) REDACTED:84— index.startSmithyServer has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocumentTagInput.DocumentTagInput (cyclomatic 16) packages/ui/src/documents/components/DocumentTagInput.tsx:15— DocumentTagInput.DocumentTagInput has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (handleKeyDown, a function literal at line 26, handleAddTag, …). 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.
usePlanApi.useCreatePlan (cyclomatic 16) packages/ui/src/plans/hooks/usePlanApi.ts:233— usePlanApi.useCreatePlan 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 274, 236). 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.
D1 · Cyclomatic Complexity· Zu (cyclomatic 16) · ×1
Zu (cyclomatic 16) REDACTED:813— Zu 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 items inside it that branch (a function literal at line 813, (anonymous)::C, a function literal at line 813, …). 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: _n (cyclomatic 23) 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.
Deprecated: recharts packages/ui/package.json:149— recharts 2.15.4, declared in packages/ui/package.json, is marked deprecated by its publisher: "1.x and 2.x branches are no longer active. Bump to Recharts v3 to receive latest features and bugfixes. See https://github.com/recharts/recharts/wiki/3.0-migration-guide". Replace it with the package or version that message names, or record why this one must stay.
index.createQuarryApp (cognitive 619) REDACTED:129— index.createQuarryApp has cognitive complexity 619 (threshold 15). Drivers by points: if/else 251 (340 pts), boolean chains 152, error handling 73 (75 pts), ternaries 25 (33 pts), loops 16 (18 pts), match/switch 1 (nesting depth added 101). Most of this is not in the body itself: 8 of the 619 points are its own statements and the rest belongs to 92 function items inside it that branch (a function literal at line 3017, a function literal at line 2494, a function literal at line 3171, …). 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.
documents.createDocumentRoutes (cognitive 280) packages/shared-routes/src/documents.ts:30— documents.createDocumentRoutes has cognitive complexity 280 (threshold 15). Drivers by points: if/else 140 (168 pts), boolean chains 66, error handling 26 (30 pts), loops 7 (10 pts), ternaries 6 (nesting depth added 35). None of this is in the body itself: all 280 points belong to 28 function literals inside it that branch (lines 35, 261, 366, …). 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.
index.FileEditorPage (cognitive 229) apps/smithy-web/src/routes/editor/index.tsx:219— index.FileEditorPage has cognitive complexity 229 (threshold 15). Drivers by points: if/else 68 (88 pts), ternaries 32 (73 pts), boolean chains 58, error handling 7 (8 pts), loops 1 (2 pts) (nesting depth added 63). Of this number, 60 points are the body's own statements and 169 belong to 45 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.
App.App (cognitive 191) apps/smithy-next/src/App.tsx:371— App.App has cognitive complexity 191 (threshold 15). Drivers by points: boolean chains 102, if/else 44 (54 pts), ternaries 21 (32 pts), match/switch 2 (3 pts) (nesting depth added 22). Of this number, 18 points are the body's own statements and 173 belong to 57 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.
tasks.createTaskRoutes (cognitive 168) packages/smithy/src/server/routes/tasks.ts:46— tasks.createTaskRoutes has cognitive complexity 168 (threshold 15). Drivers by points: if/else 81 (94 pts), boolean chains 42, error handling 23 (24 pts), ternaries 7 (8 pts) (nesting depth added 15). None of this is in the body itself: all 168 points belong to 31 function literals inside it that branch (lines 133, 262, 602, …). 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.
tasks.createTaskRoutes (cognitive 159) apps/smithy-server/src/routes/tasks.ts:43— tasks.createTaskRoutes has cognitive complexity 159 (threshold 15). Drivers by points: if/else 76 (85 pts), boolean chains 41, error handling 23 (25 pts), ternaries 7 (8 pts) (nesting depth added 12). None of this is in the body itself: all 159 points belong to 31 function literals inside it that branch (lines 205, 543, 108, …). 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.
StreamViewer.StreamViewer (cognitive 150) apps/smithy-web/src/components/workspace/StreamViewer.tsx:335— StreamViewer.StreamViewer has cognitive complexity 150 (threshold 15). Drivers by points: if/else 57 (81 pts), boolean chains 38, ternaries 11 (19 pts), error handling 7 (9 pts), loops 2 (3 pts) (nesting depth added 35). Most of this is not in the body itself: 12 of the 150 points are its own statements and the rest belongs to 32 function items inside it that branch (a function literal at line 674, a function literal at line 637, a function literal at line 1003, …). 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.
WorkflowEditorModal.WorkflowEditorModal (cognitive 147) packages/ui/src/workflows/components/WorkflowEditorModal.tsx:980— WorkflowEditorModal.WorkflowEditorModal has cognitive complexity 147 (threshold 15). Drivers by points: if/else 40 (67 pts), boolean chains 45, ternaries 19 (30 pts), loops 3, error handling 2 (nesting depth added 38). Of this number, 26 points are the body's own statements and 121 belong to 13 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.
QuarryAPIImpl.create (cognitive 145) packages/quarry/src/api/quarry-api.ts:892— QuarryAPIImpl.create has cognitive complexity 145 (threshold 15). Drivers by points: if/else 32 (88 pts), error handling 4 (26 pts), loops 5 (20 pts), boolean chains 7, ternaries 1 (4 pts) (nesting depth added 96). Of this number, 140 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
agents.createAgentRoutes (cognitive 139) packages/smithy/src/server/routes/agents.ts:16— agents.createAgentRoutes has cognitive complexity 139 (threshold 15). Drivers by points: if/else 53 (79 pts), boolean chains 27, error handling 17 (24 pts), loops 2 (4 pts), ternaries 4, match/switch 1 (nesting depth added 35). None of this is in the body itself: all 139 points belong to 13 function literals inside it that branch (lines 306, 211, 34, …). 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.
utils-vendor-CfYKiENT.Oi (cognitive 136) REDACTED:1— utils-vendor-CfYKiENT.Oi has cognitive complexity 136 (threshold 15). Drivers by points: boolean chains 72, ternaries 32 (48 pts), if/else 12 (16 pts) (nesting depth added 20). Of this number, 77 points are the body's own statements and 59 belong to 17 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.
DirectorPanel.DirectorPanel (cognitive 131) apps/smithy-next/src/components/DirectorPanel.tsx:112— DirectorPanel.DirectorPanel has cognitive complexity 131 (threshold 15). Drivers by points: ternaries 30 (56 pts), boolean chains 49, if/else 20 (26 pts) (nesting depth added 32). Of this number, 83 points are the body's own statements and 48 belong to 38 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.
messages.createMessageRoutes (cognitive 121) packages/shared-routes/src/messages.ts:12— messages.createMessageRoutes has cognitive complexity 121 (threshold 15). Drivers by points: if/else 38 (80 pts), boolean chains 23, error handling 6 (11 pts), loops 4 (6 pts), ternaries 1 (nesting depth added 49). None of this is in the body itself: all 121 points belong to 4 function literals inside it that branch (lines 17, 256, 373, …). 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.
sessions.createSessionRoutes (cognitive 116) apps/smithy-server/src/routes/sessions.ts:207— sessions.createSessionRoutes has cognitive complexity 116 (threshold 15). Drivers by points: if/else 42 (56 pts), error handling 15 (18 pts), ternaries 9 (16 pts), boolean chains 15, loops 6 (11 pts) (nesting depth added 29). None of this is in the body itself: all 116 points belong to 15 function literals inside it that branch (lines 215, 896, 538, …). 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.
channels.createChannelRoutes (cognitive 116) packages/shared-routes/src/channels.ts:13— channels.createChannelRoutes has cognitive complexity 116 (threshold 15). Drivers by points: if/else 51 (73 pts), boolean chains 33, error handling 10 (nesting depth added 22). None of this is in the body itself: all 116 points belong to 15 function literals inside it that branch (lines 112, 327, 18, …). 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.
sessions.createSessionRoutes (cognitive 113) packages/smithy/src/server/routes/sessions.ts:213— sessions.createSessionRoutes has cognitive complexity 113 (threshold 15). Drivers by points: if/else 42 (57 pts), error handling 16 (20 pts), boolean chains 15, loops 6 (11 pts), ternaries 7 (10 pts) (nesting depth added 27). None of this is in the body itself: all 113 points belong to 15 function literals inside it that branch (lines 221, 908, 560, …). 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.
plans.createPlanRoutes (cognitive 112) packages/shared-routes/src/plans.ts:22— plans.createPlanRoutes has cognitive complexity 112 (threshold 15). Drivers by points: if/else 56 (72 pts), boolean chains 26, error handling 11 (12 pts), loops 2 (nesting depth added 17). None of this is in the body itself: all 112 points belong to 10 function literals inside it that branch (lines 348, 196, 513, …). 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.
RoleDefinitionDetailView.RoleDefinitionDetailView (cognitive 111) apps/smithy-next/src/components/overlays/agents/RoleDefinitionDetailView.tsx:277— RoleDefinitionDetailView.RoleDefinitionDetailView has cognitive complexity 111 (threshold 15). Drivers by points: boolean chains 53, ternaries 24 (36 pts), if/else 14 (22 pts) (nesting depth added 20). Of this number, 50 points are the body's own statements and 61 belong to 17 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.
AppShell.AppShell (cognitive 98) apps/smithy-web/src/components/layout/AppShell.tsx:663— AppShell.AppShell has cognitive complexity 98 (threshold 15). Drivers by points: if/else 44 (58 pts), boolean chains 26, ternaries 9 (14 pts) (nesting depth added 19). Of this number, 28 points are the body's own statements and 70 belong to 19 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.
DocumentDetailPanel.DocumentDetailPanel (cognitive 95) apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:59— DocumentDetailPanel.DocumentDetailPanel has cognitive complexity 95 (threshold 15). Drivers by points: boolean chains 40, ternaries 24 (33 pts), if/else 16, error handling 5 (6 pts) (nesting depth added 10). Of this number, 66 points are the body's own statements and 29 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.
TaskDetailOverlay.TaskDetailOverlay (cognitive 93) apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:36— TaskDetailOverlay.TaskDetailOverlay has cognitive complexity 93 (threshold 15). Drivers by points: boolean chains 59, ternaries 29 (31 pts), if/else 3 (nesting depth added 2). Of this number, 63 points are the body's own statements and 30 belong to 26 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.
admin.doctorHandler (cognitive 91) packages/quarry/src/cli/commands/admin.ts:57— admin.doctorHandler has cognitive complexity 91 (threshold 15). Drivers by points: if/else 25 (43 pts), ternaries 10 (22 pts), error handling 9 (16 pts), loops 2 (6 pts), boolean chains 4 (nesting depth added 41). 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.
playbook.playbookValidateHandler (cognitive 90) packages/quarry/src/cli/commands/playbook.ts:326— playbook.playbookValidateHandler has cognitive complexity 90 (threshold 15). Drivers by points: if/else 24 (44 pts), ternaries 7 (16 pts), loops 6 (13 pts), boolean chains 9, error handling 6 (8 pts) (nesting depth added 38). 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.
parser.parseArgs (cognitive 89) packages/quarry/src/cli/parser.ts:92— parser.parseArgs has cognitive complexity 89 (threshold 15). Drivers by points: if/else 24 (72 pts), loops 4 (9 pts), boolean chains 8 (nesting depth added 53). 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.
DispatchDaemonImpl.recoverOrphanedAssignments (cognitive 89) packages/smithy/src/services/dispatch-daemon.ts:1203— DispatchDaemonImpl.recoverOrphanedAssignments has cognitive complexity 89 (threshold 15). Drivers by points: if/else 21 (44 pts), ternaries 7 (22 pts), error handling 6 (15 pts), loops 4 (5 pts), boolean chains 3 (nesting depth added 48). 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.
WorkflowEditorModal.generateYaml (cognitive 89) packages/ui/src/workflows/components/WorkflowEditorModal.tsx:205— WorkflowEditorModal.generateYaml has cognitive complexity 89 (threshold 15). Drivers by points: if/else 19 (55 pts), loops 6 (23 pts), ternaries 2 (9 pts), boolean chains 2 (nesting depth added 60). 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.
XTerminal.XTerminal (cognitive 86) apps/smithy-web/src/components/terminal/XTerminal.tsx:125— XTerminal.XTerminal has cognitive complexity 86 (threshold 15). Drivers by points: if/else 43 (56 pts), boolean chains 22, ternaries 3 (4 pts), error handling 2, loops 1, match/switch 1 (nesting depth added 14). Most of this is not in the body itself: 2 of the 86 points are its own statements and the rest belongs to 24 function literals inside it that branch (lines 665, 242, 439, …). 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.
WorkspaceGrid.WorkspaceGrid (cognitive 86) apps/smithy-web/src/components/workspace/WorkspaceGrid.tsx:347— WorkspaceGrid.WorkspaceGrid has cognitive complexity 86 (threshold 15). Drivers by points: ternaries 23 (54 pts), boolean chains 18, if/else 13 (14 pts) (nesting depth added 32). Of this number, 44 points are the body's own statements and 42 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.
index.InboxPage (cognitive 84) apps/smithy-web/src/routes/inbox/index.tsx:853— index.InboxPage has cognitive complexity 84 (threshold 15). Drivers by points: ternaries 16 (34 pts), boolean chains 25, if/else 19 (24 pts), error handling 1 (nesting depth added 23). Of this number, 44 points are the body's own statements and 40 belong to 12 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.
workflows.createWorkflowRoutes (cognitive 83) packages/smithy/src/server/routes/workflows.ts:143— workflows.createWorkflowRoutes has cognitive complexity 83 (threshold 15). Drivers by points: if/else 34 (48 pts), error handling 15 (16 pts), loops 6 (10 pts), boolean chains 6, ternaries 3 (nesting depth added 19). None of this is in the body itself: all 83 points belong to 14 function literals inside it that branch (lines 660, 238, 154, …). 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.
agents.createAgentRoutes (cognitive 82) apps/smithy-server/src/routes/agents.ts:16— agents.createAgentRoutes has cognitive complexity 82 (threshold 15). Drivers by points: if/else 34 (47 pts), boolean chains 16, error handling 12, ternaries 4, loops 1 (2 pts), match/switch 1 (nesting depth added 14). None of this is in the body itself: all 82 points belong to 12 function literals inside it that branch (lines 196, 283, 34, …). 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.
index.DocumentsPage (cognitive 81) apps/smithy-web/src/routes/documents/index.tsx:53— index.DocumentsPage has cognitive complexity 81 (threshold 15). Drivers by points: boolean chains 37, if/else 28 (32 pts), error handling 4 (5 pts), ternaries 3 (4 pts), loops 2 (3 pts) (nesting depth added 7). Of this number, 27 points are the body's own statements and 54 belong to 19 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
file.convertYamlToConfig (cognitive 81) packages/quarry/src/config/file.ts:189— file.convertYamlToConfig has cognitive complexity 81 (threshold 15). Drivers by points: if/else 43 (80 pts), boolean chains 1 (nesting depth added 37). 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.
inbox.InboxPage (cognitive 78) apps/quarry-web/src/routes/inbox.tsx:853— inbox.InboxPage has cognitive complexity 78 (threshold 15). Drivers by points: ternaries 16 (34 pts), boolean chains 22, if/else 16 (21 pts), error handling 1 (nesting depth added 23). Of this number, 44 points are the body's own statements and 34 belong to 11 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.
ImageUploadModal.ImageUploadModal (cognitive 77) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:53— ImageUploadModal.ImageUploadModal has cognitive complexity 77 (threshold 15). Drivers by points: boolean chains 35, if/else 22 (25 pts), ternaries 9 (13 pts), error handling 4 (nesting depth added 7). Of this number, 40 points are the body's own statements and 37 belong to 16 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.
crud.updateHandler (cognitive 77) packages/quarry/src/cli/commands/crud.ts:820— crud.updateHandler has cognitive complexity 77 (threshold 15). Drivers by points: if/else 38 (56 pts), ternaries 4 (8 pts), boolean chains 6, loops 2 (4 pts), error handling 2 (3 pts) (nesting depth added 25). 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.
EntityDetailPanel.OverviewTabContent (cognitive 76) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:592— EntityDetailPanel.OverviewTabContent has cognitive complexity 76 (threshold 15). Drivers by points: ternaries 26 (51 pts), boolean chains 19, if/else 2 (4 pts), error handling 1 (2 pts) (nesting depth added 28). Of this number, 53 points are the body's own statements and 23 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.
EditorOverlayNew.EditorOverlayNew (cognitive 76) apps/smithy-next/src/components/overlays/editor/EditorOverlayNew.tsx:36— EditorOverlayNew.EditorOverlayNew has cognitive complexity 76 (threshold 15). Drivers by points: boolean chains 30, if/else 22 (25 pts), ternaries 15 (19 pts), loops 1 (2 pts) (nesting depth added 8). Of this number, 28 points are the body's own statements and 48 belong to 15 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.
external-sync.linkAllDocumentsHandler (cognitive 76) packages/quarry/src/cli/commands/external-sync.ts:2089— external-sync.linkAllDocumentsHandler has cognitive complexity 76 (threshold 15). Drivers by points: if/else 42 (60 pts), boolean chains 8, ternaries 3 (4 pts), loops 2 (3 pts), error handling 1 (nesting depth added 20). Of this number, 72 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CanvasView.CanvasView (cognitive 75) apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:36— CanvasView.CanvasView has cognitive complexity 75 (threshold 15). Drivers by points: if/else 30 (35 pts), boolean chains 20, error handling 8, ternaries 7 (8 pts), loops 4 (nesting depth added 6). Most of this is not in the body itself: 15 of the 75 points are its own statements and the rest belongs to 34 function literals inside it that branch (lines 317, 348, 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.
DirectorPanel.DirectorPanel (cognitive 71) apps/smithy-web/src/components/layout/DirectorPanel.tsx:303— DirectorPanel.DirectorPanel has cognitive complexity 71 (threshold 15). Drivers by points: if/else 30 (33 pts), boolean chains 21, ternaries 9 (11 pts), error handling 5 (6 pts) (nesting depth added 6). Of this number, 27 points are the body's own statements and 44 belong to 24 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.
DocumentDetailPanel.DocumentDetailPanel (cognitive 71) apps/smithy-web/src/routes/documents/components/DocumentDetailPanel.tsx:49— DocumentDetailPanel.DocumentDetailPanel has cognitive complexity 71 (threshold 15). Drivers by points: boolean chains 32, ternaries 19 (25 pts), if/else 11, error handling 2 (3 pts) (nesting depth added 7). Of this number, 54 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
steward-scheduler.createStewardExecutor.<returned closure> (cognitive 71) REDACTED:1442— steward-scheduler.createStewardExecutor.<returned closure> has cognitive complexity 71 (threshold 15). Drivers by points: ternaries 11 (28 pts), if/else 11 (24 pts), error handling 5 (11 pts), boolean chains 7, match/switch 1 (nesting depth added 36). 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.
RuntimeDetailView.EditMode (cognitive 70) apps/smithy-next/src/components/overlays/agents/RuntimeDetailView.tsx:275— RuntimeDetailView.EditMode has cognitive complexity 70 (threshold 15). Drivers by points: boolean chains 32, ternaries 25 (29 pts), if/else 9 (nesting depth added 4). Of this number, 33 points are the body's own statements and 37 belong to 10 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.
RuntimeCreateView.RuntimeCreateView (cognitive 70) apps/smithy-next/src/components/overlays/runtimes/RuntimeCreateView.tsx:25— RuntimeCreateView.RuntimeCreateView has cognitive complexity 70 (threshold 15). Drivers by points: ternaries 21 (38 pts), boolean chains 20, if/else 11 (12 pts) (nesting depth added 18). Of this number, 30 points are the body's own statements and 40 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.
index.TasksPage (cognitive 70) apps/smithy-web/src/routes/tasks/index.tsx:89— index.TasksPage has cognitive complexity 70 (threshold 15). Drivers by points: if/else 22 (23 pts), boolean chains 22, ternaries 11 (21 pts), error handling 3, match/switch 1 (nesting depth added 11). Of this number, 18 points are the body's own statements and 52 belong to 19 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.
App.parseUrl (cognitive 69) apps/smithy-next/src/App.tsx:108— App.parseUrl has cognitive complexity 69 (threshold 15). Drivers by points: if/else 33 (50 pts), boolean chains 17, ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App.buildUrl (cognitive 69) apps/smithy-next/src/App.tsx:269— App.buildUrl has cognitive complexity 69 (threshold 15). Drivers by points: if/else 31 (62 pts), ternaries 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 33). 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.
external-sync.linkAllHandler (cognitive 67) packages/quarry/src/cli/commands/external-sync.ts:2392— external-sync.linkAllHandler has cognitive complexity 67 (threshold 15). Drivers by points: if/else 36 (49 pts), boolean chains 8, ternaries 4 (6 pts), loops 2 (3 pts), error handling 1 (nesting depth added 16). Of this number, 63 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.TasksPage (cognitive 66) apps/quarry-web/src/routes/tasks/index.tsx:90— index.TasksPage has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 27, if/else 21 (24 pts), ternaries 14 (15 pts) (nesting depth added 4). Of this number, 21 points are the body's own statements and 45 belong to 19 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
KanbanBoard.KanbanBoard (cognitive 66) apps/smithy-next/src/components/KanbanBoard.tsx:40— KanbanBoard.KanbanBoard has cognitive complexity 66 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 23, ternaries 15 (16 pts), match/switch 2 (nesting depth added 5). Of this number, 17 points are the body's own statements and 49 belong to 25 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.
utils-vendor-CfYKiENT.zn (cognitive 66) REDACTED:811— utils-vendor-CfYKiENT.zn has cognitive complexity 66 (threshold 15). Drivers by points: boolean chains 27, if/else 10 (19 pts), ternaries 8 (13 pts), loops 4 (5 pts), match/switch 1 (2 pts) (nesting depth added 16). None of this is in the body itself: all 66 points belong to 24 function items inside it that branch (a function literal at line 811, pe, a function literal at line 811, …). 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.
EditorFileTree.EditorFileTree (cognitive 65) apps/smithy-web/src/components/editor/EditorFileTree.tsx:733— EditorFileTree.EditorFileTree has cognitive complexity 65 (threshold 15). Drivers by points: if/else 24 (38 pts), ternaries 7 (12 pts), boolean chains 7, error handling 4 (5 pts), loops 3 (nesting depth added 20). Most of this is not in the body itself: 7 of the 65 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 926, 973, 811, …). 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.
file.convertConfigToYaml (cognitive 65) packages/quarry/src/config/file.ts:423— file.convertConfigToYaml has cognitive complexity 65 (threshold 15). Drivers by points: if/else 39 (64 pts), boolean chains 1 (nesting depth added 25). 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.
message.msgSendHandler (cognitive 65) packages/quarry/src/cli/commands/message.ts:110— message.msgSendHandler has cognitive complexity 65 (threshold 15). Drivers by points: if/else 30 (49 pts), boolean chains 7, ternaries 4 (6 pts), loops 1 (2 pts), error handling 1 (nesting depth added 22). 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.
DocsStewardServiceImpl.verifyFilePaths (cognitive 64) REDACTED:277— DocsStewardServiceImpl.verifyFilePaths has cognitive complexity 64 (threshold 15). Drivers by points: if/else 8 (32 pts), ternaries 4 (22 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 45). 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.
CommandPalette.CommandPalette (cognitive 63) apps/quarry-web/src/components/navigation/CommandPalette.tsx:95— CommandPalette.CommandPalette has cognitive complexity 63 (threshold 15). Drivers by points: if/else 18 (32 pts), ternaries 9 (25 pts), boolean chains 6 (nesting depth added 30). Of this number, 28 points are the body's own statements and 35 belong to 14 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.
task-utils.groupTasks (cognitive 63) apps/smithy-web/src/lib/task-utils.tsx:190— task-utils.groupTasks has cognitive complexity 63 (threshold 15). Drivers by points: if/else 17 (32 pts), loops 8 (15 pts), boolean chains 8, ternaries 2 (6 pts), match/switch 1 (2 pts) (nesting depth added 27). Of this number, 46 points are the body's own statements and 17 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generator.generateId (cognitive 62) packages/core/src/id/generator.ts:626— generator.generateId has cognitive complexity 62 (threshold 15). Drivers by points: if/else 20 (57 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 38). 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.
playbook-yaml.validateYamlPlaybook (cognitive 62) packages/core/src/types/playbook-yaml.ts:409— playbook-yaml.validateYamlPlaybook has cognitive complexity 62 (threshold 15). Drivers by points: if/else 22 (45 pts), loops 5 (12 pts), boolean chains 4, ternaries 1 (nesting depth added 30). 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.
external-sync.unlinkAllHandler (cognitive 61) packages/quarry/src/cli/commands/external-sync.ts:766— external-sync.unlinkAllHandler has cognitive complexity 61 (threshold 15). Drivers by points: if/else 21 (34 pts), ternaries 4 (11 pts), boolean chains 6, loops 4 (6 pts), error handling 2 (4 pts) (nesting depth added 24). 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.
CreateActionDialog.parseYaml (cognitive 60) apps/smithy-next/src/components/overlays/ci/CreateActionDialog.tsx:65— CreateActionDialog.parseYaml has cognitive complexity 60 (threshold 15). Drivers by points: if/else 16 (49 pts), boolean chains 9, loops 1, ternaries 1 (nesting depth added 33). 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.
DocListView.DocListView (cognitive 60) apps/smithy-next/src/components/overlays/documents/DocListView.tsx:358— DocListView.DocListView has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 16, ternaries 10 (13 pts), loops 2 (nesting depth added 13). Of this number, 18 points are the body's own statements and 42 belong to 6 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.
constructor (cognitive 60) REDACTED:1— constructor has cognitive complexity 60 (threshold 15). Drivers by points: ternaries 22 (38 pts), boolean chains 12, if/else 6 (7 pts), error handling 2 (3 pts) (nesting depth added 18). None of this is in the body itself: all 60 points belong to 29 function items inside it that branch (a function literal at line 1, a function literal at line 1, promise, …). 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.
ActiveAgentsStrip.ActiveAgentsStrip (cognitive 59) apps/smithy-next/src/components/ActiveAgentsStrip.tsx:22— ActiveAgentsStrip.ActiveAgentsStrip has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 27, if/else 11 (16 pts), ternaries 9, error handling 4, loops 2 (3 pts) (nesting depth added 6). Of this number, 29 points are the body's own statements and 30 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.
workflows.createWorkflowRoutes (cognitive 59) apps/smithy-server/src/routes/workflows.ts:98— workflows.createWorkflowRoutes has cognitive complexity 59 (threshold 15). Drivers by points: if/else 27 (31 pts), error handling 14, loops 5 (6 pts), boolean chains 5, ternaries 3 (nesting depth added 5). None of this is in the body itself: all 59 points belong to 14 function literals inside it that branch (lines 193, 109, 443, …). 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.
crud.createHandler (cognitive 59) packages/quarry/src/cli/commands/crud.ts:100— crud.createHandler has cognitive complexity 59 (threshold 15). Drivers by points: if/else 27 (39 pts), boolean chains 12, ternaries 2 (5 pts), error handling 2 (3 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.
inbox.createInboxRoutes (cognitive 59) packages/shared-routes/src/inbox.ts:13— inbox.createInboxRoutes has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 23, if/else 20 (22 pts), error handling 7, ternaries 6, match/switch 1 (nesting depth added 2). None of this is in the body itself: all 59 points belong to 9 function literals inside it that branch (lines 276, 28, 570, …). 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.
index.AgentsPage (cognitive 58) apps/smithy-web/src/routes/agents/index.tsx:23— index.AgentsPage has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 16 (37 pts), boolean chains 8, if/else 7, loops 5, error handling 1 (nesting depth added 21). Of this number, 36 points are the body's own statements and 22 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.
dependency.isValidAwaitsMetadata (cognitive 58) packages/core/src/types/dependency.ts:386— dependency.isValidAwaitsMetadata has cognitive complexity 58 (threshold 15). Drivers by points: if/else 21 (44 pts), boolean chains 13, match/switch 1 (nesting depth added 23). 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.
EditorSearchPanel.EditorSearchPanel (cognitive 57) apps/smithy-next/src/components/overlays/editor/EditorSearchPanel.tsx:17— EditorSearchPanel.EditorSearchPanel has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 7 (17 pts), boolean chains 8, error handling 1 (4 pts), loops 3 (4 pts) (nesting depth added 25). Most of this is not in the body itself: 4 of the 57 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 24, 220, 71, …). 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.
init.initHandler (cognitive 57) packages/quarry/src/cli/commands/init.ts:538— init.initHandler has cognitive complexity 57 (threshold 15). Drivers by points: if/else 29 (35 pts), ternaries 11 (14 pts), boolean chains 6, error handling 2 (nesting depth added 9). 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.
DocsStewardServiceImpl.verifyInternalLinks (cognitive 57) REDACTED:353— DocsStewardServiceImpl.verifyInternalLinks has cognitive complexity 57 (threshold 15). Drivers by points: if/else 10 (39 pts), error handling 2 (11 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 41). 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.
task-utils.groupTasks (cognitive 56) apps/quarry-web/src/lib/task-utils.tsx:187— task-utils.groupTasks has cognitive complexity 56 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 8 (15 pts), boolean chains 7, ternaries 2 (6 pts), match/switch 1 (2 pts) (nesting depth added 24). Of this number, 46 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.
index.TimelinePage (cognitive 55) apps/quarry-web/src/routes/timeline/index.tsx:32— index.TimelinePage has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 24, if/else 14 (17 pts), ternaries 8 (13 pts), loops 1 (nesting depth added 8). Of this number, 23 points are the body's own statements and 32 belong to 13 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.
validation.validateConfiguration (cognitive 55) packages/quarry/src/config/validation.ts:321— validation.validateConfiguration has cognitive complexity 55 (threshold 15). Drivers by points: if/else 38 (43 pts), boolean chains 11, 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.
EntityDetailPanel.InboxTabContent (cognitive 54) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:1087— EntityDetailPanel.InboxTabContent has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 13 (29 pts), boolean chains 14, if/else 7 (11 pts) (nesting depth added 20). Of this number, 34 points are the body's own statements and 20 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.
AgentOverviewTab.AgentOverviewTab (cognitive 54) apps/smithy-next/src/components/overlays/agents/AgentOverviewTab.tsx:22— AgentOverviewTab.AgentOverviewTab has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 16 (36 pts), boolean chains 12, if/else 1 (3 pts), loops 2 (3 pts) (nesting depth added 23). Most of this is not in the body itself: 9 of the 54 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 166, 130, 30, …). 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.
playbook-yaml.validateYamlStep (cognitive 54) packages/core/src/types/playbook-yaml.ts:651— playbook-yaml.validateYamlStep has cognitive complexity 54 (threshold 15). Drivers by points: if/else 25 (37 pts), boolean chains 15, 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.
SessionsOverlay.SessionsOverlay (cognitive 53) apps/smithy-next/src/components/overlays/SessionsOverlay.tsx:47— SessionsOverlay.SessionsOverlay has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (19 pts), ternaries 11 (14 pts), boolean chains 12, error handling 8 (nesting depth added 6). Of this number, 16 points are the body's own statements and 37 belong to 19 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.
dependency.validateAwaitsMetadata (cognitive 53) packages/core/src/types/dependency.ts:559— dependency.validateAwaitsMetadata has cognitive complexity 53 (threshold 15). Drivers by points: if/else 18 (39 pts), boolean chains 11, loops 1 (2 pts), match/switch 1 (nesting depth added 22). 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.
TeamDetailPanel.TeamDetailPanel (cognitive 52) apps/quarry-web/src/routes/teams/components/TeamDetailPanel.tsx:25— TeamDetailPanel.TeamDetailPanel has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 25, ternaries 8 (13 pts), if/else 8, error handling 4, loops 1 (2 pts) (nesting depth added 6). Of this number, 34 points are the body's own statements and 18 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.
task.taskMergeStatusHandler (cognitive 52) packages/smithy/src/cli/commands/task.ts:1102— task.taskMergeStatusHandler has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (37 pts), boolean chains 6, error handling 2 (6 pts), ternaries 2 (3 pts) (nesting depth added 27). 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.
HorizontalTimeline.HorizontalTimeline (cognitive 51) apps/quarry-web/src/routes/timeline/components/HorizontalTimeline.tsx:32— HorizontalTimeline.HorizontalTimeline has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 15, ternaries 7 (11 pts), loops 3 (4 pts) (nesting depth added 9). Of this number, 21 points are the body's own statements and 30 belong to 11 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.
index.DocumentsPage (cognitive 51) apps/quarry-web/src/routes/documents/index.tsx:34— index.DocumentsPage has cognitive complexity 51 (threshold 15). Drivers by points: boolean chains 23, if/else 19 (21 pts), ternaries 3 (4 pts), loops 2 (3 pts) (nesting depth added 4). Of this number, 21 points are the body's own statements and 30 belong to 13 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.
EntityDetailPanel.EntityDetailPanel (cognitive 51) apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:95— EntityDetailPanel.EntityDetailPanel has cognitive complexity 51 (threshold 15). Drivers by points: if/else 20, boolean chains 16, ternaries 9 (11 pts), error handling 3, match/switch 1 (nesting depth added 2). Of this number, 18 points are the body's own statements and 33 belong to 11 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.
validation.validatePartialConfiguration (cognitive 51) packages/quarry/src/config/validation.ts:640— validation.validatePartialConfiguration has cognitive complexity 51 (threshold 15). Drivers by points: if/else 32 (42 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 11). 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.
MRDiffViewer.MRDiffViewer (cognitive 50) apps/smithy-next/src/components/overlays/mr/MRDiffViewer.tsx:30— MRDiffViewer.MRDiffViewer has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 21, if/else 19 (21 pts), ternaries 8 (nesting depth added 2). None of this is in the body itself: all 50 points belong to 17 function items inside it that branch (a function literal at line 144, isLineSelected, a function literal at line 76, …). 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.
LspMonacoEditor.LspMonacoEditorComponent (cognitive 50) apps/smithy-web/src/components/editor/LspMonacoEditor.tsx:176— LspMonacoEditor.LspMonacoEditorComponent has cognitive complexity 50 (threshold 15). Drivers by points: if/else 31 (33 pts), boolean chains 10, ternaries 5, error handling 1, loops 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 50 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 397, 373, 326, …). 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.
playbook.isValidPlaybookStep (cognitive 50) packages/core/src/types/playbook.ts:640— playbook.isValidPlaybookStep has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (39 pts), boolean chains 11 (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.
SyncService.importFromStrings (cognitive 50) packages/quarry/src/sync/service.ts:280— SyncService.importFromStrings has cognitive complexity 50 (threshold 15). Drivers by points: if/else 13 (33 pts), loops 6 (10 pts), ternaries 1 (5 pts), boolean chains 2 (nesting depth added 28). Of this number, 21 points are the body's own statements and 29 belong to one function literal inside it that branches. 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.
QuarryAPIImpl.update (cognitive 50) packages/quarry/src/api/quarry-api.ts:1286— QuarryAPIImpl.update has cognitive complexity 50 (threshold 15). Drivers by points: if/else 25 (37 pts), boolean chains 11, loops 1 (2 pts) (nesting depth added 13). Of this number, 18 points are the body's own statements and 32 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContributionChart.ContributionChart (cognitive 49) apps/quarry-web/src/components/shared/ContributionChart.tsx:101— ContributionChart.ContributionChart has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 19 (32 pts), if/else 8 (9 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 15). Most of this is not in the body itself: 4 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 118, a function literal at line 273, a function literal at line 293, …). 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.
EditorCodeView.EditorCodeView (cognitive 49) apps/smithy-next/src/components/overlays/editor/EditorCodeView.tsx:20— EditorCodeView.EditorCodeView has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 12 (24 pts), if/else 11 (14 pts), boolean chains 10, loops 1 (nesting depth added 15). Most of this is not in the body itself: 8 of the 49 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 217, a function literal at line 55, a function literal at line 43, …). 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.
RuntimeListView.RuntimeListView (cognitive 49) apps/smithy-next/src/components/overlays/runtimes/RuntimeListView.tsx:30— RuntimeListView.RuntimeListView has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 20, if/else 12 (15 pts), ternaries 10 (11 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 5). Of this number, 22 points are the body's own statements and 27 belong to 16 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.
EditorExtensionsPanel.EditorExtensionsPanel (cognitive 49) apps/smithy-web/src/components/editor/EditorExtensionsPanel.tsx:83— EditorExtensionsPanel.EditorExtensionsPanel has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 11, loops 4 (8 pts), ternaries 2 (3 pts), error handling 2, match/switch 2 (nesting depth added 11). Most of this is not in the body itself: 5 of the 49 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 352, 505, 166, …). 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.
ExtensionDetailPage.ExtensionDetailPage (cognitive 49) REDACTED:172— ExtensionDetailPage.ExtensionDetailPage has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 20, ternaries 12 (19 pts), if/else 8, error handling 2 (nesting depth added 7). Of this number, 40 points are the body's own statements and 9 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.
PreviewOverlay.PreviewOverlay (cognitive 48) apps/smithy-next/src/components/overlays/PreviewOverlay.tsx:41— PreviewOverlay.PreviewOverlay has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 21, ternaries 14 (19 pts), if/else 7, loops 1 (nesting depth added 5). Of this number, 37 points are the body's own statements and 11 belong to 14 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.
pools.createPoolRoutes (cognitive 48) packages/smithy/src/server/routes/pools.ts:16— pools.createPoolRoutes has cognitive complexity 48 (threshold 15). Drivers by points: if/else 22 (27 pts), error handling 7, boolean chains 6, loops 2 (4 pts), ternaries 3 (4 pts) (nesting depth added 8). Most of this is not in the body itself: 1 of the 48 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 127, 51, 167, …). 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.
WorkflowRunPage.WorkflowRunPage (cognitive 47) apps/smithy-next/src/components/overlays/automations/WorkflowRunPage.tsx:46— WorkflowRunPage.WorkflowRunPage has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 26, ternaries 14 (20 pts), if/else 1 (nesting depth added 6). Of this number, 43 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.
DispatchDaemonImpl.assignTaskToWorker (cognitive 46) packages/smithy/src/services/dispatch-daemon.ts:2711— DispatchDaemonImpl.assignTaskToWorker has cognitive complexity 46 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 5, ternaries 2 (5 pts), error handling 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlanDetailView.PlanDetailView (cognitive 45) apps/smithy-next/src/components/overlays/plans/PlanDetailView.tsx:40— PlanDetailView.PlanDetailView has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 31, ternaries 8 (12 pts), if/else 2 (nesting depth added 4). Of this number, 24 points are the body's own statements and 21 belong to 7 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.
InfiniteCanvas.InfiniteCanvas (cognitive 45) apps/smithy-next/src/components/overlays/sessions/canvas/InfiniteCanvas.tsx:26— InfiniteCanvas.InfiniteCanvas has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (27 pts), boolean chains 16, loops 1 (2 pts) (nesting depth added 10). None of this is in the body itself: all 45 points belong to 8 function literals inside it that branch (lines 63, 105, 139, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
plugin-registry.registerPluginCommands (cognitive 45) packages/quarry/src/cli/plugin-registry.ts:75— plugin-registry.registerPluginCommands has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (41 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 26). 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.
DispatchDaemonImpl.pollInboxes (cognitive 45) packages/smithy/src/services/dispatch-daemon.ts:938— DispatchDaemonImpl.pollInboxes has cognitive complexity 45 (threshold 15). Drivers by points: if/else 8 (24 pts), ternaries 4 (10 pts), error handling 3 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 26). 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.
(anonymous) (cognitive 45) REDACTED:1— (anonymous) has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 21, ternaries 13 (16 pts), if/else 5, error handling 2 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 3 of the 45 points are its own statements and the rest belongs to 42 function items inside it that branch (a function literal at line 1, (anonymous)::y, a function literal at line 1, …). 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.
task.describeHandler (cognitive 44) packages/quarry/src/cli/commands/task.ts:1016— task.describeHandler has cognitive complexity 44 (threshold 15). Drivers by points: if/else 23 (37 pts), ternaries 2 (4 pts), boolean chains 2, error handling 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.
HistoryEventItem.HistoryEventItem (cognitive 43) apps/quarry-web/src/routes/entities/components/HistoryEventItem.tsx:15— HistoryEventItem.HistoryEventItem has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 14, ternaries 6 (8 pts), match/switch 2 (nesting depth added 7). Most of this is not in the body itself: 8 of the 43 points are its own statements and the rest belongs to 9 function items inside it that branch (formatValue, getChangedFields, formatTimestamp, …). 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.
ActivityRail.ActivityRail (cognitive 43) apps/smithy-next/src/components/ActivityRail.tsx:79— ActivityRail.ActivityRail has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 35, if/else 6, ternaries 2. Of this number, 34 points are the body's own statements and 9 belong to 15 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.
WorkspacesOverlay.WorkspacesOverlay (cognitive 43) apps/smithy-next/src/components/overlays/WorkspacesOverlay.tsx:46— WorkspacesOverlay.WorkspacesOverlay has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 21, if/else 16, ternaries 6. Most of this is not in the body itself: 15 of the 43 points are its own statements and the rest belongs to 29 function literals inside it that branch (lines 86, 110, 61, …). 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.
task.taskMergeHandler (cognitive 43) packages/smithy/src/cli/commands/task.ts:386— task.taskMergeHandler has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (17 pts), error handling 8 (11 pts), ternaries 6 (11 pts), loops 1 (3 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.
MessageRichComposer.MessageRichComposer (cognitive 43) packages/ui/src/message/MessageRichComposer.tsx:134— MessageRichComposer.MessageRichComposer has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 11, ternaries 6 (7 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 43 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 238, 270, 304, …). 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.
utils.generateChangesPreview (cognitive 42) apps/quarry-web/src/routes/timeline/utils.ts:67— utils.generateChangesPreview has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 8, ternaries 1 (3 pts), loops 1 (2 pts) (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.
TaskDetailPanel.TaskDetailPanel (cognitive 42) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:99— TaskDetailPanel.TaskDetailPanel has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 29, if/else 10, error handling 3. Of this number, 31 points are the body's own statements and 11 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkspacePane.WorkspacePane (cognitive 42) apps/smithy-web/src/components/workspace/WorkspacePane.tsx:66— WorkspacePane.WorkspacePane has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 23, ternaries 9 (12 pts), if/else 4, error handling 3 (nesting depth added 3). Of this number, 31 points are the body's own statements and 11 belong to 7 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.
formatter.formatChanges (cognitive 42) packages/quarry/src/cli/formatter.ts:540— formatter.formatChanges has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 3 (10 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 19). 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.
merge.mergeHandler (cognitive 42) packages/smithy/src/cli/commands/merge.ts:78— merge.mergeHandler has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (21 pts), error handling 6 (10 pts), boolean chains 4, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 18). 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.
inbox.InboxMessageContent (cognitive 41) apps/quarry-web/src/routes/inbox.tsx:402— inbox.InboxMessageContent has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 20, ternaries 9 (15 pts), if/else 4, match/switch 2 (nesting depth added 6). Of this number, 27 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.
CIRunListView.CIRunListView (cognitive 41) apps/smithy-next/src/components/overlays/ci/CIRunListView.tsx:31— CIRunListView.CIRunListView has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 20, if/else 10 (12 pts), ternaries 6, match/switch 1 (2 pts), loops 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 25 belong to 14 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.
DesignModeOverlay.DesignModeOverlay (cognitive 41) apps/smithy-next/src/components/overlays/preview/DesignModeOverlay.tsx:20— DesignModeOverlay.DesignModeOverlay has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 14, ternaries 4 (7 pts) (nesting depth added 4). Most of this is not in the body itself: 12 of the 41 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 132, 86, 113, …). 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.
task-utils.taskSortCompareFn (cognitive 41) apps/smithy-web/src/lib/task-utils.tsx:126— task-utils.taskSortCompareFn has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 9 (20 pts), if/else 12 (15 pts), boolean chains 6 (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.
index.InboxMessageContent (cognitive 41) apps/smithy-web/src/routes/inbox/index.tsx:402— index.InboxMessageContent has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 20, ternaries 9 (15 pts), if/else 4, match/switch 2 (nesting depth added 6). Of this number, 27 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.
StewardSchedulerImpl.parseCronField (cognitive 41) REDACTED:1033— StewardSchedulerImpl.parseCronField has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 4 (10 pts), boolean chains 3, ternaries 1 (nesting depth added 23). 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.
task.taskSyncHandler (cognitive 41) packages/smithy/src/cli/commands/task.ts:746— task.taskSyncHandler has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (30 pts), error handling 4 (5 pts), ternaries 2 (3 pts), loops 1 (2 pts), boolean chains 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.
EmojiAutocomplete.fuzzySearchEmoji (cognitive 39) apps/quarry-web/src/components/editor/EmojiAutocomplete.tsx:642— EmojiAutocomplete.fuzzySearchEmoji has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 5 (9 pts), error handling 1 (3 pts), boolean chains 1 (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.
WorkflowListView.WorkflowListView (cognitive 39) apps/smithy-next/src/components/overlays/automations/WorkflowListView.tsx:47— WorkflowListView.WorkflowListView has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 18, if/else 11 (13 pts), ternaries 5, match/switch 1 (2 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 14 of the 39 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 68, 107, 111, …). 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.
ChannelDetailView.ChannelDetailView (cognitive 39) apps/smithy-next/src/components/overlays/messages/ChannelDetailView.tsx:121— ChannelDetailView.ChannelDetailView has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 14, ternaries 12 (13 pts), if/else 12 (nesting depth added 1). 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: 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.
DocEditorView.renderMarkdown (cognitive 39) apps/smithy-next/src/components/overlays/documents/DocEditorView.tsx:44— DocEditorView.renderMarkdown has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (33 pts), loops 2 (4 pts), boolean chains 2 (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.
SessionHistoryModal.SessionHistoryModal (cognitive 39) apps/smithy-web/src/components/workspace/SessionHistoryModal.tsx:335— SessionHistoryModal.SessionHistoryModal has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 10 (13 pts), boolean chains 9, error handling 1, loops 1 (nesting depth added 12). Most of this is not in the body itself: 9 of the 39 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 395, a function literal at line 358, a function literal at line 420, …). 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.
task.isTask (cognitive 39) packages/core/src/types/task.ts:464— task.isTask has cognitive complexity 39 (threshold 15). Drivers by points: if/else 25, boolean chains 14. 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.
task.taskListHandler (cognitive 39) packages/quarry/src/cli/commands/task.ts:1306— task.taskListHandler has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (27 pts), ternaries 3 (7 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 19). Of this number, 35 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
notion-blocks.markdownToNotionBlocks (cognitive 39) packages/quarry/src/external-sync/providers/notion/notion-blocks.ts:207— notion-blocks.markdownToNotionBlocks has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 4 (9 pts), boolean chains 5 (nesting depth added 19). 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.
playbook.playbookCreateHandler (cognitive 39) packages/quarry/src/cli/commands/playbook.ts:696— playbook.playbookCreateHandler has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 5 (14 pts), if/else 10 (11 pts), error handling 3 (7 pts), loops 2 (4 pts), boolean chains 3 (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.
DispatchDaemonImpl.spawnRecoveryStewardForTask (cognitive 39) packages/smithy/src/services/dispatch-daemon.ts:3393— DispatchDaemonImpl.spawnRecoveryStewardForTask has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (27 pts), error handling 3 (7 pts), loops 2 (4 pts), boolean chains 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.
AgentListView.AgentListView (cognitive 38) apps/smithy-next/src/components/overlays/agents/AgentListView.tsx:51— AgentListView.AgentListView has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 12, ternaries 5, match/switch 1 (2 pts), loops 1 (nesting depth added 7). Most of this is not in the body itself: 11 of the 38 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 112, 71, 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.
vsix-parser.getContributedFilePaths (cognitive 38) apps/smithy-web/src/lib/openvsx/vsix-parser.ts:324— vsix-parser.getContributedFilePaths has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 6 (12 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.startNodeServer (cognitive 38) REDACTED:146— server.startNodeServer has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (20 pts), ternaries 4 (9 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 154, 293, 209, …). 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.
MRListView.MRListView (cognitive 37) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:19— MRListView.MRListView has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 13, ternaries 5, match/switch 1 (2 pts), loops 1 (nesting depth added 5). Most of this is not in the body itself: 13 of the 37 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 32, 85, 91, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EditorExplorerPanel.TreeItem (cognitive 37) apps/smithy-next/src/components/overlays/editor/EditorExplorerPanel.tsx:250— EditorExplorerPanel.TreeItem has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 11 (13 pts), boolean chains 8 (nesting depth added 5). Of this number, 18 points are the body's own statements and 19 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
index.MetricsPage (cognitive 37) apps/smithy-web/src/routes/metrics/index.tsx:576— index.MetricsPage has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 18, ternaries 7 (10 pts), if/else 5 (7 pts), loops 2 (nesting depth added 5). Most of this is not in the body itself: 7 of the 37 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 680, 749, 721, …). 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.
LibraryTree.LibraryTree (cognitive 37) apps/smithy-web/src/routes/documents/components/LibraryTree.tsx:176— LibraryTree.LibraryTree has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 12 (14 pts), boolean chains 5, loops 3 (nesting depth added 6). Of this number, 18 points are the body's own statements and 19 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, 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.
index.MergeRequestsPage (cognitive 37) apps/smithy-web/src/routes/merge-requests/index.tsx:35— index.MergeRequestsPage has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 7 (12 pts), boolean chains 9, match/switch 1 (nesting depth added 14). Most of this is not in the body itself: 8 of the 37 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 90, 78, 73, …). 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.
external-sync.pushHandler (cognitive 37) packages/quarry/src/cli/commands/external-sync.ts:960— external-sync.pushHandler has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (21 pts), ternaries 4 (6 pts), boolean chains 5, loops 2 (4 pts), error handling 1 (nesting depth added 5). Of this number, 34 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MessageImageAttachment.MessageImageAttachment (cognitive 37) packages/ui/src/message/MessageImageAttachment.tsx:45— MessageImageAttachment.MessageImageAttachment has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 13, ternaries 4, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 12 of the 37 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 199, uploadFile, 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.
task-utils.taskSortCompareFn (cognitive 36) apps/quarry-web/src/lib/task-utils.tsx:125— task-utils.taskSortCompareFn has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 7 (15 pts), boolean chains 6 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SyncSection.SyncSection (cognitive 36) apps/quarry-web/src/routes/settings/components/SyncSection.tsx:17— SyncSection.SyncSection has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 10 (15 pts), if/else 10 (11 pts), boolean chains 8, error handling 1, loops 1 (nesting depth added 6). Of this number, 22 points are the body's own statements and 14 belong to 5 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.
DocEditorView.DocEditorView (cognitive 36) apps/smithy-next/src/components/overlays/documents/DocEditorView.tsx:371— DocEditorView.DocEditorView has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 10, if/else 9 (10 pts) (nesting depth added 5). Of this number, 17 points are the body's own statements and 19 belong to 8 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.
OnboardingTour.OnboardingTour (cognitive 36) apps/smithy-web/src/components/onboarding/OnboardingTour.tsx:545— OnboardingTour.OnboardingTour has cognitive complexity 36 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 9, loops 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 36 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 607, 570, 586, …). 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.
crud.listHandler (cognitive 36) packages/quarry/src/cli/commands/crud.ts:397— crud.listHandler has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (22 pts), ternaries 7 (8 pts), boolean chains 5, error handling 1 (nesting depth added 6). Of this number, 30 points are the body's own statements and 6 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.
MergeStewardServiceImpl.processTask (cognitive 36) packages/smithy/src/services/merge-steward-service.ts:439— MergeStewardServiceImpl.processTask has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (24 pts), error handling 4 (7 pts), boolean chains 3, ternaries 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.
CreateWorkflowModal.CreateWorkflowModal (cognitive 36) packages/ui/src/workflows/components/CreateWorkflowModal.tsx:228— CreateWorkflowModal.CreateWorkflowModal has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 13, loops 2 (4 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 8). Most of this is not in the body itself: 11 of the 36 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 261, a function literal at line 290, handleSubmit, …). 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.
ChannelListView.ChannelListView (cognitive 35) apps/smithy-next/src/components/overlays/messages/ChannelListView.tsx:19— ChannelListView.ChannelListView has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 18, ternaries 8 (9 pts), if/else 5, match/switch 1 (2 pts), loops 1 (nesting depth added 2). Of this number, 20 points are the body's own statements and 15 belong to 11 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.
CronScheduleBuilder.CronScheduleBuilder (cognitive 35) apps/smithy-web/src/components/agent/CronScheduleBuilder.tsx:271— CronScheduleBuilder.CronScheduleBuilder has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 8 (11 pts), boolean chains 8, loops 2 (nesting depth added 5). Most of this is not in the body itself: 11 of the 35 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 283, a function literal at line 341, formatHour, …). 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.
StartAgentDialog.StartAgentDialog (cognitive 35) apps/smithy-web/src/components/agent/StartAgentDialog.tsx:43— StartAgentDialog.StartAgentDialog has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 12, ternaries 8 (12 pts), if/else 7 (8 pts), error handling 2 (3 pts) (nesting depth added 6). Of this number, 16 points are the body's own statements and 19 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
registry.convertVSCodeThemeToMonaco (cognitive 35) apps/smithy-web/src/lib/extensions/registry.ts:214— registry.convertVSCodeThemeToMonaco has cognitive complexity 35 (threshold 15). Drivers by points: if/else 5 (15 pts), ternaries 3 (12 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 22). 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.
index.PlansPage (cognitive 35) apps/smithy-web/src/routes/plans/index.tsx:42— index.PlansPage has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 9 (19 pts), boolean chains 12, if/else 4 (nesting depth added 10). Of this number, 29 points are the body's own statements and 6 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.
log.logHandler (cognitive 35) packages/quarry/src/cli/commands/log.ts:163— log.logHandler has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (21 pts), ternaries 4 (7 pts), boolean chains 3, error handling 2 (3 pts), loops 1 (nesting depth added 8). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
PlanDetailPanel.PlanDetailPanel (cognitive 35) packages/ui/src/plans/components/PlanDetailPanel.tsx:76— PlanDetailPanel.PlanDetailPanel has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 12, error handling 5, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 13 of the 35 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 176, 116, 136, …). 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.
index.PlansPage (cognitive 34) apps/quarry-web/src/routes/plans/index.tsx:49— index.PlansPage has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 18, if/else 8 (9 pts), ternaries 6 (7 pts) (nesting depth added 2). Of this number, 19 points are the body's own statements and 15 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.
KanbanBoard.TaskCard (cognitive 34) apps/smithy-next/src/components/KanbanBoard.tsx:456— KanbanBoard.TaskCard has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 23, ternaries 7 (9 pts), if/else 2 (nesting depth added 2). Of this number, 29 points are the body's own statements and 5 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.
RichTextEditor.RichTextEditor (cognitive 34) apps/smithy-next/src/components/overlays/mr/RichTextEditor.tsx:13— RichTextEditor.RichTextEditor has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (25 pts), ternaries 5, boolean chains 4 (nesting depth added 10). Most of this is not in the body itself: 7 of the 34 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 145, a function literal at line 51, insertMarkdown, …). 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.
SessionListView.SessionListView (cognitive 34) apps/smithy-next/src/components/overlays/sessions/SessionListView.tsx:62— SessionListView.SessionListView has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 15, if/else 10 (12 pts), ternaries 5 (6 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 14 of the 34 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 122, 309, 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.
pools.createPoolRoutes (cognitive 34) apps/smithy-server/src/routes/pools.ts:15— pools.createPoolRoutes has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (19 pts), error handling 7, boolean chains 4, ternaries 3 (4 pts) (nesting depth added 2). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 117, 50, 148, …). 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.startNodeServer (cognitive 34) REDACTED:111— server.startNodeServer has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 4 (9 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 9). None of this is in the body itself: all 34 points belong to 8 function literals inside it that branch (lines 115, 253, 169, …). 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.
CronScheduleBuilder.describeCron (cognitive 34) apps/smithy-web/src/components/agent/CronScheduleBuilder.tsx:174— CronScheduleBuilder.describeCron has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 10, if/else 9 (nesting depth added 6). Of this number, 29 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
merge.diffConfigurations (cognitive 34) packages/quarry/src/config/merge.ts:225— merge.diffConfigurations has cognitive complexity 34 (threshold 15). Drivers by points: if/else 34. 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.
WorktreeManagerImpl.createWorktree (cognitive 34) REDACTED:426— WorktreeManagerImpl.createWorktree has cognitive complexity 34 (threshold 15). Drivers by points: error handling 10 (21 pts), if/else 9 (11 pts), boolean chains 1, ternaries 1 (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.
DocsStewardServiceImpl.verifyExports (cognitive 34) REDACTED:477— DocsStewardServiceImpl.verifyExports has cognitive complexity 34 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 4 (10 pts), error handling 1 (5 pts), boolean chains 1 (nesting depth added 23). 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.
pool.poolUpdateHandler (cognitive 34) packages/smithy/src/cli/commands/pool.ts:550— pool.poolUpdateHandler has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 8, ternaries 5 (8 pts), loops 1 (2 pts), error handling 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.
Sidebar.Sidebar (cognitive 33) apps/quarry-web/src/components/layout/Sidebar.tsx:117— Sidebar.Sidebar has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 16, ternaries 12 (13 pts), if/else 4 (nesting depth added 1). Most of this is not in the body itself: 13 of the 33 points are its own statements and the rest belongs to 3 function items inside it that branch (renderNavItem, renderSection, a function literal at line 134). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
InboxComponents.InboxMessageContent (cognitive 33) apps/quarry-web/src/routes/entities/components/InboxComponents.tsx:152— InboxComponents.InboxMessageContent has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 14, if/else 4 (nesting depth added 6). Of this number, 21 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlanListView.PlanListView (cognitive 33) apps/smithy-next/src/components/overlays/plans/PlanListView.tsx:27— PlanListView.PlanListView has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (9 pts), ternaries 8 (9 pts), match/switch 2 (3 pts), loops 2 (nesting depth added 4). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 89, 50, 74, …). 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.
WorkspacesOverlay.WorkspaceCard (cognitive 33) apps/smithy-next/src/components/overlays/WorkspacesOverlay.tsx:437— WorkspacesOverlay.WorkspaceCard has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 17 (26 pts), boolean chains 5, if/else 2 (nesting depth added 9). Of this number, 31 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useActiveAgentOutputs.useActiveAgentOutputs (cognitive 33) apps/smithy-web/src/api/hooks/useActiveAgentOutputs.ts:106— useActiveAgentOutputs.useActiveAgentOutputs has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (24 pts), loops 5 (6 pts), boolean chains 3 (nesting depth added 10). None of this is in the body itself: all 33 points belong to 3 function literals inside it that branch (lines 150, 113, 140). 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.
ExtensionCard.ExtensionCard (cognitive 33) apps/smithy-web/src/components/editor/ExtensionCard.tsx:59— ExtensionCard.ExtensionCard has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 10 (17 pts), boolean chains 11, if/else 5 (nesting depth added 7). Of this number, 27 points are the body's own statements and 6 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.
crud.showHandler (cognitive 33) packages/quarry/src/cli/commands/crud.ts:585— crud.showHandler has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 5, ternaries 2 (4 pts), error handling 2 (3 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SpawnerServiceImpl.processProviderMessages (cognitive 33) packages/smithy/src/runtime/spawner.ts:966— SpawnerServiceImpl.processProviderMessages has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 7, error handling 1, loops 1, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DispatchDaemonImpl.reapStaleSessions (cognitive 33) packages/smithy/src/services/dispatch-daemon.ts:2203— DispatchDaemonImpl.reapStaleSessions has cognitive complexity 33 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 3 (10 pts), error handling 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 19). 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.
ShortcutsSection.ShortcutEditModal (cognitive 33) packages/ui/src/settings/shortcuts/ShortcutsSection.tsx:33— ShortcutsSection.ShortcutEditModal has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 10, boolean chains 7 (nesting depth added 4). Most of this is not in the body itself: 14 of the 33 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 48, handleSave, a function literal at line 90). 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.
CreateChannelModal.CreateChannelModal (cognitive 33) packages/ui/src/message/CreateChannelModal.tsx:80— CreateChannelModal.CreateChannelModal has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 15, if/else 9 (12 pts), ternaries 5, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 14 of the 33 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 100, a function literal at line 107, …). 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.
KanbanBoard.ListRow (cognitive 32) apps/smithy-next/src/components/KanbanBoard.tsx:585— KanbanBoard.ListRow has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 22, ternaries 7 (8 pts), if/else 2 (nesting depth added 1). Of this number, 27 points are the body's own statements and 5 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.
manager.installExtension (cognitive 32) apps/smithy-web/src/lib/extensions/manager.ts:146— manager.installExtension has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 9 (10 pts), error handling 6 (9 pts), boolean chains 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.
EditPoolDialog.EditPoolDialog (cognitive 32) apps/smithy-web/src/components/pool/EditPoolDialog.tsx:75— EditPoolDialog.EditPoolDialog has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 12 (13 pts), boolean chains 10, if/else 5 (7 pts), error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 9 of the 32 points are its own statements and the rest belongs to 4 function items inside it that branch (handleSubmit, a function literal at line 145, a function literal at line 83, …). 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.
plan.planAutoCompleteHandler (cognitive 32) packages/quarry/src/cli/commands/plan.ts:859— plan.planAutoCompleteHandler has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 4 (9 pts), loops 3 (5 pts), error handling 2 (3 pts), boolean chains 1 (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.
SpawnerServiceImpl.terminate (cognitive 32) packages/smithy/src/runtime/spawner.ts:572— SpawnerServiceImpl.terminate has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (27 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 13). Of this number, 19 points are the body's own statements and 13 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.
DispatchDaemonImpl.recoverStuckMergeTasks (cognitive 32) packages/smithy/src/services/dispatch-daemon.ts:1647— DispatchDaemonImpl.recoverStuckMergeTasks has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 4 (9 pts), error handling 3 (5 pts), loops 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.
Sidebar.Sidebar (cognitive 32) packages/ui/src/layout/Sidebar.tsx:120— Sidebar.Sidebar has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 16, ternaries 12 (13 pts), if/else 3 (nesting depth added 1). Most of this is not in the body itself: 14 of the 32 points are its own statements and the rest belongs to 3 function items inside it that branch (renderNavItem, renderSection, a function literal at line 139). 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.
Pagination.Pagination (cognitive 31) apps/quarry-web/src/components/shared/Pagination.tsx:28— Pagination.Pagination has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 7 (10 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 10). Of this number, 16 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KanbanBoard.FilterPanel (cognitive 31) apps/smithy-next/src/components/KanbanBoard.tsx:831— KanbanBoard.FilterPanel has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 13, if/else 7 (9 pts), ternaries 6 (8 pts), match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 13 function items inside it that branch (getCounts, a function literal at line 857, getDisplayName, …). 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.
PreviewConfigDialog.PreviewConfigDialog (cognitive 31) apps/smithy-next/src/components/overlays/PreviewConfigDialog.tsx:11— PreviewConfigDialog.PreviewConfigDialog has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 15, ternaries 8 (13 pts), if/else 3 (nesting depth added 5). Of this number, 19 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsOverlay.OrganizationSection (cognitive 31) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:619— SettingsOverlay.OrganizationSection has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 12, ternaries 10, if/else 7 (9 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 827, a function literal at line 636, commitRename, …). 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.
RuntimeDetailView.RuntimeDetailView (cognitive 31) apps/smithy-next/src/components/overlays/runtimes/RuntimeDetailView.tsx:30— RuntimeDetailView.RuntimeDetailView has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 28, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 27 points are the body's own statements and 4 belong to 4 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.
CreateAgentDialog.CreateAgentDialog (cognitive 31) REDACTED:195— CreateAgentDialog.CreateAgentDialog has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 25, ternaries 15 (22 pts), if/else 11 (13 pts), error handling 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 (CreateAgentDialog.CreateAgentDialog::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
playbook.isPlaybook (cognitive 31) packages/core/src/types/playbook.ts:1251— playbook.isPlaybook has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (24 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 6). 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.
QuarryAPIImpl.listPaginated (cognitive 31) packages/quarry/src/api/quarry-api.ts:711— QuarryAPIImpl.listPaginated has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 10 (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.
SyncEngine.pullItem (cognitive 31) packages/quarry/src/external-sync/sync-engine.ts:745— SyncEngine.pullItem has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (6 pts), boolean chains 4 (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.
gc.gcWorkflowsHandler (cognitive 31) packages/quarry/src/cli/commands/gc.ts:158— gc.gcWorkflowsHandler has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 6 (10 pts), boolean chains 3, error handling 1 (nesting depth added 10). Of this number, 21 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.
KanbanBoard.KanbanBoard (cognitive 30) apps/quarry-web/src/components/task/KanbanBoard.tsx:844— KanbanBoard.KanbanBoard has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 13, loops 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (handleDragEnd, a function literal at line 884, a function literal at line 852, …). 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.
ThemeSection.ThemeSection (cognitive 30) apps/quarry-web/src/routes/settings/components/ThemeSection.tsx:73— ThemeSection.ThemeSection has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 17 (28 pts), boolean chains 1, if/else 1 (nesting depth added 11). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionDetailView.SessionDetailView (cognitive 30) apps/smithy-next/src/components/overlays/sessions/SessionDetailView.tsx:39— SessionDetailView.SessionDetailView has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 13 (14 pts), boolean chains 11, if/else 5 (nesting depth added 1). Of this number, 24 points are the body's own statements and 6 belong to 8 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Sidebar.Sidebar (cognitive 30) apps/smithy-web/src/components/layout/Sidebar.tsx:108— Sidebar.Sidebar has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, ternaries 12 (13 pts), if/else 3 (nesting depth added 1). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 4 function items inside it that branch (renderNavItem, renderSection, a function literal at line 121, …). 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.
InboxService.buildFilterQuery (cognitive 30) packages/quarry/src/services/inbox.ts:467— InboxService.buildFilterQuery has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 2 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dep.depListHandler (cognitive 30) packages/quarry/src/cli/commands/dep.ts:325— dep.depListHandler has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 8, ternaries 2 (3 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SyncEngine.pull (cognitive 30) packages/quarry/src/external-sync/sync-engine.ts:560— SyncEngine.pull has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4 (8 pts), error handling 2 (6 pts), loops 2 (4 pts), boolean chains 3 (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.
external-sync.statusHandler (cognitive 30) packages/quarry/src/cli/commands/external-sync.ts:1461— external-sync.statusHandler has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 5 (7 pts), ternaries 3 (6 pts), error handling 2, 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.
serve.startSmithy (cognitive 30) REDACTED:381— serve.startSmithy has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 7 (8 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (2 pts) (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.
SessionManagerImpl.listSessions (cognitive 30) packages/smithy/src/runtime/session-manager.ts:895— SessionManagerImpl.listSessions has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (25 pts), ternaries 1 (3 pts), boolean chains 1, loops 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.
DispatchDaemonImpl.pollWorkflowTasks (cognitive 30) packages/smithy/src/services/dispatch-daemon.ts:1076— DispatchDaemonImpl.pollWorkflowTasks has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 4 (9 pts), error handling 3 (5 pts), loops 3, boolean chains 1 (nesting depth added 13). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pool.parseAgentTypeConfig (cognitive 30) packages/smithy/src/cli/commands/pool.ts:75— pool.parseAgentTypeConfig has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 8 (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.
CreateActionDialog.CreateActionDialog (cognitive 29) apps/smithy-next/src/components/overlays/ci/CreateActionDialog.tsx:132— CreateActionDialog.CreateActionDialog has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 13, ternaries 10 (12 pts), if/else 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 279, addTrigger, handleSubmit, …). 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.
CILogViewer.CILogViewer (cognitive 29) apps/smithy-next/src/components/overlays/ci/CILogViewer.tsx:10— CILogViewer.CILogViewer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 10, ternaries 7 (8 pts) (nesting depth added 4). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 103, getLineColor, a function literal at line 25, …). 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.
WorkflowPipelineViz.WorkflowPipelineViz (cognitive 29) apps/smithy-next/src/components/overlays/automations/WorkflowPipelineViz.tsx:15— WorkflowPipelineViz.WorkflowPipelineViz has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 7 (8 pts), boolean chains 7, loops 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 97, a function literal at line 129, getDepth, …). 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.
WorkflowRunTimeline.WorkflowRunTimeline (cognitive 29) apps/smithy-next/src/components/overlays/automations/WorkflowRunTimeline.tsx:33— WorkflowRunTimeline.WorkflowRunTimeline has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 13 (24 pts), boolean chains 4, loops 1 (nesting depth added 11). Of this number, 17 points are the body's own statements and 12 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CreateAgentView.CreateAgentView (cognitive 29) apps/smithy-next/src/components/overlays/agents/CreateAgentView.tsx:26— CreateAgentView.CreateAgentView has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (10 pts), ternaries 7 (8 pts) (nesting depth added 3). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 93, a function literal at line 93, a function literal at line 131, …). 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.
CreatePoolDialog.CreatePoolDialog (cognitive 29) apps/smithy-web/src/components/pool/CreatePoolDialog.tsx:49— CreatePoolDialog.CreatePoolDialog has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 8, if/else 5 (7 pts), error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 29 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSubmit, a function literal at line 114, a function literal at line 77). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
terminal.PopoutTerminalPage (cognitive 29) apps/smithy-web/src/routes/popout/terminal.tsx:32— terminal.PopoutTerminalPage has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 11, ternaries 7 (10 pts), if/else 6, error handling 2 (nesting depth added 3). Of this number, 22 points are the body's own statements and 7 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.
BlockedCacheService.computeBlockingState (cognitive 29) packages/quarry/src/services/blocked-cache.ts:396— BlockedCacheService.computeBlockingState has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (21 pts), error handling 1 (4 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 19). 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.
QuarryAPIImpl.getOrderedTasksInWorkflow (cognitive 29) packages/quarry/src/api/quarry-api.ts:4285— QuarryAPIImpl.getOrderedTasksInWorkflow has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 8 (9 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SyncEngine.pullDocumentItem (cognitive 29) packages/quarry/src/external-sync/sync-engine.ts:987— SyncEngine.pullDocumentItem has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 2 (6 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.
ClaudeHeadlessSession.createMessageIterator (cognitive 29) packages/smithy/src/providers/claude/headless.ts:138— ClaudeHeadlessSession.createMessageIterator has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 2 (5 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (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.
DispatchDaemonImpl.processInboxItem (cognitive 29) packages/smithy/src/services/dispatch-daemon.ts:3729— DispatchDaemonImpl.processInboxItem has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 5 (nesting depth added 13). 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.
ResponsiveModal.ResponsiveModal (cognitive 29) packages/ui/src/layout/ResponsiveModal.tsx:47— ResponsiveModal.ResponsiveModal has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16, boolean chains 11, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 10 function items inside it that branch (handleTouchMove, handleTouchEnd, a function literal at line 90, …). 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.
CreateTeamModal.CreateTeamModal (cognitive 28) apps/quarry-web/src/components/team/CreateTeamModal.tsx:92— CreateTeamModal.CreateTeamModal has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 12, if/else 8, ternaries 7, error handling 1. Of this number, 15 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DemoModeSection.DemoModeSection (cognitive 28) apps/quarry-web/src/routes/settings/components/DemoModeSection.tsx:31— DemoModeSection.DemoModeSection has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 6 (15 pts), boolean chains 7, if/else 6 (nesting depth added 9). Of this number, 22 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DirectorPanel.CrossWorkspaceThreadsView (cognitive 28) apps/smithy-next/src/components/DirectorPanel.tsx:1115— DirectorPanel.CrossWorkspaceThreadsView has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 10 (16 pts), boolean chains 8, if/else 2 (4 pts) (nesting depth added 8). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1196, 1159, 1170, …). 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.
CIRunHeader.CIRunHeader (cognitive 28) apps/smithy-next/src/components/overlays/ci/CIRunHeader.tsx:31— CIRunHeader.CIRunHeader has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 16, ternaries 8 (12 pts) (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CIRunDetailView.CIRunDetailView (cognitive 28) apps/smithy-next/src/components/overlays/ci/CIRunDetailView.tsx:29— CIRunDetailView.CIRunDetailView has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 13, ternaries 10 (11 pts), if/else 4 (nesting depth added 1). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 112, 45, 62, …). 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.
WorkflowCreateView.WorkflowCreateView (cognitive 28) apps/smithy-next/src/components/overlays/automations/WorkflowCreateView.tsx:75— WorkflowCreateView.WorkflowCreateView has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 21, ternaries 7. Of this number, 23 points are the body's own statements and 5 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SessionDetailHeader.SessionDetailHeader (cognitive 28) apps/smithy-next/src/components/overlays/sessions/SessionDetailHeader.tsx:51— SessionDetailHeader.SessionDetailHeader has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 10 (13 pts), boolean chains 9, if/else 6 (nesting depth added 3). Of this number, 15 points are the body's own statements and 13 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocVersionHistory.DocVersionHistory (cognitive 28) apps/smithy-next/src/components/overlays/documents/DocVersionHistory.tsx:23— DocVersionHistory.DocVersionHistory has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 8 (18 pts), if/else 3 (6 pts), boolean chains 4 (nesting depth added 13). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 61, 76, 79, …). 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.
CommandPalette.CommandPalette (cognitive 28) apps/smithy-next/src/components/CommandPalette.tsx:39— CommandPalette.CommandPalette has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 8 (11 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 234, 114, 76, …). 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.
useKeyboardShortcuts.useGlobalKeyboardShortcuts (cognitive 28) apps/smithy-web/src/hooks/useKeyboardShortcuts.ts:58— useKeyboardShortcuts.useGlobalKeyboardShortcuts has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 1, loops 1 (nesting depth added 14). None of this is in the body itself: all 28 points belong to 2 function literals inside it that branch (lines 82, 65). 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.
merge.mergeConfiguration (cognitive 28) packages/quarry/src/config/merge.ts:72— merge.mergeConfiguration has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 28. 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.
config.mergeTrackedConfig (cognitive 28) packages/quarry/src/config/config.ts:366— config.mergeTrackedConfig has cognitive complexity 28 (threshold 15). Drivers by points: if/else 28. 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.
external-sync.pullHandler (cognitive 28) packages/quarry/src/cli/commands/external-sync.ts:1160— external-sync.pullHandler has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (16 pts), ternaries 4 (6 pts), loops 3 (5 pts), error handling 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.
SpawnerServiceImpl.parseAndEmitEvent (cognitive 28) packages/smithy/src/runtime/spawner.ts:1231— SpawnerServiceImpl.parseAndEmitEvent has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 7, loops 1 (2 pts), error handling 1, ternaries 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.
WorktreeManagerImpl.installDependencies (cognitive 28) REDACTED:1050— WorktreeManagerImpl.installDependencies has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 6 (14 pts), error handling 3 (6 pts), if/else 6, boolean chains 2 (nesting depth added 11). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkflowEditorModal.formDataToStep (cognitive 28) packages/ui/src/workflows/components/WorkflowEditorModal.tsx:116— WorkflowEditorModal.formDataToStep has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (27 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.
MRListView.MRFilterPanel (cognitive 27) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:246— MRListView.MRFilterPanel has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 13, ternaries 7 (11 pts), if/else 2, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 18 function items inside it that branch (a function literal at line 276, a function literal at line 305, a function literal at line 253, …). 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.
SessionHistoryModal.extractSessionName (cognitive 27) apps/smithy-web/src/components/workspace/SessionHistoryModal.tsx:164— SessionHistoryModal.extractSessionName has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3, ternaries 2, 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.
channel.channelCreateHandler (cognitive 27) packages/quarry/src/cli/commands/channel.ts:97— channel.channelCreateHandler has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 8, ternaries 1 (2 pts), error handling 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.
document.docUpdateHandler (cognitive 27) packages/quarry/src/cli/commands/document.ts:624— document.docUpdateHandler has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 4, error handling 2 (3 pts), ternaries 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.
docs.docsAddHandler (cognitive 27) packages/quarry/src/cli/commands/docs.ts:248— docs.docsAddHandler has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 3 (6 pts), error handling 2 (3 pts), loops 2, 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.
settings.createSettingsRoutes (cognitive 27) packages/smithy/src/server/routes/settings.ts:23— settings.createSettingsRoutes has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (14 pts), error handling 7, boolean chains 4, loops 1 (2 pts) (nesting depth added 3). None of this is in the body itself: all 27 points belong to 7 function literals inside it that branch (lines 39, 194, 111, …). 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.
MRHeader.MRHeader (cognitive 26) apps/smithy-next/src/components/overlays/mr/MRHeader.tsx:19— MRHeader.MRHeader has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12 (19 pts), boolean chains 5, if/else 2 (nesting depth added 7). Of this number, 21 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workflow.isWorkflow (cognitive 26) packages/core/src/types/workflow.ts:357— workflow.isWorkflow has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18, boolean chains 8. 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.
LinearApiClient.graphql (cognitive 26) packages/quarry/src/external-sync/providers/linear/linear-api.ts:273— LinearApiClient.graphql has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 6 (8 pts), error handling 3 (4 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
external-sync.linkHandler (cognitive 26) packages/quarry/src/cli/commands/external-sync.ts:530— external-sync.linkHandler has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 3 (6 pts), error handling 2, 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.
identity.verifyHandler (cognitive 26) packages/quarry/src/cli/commands/identity.ts:496— identity.verifyHandler has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (16 pts), ternaries 3 (7 pts), error handling 2 (3 pts) (nesting depth added 6). 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.
document.docCreateHandler (cognitive 26) packages/quarry/src/cli/commands/document.ts:89— document.docCreateHandler has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 7, error handling 2 (3 pts), ternaries 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.
inbox.inboxListHandler (cognitive 26) packages/quarry/src/cli/commands/inbox.ts:118— inbox.inboxListHandler has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (17 pts), ternaries 3 (5 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 6). Of this number, 23 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils-vendor-CfYKiENT.Oc (cognitive 26) REDACTED:1— utils-vendor-CfYKiENT.Oc has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 22, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 23 points are the body's own statements and 3 belong to 14 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.
UserSelector.UserSelector (cognitive 26) packages/ui/src/domain/UserSelector.tsx:22— UserSelector.UserSelector has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4 (7 pts), boolean chains 6, match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 96, 55, 68, …). 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.
StatusPieChart.StatusPieChart (cognitive 26) packages/ui/src/visualizations/StatusPieChart.tsx:68— StatusPieChart.StatusPieChart has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 12, ternaries 8 (9 pts), if/else 5 (nesting depth added 1). Of this number, 13 points are the body's own statements and 13 belong to 5 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
usePlanApi.useCreatePlan (cognitive 26) packages/ui/src/plans/hooks/usePlanApi.ts:233— usePlanApi.useCreatePlan has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 7, error handling 2 (5 pts) (nesting depth added 10). None of this is in the body itself: all 26 points belong to 2 function literals inside it that branch (lines 274, 236). 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.
PlanDetailPanel.PlanDetailPanel (cognitive 25) apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx:64— PlanDetailPanel.PlanDetailPanel has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, error handling 4, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 94, 114, 204, …). 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.
SessionFilterPanel.SessionFilterPanel (cognitive 25) apps/smithy-next/src/components/overlays/sessions/SessionFilterPanel.tsx:23— SessionFilterPanel.SessionFilterPanel has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 5, boolean chains 4, loops 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 95, 28, 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.
CreateDocumentDialog.CreateDocumentDialog (cognitive 25) apps/smithy-next/src/components/overlays/documents/CreateDocumentDialog.tsx:34— CreateDocumentDialog.CreateDocumentDialog has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 9, ternaries 8 (9 pts), if/else 6 (7 pts) (nesting depth added 2). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (handleTagKeyDown, handleCreate, a function literal at line 169, …). 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.
AgentCard.AgentCard (cognitive 25) apps/smithy-web/src/components/agent/AgentCard.tsx:34— AgentCard.AgentCard has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 19, ternaries 4, if/else 2. Of this number, 22 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
event.isValidEventFilter (cognitive 25) packages/core/src/types/event.ts:411— event.isValidEventFilter has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 11 (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.
event.validateEventFilter (cognitive 25) packages/core/src/types/event.ts:463— event.validateEventFilter has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 7 (nesting depth added 5). Of this number, 22 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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.
BlockedCacheService.rebuild (cognitive 25) packages/quarry/src/services/blocked-cache.ts:882— BlockedCacheService.rebuild has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 8 (9 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.
reset.resetHandler (cognitive 25) packages/quarry/src/cli/commands/reset.ts:186— reset.resetHandler has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 2 (4 pts), error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
admin.buildDoctorResult (cognitive 25) packages/quarry/src/cli/commands/admin.ts:708— admin.buildDoctorResult has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 6 (7 pts), loops 3 (6 pts), boolean chains 2 (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.
playbook.playbookShowHandler (cognitive 25) packages/quarry/src/cli/commands/playbook.ts:153— playbook.playbookShowHandler has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11, ternaries 4 (8 pts), boolean chains 5, error handling 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 7 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.
completion.generateFishCompletion (cognitive 25) packages/quarry/src/cli/completion.ts:229— completion.generateFishCompletion has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (12 pts), loops 4 (8 pts), if/else 2 (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.
DispatchDaemonImpl.runPollCycle (cognitive 25) packages/smithy/src/services/dispatch-daemon.ts:2036— DispatchDaemonImpl.runPollCycle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (24 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.
external-sync.createExternalSyncRoutes (cognitive 25) packages/smithy/src/server/routes/external-sync.ts:24— external-sync.createExternalSyncRoutes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, error handling 5, loops 1 (nesting depth added 6). None of this is in the body itself: all 25 points belong to 5 function literals inside it that branch (lines 145, 57, 112, …). 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.
WorkflowRunDetail.WorkflowRunDetail (cognitive 24) apps/smithy-next/src/components/overlays/automations/WorkflowRunDetail.tsx:33— WorkflowRunDetail.WorkflowRunDetail has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, ternaries 8 (11 pts) (nesting depth added 3). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentSettingsTab.AgentSettingsTab (cognitive 24) apps/smithy-next/src/components/overlays/agents/AgentSettingsTab.tsx:28— AgentSettingsTab.AgentSettingsTab has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 7 (9 pts), ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 69, 61, 124, …). 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.
AgentsOverlay.AgentsOverlay::renderView (cognitive 24) apps/smithy-next/src/components/overlays/AgentsOverlay.tsx:204— AgentsOverlay.AgentsOverlay::renderView has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (9 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CreateTaskDialog.CreateTaskDialog (cognitive 24) apps/smithy-next/src/components/CreateTaskDialog.tsx:15— CreateTaskDialog.CreateTaskDialog has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11, boolean chains 9, if/else 4. Of this number, 14 points are the body's own statements and 10 belong to 8 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
language-detection.detectLanguageFromContentType (cognitive 24) apps/smithy-web/src/lib/language-detection.ts:345— language-detection.detectLanguageFromContentType has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15, boolean chains 9. 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.
ApprovalRequestCard.ApprovalRequestCard (cognitive 24) apps/smithy-web/src/components/notification/ApprovalRequestCard.tsx:79— ApprovalRequestCard.ApprovalRequestCard has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (17 pts), boolean chains 7 (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.
model-pricing.lookupModelPricing (cognitive 24) packages/core/src/config/model-pricing.ts:86— model-pricing.lookupModelPricing has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 4 (7 pts), boolean chains 2 (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.
history.historyHandler (cognitive 24) packages/quarry/src/cli/commands/history.ts:66— history.historyHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
channel.channelRemoveHandler (cognitive 24) packages/quarry/src/cli/commands/channel.ts:647— channel.channelRemoveHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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.
document.docShowHandler (cognitive 24) packages/quarry/src/cli/commands/document.ts:771— document.docShowHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2, ternaries 1 (2 pts), error handling 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.
tasks.createTaskRoutes (cognitive 24) packages/shared-routes/src/tasks.ts:12— tasks.createTaskRoutes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 4 (6 pts), boolean chains 5, loops 3 (nesting depth added 5). None of this is in the body itself: all 24 points belong to 2 function literals inside it that branch (lines 27, 100). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
agent.agentListHandler (cognitive 24) packages/smithy/src/cli/commands/agent.ts:175— agent.agentListHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 5). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
agent.agentStartHandler (cognitive 24) packages/smithy/src/cli/commands/agent.ts:886— agent.agentStartHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 5 (6 pts), boolean chains 2, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
services.initializeServices::onSessionStarted::onResultEvent (cognitive 24) packages/smithy/src/server/services.ts:409— services.initializeServices::onSessionStarted::onResultEvent has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MobileDocumentFilter.MobileDocumentFilter (cognitive 24) packages/ui/src/documents/components/MobileDocumentFilter.tsx:20— MobileDocumentFilter.MobileDocumentFilter has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14, boolean chains 6, ternaries 4. Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 13 function items inside it that branch (handleTouchMove, handleTouchEnd, 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.
BlockEditor.BlockEditor (cognitive 23) apps/quarry-web/src/components/editor/BlockEditor.tsx:161— BlockEditor.BlockEditor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 9, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 279, 267, 350, …). 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.
MRDiffViewer.SplitDiffView (cognitive 23) apps/smithy-next/src/components/overlays/mr/MRDiffViewer.tsx:341— MRDiffViewer.SplitDiffView has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 10 (12 pts), if/else 6 (9 pts), boolean chains 1, loops 1 (nesting depth added 5). None of this is in the body itself: all 23 points belong to 3 function literals inside it that branch (lines 344, 383, 402). 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.
MRReviewSidebar.MRReviewSidebar (cognitive 23) apps/smithy-next/src/components/overlays/mr/MRReviewSidebar.tsx:31— MRReviewSidebar.MRReviewSidebar has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 16, ternaries 3 (5 pts), if/else 2 (nesting depth added 2). Of this number, 14 points are the body's own statements and 9 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.
EditorFuzzyFinder.EditorFuzzyFinder (cognitive 23) apps/smithy-next/src/components/overlays/editor/EditorFuzzyFinder.tsx:24— EditorFuzzyFinder.EditorFuzzyFinder has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 6, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, a function literal at line 37, a function literal at line 140, …). 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.
WorkflowStepCard.WorkflowStepCard (cognitive 23) apps/smithy-next/src/components/overlays/automations/WorkflowStepCard.tsx:20— WorkflowStepCard.WorkflowStepCard has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, ternaries 8, if/else 2. Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ChangeTriggerDialog.ChangeTriggerDialog (cognitive 23) apps/smithy-web/src/components/agent/ChangeTriggerDialog.tsx:22— ChangeTriggerDialog.ChangeTriggerDialog has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 5 (7 pts), boolean chains 5, error handling 1, loops 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 34, a function literal at line 57, …). 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.
FileContentSearch.FileContentSearch (cognitive 23) apps/smithy-web/src/components/command/FileContentSearch.tsx:235— FileContentSearch.FileContentSearch has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 16, if/else 6, ternaries 1. Of this number, 16 points are the body's own statements and 7 belong to 4 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.
CreateTaskModal.CreateTaskModal (cognitive 23) apps/smithy-web/src/components/task/CreateTaskModal.tsx:48— CreateTaskModal.CreateTaskModal has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, if/else 7, ternaries 4 (5 pts), error handling 1 (nesting depth added 1). Of this number, 12 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Pagination.Pagination (cognitive 23) apps/smithy-web/src/components/shared/Pagination.tsx:27— Pagination.Pagination has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (7 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (getPageNumbers, a function literal at line 149). 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.
SyncEngine.pullDocumentsFromProvider (cognitive 23) packages/quarry/src/external-sync/sync-engine.ts:889— SyncEngine.pullDocumentsFromProvider has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (2 pts), loops 2 (nesting depth added 8). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MergeStewardServiceImpl.checkPendingApprovals (cognitive 23) packages/smithy/src/services/merge-steward-service.ts:1022— MergeStewardServiceImpl.checkPendingApprovals has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (6 pts), ternaries 1 (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.
DispatchDaemonImpl.reconcileClosedUnmergedTasks (cognitive 23) packages/smithy/src/services/dispatch-daemon.ts:1547— DispatchDaemonImpl.reconcileClosedUnmergedTasks has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 4 (9 pts), error handling 2 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkflowDetailPanel.WorkflowDetailPanel (cognitive 23) packages/ui/src/workflows/components/WorkflowDetailPanel.tsx:76— WorkflowDetailPanel.WorkflowDetailPanel has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 7, error handling 4, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 106, 126, 220, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CreateTaskModal.CreateTaskModal (cognitive 22) apps/quarry-web/src/components/task/CreateTaskModal.tsx:102— CreateTaskModal.CreateTaskModal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10, boolean chains 7, ternaries 3 (4 pts), error handling 1 (nesting depth added 1). Of this number, 11 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MRListView.MRRow (cognitive 22) apps/smithy-next/src/components/overlays/mr/MRListView.tsx:426— MRListView.MRRow has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (17 pts), boolean chains 3, if/else 2 (nesting depth added 8). Of this number, 20 points are the body's own statements and 2 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.
AgentDetailView.AgentDetailView (cognitive 22) apps/smithy-next/src/components/overlays/agents/AgentDetailView.tsx:39— AgentDetailView.AgentDetailView has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, ternaries 6, if/else 2. Of this number, 16 points are the body's own statements and 6 belong to 4 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.
App._unused_TaskDetail (cognitive 22) apps/smithy-next/src/App.tsx:1145— App._unused_TaskDetail has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 21 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PoolCard.PoolCard (cognitive 22) apps/smithy-web/src/components/pool/PoolCard.tsx:16— PoolCard.PoolCard has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (13 pts), boolean chains 9 (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.
document.isDocument (cognitive 22) packages/core/src/types/document.ts:388— document.isDocument has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17, boolean chains 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
types.isValidElementFilter (cognitive 22) packages/quarry/src/api/types.ts:1602— types.isValidElementFilter has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7 (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.
BlockedCacheService.invalidateElement (cognitive 22) packages/quarry/src/services/blocked-cache.ts:491— BlockedCacheService.invalidateElement has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6 (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.
QuarryAPIImpl.garbageCollectWorkflows (cognitive 22) packages/quarry/src/api/quarry-api.ts:4011— QuarryAPIImpl.garbageCollectWorkflows has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (7 pts), boolean chains 1, ternaries 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.
QuarryAPIImpl.hydrateMessages (cognitive 22) packages/quarry/src/api/quarry-api.ts:5385— QuarryAPIImpl.hydrateMessages has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 8). Of this number, 11 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plugin-types.isValidCLIPlugin (cognitive 22) packages/quarry/src/cli/plugin-types.ts:149— plugin-types.isValidCLIPlugin has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
external-sync.syncHandler (cognitive 22) packages/quarry/src/cli/commands/external-sync.ts:1333— external-sync.syncHandler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11, ternaries 4 (6 pts), loops 2 (4 pts), error handling 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.
SessionManagerImpl.reconcileOnStartup (cognitive 22) packages/smithy/src/runtime/session-manager.ts:1243— SessionManagerImpl.reconcileOnStartup has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 2 (5 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionManagerImpl.setupSessionEventForwarding (cognitive 22) packages/smithy/src/runtime/session-manager.ts:1415— SessionManagerImpl.setupSessionEventForwarding has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (15 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 4). None of this is in the body itself: all 22 points belong to 8 function items inside it that branch (onExit, onProviderSessionId, onEvent, …). 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.
WorktreeManagerImpl.removeWorktree (cognitive 22) REDACTED:671— WorktreeManagerImpl.removeWorktree has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 4 (7 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.
EntityLink.EntityLink (cognitive 22) packages/ui/src/domain/EntityLink.tsx:172— EntityLink.EntityLink has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (14 pts), boolean chains 6, if/else 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.
ActivityFeedItem.ActivityFeedItem (cognitive 21) apps/quarry-web/src/routes/entities/components/ActivityFeedItem.tsx:23— ActivityFeedItem.ActivityFeedItem has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9, boolean chains 8, match/switch 4. None of this is in the body itself: all 21 points belong to 4 function items inside it that branch (getDescription, formatTime, getEventIcon, …). 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.
BottomPanel.BottomPanel (cognitive 21) apps/smithy-next/src/components/BottomPanel.tsx:21— BottomPanel.BottomPanel has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 5, match/switch 1. Of this number, 11 points are the body's own statements and 10 belong to 12 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentListView.AgentRow (cognitive 21) apps/smithy-next/src/components/overlays/agents/AgentListView.tsx:287— AgentListView.AgentRow has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 14 (19 pts), boolean chains 2 (nesting depth added 5). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsOverlay.RolesAccessSection (cognitive 21) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1277— SettingsOverlay.RolesAccessSection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 3 (4 pts), boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 1312, isChecked, a function literal at line 1321, …). 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.
AgentNode.AgentNodeComponent (cognitive 21) apps/smithy-web/src/components/agent-graph/AgentNode.tsx:79— AgentNode.AgentNodeComponent has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 15, ternaries 6. 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.
DirectorTabContent.DirectorTabContent (cognitive 21) apps/smithy-web/src/components/layout/DirectorTabContent.tsx:29— DirectorTabContent.DirectorTabContent has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 5, ternaries 3 (4 pts), error handling 2 (nesting depth added 1). 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 literals inside it that branch (lines 57, 43, 86, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MergeRequestDetailPanel.MergeRequestDetailPanel (cognitive 21) apps/smithy-web/src/components/merge-request/MergeRequestDetailPanel.tsx:42— MergeRequestDetailPanel.MergeRequestDetailPanel has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 17, if/else 2, ternaries 2. 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.
QuarryAPIImpl.bulkTagPlanTasks (cognitive 21) packages/quarry/src/api/quarry-api.ts:2337— QuarryAPIImpl.bulkTagPlanTasks has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 3 (5 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
task.reopenHandler (cognitive 21) packages/quarry/src/cli/commands/task.ts:547— task.reopenHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 6). 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.
dep.depAddHandler (cognitive 21) packages/quarry/src/cli/commands/dep.ts:50— dep.depAddHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, error handling 2 (3 pts), ternaries 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.
NotionApiClient.request (cognitive 21) packages/quarry/src/external-sync/providers/notion/notion-api.ts:513— NotionApiClient.request has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (12 pts), ternaries 1 (5 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (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.
SyncEngine.pullFromProvider (cognitive 21) packages/quarry/src/external-sync/sync-engine.ts:659— SyncEngine.pullFromProvider has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts), loops 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.
SyncEngine.findLinkedElements (cognitive 21) packages/quarry/src/external-sync/sync-engine.ts:1197— SyncEngine.findLinkedElements has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 8, loops 1 (2 pts), ternaries 1 (nesting depth added 6). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
identity.signHandler (cognitive 21) packages/quarry/src/cli/commands/identity.ts:311— identity.signHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 3 (7 pts), error handling 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workflow.workflowListHandler (cognitive 21) packages/quarry/src/cli/commands/workflow.ts:193— workflow.workflowListHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
channel.channelAddHandler (cognitive 21) packages/quarry/src/cli/commands/channel.ts:581— channel.channelAddHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
document.docSearchHandler (cognitive 21) packages/quarry/src/cli/commands/document.ts:1096— document.docSearchHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 2 (3 pts), boolean chains 1, error handling 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.
message.msgListHandler (cognitive 21) packages/quarry/src/cli/commands/message.ts:506— message.msgListHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3 (4 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
runner.run (cognitive 21) packages/quarry/src/cli/runner.ts:118— runner.run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (7 pts), error handling 3 (4 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.
libraries.createLibraryRoutes::getSiblingLibraries (cognitive 21) packages/shared-routes/src/libraries.ts:148— libraries.createLibraryRoutes::getSiblingLibraries has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (4 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.
DispatchDaemonImpl.pollWorkerAvailability (cognitive 21) packages/smithy/src/services/dispatch-daemon.ts:857— DispatchDaemonImpl.pollWorkerAvailability has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (6 pts), error handling 2 (3 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DispatchDaemonImpl.buildStewardPrompt (cognitive 21) packages/smithy/src/services/dispatch-daemon.ts:3107— DispatchDaemonImpl.buildStewardPrompt has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), loops 1 (3 pts), error handling 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
TaskCard.TaskCard (cognitive 21) packages/ui/src/domain/TaskCard.tsx:62— TaskCard.TaskCard has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 16, ternaries 2 (3 pts), if/else 2 (nesting depth added 1). Of this number, 15 points are the body's own statements and 6 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.
HorizontalBarChart.HorizontalBarChart (cognitive 21) packages/ui/src/visualizations/HorizontalBarChart.tsx:54— HorizontalBarChart.HorizontalBarChart has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 6 (nesting depth added 1). 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: 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.
sa (cognitive 21) REDACTED:811— sa has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (8 pts), if/else 2, loops 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CreateEntityModal.CreateEntityModal (cognitive 20) apps/quarry-web/src/components/entity/CreateEntityModal.tsx:68— CreateEntityModal.CreateEntityModal has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9, if/else 7, boolean chains 3, error handling 1. Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 199, a function literal at line 82, …). 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.
NotificationInbox.NotificationInbox (cognitive 20) apps/smithy-next/src/components/NotificationInbox.tsx:40— NotificationInbox.NotificationInbox has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), ternaries 4, loops 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 5 belong to 7 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.
PropertyDropdowns.DropdownWrapper (cognitive 20) apps/smithy-next/src/components/dropdowns/PropertyDropdowns.tsx:12— PropertyDropdowns.DropdownWrapper has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 5 (6 pts), boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 47, 18, 39). 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.
MRMergeFlow.MRMergeFlow (cognitive 20) apps/smithy-next/src/components/overlays/mr/MRMergeFlow.tsx:15— MRMergeFlow.MRMergeFlow has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (13 pts), boolean chains 5, if/else 2 (nesting depth added 5). Of this number, 17 points are the body's own statements and 3 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.
ChannelDetailView.groupConsecutiveSessionCards (cognitive 20) apps/smithy-next/src/components/overlays/messages/ChannelDetailView.tsx:75— ChannelDetailView.groupConsecutiveSessionCards has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (flushGroup). 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.
CIJobPanel.JobRow (cognitive 20) apps/smithy-next/src/components/overlays/ci/CIJobPanel.tsx:44— CIJobPanel.JobRow has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, ternaries 6, if/else 2. Of this number, 14 points are the body's own statements and 6 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.
AgentInboxDrawer.AgentInboxDrawer (cognitive 20) apps/smithy-web/src/components/agent/AgentInboxDrawer.tsx:297— AgentInboxDrawer.AgentInboxDrawer has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 3, if/else 2 (nesting depth added 7). Of this number, 14 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.
OnboardingTour.TourTooltip (cognitive 20) apps/smithy-web/src/components/onboarding/OnboardingTour.tsx:362— OnboardingTour.TourTooltip has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (8 pts), if/else 2 (3 pts), loops 1 (nesting depth added 4). Of this number, 10 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskDetailPanel.EditableDescription (cognitive 20) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1348— TaskDetailPanel.EditableDescription has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 7, ternaries 3. Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 1375, handleKeyDown, a function literal at line 1397, …). 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.
KanbanBoard.FilterSortDropdown (cognitive 20) apps/smithy-web/src/components/task/KanbanBoard.tsx:398— KanbanBoard.FilterSortDropdown has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 14, if/else 5, ternaries 1. Of this number, 13 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
event.applyEventToState (cognitive 20) packages/core/src/types/event.ts:835— event.applyEventToState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, ternaries 1 (2 pts), 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.
plan.isPlan (cognitive 20) packages/core/src/types/plan.ts:261— plan.isPlan has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14, boolean chains 6. 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.
playbook-yaml.convertYamlStep (cognitive 20) packages/core/src/types/playbook-yaml.ts:288— playbook-yaml.convertYamlStep has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (20 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.
playbook-yaml.convertStepToYaml (cognitive 20) packages/core/src/types/playbook-yaml.ts:1052— playbook-yaml.convertStepToYaml has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quarry-api.buildTaskWhereClause (cognitive 20) packages/quarry/src/api/quarry-api.ts:331— quarry-api.buildTaskWhereClause has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 5 (9 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
help.getCommandHelp (cognitive 20) packages/quarry/src/cli/commands/help.ts:167— help.getCommandHelp has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4 (6 pts), loops 2 (4 pts), boolean chains 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.
task.readyHandler (cognitive 20) packages/quarry/src/cli/commands/task.ts:86— task.readyHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
document-sync-adapter.resolveDocumentLibraryPath (cognitive 20) packages/quarry/src/external-sync/adapters/document-sync-adapter.ts:183— document-sync-adapter.resolveDocumentLibraryPath has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 3 (4 pts), ternaries 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.
conflict-resolver.resolveWithFieldMerge (cognitive 20) packages/quarry/src/external-sync/conflict-resolver.ts:472— conflict-resolver.resolveWithFieldMerge has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4 (6 pts), boolean chains 3, loops 2 (3 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.
workflow.workflowGcHandler (cognitive 20) packages/quarry/src/cli/commands/workflow.ts:805— workflow.workflowGcHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (6 pts), boolean chains 1, error handling 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils-vendor-CfYKiENT.uu (cognitive 20) REDACTED:813— utils-vendor-CfYKiENT.uu has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 10). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 813, 813). 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.
ClaudeHeadlessSession.decomposeContentBlocks (cognitive 20) packages/smithy/src/providers/claude/headless.ts:233— ClaudeHeadlessSession.decomposeContentBlocks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 1 (3 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
task.verifyMergeStatus (cognitive 20) packages/smithy/src/cli/commands/task.ts:1026— task.verifyMergeStatus has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 2 (5 pts), boolean chains 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.
DispatchDaemonImpl.resolveOwningDirector (cognitive 20) packages/smithy/src/services/dispatch-daemon.ts:2924— DispatchDaemonImpl.resolveOwningDirector has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 2 (3 pts), error handling 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.
DispatchDaemonImpl.spawnMergeStewardForTask (cognitive 20) packages/smithy/src/services/dispatch-daemon.ts:3224— DispatchDaemonImpl.spawnMergeStewardForTask has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 1 (4 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.
pool.poolShowHandler (cognitive 20) packages/smithy/src/cli/commands/pool.ts:261— pool.poolShowHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, loops 2 (4 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 3). 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.
index.startSmithyServer (cognitive 20) REDACTED:84— index.startSmithyServer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts), loops 2 (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.
ChannelMembersPanel.ChannelMembersPanel (cognitive 20) packages/ui/src/message/ChannelMembersPanel.tsx:403— ChannelMembersPanel.ChannelMembersPanel has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 13, error handling 3, ternaries 2 (3 pts), if/else 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, 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.
useAllElements.useAllElements (cognitive 19) apps/quarry-web/src/api/hooks/useAllElements.ts:192— useAllElements.useAllElements has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (19 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.
KanbanBoard.FilterSortDropdown (cognitive 19) apps/quarry-web/src/components/task/KanbanBoard.tsx:398— KanbanBoard.FilterSortDropdown has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, if/else 5, ternaries 1. Of this number, 12 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Tooltip.Tooltip (cognitive 19) apps/smithy-next/src/components/Tooltip.tsx:15— Tooltip.Tooltip has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 8, match/switch 1. Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 22, 79). 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.
CreateMRDialog.CreateMRDialog (cognitive 19) apps/smithy-next/src/components/overlays/mr/CreateMRDialog.tsx:21— CreateMRDialog.CreateMRDialog has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11, boolean chains 6, if/else 2. Of this number, 13 points are the body's own statements and 6 belong to 6 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RoleDefinitionListView.RoleDefinitionListView (cognitive 19) apps/smithy-next/src/components/overlays/agents/RoleDefinitionListView.tsx:24— RoleDefinitionListView.RoleDefinitionListView has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 7, boolean chains 5 (nesting depth added 2). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 32, 128, 87). 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.
useActivity.fetchActivity (cognitive 19) apps/smithy-web/src/api/hooks/useActivity.ts:37— useActivity.fetchActivity has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 3 (5 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ActiveAgentsDashboard.ActiveAgentsDashboard (cognitive 19) apps/smithy-web/src/components/activity/ActiveAgentsDashboard.tsx:26— ActiveAgentsDashboard.ActiveAgentsDashboard has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 4, ternaries 3 (4 pts), boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 58, 129, 72, …). 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.
EditorFileTree.getIconColor (cognitive 19) apps/smithy-web/src/components/editor/EditorFileTree.tsx:187— EditorFileTree.getIconColor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EditorSearchPanel.EditorSearchPanel (cognitive 19) apps/smithy-web/src/components/editor/EditorSearchPanel.tsx:227— EditorSearchPanel.EditorSearchPanel has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 3, ternaries 1. Of this number, 15 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EditorTabBar.EditorTabBar (cognitive 19) apps/smithy-web/src/components/editor/EditorTabBar.tsx:399— EditorTabBar.EditorTabBar has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 1). 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 (handleDragEnd, a function literal at line 467, a function literal at line 485, …). 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.
DaemonToggle.DaemonToggle (cognitive 19) apps/smithy-web/src/components/layout/DaemonToggle.tsx:12— DaemonToggle.DaemonToggle has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (11 pts), if/else 5, boolean chains 3 (nesting depth added 3). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: 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.
NotificationSidebar.NotificationSidebar (cognitive 19) apps/smithy-web/src/components/notification/NotificationSidebar.tsx:209— NotificationSidebar.NotificationSidebar has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 3, ternaries 1. Of this number, 16 points are the body's own statements and 3 belong to 4 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.
TaskDependencySection.AddBlockerModal (cognitive 19) apps/smithy-web/src/components/task/TaskDependencySection.tsx:288— TaskDependencySection.AddBlockerModal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 4). 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 321, 293, 301, …). 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.
TaskDetailPanel.DeadlineInput (cognitive 19) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1073— TaskDetailPanel.DeadlineInput has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (7 pts), boolean chains 6, if/else 6 (nesting depth added 1). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSave, handleKeyDown, a function literal at line 1086, …). 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.
KanbanBoard.KanbanBoard::handleDragEnd (cognitive 19) apps/smithy-web/src/components/task/KanbanBoard.tsx:961— KanbanBoard.KanbanBoard::handleDragEnd has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, 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.
index.WorkspacesPage (cognitive 19) apps/smithy-web/src/routes/workspaces/index.tsx:40— index.WorkspacesPage has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (8 pts), ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 9 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 102, a function literal at line 52, handleSaveLayout, …). 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.
playbook.validatePlaybookStep (cognitive 19) packages/core/src/types/playbook.ts:689— playbook.validatePlaybookStep has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, 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.
playbook.validateSteps (cognitive 19) packages/core/src/types/playbook.ts:1083— playbook.validateSteps has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 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.
playbook-yaml.findPlaybookFile (cognitive 19) packages/core/src/types/playbook-yaml.ts:929— playbook-yaml.findPlaybookFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sync.importHandler (cognitive 19) packages/quarry/src/cli/commands/sync.ts:205— sync.importHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 2 (4 pts), ternaries 3 (4 pts), error handling 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.
SyncEngine.push (cognitive 19) packages/quarry/src/external-sync/sync-engine.ts:283— SyncEngine.push has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (5 pts), loops 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.
entity.entityRegisterHandler (cognitive 19) packages/quarry/src/cli/commands/entity.ts:42— entity.entityRegisterHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, ternaries 1 (2 pts), error handling 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.
admin.collectRuntimeDiagnostics (cognitive 19) packages/quarry/src/cli/commands/admin.ts:545— admin.collectRuntimeDiagnostics has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, ternaries 4 (7 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
plan.planListHandler (cognitive 19) packages/quarry/src/cli/commands/plan.ts:159— plan.planListHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), error handling 2 (3 pts), ternaries 1 (2 pts), boolean chains 1, 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.
workflow.workflowShowHandler (cognitive 19) packages/quarry/src/cli/commands/workflow.ts:304— workflow.workflowShowHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
workflow.workflowTasksHandler (cognitive 19) packages/quarry/src/cli/commands/workflow.ts:431— workflow.workflowTasksHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (6 pts), boolean chains 1, error handling 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
playbook.parseVariable (cognitive 19) packages/quarry/src/cli/commands/playbook.ts:645— playbook.parseVariable has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
channel.channelLeaveHandler (cognitive 19) packages/quarry/src/cli/commands/channel.ts:303— channel.channelLeaveHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
document.docListHandler (cognitive 19) packages/quarry/src/cli/commands/document.ts:252— document.docListHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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.
message.msgThreadHandler (cognitive 19) packages/quarry/src/cli/commands/message.ts:356— message.msgThreadHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 3 (4 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 3). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
agent-pool.isValidPoolAgentTypeConfig (cognitive 19) packages/smithy/src/types/agent-pool.ts:251— agent-pool.isValidPoolAgentTypeConfig has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
agent.agentRegisterHandler (cognitive 19) packages/smithy/src/cli/commands/agent.ts:480— agent.agentRegisterHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (4 pts), boolean chains 1, error handling 1, 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.
AgentPoolServiceImpl.getPoolsForAgentType (cognitive 19) packages/smithy/src/services/agent-pool-service.ts:536— AgentPoolServiceImpl.getPoolsForAgentType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (nesting depth added 9). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 552). 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.
DispatchDaemonImpl.buildRecoveryStewardPrompt (cognitive 19) packages/smithy/src/services/dispatch-daemon.ts:3624— DispatchDaemonImpl.buildRecoveryStewardPrompt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 2 (4 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 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.
Input.Input (cognitive 19) packages/ui/src/components/Input.tsx:45— Input.Input has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 6, if/else 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MobileDrawer.MobileDrawer (cognitive 19) packages/ui/src/layout/MobileDrawer.tsx:46— MobileDrawer.MobileDrawer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3, boolean chains 2 (nesting depth added 2). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 124, handleTouchMove, a function literal at line 111, …). 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.
HashAutocomplete.HashAutocompleteMenu (cognitive 19) packages/ui/src/message/HashAutocomplete.tsx:55— HashAutocomplete.HashAutocompleteMenu has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 4). 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 75, 64, 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.
DashboardCharts.TasksByStatusChart (cognitive 18) apps/quarry-web/src/components/dashboard/DashboardCharts.tsx:243— DashboardCharts.TasksByStatusChart has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 4, if/else 4 (nesting depth added 1). Of this number, 10 points are the body's own statements and 8 belong to 4 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.
DashboardCharts.WorkloadByAgentChart (cognitive 18) apps/quarry-web/src/components/dashboard/DashboardCharts.tsx:444— DashboardCharts.WorkloadByAgentChart has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 5 (nesting depth added 1). Of this number, 11 points are the body's own statements and 7 belong to 2 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.
PlanListView.DisplayPanel (cognitive 18) apps/smithy-next/src/components/overlays/plans/PlanListView.tsx:420— PlanListView.DisplayPanel has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 4, if/else 2 (nesting depth added 1). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 454, 487, 462, …). 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.
MRTimelineEvent.CommitPushEvent (cognitive 18) apps/smithy-next/src/components/overlays/mr/MRTimelineEvent.tsx:209— MRTimelineEvent.CommitPushEvent has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CIRunListView.RunRow (cognitive 18) apps/smithy-next/src/components/overlays/ci/CIRunListView.tsx:384— CIRunListView.RunRow has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 6 (8 pts) (nesting depth added 2). 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, 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.
TaskDetailOverlay.getActivity (cognitive 18) apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:928— TaskDetailOverlay.getActivity has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 3. 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.
MetricsQualityTab.MetricsQualityTab (cognitive 18) apps/smithy-next/src/components/overlays/metrics/MetricsQualityTab.tsx:22— MetricsQualityTab.MetricsQualityTab has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 4 (nesting depth added 3). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 103, 153, 49, …). 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.
DocumentsOverlay.DocumentsOverlay (cognitive 18) apps/smithy-next/src/components/overlays/DocumentsOverlay.tsx:18— DocumentsOverlay.DocumentsOverlay has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 4, loops 1 (nesting depth added 1). Of this number, 9 points are the body's own statements and 9 belong to 7 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.
SettingsOverlay.SettingsOverlay (cognitive 18) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:74— SettingsOverlay.SettingsOverlay has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (10 pts), boolean chains 4, if/else 3, match/switch 1 (nesting depth added 3). 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 items inside it that branch (renderContent, a function literal at line 128, a function literal at line 76, …). 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.
IntegrationsStep.SyncOptionRow (cognitive 18) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:129— IntegrationsStep.SyncOptionRow has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (11 pts), boolean chains 7 (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.
IntegrationsStep.MiniDropdown (cognitive 18) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:479— IntegrationsStep.MiniDropdown has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 4 (5 pts), if/else 4 (nesting depth added 1). Of this number, 12 points are the body's own statements and 6 belong to 4 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.
CreateAgentDialog.CreateAgentDialog::handleSubmit (cognitive 18) REDACTED:300— CreateAgentDialog.CreateAgentDialog::handleSubmit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, ternaries 3 (4 pts), error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (CreateAgentDialog.CreateAgentDialog) 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.
WorkspaceGrid.CustomResizeHandle (cognitive 18) apps/smithy-web/src/components/workspace/WorkspaceGrid.tsx:52— WorkspaceGrid.CustomResizeHandle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 103, 77, 124, …). 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.
dependency.isDependency (cognitive 18) packages/core/src/types/dependency.ts:466— dependency.isDependency has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
playbook.validateFunctionStep (cognitive 18) packages/core/src/types/playbook.ts:828— playbook.validateFunctionStep has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 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.
QuarryAPIImpl.getTasksInPlan (cognitive 18) packages/quarry/src/api/quarry-api.ts:1966— QuarryAPIImpl.getTasksInPlan has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (QuarryAPIImpl.getTasksInWorkflow) 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.
QuarryAPIImpl.ready (cognitive 18) packages/quarry/src/api/quarry-api.ts:2433— QuarryAPIImpl.ready has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 3). 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: 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.
QuarryAPIImpl.getTasksInWorkflow (cognitive 18) packages/quarry/src/api/quarry-api.ts:4087— QuarryAPIImpl.getTasksInWorkflow has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (QuarryAPIImpl.getTasksInPlan) 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.
task.blockedHandler (cognitive 18) packages/quarry/src/cli/commands/task.ts:335— task.blockedHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
dep.depTreeHandler (cognitive 18) packages/quarry/src/cli/commands/dep.ts:517— dep.depTreeHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, ternaries 3 (4 pts), boolean chains 3, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
notion-blocks.parseInlineMarkdown (cognitive 18) packages/quarry/src/external-sync/providers/notion/notion-blocks.ts:638— notion-blocks.parseInlineMarkdown has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
external-sync.configSetAutoLinkHandler (cognitive 18) packages/quarry/src/cli/commands/external-sync.ts:335— external-sync.configSetAutoLinkHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), 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.
external-sync.createProviderFromSettings (cognitive 18) packages/quarry/src/cli/commands/external-sync.ts:1834— external-sync.createProviderFromSettings has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
external-sync.processDocumentBatch (cognitive 18) packages/quarry/src/cli/commands/external-sync.ts:2003— external-sync.processDocumentBatch has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (10 pts), error handling 2 (4 pts), if/else 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
channel.channelListHandler (cognitive 18) packages/quarry/src/cli/commands/channel.ts:392— channel.channelListHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
task-meta.isOrchestratorTaskMeta (cognitive 18) packages/smithy/src/types/task-meta.ts:346— task-meta.isOrchestratorTaskMeta has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 9. 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.
settings-service.createSettingsService.getExternalSyncSettings (cognitive 18) packages/smithy/src/services/settings-service.ts:260— settings-service.createSettingsService.getExternalSyncSettings has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), boolean chains 3, ternaries 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.
MergeStewardServiceImpl.createApprovalPR (cognitive 18) packages/smithy/src/services/merge-steward-service.ts:1197— MergeStewardServiceImpl.createApprovalPR has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, ternaries 3 (6 pts), error handling 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.
DispatchDaemonImpl.pollPlanAutoComplete (cognitive 18) packages/smithy/src/services/dispatch-daemon.ts:1759— DispatchDaemonImpl.pollPlanAutoComplete has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 3 (6 pts), error handling 2 (3 pts), loops 2 (3 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.
DispatchDaemonImpl.pollWorkflowAutoTransition (cognitive 18) packages/smithy/src/services/dispatch-daemon.ts:1836— DispatchDaemonImpl.pollWorkflowAutoTransition has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 5, error handling 2 (3 pts), if/else 2 (3 pts), loops 1 (nesting depth added 5). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DispatchDaemonImpl.recoverOrphanedTask (cognitive 18) packages/smithy/src/services/dispatch-daemon.ts:2259— DispatchDaemonImpl.recoverOrphanedTask has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pool.poolCreateHandler (cognitive 18) packages/smithy/src/cli/commands/pool.ts:397— pool.poolCreateHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 5 (7 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
pool.poolStatusHandler (cognitive 18) packages/smithy/src/cli/commands/pool.ts:767— pool.poolStatusHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, loops 2 (4 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 3). 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.
TrendLineChart.TrendLineChart (cognitive 18) packages/ui/src/visualizations/TrendLineChart.tsx:44— TrendLineChart.TrendLineChart has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 6, if/else 3 (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.
CreatePlanModal.CreatePlanModal (cognitive 18) packages/ui/src/plans/components/CreatePlanModal.tsx:39— CreatePlanModal.CreatePlanModal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 3 (4 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 81, handleSubmit, a function literal at line 58, …). 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.
useGlobalQuickActions.GlobalQuickActionsProvider (cognitive 17) apps/quarry-web/src/hooks/useGlobalQuickActions.tsx:57— useGlobalQuickActions.GlobalQuickActionsProvider has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, boolean chains 1. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 176, 275, 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.
anchors.findByFuzzyContext (cognitive 17) apps/quarry-web/src/lib/anchors.ts:235— anchors.findByFuzzyContext has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts), boolean chains 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.
HistoryTabContent.HistoryTabContent (cognitive 17) apps/quarry-web/src/routes/entities/components/HistoryTabContent.tsx:17— HistoryTabContent.HistoryTabContent has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 3, boolean chains 2 (nesting depth added 6). Of this number, 13 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MRConversationTab.ActionRow (cognitive 17) apps/smithy-next/src/components/overlays/mr/MRConversationTab.tsx:231— MRConversationTab.ActionRow has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (13 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.
WorkflowStepCard.AgentStepContent (cognitive 17) apps/smithy-next/src/components/overlays/automations/WorkflowStepCard.tsx:174— WorkflowStepCard.AgentStepContent has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (5 pts), if/else 2 (nesting depth added 1). Of this number, 15 points are the body's own statements and 2 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.
WorkflowRunPage.StepDetail (cognitive 17) apps/smithy-next/src/components/overlays/automations/WorkflowRunPage.tsx:346— WorkflowRunPage.StepDetail has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 13, ternaries 3, if/else 1. Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RuntimeDetailView.ViewMode (cognitive 17) apps/smithy-next/src/components/overlays/agents/RuntimeDetailView.tsx:87— RuntimeDetailView.ViewMode has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, ternaries 4 (6 pts) (nesting depth added 2). 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.
SessionEventList.SessionEventList (cognitive 17) apps/smithy-next/src/components/overlays/sessions/SessionEventList.tsx:40— SessionEventList.SessionEventList has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), ternaries 2 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 57, 45, 65, …). 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.
CanvasLayoutPicker.CanvasLayoutPicker (cognitive 17) apps/smithy-next/src/components/overlays/sessions/canvas/CanvasLayoutPicker.tsx:19— CanvasLayoutPicker.CanvasLayoutPicker has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 5, if/else 2 (nesting depth added 4). Of this number, 13 points are the body's own statements and 4 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.
MetricsCharts.ActivityHeatmap (cognitive 17) apps/smithy-next/src/components/overlays/metrics/MetricsCharts.tsx:194— MetricsCharts.ActivityHeatmap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (5 pts), boolean chains 2, ternaries 2 (nesting depth added 4). Of this number, 10 points are the body's own statements and 7 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.
SettingsOverlay.IntegrationSyncGroup (cognitive 17) apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1718— SettingsOverlay.IntegrationSyncGroup has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 2. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 1752, 1779, 1780). 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.
IntegrationsStep.InstallFlowBlock (cognitive 17) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:285— IntegrationsStep.InstallFlowBlock has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 13, if/else 2, ternaries 2. Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CronScheduleBuilder.cronToBuilder (cognitive 17) apps/smithy-web/src/components/agent/CronScheduleBuilder.tsx:115— CronScheduleBuilder.cronToBuilder has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 8. 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.
useFileContentSearch.useFileContentSearch (cognitive 17) apps/smithy-web/src/hooks/useFileContentSearch.ts:221— useFileContentSearch.useFileContentSearch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 2 (3 pts), error handling 1 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 4 function literals inside it that branch (lines 312, 286, 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.
useImageDrop.extractImageFiles (cognitive 17) apps/smithy-web/src/hooks/useImageDrop.ts:87— useImageDrop.extractImageFiles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 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.
QuickFileOpen.QuickFileOpen (cognitive 17) apps/smithy-web/src/components/command/QuickFileOpen.tsx:128— QuickFileOpen.QuickFileOpen has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 5, ternaries 1. Of this number, 11 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, 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.
vsix-parser.isDeclarativeExtension (cognitive 17) apps/smithy-web/src/lib/openvsx/vsix-parser.ts:233— vsix-parser.isDeclarativeExtension has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (nesting depth added 4). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-lsp.useLsp (cognitive 17) apps/smithy-web/src/lib/monaco-lsp/use-lsp.ts:62— use-lsp.useLsp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 7. None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 188, 204, 96, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
BulkActionMenu.BulkActionMenu (cognitive 17) apps/smithy-web/src/components/task/BulkActionMenu.tsx:26— BulkActionMenu.BulkActionMenu has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 4, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 10 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
document.validateDocument (cognitive 17) packages/core/src/types/document.ts:429— document.validateDocument has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 6. 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.
QuarryAPIImpl.mergeChannels (cognitive 17) packages/quarry/src/api/quarry-api.ts:3742— QuarryAPIImpl.mergeChannels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3, boolean chains 2 (nesting depth added 3). Of this number, 12 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuarryAPIImpl.searchDocumentsFTS (cognitive 17) packages/quarry/src/api/quarry-api.ts:4559— QuarryAPIImpl.searchDocumentsFTS has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (4 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
document.docHistoryHandler (cognitive 17) packages/quarry/src/cli/commands/document.ts:397— document.docHistoryHandler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
document.docRollbackHandler (cognitive 17) packages/quarry/src/cli/commands/document.ts:498— document.docRollbackHandler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
OpenCodeHeadlessProvider.spawn (cognitive 17) packages/smithy/src/providers/opencode/headless.ts:185— OpenCodeHeadlessProvider.spawn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (6 pts), boolean chains 1, error handling 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.
daemon.daemonStatusHandler (cognitive 17) packages/smithy/src/cli/commands/daemon.ts:255— daemon.daemonStatusHandler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 1 (3 pts), ternaries 2 (3 pts) (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.
StewardSchedulerImpl.runExecution (cognitive 17) REDACTED:1091— StewardSchedulerImpl.runExecution has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (4 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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.
PluginExecutorImpl.validate (cognitive 17) packages/smithy/src/services/plugin-executor.ts:447— PluginExecutorImpl.validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, 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.
DispatchDaemonImpl.spawnTriageSession (cognitive 17) packages/smithy/src/services/dispatch-daemon.ts:3944— DispatchDaemonImpl.spawnTriageSession has cognitive complexity 17 (threshold 15). Drivers by points: error handling 5 (8 pts), if/else 6 (8 pts), loops 1 (nesting depth added 5). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApiClient.request (cognitive 17) packages/ui/src/api/api-client.ts:116— ApiClient.request has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 2 (3 pts), boolean chains 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.
BulkActionMenu.BulkActionMenu (cognitive 16) apps/quarry-web/src/components/task/BulkActionMenu.tsx:25— BulkActionMenu.BulkActionMenu has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 4, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 9 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TaskDetailPanel.AssigneeDropdown (cognitive 16) apps/quarry-web/src/components/task/TaskDetailPanel.tsx:1758— TaskDetailPanel.AssigneeDropdown has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 3. Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 1774, 1784, 1791, …). 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.
NotificationsSection.NotificationsSection (cognitive 16) apps/quarry-web/src/routes/settings/components/NotificationsSection.tsx:59— NotificationsSection.NotificationsSection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, ternaries 4 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (toggleBrowserNotifications, a function literal at line 246, a function literal at line 275). 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.
index.DependencyGraphPage (cognitive 16) apps/quarry-web/src/routes/dependency-graph/index.tsx:35— index.DependencyGraphPage has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 6. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 103, 92, 112, …). 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.
MRChecksTab.JobRow (cognitive 16) apps/smithy-next/src/components/overlays/mr/MRChecksTab.tsx:98— MRChecksTab.JobRow has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 1. Of this number, 15 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EditorFolderView.EditorFolderView (cognitive 16) apps/smithy-next/src/components/overlays/editor/EditorFolderView.tsx:24— EditorFolderView.EditorFolderView has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (7 pts), if/else 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 26, 32, …). 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.
EditorFindBar.EditorFindBar (cognitive 16) apps/smithy-next/src/components/overlays/editor/EditorFindBar.tsx:12— EditorFindBar.EditorFindBar has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 2, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (handleKeyDown, a function literal at line 25, a function literal at line 18, …). 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.
WorkflowDetailView.WorkflowDetailView (cognitive 16) apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.tsx:49— WorkflowDetailView.WorkflowDetailView has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, ternaries 4. Of this number, 12 points are the body's own statements and 4 belong to 7 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.
SessionListView.SessionDisplayPanel (cognitive 16) apps/smithy-next/src/components/overlays/sessions/SessionListView.tsx:493— SessionListView.SessionDisplayPanel has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8, boolean chains 4, if/else 4. Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 531, 564, 502, …). 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.
SessionChatView.SessionChatView (cognitive 16) apps/smithy-next/src/components/overlays/sessions/SessionChatView.tsx:24— SessionChatView.SessionChatView has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 64, 30, 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.
IntegrationsStep.FlowStep (cognitive 16) apps/smithy-next/src/components/onboarding/IntegrationsStep.tsx:412— IntegrationsStep.FlowStep has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 7 (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.
ChangeProviderDialog.ChangeProviderDialog (cognitive 16) apps/smithy-web/src/components/agent/ChangeProviderDialog.tsx:26— ChangeProviderDialog.ChangeProviderDialog has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (6 pts), boolean chains 5, if/else 4, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (handleSubmit, a function literal at line 41, a function literal at line 182). 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.
ChangeModelDialog.ChangeModelDialog (cognitive 16) apps/smithy-web/src/components/agent/ChangeModelDialog.tsx:18— ChangeModelDialog.ChangeModelDialog has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 4, if/else 3, error handling 1 (nesting depth added 3). Of this number, 8 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body 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.
EditorFileTree.getFileIcon (cognitive 16) apps/smithy-web/src/components/editor/EditorFileTree.tsx:117— EditorFileTree.getFileIcon has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, boolean chains 2, ternaries 1 (2 pts) (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.
EditorFileTree.FileNode (cognitive 16) apps/smithy-web/src/components/editor/EditorFileTree.tsx:505— EditorFileTree.FileNode has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (11 pts), if/else 3, boolean chains 2 (nesting depth added 3). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, 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.
LightweightLspClient.registerProviders (cognitive 16) apps/smithy-web/src/lib/monaco-lsp/lightweight-client.ts:172— LightweightLspClient.registerProviders has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, ternaries 5, error handling 3, boolean chains 2. Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 220, 182, 231, …). 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.
TaskDetailPanel.EditableTags (cognitive 16) apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1170— TaskDetailPanel.EditableTags has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (handleKeyDown, a function literal at line 1186, handleAddTag, …). 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.
merge.mergeDependencies (cognitive 16) packages/quarry/src/sync/merge.ts:307— merge.mergeDependencies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, 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.
QuarryAPIImpl.getDependencyTree::buildNode (cognitive 16) packages/quarry/src/api/quarry-api.ts:2857— QuarryAPIImpl.getDependencyTree::buildNode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 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.
plugin-types.isValidCommand (cognitive 16) packages/quarry/src/cli/plugin-types.ts:197— plugin-types.isValidCommand has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 1 (2 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.
install.installSkillsHandler (cognitive 16) packages/quarry/src/cli/commands/install.ts:194— install.installSkillsHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 3 (6 pts), boolean chains 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.
task.backlogHandler (cognitive 16) packages/quarry/src/cli/commands/task.ts:220— task.backlogHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
NotionDocumentAdapter.updatePage (cognitive 16) packages/quarry/src/external-sync/providers/notion/notion-document-adapter.ts:402— NotionDocumentAdapter.updatePage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4 (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.
external-sync.processBatch (cognitive 16) packages/quarry/src/cli/commands/external-sync.ts:1926— external-sync.processBatch has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (10 pts), if/else 1 (3 pts), error handling 1 (2 pts), 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.
admin.migrateHandler (cognitive 16) packages/quarry/src/cli/commands/admin.ts:792— admin.migrateHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5, loops 2 (4 pts), ternaries 2 (4 pts), error handling 2, boolean chains 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.
plan.planShowHandler (cognitive 16) packages/quarry/src/cli/commands/plan.ts:288— plan.planShowHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 2). 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, 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.
plan.planTasksHandler (cognitive 16) packages/quarry/src/cli/commands/plan.ts:753— plan.planTasksHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
workflow.workflowCreateHandler (cognitive 16) packages/quarry/src/cli/commands/workflow.ts:70— workflow.workflowCreateHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (5 pts), loops 1 (2 pts), boolean chains 1, error handling 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.
library.libraryDocsHandler (cognitive 16) packages/quarry/src/cli/commands/library.ts:332— library.libraryDocsHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 2). 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, 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.
library.libraryNestHandler (cognitive 16) packages/quarry/src/cli/commands/library.ts:425— library.libraryNestHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
library.libraryStatsHandler (cognitive 16) packages/quarry/src/cli/commands/library.ts:520— library.libraryStatsHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
role-definition.isBaseRoleDefinition (cognitive 16) packages/smithy/src/types/role-definition.ts:346— role-definition.isBaseRoleDefinition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OrchestratorAPIImpl.listAgents (cognitive 16) packages/smithy/src/api/orchestrator-api.ts:398— OrchestratorAPIImpl.listAgents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3 (nesting depth added 6). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
SessionManagerImpl.resumeSession (cognitive 16) packages/smithy/src/runtime/session-manager.ts:620— SessionManagerImpl.resumeSession has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3 (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.
SessionManagerImpl.messageSession (cognitive 16) packages/smithy/src/runtime/session-manager.ts:1056— SessionManagerImpl.messageSession has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
SessionManagerImpl.loadSessionState (cognitive 16) packages/smithy/src/runtime/session-manager.ts:1190— SessionManagerImpl.loadSessionState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 5). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
DispatchDaemonImpl.attachRapidExitDetector::onExit (cognitive 16) packages/smithy/src/services/dispatch-daemon.ts:2473— DispatchDaemonImpl.attachRapidExitDetector::onExit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 3, loops 1 (2 pts), error handling 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
diagnostics.collectMergeQueue (cognitive 16) packages/smithy/src/server/routes/diagnostics.ts:197— diagnostics.collectMergeQueue has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 3 (6 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.startBunServer (cognitive 16) REDACTED:44— server.startBunServer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 3, ternaries 3, error handling 1 (2 pts), loops 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 5 belong to 3 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Off the main sequence: @stoneforge/core — @stoneforge/core: abstractness 0.15, instability 0.00, distance 0.85 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Duplication concentrated across 3 sibling directories (190 clone groups) apps/quarry-web/src/routes/inbox.tsx:8— 190 duplicated blocks under apps/ have copies in at least two of the sibling directories quarry-web, smithy-next, smithy-web — 149 of them are reported below, and 41 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 190 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 190 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 190 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 2 sibling directories (180 clone groups) apps/smithy-server/src/routes/tasks.ts:7— 180 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages — 128 of them are reported below, and 52 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 180 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 180 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 180 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 13 sibling directories (148 clone groups) apps/smithy-next/src/components/overlays/documents/DocListView.tsx:358— 148 duplicated blocks under apps/smithy-next/src/components/overlays/ have copies in at least two of the sibling directories agents, automations, ci, documents, editor, messages (+7 more sibling(s) not listed) — 89 of them are reported below, and 59 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 148 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 148 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 148 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (103 clone groups) REDACTED:1781— 103 duplicated blocks under packages/ have copies in at least two of the sibling directories core, quarry, shared-routes, smithy, ui — 77 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 103 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 103 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 103 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 16 sibling directories (37 clone groups) apps/smithy-web/src/components/command/FileContentSearch.tsx:59— 37 duplicated blocks under apps/smithy-web/src/components/ have copies in at least two of the sibling directories activity, agent, agent-graph, command, document, editor (+10 more sibling(s) not listed) — 23 of them are reported below, and 14 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 37 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 37 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 37 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 8 sibling directories (22 clone groups) apps/quarry-web/src/routes/entities/hooks.ts:242— 22 duplicated blocks under apps/quarry-web/src/routes/ have copies in at least two of the sibling directories dashboard, dependency-graph, entities, plans, settings, tasks (+2 more sibling(s) not listed) — 12 of them are reported below, and 10 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (22 clone groups) apps/smithy-next/src/components/onboarding/WorkerEnvironmentStep.tsx:140— 22 duplicated blocks under apps/smithy-next/src/components/ have copies in at least two of the sibling directories dropdowns, onboarding, overlays — 9 of them are reported below, and 13 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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 8 sibling directories (16 clone groups) packages/smithy/src/api/orchestrator-api.ts:447— 16 duplicated blocks under packages/smithy/src/ have copies in at least two of the sibling directories api, cli, permissions, runtime, server, services (+2 more sibling(s) not listed) — 10 of them are reported below, and 6 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (11 clone groups) apps/quarry-web/src/components/team/CreateTeamModal.tsx:108— 11 duplicated blocks under apps/quarry-web/src/ have copies in at least two of the sibling directories api, components, hooks, lib, routes — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (10 clone groups) apps/smithy-web/src/routes/merge-requests/index.tsx:259— 10 duplicated blocks under apps/smithy-web/src/routes/ have copies in at least two of the sibling directories activity, agents, merge-requests, metrics, settings, tasks — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (10 clone groups) packages/quarry/src/api/quarry-api.ts:156— 10 duplicated blocks under packages/quarry/src/ have copies in at least two of the sibling directories api, cli, config, external-sync, server, services (+2 more sibling(s) not listed) — 4 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (10 clone groups) packages/smithy/src/providers/codex/interactive.ts:28— 10 of the duplicated blocks reported below have copies in at least two of the sibling directories claude, codex, opencode under packages/smithy/src/providers/. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (925 identical lines × 2 files) apps/quarry-web/src/routes/inbox.tsx:8— apps/quarry-web/src/routes/inbox.tsx:8 · apps/smithy-web/src/routes/inbox/index.tsx:8 — these 2 files are line-for-line copies of one another — 925 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.
Wholesale file copy (702 identical lines × 2 files) apps/smithy-server/src/routes/tasks.ts:7— apps/smithy-server/src/routes/tasks.ts:7 · packages/smithy/src/server/routes/tasks.ts:7 — these 2 files are line-for-line copies of one another — 702 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.
Wholesale file copy (566 identical lines × 2 files) apps/smithy-server/src/routes/sessions.ts:7— apps/smithy-server/src/routes/sessions.ts:7 · packages/smithy/src/server/routes/sessions.ts:7 — these 2 files are line-for-line copies of one another — 566 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.
Wholesale file copy (413 identical lines × 2 files) apps/quarry-web/src/api/hooks/useAllElements.ts:8— apps/quarry-web/src/api/hooks/useAllElements.ts:8 · apps/smithy-web/src/api/hooks/useAllElements.ts:8 — these 2 files are line-for-line copies of one another — 413 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (373 matched lines × 2 locations) · ×1
Duplicated block with local edits (373 matched lines × 2 locations) packages/core/src/types/task.ts:47— packages/core/src/types/task.ts:47 · packages/core/src/types/workflow.ts:57 — the two spans are one implementation copied and then locally edited — 2355 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 (356 identical lines × 2 files) apps/smithy-server/src/routes/workflows.ts:7— apps/smithy-server/src/routes/workflows.ts:7 · packages/smithy/src/server/routes/workflows.ts:7 — these 2 files are line-for-line copies of one another — 356 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.
Wholesale file copy (349 identical lines × 2 files) apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:5— apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:5 · apps/smithy-web/src/routes/messages/components/MessageComposer.tsx:5 — these 2 files are line-for-line copies of one another — 349 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (348 matched lines × 2 locations) · ×1
Duplicated block with local edits (348 matched lines × 2 locations) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:60— apps/quarry-web/src/components/editor/ImageUploadModal.tsx:60 · packages/ui/src/message/MessageImageAttachment.tsx:54 — the two spans are one implementation copied and then locally edited — 1859 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 (329 identical lines × 2 files) REDACTED:8— REDACTED:8 · REDACTED:8 — these 2 files are line-for-line copies of one another — 329 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (326 matched lines × 2 locations) · ×1
Duplicated block with local edits (326 matched lines × 2 locations) apps/smithy-server/src/routes/agents.ts:17— apps/smithy-server/src/routes/agents.ts:17 · packages/smithy/src/server/routes/agents.ts:17 — the two spans are one implementation copied and then locally edited — 2923 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 (318 identical lines × 2 files) apps/quarry-web/src/routes/messages/components/ChannelView.tsx:5— apps/quarry-web/src/routes/messages/components/ChannelView.tsx:5 · apps/smithy-web/src/routes/messages/components/ChannelView.tsx:5 — these 2 files are line-for-line copies of one another — 318 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (286 matched lines × 2 locations) · ×1
Duplicated block with local edits (286 matched lines × 2 locations) apps/smithy-web/src/components/command/FileContentSearch.tsx:59— apps/smithy-web/src/components/command/FileContentSearch.tsx:59 · apps/smithy-web/src/components/editor/EditorSearchPanel.tsx:65 — the two spans are one implementation copied and then locally edited — 1547 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 (274 identical lines × 2 files) apps/quarry-web/src/routes/workflows/index.tsx:11— apps/quarry-web/src/routes/workflows/index.tsx:11 · apps/smithy-web/src/routes/workflows/index.tsx:10 — these 2 files are line-for-line copies of one another — 274 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (261 matched lines × 2 locations) · ×1
Duplicated block with local edits (261 matched lines × 2 locations) apps/quarry-web/src/lib/task-utils.tsx:38— apps/quarry-web/src/lib/task-utils.tsx:38 · apps/smithy-web/src/lib/task-utils.tsx:39 — the two spans are one implementation copied and then locally edited — 1990 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 (241 identical lines × 2 files) apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:5— apps/quarry-web/src/routes/messages/components/MessageBubble.tsx:5 · apps/smithy-web/src/routes/messages/components/MessageBubble.tsx:5 — these 2 files are line-for-line copies of one another — 241 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.
Wholesale file copy (239 identical lines × 3 files) apps/quarry-web/src/components/editor/MentionAutocomplete.tsx:17— apps/quarry-web/src/components/editor/MentionAutocomplete.tsx:17 · apps/smithy-web/src/components/editor/MentionAutocomplete.tsx:17 · packages/ui/src/message/MentionAutocomplete.tsx:17 — these 3 files are line-for-line copies of one another — 239 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.
Wholesale file copy (235 identical lines × 2 files) apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:8— apps/quarry-web/src/routes/documents/components/DocumentLinkComponents.tsx:8 · apps/smithy-web/src/routes/documents/components/DocumentLinkComponents.tsx:8 — these 2 files are line-for-line copies of one another — 235 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.
Wholesale file copy (231 identical lines × 2 files) apps/quarry-web/src/components/document/CreateDocumentModal.tsx:1— apps/quarry-web/src/components/document/CreateDocumentModal.tsx:1 · apps/smithy-web/src/components/document/CreateDocumentModal.tsx:1 — these 2 files are line-for-line copies of one another — 231 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (221 matched lines × 2 locations) · ×1
Duplicated block with local edits (221 matched lines × 2 locations) apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:366— apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:366 · apps/smithy-web/src/routes/documents/components/DocumentDetailPanel.tsx:225 — the two spans are one implementation copied and then locally edited — 1072 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 (218 identical lines × 2 files) apps/quarry-web/src/routes/documents/components/LibraryView.tsx:5— apps/quarry-web/src/routes/documents/components/LibraryView.tsx:5 · apps/smithy-web/src/routes/documents/components/LibraryView.tsx:5 — these 2 files are line-for-line copies of one another — 218 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.
Wholesale file copy (217 identical lines × 2 files) packages/storage/src/bun-backend.ts:9— packages/storage/src/bun-backend.ts:9 · packages/storage/src/node-backend.ts:11 — these 2 files are line-for-line copies of one another — 217 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (198 matched lines × 2 locations) · ×1
Duplicated block with local edits (198 matched lines × 2 locations) apps/smithy-web/src/components/pool/CreatePoolDialog.tsx:100— apps/smithy-web/src/components/pool/CreatePoolDialog.tsx:100 · apps/smithy-web/src/components/pool/EditPoolDialog.tsx:131 — the two spans are one implementation copied and then locally edited — 1149 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 (196 matched lines × 2 locations) · ×1
Duplicated block with local edits (196 matched lines × 2 locations) REDACTED:40— REDACTED:40 · REDACTED:56 — the two spans are one implementation copied and then locally edited — 1675 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 (195 identical lines × 2 files) apps/quarry-web/src/routes/plans/components/RoadmapView.tsx:5— apps/quarry-web/src/routes/plans/components/RoadmapView.tsx:5 · packages/ui/src/plans/components/RoadmapView.tsx:5 — these 2 files are line-for-line copies of one another — 195 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.
Complex function TaskDetailOverlay (cyclomatic 75, cognitive 68) apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx:36— TaskDetailOverlay has cyclomatic complexity 75 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 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 DocumentDetailPanel (cyclomatic 74, cognitive 68) apps/quarry-web/src/routes/documents/components/DocumentDetailPanel.tsx:59— DocumentDetailPanel has cyclomatic complexity 74 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 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 DocumentDetailPanel (cyclomatic 64, cognitive 58) apps/smithy-web/src/routes/documents/components/DocumentDetailPanel.tsx:49— DocumentDetailPanel has cyclomatic complexity 64 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 FileEditorPage (cyclomatic 63, cognitive 62) apps/smithy-web/src/routes/editor/index.tsx:219— FileEditorPage has cyclomatic complexity 63 and cognitive complexity 62; 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.
R2 · Cyclomatic Complexity· Complex function Oi (cyclomatic 62, cognitive 56) · ×1
Complex function Oi (cyclomatic 62, cognitive 56) REDACTED:1— Oi has cyclomatic complexity 62 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 linkAllDocumentsHandler (cyclomatic 58, cognitive 77) packages/quarry/src/cli/commands/external-sync.ts:2089— linkAllDocumentsHandler has cyclomatic complexity 58 and cognitive complexity 77; 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 parseUrl (cyclomatic 56, cognitive 75) apps/smithy-next/src/App.tsx:108— parseUrl has cyclomatic complexity 56 and cognitive complexity 75; 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 updateHandler (cyclomatic 55, cognitive 82) packages/quarry/src/cli/commands/crud.ts:820— updateHandler has cyclomatic complexity 55 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 54, cognitive 77) packages/ui/src/workflows/components/WorkflowEditorModal.tsx:1160— (anonymous) has cyclomatic complexity 54 and cognitive complexity 77; 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 linkAllHandler (cyclomatic 54, cognitive 68) packages/quarry/src/cli/commands/external-sync.ts:2392— linkAllHandler has cyclomatic complexity 54 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 DirectorPanel (cyclomatic 54, cognitive 49) apps/smithy-next/src/components/DirectorPanel.tsx:112— DirectorPanel has cyclomatic complexity 54 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function playbookValidateHandler (cyclomatic 52, cognitive 90) packages/quarry/src/cli/commands/playbook.ts:326— playbookValidateHandler has cyclomatic complexity 52 and cognitive complexity 90; 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 validateYamlStep (cyclomatic 52, cognitive 56) packages/core/src/types/playbook-yaml.ts:651— validateYamlStep has cyclomatic complexity 52 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 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 WorkspacePane (cyclomatic 52, cognitive 45) apps/smithy-web/src/components/workspace/WorkspacePane.tsx:66— WorkspacePane has cyclomatic complexity 52 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 51, cognitive 72) packages/smithy/src/server/routes/agents.ts:306— (anonymous) has cyclomatic complexity 51 and cognitive complexity 72; 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 ImageUploadModal (cyclomatic 51, cognitive 58) apps/quarry-web/src/components/editor/ImageUploadModal.tsx:53— ImageUploadModal has cyclomatic complexity 51 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateConfiguration (cyclomatic 51, cognitive 55) packages/quarry/src/config/validation.ts:321— validateConfiguration has cyclomatic complexity 51 and cognitive complexity 55; 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 buildUrl (cyclomatic 50, cognitive 69) apps/smithy-next/src/App.tsx:269— buildUrl has cyclomatic complexity 50 and cognitive complexity 69; 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.
R3 · Large Files· packages/quarry/src/api/quarry-api.ts · ×1
packages/quarry/src/api/quarry-api.ts: 4852 lines of code packages/quarry/src/api/quarry-api.ts:1— packages/quarry/src/api/quarry-api.ts has 4852 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/smithy/src/services/dispatch-daemon.ts · ×1
packages/smithy/src/services/dispatch-daemon.ts: 3807 lines of code packages/smithy/src/services/dispatch-daemon.ts:1— packages/smithy/src/services/dispatch-daemon.ts has 3807 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: 3350 lines of code REDACTED:1— REDACTED has 3350 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/core/src/types/entity.ts · ×1
packages/core/src/types/entity.ts: 2993 lines of code packages/core/src/types/entity.ts:1— packages/core/src/types/entity.ts has 2993 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/quarry/src/cli/commands/external-sync.ts · ×1
packages/quarry/src/cli/commands/external-sync.ts: 2723 lines of code packages/quarry/src/cli/commands/external-sync.ts:1— packages/quarry/src/cli/commands/external-sync.ts has 2723 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· apps/smithy-web/src/components/task/TaskDetailPanel.tsx · ×1
apps/smithy-web/src/components/task/TaskDetailPanel.tsx: 2441 lines of code apps/smithy-web/src/components/task/TaskDetailPanel.tsx:1— apps/smithy-web/src/components/task/TaskDetailPanel.tsx has 2441 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· apps/smithy-next/src/mock-data.ts · ×1
apps/smithy-next/src/mock-data.ts: 2307 lines of code apps/smithy-next/src/mock-data.ts:1— apps/smithy-next/src/mock-data.ts has 2307 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/core/src/types/playbook.ts · ×1
packages/core/src/types/playbook.ts: 2085 lines of code packages/core/src/types/playbook.ts:1— packages/core/src/types/playbook.ts has 2085 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· apps/smithy-next/src/components/overlays/SettingsOverlay.tsx · ×1
apps/smithy-next/src/components/overlays/SettingsOverlay.tsx: 2065 lines of code apps/smithy-next/src/components/overlays/SettingsOverlay.tsx:1— apps/smithy-next/src/components/overlays/SettingsOverlay.tsx has 2065 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· apps/quarry-web/src/components/task/TaskDetailPanel.tsx · ×1
apps/quarry-web/src/components/task/TaskDetailPanel.tsx: 2003 lines of code apps/quarry-web/src/components/task/TaskDetailPanel.tsx:1— apps/quarry-web/src/components/task/TaskDetailPanel.tsx has 2003 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/quarry/src/api/types.ts · ×1
packages/quarry/src/api/types.ts: 1721 lines of code packages/quarry/src/api/types.ts:1— packages/quarry/src/api/types.ts has 1721 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/workflows/components/WorkflowEditorModal.tsx · ×1
packages/ui/src/workflows/components/WorkflowEditorModal.tsx: 1578 lines of code packages/ui/src/workflows/components/WorkflowEditorModal.tsx:1— packages/ui/src/workflows/components/WorkflowEditorModal.tsx has 1578 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/smithy/src/runtime/session-manager.ts · ×1
packages/smithy/src/runtime/session-manager.ts: 1523 lines of code packages/smithy/src/runtime/session-manager.ts:1— packages/smithy/src/runtime/session-manager.ts has 1523 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· apps/smithy-next/src/components/DirectorPanel.tsx · ×1
apps/smithy-next/src/components/DirectorPanel.tsx: 1515 lines of code apps/smithy-next/src/components/DirectorPanel.tsx:1— apps/smithy-next/src/components/DirectorPanel.tsx has 1515 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: 1473 lines of code REDACTED:1— REDACTED has 1473 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· apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx · ×1
apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx: 1459 lines of code apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:1— apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx has 1459 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/quarry/src/external-sync/sync-engine.ts · ×1
packages/quarry/src/external-sync/sync-engine.ts: 1441 lines of code packages/quarry/src/external-sync/sync-engine.ts:1— packages/quarry/src/external-sync/sync-engine.ts has 1441 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/core/src/types/playbook-yaml.ts · ×1
packages/core/src/types/playbook-yaml.ts: 1415 lines of code packages/core/src/types/playbook-yaml.ts:1— packages/core/src/types/playbook-yaml.ts has 1415 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/quarry/src/cli/commands/task.ts · ×1
packages/quarry/src/cli/commands/task.ts: 1345 lines of code packages/quarry/src/cli/commands/task.ts:1— packages/quarry/src/cli/commands/task.ts has 1345 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· apps/smithy-web/src/components/layout/AppShell.tsx · ×1
apps/smithy-web/src/components/layout/AppShell.tsx: 1338 lines of code apps/smithy-web/src/components/layout/AppShell.tsx:1— apps/smithy-web/src/components/layout/AppShell.tsx has 1338 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/smithy/src/services/merge-steward-service.ts · ×1
packages/smithy/src/services/merge-steward-service.ts: 1333 lines of code packages/smithy/src/services/merge-steward-service.ts:1— packages/smithy/src/services/merge-steward-service.ts has 1333 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· apps/smithy-web/src/routes/inbox/index.tsx · ×1
apps/smithy-web/src/routes/inbox/index.tsx: 1324 lines of code apps/smithy-web/src/routes/inbox/index.tsx:1— apps/smithy-web/src/routes/inbox/index.tsx has 1324 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· apps/quarry-web/src/routes/inbox.tsx · ×1
apps/quarry-web/src/routes/inbox.tsx: 1311 lines of code apps/quarry-web/src/routes/inbox.tsx:1— apps/quarry-web/src/routes/inbox.tsx has 1311 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· apps/smithy-web/src/routes/editor/index.tsx · ×1
apps/smithy-web/src/routes/editor/index.tsx: 1299 lines of code apps/smithy-web/src/routes/editor/index.tsx:1— apps/smithy-web/src/routes/editor/index.tsx has 1299 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· apps/smithy-web/src/routes/tasks/index.tsx · ×1
apps/smithy-web/src/routes/tasks/index.tsx: 1283 lines of code apps/smithy-web/src/routes/tasks/index.tsx:1— apps/smithy-web/src/routes/tasks/index.tsx has 1283 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/smithy/src/runtime/spawner.ts · ×1
packages/smithy/src/runtime/spawner.ts: 1264 lines of code packages/smithy/src/runtime/spawner.ts:1— packages/smithy/src/runtime/spawner.ts has 1264 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/shared-routes/src/documents.ts · ×1
packages/shared-routes/src/documents.ts: 1256 lines of code packages/shared-routes/src/documents.ts:1— packages/shared-routes/src/documents.ts has 1256 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· apps/smithy-next/src/App.tsx · ×1
apps/smithy-next/src/App.tsx: 1252 lines of code apps/smithy-next/src/App.tsx:1— apps/smithy-next/src/App.tsx has 1252 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/smithy/src/testing/orchestration-tests.ts · ×1
packages/smithy/src/testing/orchestration-tests.ts: 1225 lines of code packages/smithy/src/testing/orchestration-tests.ts:1— packages/smithy/src/testing/orchestration-tests.ts has 1225 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/smithy/src/cli/commands/task.ts · ×1
packages/smithy/src/cli/commands/task.ts: 1210 lines of code packages/smithy/src/cli/commands/task.ts:1— packages/smithy/src/cli/commands/task.ts has 1210 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/quarry/src/systems/identity.ts · ×1
packages/quarry/src/systems/identity.ts: 1190 lines of code packages/quarry/src/systems/identity.ts:1— packages/quarry/src/systems/identity.ts has 1190 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: 1187 lines of code REDACTED:1— REDACTED has 1187 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· apps/smithy-web/src/routes/metrics/index.tsx · ×1
apps/smithy-web/src/routes/metrics/index.tsx: 1168 lines of code apps/smithy-web/src/routes/metrics/index.tsx:1— apps/smithy-web/src/routes/metrics/index.tsx has 1168 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· apps/smithy-web/src/components/workspace/StreamViewer.tsx · ×1
apps/smithy-web/src/components/workspace/StreamViewer.tsx: 1143 lines of code apps/smithy-web/src/components/workspace/StreamViewer.tsx:1— apps/smithy-web/src/components/workspace/StreamViewer.tsx has 1143 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/quarry/src/cli/commands/document.ts · ×1
packages/quarry/src/cli/commands/document.ts: 1142 lines of code packages/quarry/src/cli/commands/document.ts:1— packages/quarry/src/cli/commands/document.ts has 1142 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· apps/smithy-next/src/components/KanbanBoard.tsx · ×1
apps/smithy-next/src/components/KanbanBoard.tsx: 1111 lines of code apps/smithy-next/src/components/KanbanBoard.tsx:1— apps/smithy-next/src/components/KanbanBoard.tsx has 1111 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/smithy/src/cli/commands/agent.ts · ×1
packages/smithy/src/cli/commands/agent.ts: 1065 lines of code packages/smithy/src/cli/commands/agent.ts:1— packages/smithy/src/cli/commands/agent.ts has 1065 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/smithy/src/server/routes/tasks.ts · ×1
packages/smithy/src/server/routes/tasks.ts: 1046 lines of code packages/smithy/src/server/routes/tasks.ts:1— packages/smithy/src/server/routes/tasks.ts has 1046 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/quarry/src/cli/commands/crud.ts · ×1
packages/quarry/src/cli/commands/crud.ts: 1038 lines of code packages/quarry/src/cli/commands/crud.ts:1— packages/quarry/src/cli/commands/crud.ts has 1038 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/core/src/types/dependency.ts · ×1
packages/core/src/types/dependency.ts: 1020 lines of code packages/core/src/types/dependency.ts:1— packages/core/src/types/dependency.ts has 1020 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded packages/quarry/src/cli/commands/plan.bun.test.ts:1023— This repository declares test tooling, and the ✓ above records that declaration — but packages/quarry/src/cli/commands/plan.bun.test.ts and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~1146 LoC) apps/smithy-server/src/routes/tasks.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~685 LoC) apps/smithy-server/src/routes/workflows.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~669 LoC) REDACTED— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~637 LoC) apps/smithy-next/src/components/overlays/runtimes/RuntimeListView.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-next/src/components/overlays/RuntimesOverlay.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~559 LoC) apps/smithy-next/src/components/overlays/WorkspacesOverlay.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~453 LoC) apps/smithy-web/src/components/editor/MentionAutocomplete.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~379 LoC) apps/smithy-next/src/components/overlays/runtimes/RuntimeDetailView.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-next/src/components/overlays/RuntimesOverlay.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~341 LoC) apps/smithy-server/src/routes/daemon.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~328 LoC) apps/quarry-web/src/App.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~305 LoC) apps/quarry-web/src/routes/plans/components/RoadmapView.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~257 LoC) apps/smithy-server/src/routes/extensions.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~255 LoC) apps/smithy-next/src/components/overlays/EditorOverlay.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~236 LoC) apps/quarry-web/src/components/shared/ResponsiveDataList.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~226 LoC) apps/smithy-server/src/routes/pools.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~217 LoC) apps/quarry-web/src/routes/plans/components/MobilePlanCard.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~202 LoC) apps/quarry-server/src/ws/handler.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~195 LoC) apps/quarry-web/src/components/shared/ProgressRing.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/quarry-web/src/routes/plans/components/MobilePlanCard.tsx, apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/PlanListItem.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~168 LoC) apps/smithy-next/src/components/overlays/ci/CIJobPanel.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~167 LoC) apps/smithy-next/src/components/overlays/agents/CreateAgentDialog.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~157 LoC) apps/quarry-web/src/hooks/useTheme.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~150 LoC) apps/smithy-server/src/routes/plugins.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~137 LoC) apps/quarry-web/src/routes/plans/utils.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/PlanListItem.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~132 LoC) apps/quarry-web/src/routes/plans/components/PlanTaskList.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~124 LoC) apps/smithy-next/src/components/overlays/RuntimesOverlay.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~122 LoC) apps/quarry-web/src/routes/plans/components/TaskPickerModal.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~119 LoC) apps/smithy-server/src/routes/worktrees.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~100 LoC) apps/quarry-web/src/routes/plans/components/PlanListItem.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~66 LoC) apps/quarry-web/src/routes/plans/components/PlanSearchBar.tsx— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/quarry-web/src/routes/plans/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~61 LoC) apps/smithy-server/src/routes/lsp.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/smithy-server/src/routes/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~51 LoC) apps/smithy-web/src/lib/openvsx/index.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~49 LoC) packages/quarry/src/external-sync/providers/index.ts— no import path from any entry point (187 application, 21 tooling, 349 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@changesets/cli' — Declared in the root 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 '@hono/node-server' — Declared in apps/smithy-server/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 'typescript-language-server' — Declared in apps/smithy-server/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.
Third-party script without Subresource Integrity apps/website/src/layouts/BaseLayout.astro:106— `https://plausible.io/js/script.tagged-events.outbound-links.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap packages/quarry/src/cli/plugin-types.ts:224— `isValidCLIPlugin` is exported, takes a document from its caller (line 149) and hands it to `isValidCommand`, which calls itself at line 224 (`isValidCommand`) with a piece of `obj` — and nowhere in `isValidCommand` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isValidCommand` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X29 · Per-element action decided by a fixed element· Per-element action decided by a fixed element · ×1
Per-element action decided by a fixed element apps/smithy-web/src/components/workspace/WorkspaceGrid.tsx:782— This loop runs once per element of `layoutConfig.rows`, and the statement it guards acts on the element it is on — `rowIndex`. The test deciding whether that statement runs does not: `is2x2Grid && onSwap2x2Rows` reads `layoutConfig.rows[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 763, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
Orphaned file packages/quarry/src/api/quarry-api.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 REDACTED: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/quarry/src/cli/commands/external-sync.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/core/src/types/entity.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 apps/smithy-web/src/components/task/TaskDetailPanel.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 apps/smithy-next/src/components/overlays/SettingsOverlay.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 apps/smithy-next/src/components/DirectorPanel.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 apps/smithy-next/src/components/KanbanBoard.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 apps/quarry-web/src/components/task/TaskDetailPanel.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/core/src/types/playbook.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/workflows/components/WorkflowEditorModal.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 apps/smithy-next/src/App.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/smithy/src/runtime/session-manager.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/quarry/src/api/types.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 apps/quarry-web/src/routes/entities/components/EntityDetailPanel.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 apps/smithy-web/src/routes/inbox/index.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 apps/quarry-web/src/routes/inbox.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 apps/smithy-web/src/routes/editor/index.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 REDACTED: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 apps/smithy-next/src/components/overlays/TaskDetailOverlay.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/shared-routes/src/documents.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/quarry/src/external-sync/sync-engine.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 apps/quarry-web/src/components/editor/EmojiAutocomplete.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 apps/smithy-web/src/components/layout/AppShell.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/core/src/types/playbook-yaml.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.
redundant comment apps/quarry-web/src/components/dashboard/DashboardCharts.tsx:86— "Calculate tasks by status from raw task data" repeats the code it sits on: 5 of its 6 words (calculate, tasks, status, task, data) are already in `function calculateTasksByStatus(tasks: Task[]): TasksByStatusData[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/dashboard/DashboardCharts.tsx:164— "Calculate workload by agent" repeats the code it sits on: 3 of its 3 words (calculate, workload, agent) are already in `function calculateWorkloadByAgent(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/BlockEditor.tsx:577— "Render toolbar buttons" repeats the code it sits on: 3 of its 3 words (render, toolbar, buttons) are already in `const renderToolbarButton = (action: ToolbarAction) => (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:47— "Content type labels" repeats the code it sits on: 3 of its 3 words (content, type, labels) are already in `const contentTypeLabels: Record<string, string> = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:54— "Content type colors" repeats the code it sits on: 3 of its 3 words (content, type, colors) are already in `const contentTypeColors: Record<string, string> = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/EmojiAutocomplete.tsx:641— "Fuzzy search for emojis" repeats the code it sits on: 3 of its 3 words (fuzzy, search, emojis) are already in `function fuzzySearchEmoji(query: string): EmojiItem[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/EmojiAutocomplete.tsx:903— "Update recent emojis in localStorage" repeats the code it sits on: 4 of its 5 words (recent, emojis, local, storage) are already in `const stored = localStorage.getItem('stoneforge.recentEmojis');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/MentionAutocomplete.tsx:426— "Unique plugin key for mention suggestion" repeats the code it sits on: 4 of its 5 words (plugin, key, mention, suggestion) are already in `const mentionSuggestionPluginKey = new PluginKey('mentionSuggestion');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/SlashCommands.tsx:244— "Fuzzy search for commands" repeats the code it sits on: 3 of its 3 words (fuzzy, search, commands) are already in `function fuzzySearch(query: string, items: SlashCommandItem[]): SlashCommandItem[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/SlashCommands.tsx:269— "Group items by category" repeats the code it sits on: 3 of its 3 words (group, items, category) are already in `function groupByCategory(items: SlashCommandItem[])`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/editor/blocks/DocumentEmbedBlock.tsx:26— "Content type colors" repeats the code it sits on: 3 of its 3 words (content, type, colors) are already in `const contentTypeColors: Record<string, string> = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/layout/AppShell.tsx:249— "Mobile drawer state" repeats the code it sits on: 3 of its 3 words (mobile, drawer, state) are already in `const [mobileDrawerOpen, setMobileDrawerOpen] = useState(false);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/layout/AppShell.tsx:301— "Open mobile drawer" repeats the code it sits on: 3 of its 3 words (open, mobile, drawer) are already in `const openMobileDrawer = useCallback(() =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/layout/AppShell.tsx:306— "Close mobile drawer" repeats the code it sits on: 3 of its 3 words (close, mobile, drawer) are already in `const closeMobileDrawer = useCallback(() =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/shared/ContributionChart.tsx:169— "Get month labels" repeats the code it sits on: 3 of its 3 words (get, month, labels) are already in `const monthLabels = getMonthLabels(new Date(start.getTime() - startDayOfWeek * 24 * 60 * 60 * 1000), weeks.length);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/shared/VirtualizedChatList.tsx:195— "Load more when scrolled to top" repeats the code it sits on: 3 of its 3 words (load, scrolled, top) are already in `if (atTop && hasMore && !isLoadingMore && onScrollToTop)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/task/KanbanBoard.tsx:149— "Apply filters and sorting to tasks" repeats the code it sits on: 4 of its 4 words (apply, filters, sorting, tasks) are already in `function applyFiltersAndSort(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/task/KanbanBoard.tsx:216— "Get unique assignees from tasks" repeats the code it sits on: 4 of its 4 words (get, unique, assignees, tasks) are already in `function getUniqueAssignees(tasks: Task[]): string[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/task/KanbanBoard.tsx:225— "Get unique tags from tasks" repeats the code it sits on: 4 of its 4 words (get, unique, tags, tasks) are already in `function getUniqueTags(tasks: Task[]): string[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/components/task/SortByDropdown.tsx:51— "Filter out the primary sort from secondary options" repeats the code it sits on: 4 of its 5 words (filter, sort, secondary, options) are already in `const secondarySortOptions = SORT_OPTIONS.filter(opt => opt.value !== sortField);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/hooks/useDeepLink.ts:68— "Find element position when data is available" repeats the code it sits on: 4 of its 5 words (find, element, position, data) are already in `const result = data && selectedId`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/hooks/useKeyboardShortcuts.ts:77— "Start the keyboard manager" repeats the code it sits on: 3 of its 3 words (start, keyboard, manager) are already in `keyboardManager.start();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/hooks/usePaginatedData.ts:273— "Entity type filter" repeats the code it sits on: 3 of its 3 words (entity, type, filter) are already in `if (filters.entityType && filters.entityType !== 'all')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/hooks/usePaginatedData.ts:339— "Content type filter" repeats the code it sits on: 3 of its 3 words (content, type, filter) are already in `if (filters.contentType)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/quarry-web/src/hooks/usePaginatedData.ts:394— "Channel type filter" repeats the code it sits on: 3 of its 3 words (channel, type, filter) are already in `if (filters.channelType && filters.channelType !== 'all')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
+ 546 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×27
Console output used as the logging channel packages/core/src/types/playbook-yaml.ts:1233— `packages/core/src/types/playbook-yaml.ts` reports through `console.*` at line 1233 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:222— `packages/core/src/id/generator.ts` reports through `console.*` at line 222 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:348— `packages/core/src/id/generator.ts` reports through `console.*` at line 348 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:350— `packages/core/src/id/generator.ts` reports through `console.*` at line 350 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:355— `packages/core/src/id/generator.ts` reports through `console.*` at line 355 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:357— `packages/core/src/id/generator.ts` reports through `console.*` at line 357 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:362— `packages/core/src/id/generator.ts` reports through `console.*` at line 362 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:364— `packages/core/src/id/generator.ts` reports through `console.*` at line 364 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:369— `packages/core/src/id/generator.ts` reports through `console.*` at line 369 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/src/id/generator.ts:371— `packages/core/src/id/generator.ts` reports through `console.*` at line 371 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/testing/test-context.ts:171— `packages/smithy/src/testing/test-context.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:588— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 588 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1469— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1469 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1482— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1482 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1502— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1502 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1511— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1511 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1513— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1513 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1520— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1520 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1528— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1528 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1543— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1543 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1546— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1546 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/session-manager.ts:1573— `packages/smithy/src/runtime/session-manager.ts` reports through `console.*` at line 1573 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/runtime/spawner.ts:857— `packages/smithy/src/runtime/spawner.ts` reports through `console.*` at line 857 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/git/merge.ts:576— `packages/smithy/src/git/merge.ts` reports through `console.*` at line 576 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/smithy/src/git/merge.ts:594— `packages/smithy/src/git/merge.ts` reports through `console.*` at line 594 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Duplicated predicate apps/smithy-server/src/routes/tasks.ts:1017— `!blockerTask || blockerTask.type !== ElementType.TASK` appears character-identically in 2 files — apps/smithy-server/src/routes/tasks.ts, packages/smithy/src/server/routes/tasks.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/shared-routes/src/channels.ts:339— `!body.actor || typeof body.actor !== 'string'` appears character-identically in 2 files — packages/shared-routes/src/channels.ts, packages/shared-routes/src/documents.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:543— `!body.createdBy || typeof body.createdBy !== 'string'` appears character-identically in 5 files — REDACTED, packages/shared-routes/src/channels.ts, packages/shared-routes/src/documents.ts, packages/shared-routes/src/libraries.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 apps/smithy-server/src/routes/tasks.ts:831— `!body.documentId || typeof body.documentId !== 'string'` appears character-identically in 3 files — apps/smithy-server/src/routes/tasks.ts, REDACTED, packages/smithy/src/server/routes/tasks.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/shared-routes/src/channels.ts:145— `!body.name || typeof body.name !== 'string'` appears character-identically in 2 files — packages/shared-routes/src/channels.ts, packages/shared-routes/src/libraries.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 apps/smithy-server/src/routes/plugins.ts:103— `!body.plugins || !Array.isArray(body.plugins)` appears character-identically in 2 files — apps/smithy-server/src/routes/plugins.ts, packages/smithy/src/server/routes/plugins.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:540— `!body.title || typeof body.title !== 'string'` appears character-identically in 2 files — REDACTED, packages/shared-routes/src/plans.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 apps/smithy-server/src/lsp-websocket.ts:175— `!client.process || !client.process.stdin` appears character-identically in 2 files — apps/smithy-server/src/lsp-websocket.ts, packages/smithy/src/server/lsp-websocket.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 apps/quarry-web/src/routes/messages/components/ThreadPanel.tsx:111— `!content.trim() || !channel || !currentUser` appears character-identically in 2 files — apps/quarry-web/src/routes/messages/components/ThreadPanel.tsx, apps/smithy-web/src/routes/messages/components/ThreadPanel.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 apps/quarry-web/src/routes/messages/components/ThreadPanel.tsx:157— `!content.trim() || sendMessage.isPending` appears character-identically in 2 files — apps/quarry-web/src/routes/messages/components/ThreadPanel.tsx, apps/smithy-web/src/routes/messages/components/ThreadPanel.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 apps/smithy-server/src/routes/sessions.ts:857— `!displayContent && msg.type === 'tool_result'` appears character-identically in 2 files — apps/smithy-server/src/routes/sessions.ts, packages/smithy/src/server/routes/sessions.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 apps/smithy-server/src/routes/sessions.ts:854— `!displayContent && msg.type === 'tool_use' && msg.toolName` appears character-identically in 2 files — apps/smithy-server/src/routes/sessions.ts, packages/smithy/src/server/routes/sessions.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 apps/smithy-web/src/components/layout/DirectorTabContent.tsx:159— `!hasActiveSession || stopSession.isPending` appears character-identically in 2 files — apps/smithy-web/src/components/layout/DirectorTabContent.tsx, apps/smithy-web/src/components/workspace/WorkspacePane.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 apps/quarry-web/src/routes/messages/components/MessageComposer.tsx:315— `!hasContent && !hasImages && !hasAttachments` appears character-identically in 2 files — apps/quarry-web/src/routes/messages/components/MessageComposer.tsx, apps/smithy-web/src/routes/messages/components/MessageComposer.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 apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx:1432— `!inboxData || inboxData.items.length === 0` appears character-identically in 3 files — apps/quarry-web/src/routes/entities/components/EntityDetailPanel.tsx, apps/quarry-web/src/routes/inbox.tsx, apps/smithy-web/src/routes/inbox/index.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 apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx:95— `!plan || editedTitle.trim() === plan.title` appears character-identically in 2 files — apps/quarry-web/src/routes/plans/components/PlanDetailPanel.tsx, packages/ui/src/plans/components/PlanDetailPanel.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 apps/quarry-web/src/routes/inbox.tsx:1077— `!replyContent.trim() || !selectedInboxItem || !currentUser` appears character-identically in 2 files — apps/quarry-web/src/routes/inbox.tsx, apps/smithy-web/src/routes/inbox/index.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 apps/quarry-web/src/routes/inbox.tsx:1358— `!replyContent.trim() || sendReplyMutation.isPending` appears character-identically in 2 files — apps/quarry-web/src/routes/inbox.tsx, apps/smithy-web/src/routes/inbox/index.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 apps/quarry-web/src/routes/documents/index.tsx:455— `!selectedDocumentId || !isDocumentExpanded` appears character-identically in 2 files — apps/quarry-web/src/routes/documents/index.tsx, apps/smithy-web/src/routes/documents/index.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 apps/quarry-web/src/hooks/useDeepLink.ts:113— `!selectedId || !result.found || isNavigating` appears character-identically in 2 files — apps/quarry-web/src/hooks/useDeepLink.ts, apps/smithy-web/src/hooks/useDeepLink.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 apps/quarry-web/src/routes/inbox.tsx:931— `!selectedInboxItemId || !inboxData?.items` appears character-identically in 2 files — apps/quarry-web/src/routes/inbox.tsx, apps/smithy-web/src/routes/inbox/index.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 apps/smithy-server/src/routes/sessions.ts:332— `!taskResult || taskResult.type !== ElementType.TASK` appears character-identically in 2 files — apps/smithy-server/src/routes/sessions.ts, packages/smithy/src/server/routes/sessions.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/smithy/src/providers/codex/event-mapper.ts:358— `!this.pendingText || !this.pendingText.content` appears character-identically in 2 files — packages/smithy/src/providers/codex/event-mapper.ts, packages/smithy/src/providers/opencode/event-mapper.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 apps/quarry-web/src/hooks/useBreakpoint.ts:266— `'ontouchstart' in window || navigator.maxTouchPoints > 0` appears character-identically in 2 files — apps/quarry-web/src/hooks/useBreakpoint.ts, apps/smithy-web/src/hooks/useBreakpoint.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 apps/smithy-server/src/routes/tasks.ts:861— `(body.actor as EntityId) || ('el-0000' as EntityId)` appears character-identically in 5 files — apps/smithy-server/src/routes/tasks.ts, REDACTED, packages/shared-routes/src/documents.ts, packages/shared-routes/src/libraries.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.
X7 · Silent fallback defaults· Pending state with no failure state · ×22
Pending state with no failure state packages/ui/src/plans/components/CreatePlanModal.tsx:396— The view draws `Loading tasks...` under `isLoadingTasks`, but `isLoadingTasks` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state packages/ui/src/plans/components/TaskPickerModal.tsx:78— The view draws `Loading tasks...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state packages/ui/src/message/EntityLink.tsx:109— The view draws `<span className= >` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state packages/ui/src/domain/EntityLink.tsx:204— The view draws `<span className= >` under `! navigable && ! showHoverCard && entityLoading`, but `navigable` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state packages/ui/src/domain/EntityLink.tsx:250— The view draws `<div class="flex items-center justify-center py-4">` under `entityLoading`, but `entityLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state packages/ui/src/domain/EntityLink.tsx:308— The view draws `Loading stats...` under `statsLoading`, but `statsLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state packages/ui/src/domain/UserSelector.tsx:157— The view draws `Loading...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/smithy-web/src/routes/messages/components/MessageSearch.tsx:186— The view draws `Searching...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/smithy-web/src/routes/messages/components/ThreadPanel.tsx:59— The view draws `Loading replies...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/smithy-web/src/components/terminal/XTerminal.tsx:821— The view draws `Uploading...` under `isUploading`, but `isUploading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/smithy-web/src/components/editor/DocumentPickerModal.tsx:232— The view draws `Loading documents...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/smithy-web/src/components/editor/TaskPickerModal.tsx:240— The view draws `Loading tasks...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/routes/plans/components/TaskPickerModal.tsx:77— The view draws `Loading tasks...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/routes/messages/components/MessageSearch.tsx:93— The view draws `Searching...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/routes/messages/components/ThreadPanel.tsx:59— The view draws `Loading replies...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/routes/entities/components/ManagerComponents.tsx:24— The view draws `Loading...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/routes/entities/components/ManagerComponents.tsx:112— The view draws `Loading...` under `entitiesLoading`, but `entitiesLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/routes/entities/components/ManagerComponents.tsx:144— The view draws `Updating...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/components/navigation/CommandPalette.tsx:384— The view draws `Searching...` under `isSearchingMessages`, but `isSearchingMessages` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/components/navigation/CommandPalette.tsx:565— The view draws `Searching...` under `isSearchingMessages`, but `isSearchingMessages` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/components/editor/DocumentPickerModal.tsx:232— The view draws `Loading documents...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state apps/quarry-web/src/components/editor/TaskPickerModal.tsx:240— The view draws `Loading tasks...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Silent fallback default in catch apps/quarry-web/src/lib/keyboard.ts:65— `getCustomShortcuts` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch apps/smithy-next/src/components/ActiveAgentsStrip.tsx:24— `ActiveAgentsStrip` 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 apps/smithy-next/src/components/overlays/sessions/canvas/CanvasView.tsx:54— `CanvasView` 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 apps/smithy-next/src/components/overlays/SessionsOverlay.tsx:80— `SessionsOverlay` swallows every exception into `return 'cluster'` — 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 apps/smithy-web/src/components/workspace/usePaneManager.ts:61— `loadSavedLayouts` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:813— `ka` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:1436— `getWorkflowPresetSection` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/smithy/src/services/dispatch-daemon.ts:3092— `buildWorkflowPresetContextSection` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:855— `getElementCount` swallows every exception into `return 0` — 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/storage/src/bun-backend.ts:479— `getElementCount` swallows every exception into `return 0` — 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/storage/src/node-backend.ts:482— `getElementCount` swallows every exception into `return 0` — 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/ui/src/hooks/useKeyboardShortcuts.ts:377— `getCustomShortcuts` 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: WorkspaceActions (21 required operations) apps/smithy-web/src/components/workspace/types.ts:85— `WorkspaceActions` declares 21 required operations: `addPane`, `removePane`, `setActivePane`, `updatePaneStatus`, `setLayoutPreset`, `reorderPanes`, `setPaneWeight`, `saveLayout`, `loadLayout`, `clearPanes`, `startDrag`, `updateDragTarget`, `endDrag`, `cancelDrag`, `movePaneToPosition`, `swapPanes`, `movePaneUp`, `movePaneDown`, `rotateLayout`, `swapGridSections`, `swap2x2Rows`. 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.
Fat interface: QuarryAPI (68 required operations) packages/quarry/src/api/types.ts:748— `QuarryAPI` declares 68 required operations: `getIdGeneratorConfig`, `get`, `list`, `listPaginated`, `create`, `update`, `delete`, `lookupEntityByName`, `setEntityManager`, `clearEntityManager`, `getDirectReports`, `getManagementChain`, `getOrgChart`, `addTaskToPlan`, `removeTaskFromPlan`, `getTasksInPlan`, `getPlanProgress`, `createTaskInPlan`, `bulkClosePlanTasks`, `bulkDeferPlanTasks`, `bulkReassignPlanTasks`, `bulkTagPlanTasks`, `ready`, `backlog`, `blocked`, `addDependency`, `removeDependency`, `getDependencies`, `getDependents`, `getDependencyTree`, `satisfyGate`, `recordApproval`, `removeApproval`, `search`, `searchDocumentsFTS`, `archiveDocument`, `unarchiveDocument`, `registerEmbeddingService`, `reindexAllDocumentsFTS`, `getEvents`, and 28 more. 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.
Fat interface: QuarryLikeAPI (22 required operations) packages/shared-routes/src/types.ts:33— `QuarryLikeAPI` declares 22 required operations: `get`, `list`, `listPaginated`, `create`, `update`, `delete`, `search`, `searchDocumentsFTS`, `getDependencies`, `getDependents`, `addDependency`, `removeDependency`, `addChannelMember`, `removeChannelMember`, `leaveChannel`, `mergeChannels`, `getDocumentHistory`, `getDocumentVersion`, `getPlanProgress`, `getTasksInPlan`, `addTaskToPlan`, `removeTaskFromPlan`. 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.
Fat interface: OrchestratorAPI (17 required operations) packages/smithy/src/api/orchestrator-api.ts:118— `OrchestratorAPI` declares 17 required operations: `registerDirector`, `registerWorker`, `registerSteward`, `getAgent`, `getAgentByName`, `listAgents`, `getAgentsByRole`, `getAvailableWorkers`, `getStewards`, `getDirector`, `updateAgentSession`, `getAgentChannel`, `setTaskOrchestratorMeta`, `updateTaskOrchestratorMeta`, `getTaskOrchestratorMeta`, `assignTaskToAgent`, `updateAgentMetadata`. 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.
Fat interface: AgentRegistry (20 required operations) packages/smithy/src/services/agent-registry.ts:118— `AgentRegistry` declares 20 required operations: `registerAgent`, `registerDirector`, `registerWorker`, `registerSteward`, `getAgent`, `getAgentByName`, `listAgents`, `getAgentsByRole`, `getAvailableWorkers`, `getStewards`, `getDirector`, `getDirectors`, `getAvailableDirector`, `updateAgentSession`, `updateAgentMetadata`, `updateAgent`, `deleteAgent`, `getAgentChannel`, `getAgentChannelId`, `ensureAgentChannel`. 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.
Fat interface: SessionManager (20 required operations) packages/smithy/src/runtime/session-manager.ts:251— `SessionManager` declares 20 required operations: `startSession`, `resumeSession`, `stopSession`, `suspendSession`, `interruptSession`, `getSession`, `getActiveSession`, `listSessions`, `getMostRecentResumableSession`, `getSessionHistory`, `getSessionHistoryByRole`, `getPreviousSession`, `messageSession`, `getEventEmitter`, `recordUserInput`, `getSessionUserIdleMs`, `persistSession`, `loadSessionState`, `reconcileOnStartup`, `setOperationLog`. 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.
Fat interface: WorktreeManager (17 required operations) REDACTED:206— `WorktreeManager` declares 17 required operations: `initWorkspace`, `isInitialized`, `getWorkspaceRoot`, `createWorktree`, `createReadOnlyWorktree`, `removeWorktree`, `suspendWorktree`, `resumeWorktree`, `listWorktrees`, `getWorktree`, `getWorktreePath`, `getWorktreesForAgent`, `worktreeExists`, `ensureWorktreeRemote`, `getCurrentBranch`, `getDefaultBranch`, `branchExists`. 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.
Fat interface: StewardScheduler (20 required operations) REDACTED:184— `StewardScheduler` declares 20 required operations: `start`, `stop`, `isRunning`, `registerSteward`, `unregisterSteward`, `refreshSteward`, `registerAllStewards`, `executeSteward`, `publishEvent`, `getScheduledJobs`, `getEventSubscriptions`, `getExecutionHistory`, `getLastExecution`, `getStats`, `on`, `on`, `on`, `on`, `on`, `off`. 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. Those 20 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: DispatchDaemon (26 required operations) packages/smithy/src/services/dispatch-daemon.ts:355— `DispatchDaemon` declares 26 required operations: `start`, `stop`, `isRunning`, `pollWorkerAvailability`, `pollInboxes`, `pollStewardTriggers`, `pollWorkflowTasks`, `recoverOrphanedAssignments`, `reconcileClosedUnmergedTasks`, `recoverStuckMergeTasks`, `pollPlanAutoComplete`, `pollWorkflowAutoTransition`, `handleRateLimitDetected`, `getRateLimitStatus`, `sleepUntil`, `wake`, `getConfig`, `updateConfig`, `on`, `on`, `on`, `on`, `on`, `on`, `on`, `off`. 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. Those 26 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: StorageBackend (21 required operations) packages/storage/src/backend.ts:37— `StorageBackend` declares 21 required operations: `close`, `exec`, `query`, `queryOne`, `run`, `prepare`, `transaction`, `getSchemaVersion`, `setSchemaVersion`, `migrate`, `markDirty`, `getDirtyElements`, `clearDirty`, `clearDirtyElements`, `getNextChildNumber`, `getChildCounter`, `resetChildCounter`, `getElementCount`, `checkIntegrity`, `optimize`, `getStats`. 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.
D21 · Naming Consistency· `sessionID` spells `ID` where 1530 names in the project spell it `Id` · ×6
`sessionID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:56— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `sessionId`. [rule N6]
`sessionID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:63— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `sessionId`. [rule N6]
`sessionID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:72— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `sessionId`. [rule N6]
`sessionID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:78— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `sessionId`. [rule N6]
`sessionID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:84— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `sessionId`. [rule N6]
`sessionID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:90— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `sessionId`. [rule N6]
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×5
Diagnostic log message is built whether or not it is wanted packages/smithy/src/services/dispatch-daemon.ts:4235— `debug` at line 4235 is called with an argument built by `conflicts.join(', ')` (line 4235), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/smithy/src/server/events-websocket.ts:107— `debug` at line 107 is called with an argument built by `channels.join(', ')` (line 107), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/smithy/src/server/events-websocket.ts:116— `debug` at line 116 is called with an argument built by `channels.join(', ')` (line 116), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted apps/smithy-server/src/events-websocket.ts:107— `debug` at line 107 is called with an argument built by `channels.join(', ')` (line 107), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted apps/smithy-server/src/events-websocket.ts:116— `debug` at line 116 is called with an argument built by `channels.join(', ')` (line 116), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Deprecated: lodash.isequal REDACTED:8233— lodash.isequal 4.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rollup-plugin-inject REDACTED:10214— rollup-plugin-inject 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: sourcemap-codec REDACTED:10509— sourcemap-codec 1.4.8 is resolved in REDACTED and is marked deprecated by its publisher: "Please use @jridgewell/sourcemap-codec instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file REDACTED:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file apps/smithy-next/src/mock-data.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file packages/smithy/src/services/dispatch-daemon.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Hand-rolled JSON/XML parsing via regex packages/quarry/web/assets/editor-vendor-BxraAWts.js:161— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/quarry/web/assets/editor-vendor-BxraAWts.js:221— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex packages/quarry/web/assets/index-B77vv208.js:256— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
D21 · Naming Consistency· `providerID` spells `ID` where 1530 names in the project spell it `Id` · ×2
`providerID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/server-manager.ts:42— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `providerId`. [rule N6]
`providerID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/server-manager.ts:75— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `providerId`. [rule N6]
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung apps/smithy-web/package.json:68— Accessibility checks run in tests (Verified) but aren't gated in CI — run the suite that holds those checks in your pipeline so an accessibility regression blocks the merge (Prevented). What was searched, so you can tell an absence from a miss: the 555 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.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies apps/smithy-web/src/components/activity/ActiveAgentCard.tsx:50— Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Outdated (npm): @astrojs/mdx apps/website/package.json:12— @astrojs/mdx is pinned at 4.3.13; registry.npmjs.org publishes 8.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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/`.
D21 · Naming Consistency· `getWsUrl` spells `Ws` where 24 names in the project spell it `WS` · ×1
`getWsUrl` spells `Ws` where 24 names in the project spell it `WS` apps/quarry-web/src/api/hooks/useRealtimeEvents.ts:36— 24 of 26 names in project stoneforge spell the token `WS` (24 of 26; unit: names in project stoneforge containing `WS`). Peers: apps.smithy-server.src.events-websocket.EventsWSClientData (apps/smithy-server/src/events-websocket.ts:26); events-websocket.handleEventsWSOpen (apps/smithy-server/src/events-websocket.ts:55); events-websocket.handleEventsWSMessage (apps/smithy-server/src/events-websocket.ts:84); events-websocket.handleEventsWSClose (apps/smithy-server/src/events-websocket.ts:125); apps.smithy-server.src.lsp-websocket.LspWSClientData (apps/smithy-server/src/lsp-websocket.ts:18). Rename to `getWSUrl`. [rule N6]
D21 · Naming Consistency· `getEventsWsUrl` spells `Ws` where 24 names in the project spell it `WS` · ×1
`getEventsWsUrl` spells `Ws` where 24 names in the project spell it `WS` apps/smithy-web/src/api/hooks/useRealtimeEvents.ts:36— 24 of 26 names in project stoneforge spell the token `WS` (24 of 26; unit: names in project stoneforge containing `WS`). Peers: apps.smithy-server.src.events-websocket.EventsWSClientData (apps/smithy-server/src/events-websocket.ts:26); events-websocket.handleEventsWSOpen (apps/smithy-server/src/events-websocket.ts:55); events-websocket.handleEventsWSMessage (apps/smithy-server/src/events-websocket.ts:84); events-websocket.handleEventsWSClose (apps/smithy-server/src/events-websocket.ts:125); apps.smithy-server.src.lsp-websocket.LspWSClientData (apps/smithy-server/src/lsp-websocket.ts:18). Rename to `getEventsWSUrl`. [rule N6]
D21 · Naming Consistency· `callID` spells `ID` where 1530 names in the project spell it `Id` · ×1
`callID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/event-mapper.ts:64— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `callId`. [rule N6]
D21 · Naming Consistency· `projectID` spells `ID` where 1530 names in the project spell it `Id` · ×1
`projectID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/server-manager.ts:18— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `projectId`. [rule N6]
D21 · Naming Consistency· `modelID` spells `ID` where 1530 names in the project spell it `Id` · ×1
`modelID` spells `ID` where 1530 names in the project spell it `Id` packages/smithy/src/providers/opencode/server-manager.ts:76— 1530 of 1541 names in project stoneforge spell the token `Id` (1530 of 1541; unit: names in project stoneforge containing `Id`). Peers: handler.generateClientId (apps/quarry-server/src/ws/handler.ts:30); handler.broadcastInboxEvent(itemId) (apps/quarry-server/src/ws/handler.ts:173); handler.broadcastInboxEvent(recipientId) (apps/quarry-server/src/ws/handler.ts:173); Workflow.playbookId (apps/quarry-web/src/api/hooks/useAllElements.ts:58); Message.threadId (apps/quarry-web/src/api/hooks/useAllElements.ts:109). Rename to `modelId`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 7 of 14 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `apps/smithy-web` (63757 LoC, 497 module-visible types across 43 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.
Dormant codebase — 817 of 817 significant files have no living knowledge — the codebase as a whole is dormant, not 817 separate risks. Counted over 817 of the 1076 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
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 3/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/smithy-next`, `packages/quarry`, `packages/shared-routes`.
No SAST REDACTED:6— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 7984 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation package.json:29— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
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 14/194 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) reduce the strict null checking score — ~0.9 `!` null assertions per 1k TypeScript source lines — 322 assertion(s) across the 341886 source line(s) of the 1051 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/quarry/src/cli/commands/external-sync.ts (22), packages/quarry/src/api/quarry-api.ts (19), apps/smithy-next/src/components/KanbanBoard.tsx (9). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @anthropic-ai/claude-agent-sdk — @anthropic-ai/claude-agent-sdk is pinned at 0.2.45; registry.npmjs.org publishes 0.3.319 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @astrojs/rss — @astrojs/rss is pinned at 4.0.15; registry.npmjs.org publishes 4.0.19 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @astrojs/sitemap — @astrojs/sitemap is pinned at 3.7.0; registry.npmjs.org publishes 3.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @astrojs/starlight — @astrojs/starlight is pinned at 0.32.6; registry.npmjs.org publishes 0.42.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hono/node-server — @hono/node-server is pinned at 1.19.9; registry.npmjs.org publishes 2.1.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-alert-dialog — @radix-ui/react-alert-dialog is pinned at 1.1.15; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-collapsible — @radix-ui/react-collapsible is pinned at 1.1.12; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-context-menu — @radix-ui/react-context-menu is pinned at 2.2.16; registry.npmjs.org publishes 2.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-dialog — @radix-ui/react-dialog is pinned at 1.1.15; registry.npmjs.org publishes 1.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-dropdown-menu — @radix-ui/react-dropdown-menu is pinned at 2.1.16; registry.npmjs.org publishes 2.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-hover-card — @radix-ui/react-hover-card is pinned at 1.1.15; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-select — @radix-ui/react-select is pinned at 2.2.6; registry.npmjs.org publishes 2.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-tooltip — @radix-ui/react-tooltip is pinned at 1.2.8; registry.npmjs.org publishes 1.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tanstack/react-query — @tanstack/react-query is pinned at 5.90.20; registry.npmjs.org publishes 5.107.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tanstack/react-router — @tanstack/react-router is pinned at 1.157.16; registry.npmjs.org publishes 1.170.46 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tanstack/react-virtual — @tanstack/react-virtual is pinned at 3.13.18; registry.npmjs.org publishes 3.14.26 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/core — @tiptap/core is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-bubble-menu — @tiptap/extension-bubble-menu is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-code-block-lowlight — @tiptap/extension-code-block-lowlight is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-document — @tiptap/extension-document is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-highlight — @tiptap/extension-highlight is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-horizontal-rule — @tiptap/extension-horizontal-rule is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-image — @tiptap/extension-image is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-link — @tiptap/extension-link is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tiptap/extension-placeholder — @tiptap/extension-placeholder is pinned at 3.17.1; registry.npmjs.org publishes 3.33.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names packages/core/src/errors/codes.ts:22— 15 of 352 documented parameters and 66 of 1783 summaries in `@stoneforge/core` only repeat the member or parameter name (e.g. "Required field missing" for `MISSING_REQUIRED_FIELD`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/quarry/src/api/channel-membership.integration.bun.test.ts:46— 17 of 508 documented parameters and 91 of 2051 summaries in `@stoneforge/quarry` only repeat the member or parameter name (e.g. "Create a test group channel" for `createTestGroupChannel`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names apps/quarry-web/src/api/hooks/useAllElements.ts:552— 0 of 61 documented parameters and 23 of 447 summaries in `@stoneforge/quarry-web` only repeat the member or parameter name (e.g. "Remove an element from the cache" for `removeElementFromCache`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools/seo/serp-analysis.ts:89— 0 of 0 documented parameters and 1 of 15 summaries in `@stoneforge/seo-tools` only repeat the member or parameter name (e.g. "Delay between batches in ms" for `BATCH_DELAY_MS`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/shared-routes/src/ws/broadcaster.ts:54— 0 of 0 documented parameters and 3 of 34 summaries in `@stoneforge/shared-routes` only repeat the member or parameter name (e.g. "Remove a listener" for `removeListener`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/smithy/src/api/orchestrator-api.ts:148— 15 of 285 documented parameters and 122 of 2012 summaries in `@stoneforge/smithy` only repeat the member or parameter name (e.g. "Gets an agent by name" for `getAgentByName`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names apps/smithy-server/src/daemon-state.ts:51— 0 of 0 documented parameters and 8 of 88 summaries in `@stoneforge/smithy-server` only repeat the member or parameter name (e.g. "Save the daemon state." for `saveDaemonState`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names apps/smithy-web/src/api/hooks/useActivity.ts:228— 6 of 62 documented parameters and 49 of 1150 summaries in `@stoneforge/smithy-web` only repeat the member or parameter name (e.g. "Get display name for event type" for `getEventTypeDisplayName`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/storage/src/backend.ts:142— 1 of 35 documented parameters and 6 of 200 summaries in `@stoneforge/storage` only repeat the member or parameter name (e.g. "Get the current schema version" for `getSchemaVersion`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/ui/src/api/api-client.ts:40— 0 of 13 documented parameters and 43 of 657 summaries in `@stoneforge/ui` only repeat the member or parameter name (e.g. "Request options" for `RequestOptions`). Delete the restating tags, or add what the name does not say.
Skipped (documented): (unnamed test) packages/smithy/src/runtime/spawner.integration.bun.test.ts:71— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) packages/smithy/src/runtime/spawner.integration.bun.test.ts:100— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) packages/smithy/src/runtime/spawner.integration.bun.test.ts:137— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) packages/smithy/src/runtime/spawner.integration.bun.test.ts:159— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 19 file(s) — `apps/smithy-next/src/components/overlays/TaskDetailOverlay.tsx`, `apps/smithy-next/src/components/overlays/automations/WorkflowDetailView.tsx`, `apps/smithy-next/src/components/overlays/ci/CIRunDetailView.tsx`, `apps/smithy-server/src/routes/events.ts`, `apps/smithy-server/src/routes/sessions.ts`, … (+14 more) — 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 01a1bf9c-f672-7bb1-b7d7-ce6003ea065d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 173 · Warnings: 3224 · Recommendations: 1526 · Info: 70 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 09-11-2026 @ 09:21 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.