Public report of runvendo/vendo, published 17 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.4). 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, 17 November 2026, 10:40 UTC · Survey ID cd_c17746ee398541aaacd9bc7b21206511
runvendo/vendo
Measured 17 November 2026, 10:39 UTC, at code version 4d14993
First survey, so nothing to compare with yet
CAI scoreAt risk
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: 185,982 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 3.4 person-years · Weakest lens: Production Readiness, 44.1
Findings by how serious they are
63 critical1648 serious214 minor
8 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
17 November 2026, 10:39 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 ▸
81of 81 dimensions measured by tools.
1867of 1925 findings point to an exact file and line, so you can open each one in the code. The other 58 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 185,982 lines of product code in 6 projects.
runvendo/vendo is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because three passwords or keys sit in the current code and it has packages under a licence on your banned list. It scores 54.8 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 44.1, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 9.4 points. Replacing the four deprecated dependencies comes next, worth about 8.3 points. Raising Production Readiness to 62 would lift the score to about 62.6.
Twenty-eight known security holes in the packages the code depends on can be used by attackers. Fifteen packages carry licence risk, and four passwords or keys in the code's history and three in the code are open to anyone who can read the repository. Updating the vulnerable packages, replacing or clearing the banned-licence packages and replacing each exposed password or key would close these risks. Setting a waiting period for automatic updates would fix the two automatic dependency updates that take new releases at once, and pinning each tool to an exact version would deal with the two pipeline tools referenced by a changeable name. The three loops of files that import each other need breaking.
The product code is 185,982 lines, about €500,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 44.1 to 62, the lowest score rated Strong, the score would rise from 54.8 to about 62.6.
Code composition: what the lines of code are
Product code 45%Tests 55%
Rebuild cost: about €500,000 · Estimate
Cost to rebuild
€160,000 to €830,000, for 2,742 to 8,699 hours of work, about 3.4 person-years for 2 to 7 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.8 at a score of 55. 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: 185,982 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 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3).
Raises the score by about 9.4 points · Low effort · REDACTED Scanning
2
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4).
Resolve the 15 Banned license finding(s) in License Compliance — start with REDACTED (15).
Raises the score by about 9.4 points · Medium effort · License Compliance
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
76 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (105 files) · Code Coverage (482 files under half tested) · The files: REDACTED, vendo-overlay.tsx and index.tsx
What to do: Add tests to these files and have a second person review every change to them, starting with REDACTED, vendo-overlay.tsx and index.tsx.
Where the investment is most exposed · Value at risk
This code would cost about €500,000 to build again, about 3.4 person-years of work. Its weakest lens is Production Readiness, at 44.1 (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 3 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 9.4 points for low effort, because it clears the 3 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 950,727 lines over the last 90 days, which is about 3,855,726 lines a year. At that pace, the extra work comes to an estimated 547 to 3282.2 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.
579 modules, with 1217 dependencies between them. 6 loops run through 13 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 539 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.
packages.vendo.src.apps.checking uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.apps.checking, while a change to packages.vendo.src.apps.checking can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.apps.checking uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.checking uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src.apps.checking, while a change to packages.vendo.src.apps.checking can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src.apps.checking uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.checking uses packages.vendo.src.core.genui.tree-node, so a change to packages.vendo.src.core.genui.tree-node can break packages.vendo.src.apps.checking, while a change to packages.vendo.src.apps.checking can't break packages.vendo.src.core.genui.tree-node.
Position
Below the diagonal: packages.vendo.src.apps.checking uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.automation uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.core.automation, while a change to packages.vendo.src.core.automation can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.core.automation uses a module listed above it, which is the healthy direction.
11→19 packages.vendo.src.core.tools uses packages.vendo.src.core.run-contextpart of a loop✕
Connections
1 pair of types, where a type in packages.vendo.src.core.tools uses a type in packages.vendo.src.core.run-context.
packages.vendo.src.core.tools uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.core.tools, while a change to packages.vendo.src.core.tools can't break packages.vendo.src.core.run-context.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.vendo.src.store.store uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.store.store, while a change to packages.vendo.src.store.store can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.store.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.ui.chrome uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src.ui.chrome, while a change to packages.vendo.src.ui.chrome can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src.ui.chrome uses a module listed above it, which is the healthy direction.
packages.vendo.src.ui.chrome uses packages.vendo.src.core.genui.tree-node, so a change to packages.vendo.src.core.genui.tree-node can break packages.vendo.src.ui.chrome, while a change to packages.vendo.src.ui.chrome can't break packages.vendo.src.core.genui.tree-node.
Position
Below the diagonal: packages.vendo.src.ui.chrome uses a module listed above it, which is the healthy direction.
packages.vendo.src.actions.formats uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.actions.formats, while a change to packages.vendo.src.actions.formats can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.actions.formats uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.grants uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.core.grants, while a change to packages.vendo.src.core.grants can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.core.grants uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.harness uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.core.harness, while a change to packages.vendo.src.core.harness can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.core.harness uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.harness uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.core.harness, while a change to packages.vendo.src.core.harness can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.core.harness uses a module listed above it, which is the healthy direction.
packages.vendo.src.actions.sync uses packages.vendo.src.actions.formats, so a change to packages.vendo.src.actions.formats can break packages.vendo.src.actions.sync, while a change to packages.vendo.src.actions.sync can't break packages.vendo.src.actions.formats.
Position
Below the diagonal: packages.vendo.src.actions.sync uses a module listed above it, which is the healthy direction.
packages.vendo.src.cli uses packages.vendo.src.cli.shared, so a change to packages.vendo.src.cli.shared can break packages.vendo.src.cli, while a change to packages.vendo.src.cli can't break packages.vendo.src.cli.shared.
Position
Below the diagonal: packages.vendo.src.cli uses a module listed above it, which is the healthy direction.
packages.vendo.src.cli uses packages.vendo.src.actions.formats, so a change to packages.vendo.src.actions.formats can break packages.vendo.src.cli, while a change to packages.vendo.src.cli can't break packages.vendo.src.actions.formats.
Position
Below the diagonal: packages.vendo.src.cli uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.run-context uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.core.run-context, while a change to packages.vendo.src.core.run-context can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.core.run-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.run-context uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.core.run-context, while a change to packages.vendo.src.core.run-context can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.core.run-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.guard.types uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.guard.types, while a change to packages.vendo.src.guard.types can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.guard.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.guard.types uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.guard.types, while a change to packages.vendo.src.guard.types can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.guard.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.guard.types uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.guard.types, while a change to packages.vendo.src.guard.types can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.guard.types uses a module listed above it, which is the healthy direction.
genbench.src uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break genbench.src, while a change to genbench.src can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: genbench.src uses a module listed above it, which is the healthy direction.
genbench.src uses packages.vendo.src.core.genui.tree-node, so a change to packages.vendo.src.core.genui.tree-node can break genbench.src, while a change to genbench.src can't break packages.vendo.src.core.genui.tree-node.
Position
Below the diagonal: genbench.src uses a module listed above it, which is the healthy direction.
genbench.src uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break genbench.src, while a change to genbench.src can't break packages.vendo.src.core.tools.
Position
Below the diagonal: genbench.src uses a module listed above it, which is the healthy direction.
genbench.src uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break genbench.src, while a change to genbench.src can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: genbench.src uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.conformance uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.core.conformance, while a change to packages.vendo.src.core.conformance can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.core.conformance uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.conformance uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.core.conformance, while a change to packages.vendo.src.core.conformance can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.core.conformance uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.guard uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.core.guard, while a change to packages.vendo.src.core.guard can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.core.guard uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.guard uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.core.guard, while a change to packages.vendo.src.core.guard can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.core.guard uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.guard uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.core.guard, while a change to packages.vendo.src.core.guard can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.core.guard uses a module listed above it, which is the healthy direction.
packages.vendo.src.core.guard uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.core.guard, while a change to packages.vendo.src.core.guard can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.core.guard uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.harness-turn uses packages.vendo.src.guard.types, so a change to packages.vendo.src.guard.types can break packages.vendo.src.harness-turn, while a change to packages.vendo.src.harness-turn can't break packages.vendo.src.guard.types.
Position
Below the diagonal: packages.vendo.src.harness-turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.store uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in packages.vendo.src.store uses a type in packages.vendo.src.core.store. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
packages.vendo.src.store uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.store uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.store uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.store uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.store uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.store uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.store, while a change to packages.vendo.src.store can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.store uses a module listed above it, which is the healthy direction.
packages.vendo.src.store.helpers uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.store.helpers, while a change to packages.vendo.src.store.helpers can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.store.helpers uses a module listed above it, which is the healthy direction.
packages.vendo.src.store.helpers uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.store.helpers, while a change to packages.vendo.src.store.helpers can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.store.helpers uses a module listed above it, which is the healthy direction.
packages.vendo.src.store.helpers uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.store.helpers, while a change to packages.vendo.src.store.helpers can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.store.helpers uses a module listed above it, which is the healthy direction.
packages.vendo.src.store.helpers uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.store.helpers, while a change to packages.vendo.src.store.helpers can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.store.helpers uses a module listed above it, which is the healthy direction.
packages.vendo.src.store.helpers uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.store.helpers, while a change to packages.vendo.src.store.helpers can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.store.helpers uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn.agent uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.turn.agent, while a change to packages.vendo.src.turn.agent can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.turn.agent uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn.agent uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src.turn.agent, while a change to packages.vendo.src.turn.agent can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src.turn.agent uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn.agent uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.turn.agent, while a change to packages.vendo.src.turn.agent can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.turn.agent uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn.agent uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.turn.agent, while a change to packages.vendo.src.turn.agent can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.turn.agent uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn.agent uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src.turn.agent, while a change to packages.vendo.src.turn.agent can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src.turn.agent uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn.agent uses packages.vendo.src.guard.types, so a change to packages.vendo.src.guard.types can break packages.vendo.src.turn.agent, while a change to packages.vendo.src.turn.agent can't break packages.vendo.src.guard.types.
Position
Below the diagonal: packages.vendo.src.turn.agent uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.types uses packages.vendo.src.core.guard, so a change to packages.vendo.src.core.guard can break packages.vendo.src.apps.runtime.types, while a change to packages.vendo.src.apps.runtime.types can't break packages.vendo.src.core.guard.
Position
Below the diagonal: packages.vendo.src.apps.runtime.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.automations uses packages.vendo.src.core.guard, so a change to packages.vendo.src.core.guard can break packages.vendo.src.automations, while a change to packages.vendo.src.automations can't break packages.vendo.src.core.guard.
Position
Below the diagonal: packages.vendo.src.automations uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.core uses packages.vendo.src.core.conformance, so a change to packages.vendo.src.core.conformance can break packages.vendo.src.core, while a change to packages.vendo.src.core can't break packages.vendo.src.core.conformance.
Position
Below the diagonal: packages.vendo.src.core uses a module listed above it, which is the healthy direction.
packages.vendo.src.harnesses uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.harnesses, while a change to packages.vendo.src.harnesses can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.harnesses uses a module listed above it, which is the healthy direction.
packages.vendo.src.harnesses uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.harnesses, while a change to packages.vendo.src.harnesses can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.harnesses uses a module listed above it, which is the healthy direction.
packages.vendo.src.harnesses uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src.harnesses, while a change to packages.vendo.src.harnesses can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src.harnesses uses a module listed above it, which is the healthy direction.
packages.vendo.src.harnesses uses packages.vendo.src.core.guard, so a change to packages.vendo.src.core.guard can break packages.vendo.src.harnesses, while a change to packages.vendo.src.harnesses can't break packages.vendo.src.core.guard.
Position
Below the diagonal: packages.vendo.src.harnesses uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.turn uses packages.vendo.src.turn.agent, so a change to packages.vendo.src.turn.agent can break packages.vendo.src.turn, while a change to packages.vendo.src.turn can't break packages.vendo.src.turn.agent.
Position
Below the diagonal: packages.vendo.src.turn uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.runtime-context uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.apps.runtime.runtime-context, while a change to packages.vendo.src.apps.runtime.runtime-context can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.apps.runtime.runtime-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.runtime-context uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.apps.runtime.runtime-context, while a change to packages.vendo.src.apps.runtime.runtime-context can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.apps.runtime.runtime-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.runtime.runtime-context uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.apps.runtime.runtime-context, while a change to packages.vendo.src.apps.runtime.runtime-context can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.apps.runtime.runtime-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.guard.types, so a change to packages.vendo.src.guard.types can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.guard.types.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.harness-turn, so a change to packages.vendo.src.harness-turn can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.harness-turn.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.compose-context uses packages.vendo.src.automations, so a change to packages.vendo.src.automations can break packages.vendo.src.compose-context, while a change to packages.vendo.src.compose-context can't break packages.vendo.src.automations.
Position
Below the diagonal: packages.vendo.src.compose-context uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.core.guard, so a change to packages.vendo.src.core.guard can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.core.guard.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.mcp.door uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.mcp.door, while a change to packages.vendo.src.mcp.door can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.mcp.door uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.guard.types, so a change to packages.vendo.src.guard.types can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.guard.types.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.harness-turn, so a change to packages.vendo.src.harness-turn can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.harness-turn.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.types uses packages.vendo.src.automations, so a change to packages.vendo.src.automations can break packages.vendo.src.types, while a change to packages.vendo.src.types can't break packages.vendo.src.automations.
Position
Below the diagonal: packages.vendo.src.types uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.doors uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.apps.doors, while a change to packages.vendo.src.apps.doors can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.apps.doors uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.doors uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src.apps.doors, while a change to packages.vendo.src.apps.doors can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src.apps.doors uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.doors uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.apps.doors, while a change to packages.vendo.src.apps.doors can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.apps.doors uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.doors uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.apps.doors, while a change to packages.vendo.src.apps.doors can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.apps.doors uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.doors uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.apps.doors, while a change to packages.vendo.src.apps.doors can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.apps.doors uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.doors uses packages.vendo.src.apps.runtime.runtime-context, so a change to packages.vendo.src.apps.runtime.runtime-context can break packages.vendo.src.apps.doors, while a change to packages.vendo.src.apps.doors can't break packages.vendo.src.apps.runtime.runtime-context.
Position
Below the diagonal: packages.vendo.src.apps.doors uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.genui.tree-node, so a change to packages.vendo.src.core.genui.tree-node can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.genui.tree-node.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.apps.persistence uses packages.vendo.src.apps.runtime.runtime-context, so a change to packages.vendo.src.apps.runtime.runtime-context can break packages.vendo.src.apps.persistence, while a change to packages.vendo.src.apps.persistence can't break packages.vendo.src.apps.runtime.runtime-context.
Position
Below the diagonal: packages.vendo.src.apps.persistence uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.guard.types, so a change to packages.vendo.src.guard.types can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.guard.types.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.harness-turn, so a change to packages.vendo.src.harness-turn can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.harness-turn.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.automations, so a change to packages.vendo.src.automations can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.automations.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src.wire.shared uses packages.vendo.src.mcp.door, so a change to packages.vendo.src.mcp.door can break packages.vendo.src.wire.shared, while a change to packages.vendo.src.wire.shared can't break packages.vendo.src.mcp.door.
Position
Below the diagonal: packages.vendo.src.wire.shared uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.app-document, so a change to packages.vendo.src.core.app-document can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.app-document.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.apps.catalog, so a change to packages.vendo.src.core.apps.catalog can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.apps.catalog.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.genui.tree-node, so a change to packages.vendo.src.core.genui.tree-node can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.genui.tree-node.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.principal, so a change to packages.vendo.src.core.principal can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.principal.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.store, so a change to packages.vendo.src.core.store can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.store.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.workspace, so a change to packages.vendo.src.core.workspace can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.workspace.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.automation, so a change to packages.vendo.src.core.automation can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.automation.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.tools, so a change to packages.vendo.src.core.tools can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.tools.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.store.store, so a change to packages.vendo.src.store.store can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.store.store.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.actions.formats, so a change to packages.vendo.src.actions.formats can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.actions.formats.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.grants, so a change to packages.vendo.src.core.grants can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.grants.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.harness, so a change to packages.vendo.src.core.harness can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.harness.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.run-context, so a change to packages.vendo.src.core.run-context can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.run-context.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.guard.types, so a change to packages.vendo.src.guard.types can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.guard.types.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.core.guard, so a change to packages.vendo.src.core.guard can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.core.guard.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.harness-turn, so a change to packages.vendo.src.harness-turn can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.harness-turn.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.turn.agent, so a change to packages.vendo.src.turn.agent can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.turn.agent.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.apps.runtime.types, so a change to packages.vendo.src.apps.runtime.types can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.apps.runtime.types.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.automations, so a change to packages.vendo.src.automations can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.automations.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.compose-context, so a change to packages.vendo.src.compose-context can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.compose-context.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.mcp.door, so a change to packages.vendo.src.mcp.door can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.mcp.door.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.types, so a change to packages.vendo.src.types can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.types.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
packages.vendo.src uses packages.vendo.src.wire.shared, so a change to packages.vendo.src.wire.shared can break packages.vendo.src, while a change to packages.vendo.src can't break packages.vendo.src.wire.shared.
Position
Below the diagonal: packages.vendo.src uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64.1 · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
70
High / Critical
A03:2025 — Software Supply Chain Failures
55
High / Critical
A07:2025 — Authentication Failures
8
High / Critical
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3); Resolve the 15 Banned license finding(s) in License Compliance — start with REDACTED (15); Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3).
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.
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.
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 — 63
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 — 1648
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 — 214
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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 81 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 81 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, 1867 of 1925 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 — 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. 114 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 514 production file(s) those files import are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 56.3% whatever they read, rather than published as low coverage or counted toward the figure. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from 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 (7 contributor(s) across 4049 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 6 hold 0.3% 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 — 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. 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 — 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. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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. `packages/vendo/src/actions/formats.ts`, `packages/vendo/src/actions/openapi-document.ts`, `packages/vendo/src/actions/sync/route-scan.ts`, `packages/vendo/src/actions/sync/schema-patch.ts`, `packages/vendo/src/actions/sync/server-actions.ts`, … (+61 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.
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/vendo/src/core/host-seams.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.
C1 Data Protection — 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. 'pg' is imported (packages/vendo/src/store/db-postgres.ts:7), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — 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. 'pg' is imported (packages/vendo/src/store/db-postgres.ts:7), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — 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. 'pg' is imported (packages/vendo/src/store/db-postgres.ts:7), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — 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. 'pg' is imported (packages/vendo/src/store/db-postgres.ts:7), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
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.
P2 Observability — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
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. 219 further occurrence(s) are not listed individually; the score already reflects all 259.
R2 Cyclomatic Complexity — 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. 406 further occurrence(s) are not listed individually; the score already reflects all 446.
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. 64 further occurrence(s) are not listed individually; the score already reflects all 104.
X10 Duplicated predicate — 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. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
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. 59 further occurrence(s) are not listed individually; the score already reflects all 99.
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, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages 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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
194 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was memory-store-ops.memoryStoreOps at 131. A further 1 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 boot.answerIntl at 27 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/vendo/src/core/apps/genui/component/boot.ts (boot.answerIntl at 27). 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.
+ 189 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with memory-store-ops.memoryStoreOps (cyclomatic 131), vendo-overlay.VendoOverlay (cyclomatic 98), index.VendoThread (cyclomatic 90). — 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 5 together lifts Cyclomatic Complexity from 4.7 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 282 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with memory-store-ops.memoryStoreOps (cognitive 172). — Refactoring it lifts Cognitive Complexity from 2.5 to about 3.3/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.5 / 10Strong✓ 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 45 FunctionTooLong finding(s) in God Classes — start with harness-turn.ts (2), runtime.ts (2), vendo.ts (2). — One of this dimension's main actionable groups (45 warning-level).
Resolve the 24 FileTooLong finding(s) in God Classes — start with guard.ts, store-ops.ts, REDACTED. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with guard.ts, server.ts, door.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
5 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 56.3% — 609 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in corpus/harness/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in corpus/hosts/express-host/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in examples/ai-sdk-agent/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in examples/demo-bank/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in examples/mastra-agent/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in fixtures/automations-e2e/, the 3 run(s) test reliability made; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in fixtures/existing-agents-e2e/, the 3 run(s) test reliability made; vitest in fixtures/install-seam/: not run; vitest in fixtures/integration/: not run). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
Resolve the 609 Low coverage finding(s) in Code Coverage — start with REDACTED (36), page.tsx (16), index.ts (16). — One of this dimension's main actionable groups (609 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 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.
20 skipped (6 with a documented reason), 21 zero-assertion, 6 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 9882 tests.
No assertions (empty test): postgres leg configuredpackages/vendo/tests/store/postgres-gate.test.ts:4
No assertions: auto-derives the dock from the wire catalog when no connectors prop is passed · ×20packages/vendo/tests/ui/chrome/affordances-eng225.test.tsx:292
Skipped test: dedupes every failed firing onto ONE card per missing grant per app · ×14packages/vendo/tests/audit-superset.e2e.test.ts:524
Fixed-sleep synchronisation: never re-sends the same refused report on a later resolution cycle · ×6packages/vendo/tests/config-report-producer.seam.test.ts:203
Mock-dominated test: renders a tagged open-in-product result exactly once with the %s ordering · ×2packages/vendo/tests/ui/mcp-shim-core.test.ts:132
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with postgres-gate.test.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 20 No assertions finding(s) in Test Quality — start with review-failure-protocol.test.ts (5), affordances-eng225.test.tsx (3), interruptions-adversarial.test.ts (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 14 Skipped test finding(s) in Test Quality — start with audit-superset.e2e.test.ts (2), durability.drill.test.ts, ops.conformance.test.ts. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in corpus/harness/ (189 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in corpus/hosts/express-host/ (2 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/ai-sdk-agent/ (4 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/demo-bank/ (122 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/mastra-agent/ (6 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in fixtures/automations-e2e/ (4 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in fixtures/existing-agents-e2e/ (10 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in fixtures/install-seam/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in fixtures/integration/ (0 tests)): measured (0 flaky).
Test suite executes none of its 7 test cases: fixtures/install-seam/
What to do
Resolve the 1 Test suite executes none of its 7 test cases finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d11_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.
44 outdated direct production npm dependency(ies) of 60 graded, 0 pinning defect(s), across 21 REDACTED (6 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Deprecated: eslintREDACTED:31
Deprecated: glob · ×4REDACTED:6073
Outdated (npm): @ai-sdk/anthropic · ×44
What to do
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
3 secret(s) detected. 3 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
15 of 857 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 857 package(s) this repository's committed lockfile installs for a consumer — its 60 production, optional and peer dependency(ies), across 6 product REDACTED manifest(s), and everything those install in turn. Its 172 `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. 9 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. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
Resolve the 15 Banned license finding(s) in License Compliance — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
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 (107×46=4922); packages/vendo/src/ui/chrome/vendo-overlay.tsx (44×98=4312); packages/vendo/src/ui/chrome/thread/index.tsx (32×90=2880) Repeated repair below the complexity floor: packages/vendo/src/capability-misses.ts (6 of 10 changes were fixes); packages/vendo/src/sdk-events.ts (4 of 7 changes were fixes); packages/vendo/src/cli/extract/claude-harness.ts (3 of 5 changes were fixes)
Resolve the 105 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.ts (3), vendo.ts (2), REDACTED. — One of this dimension's main actionable groups (105 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with capability-misses.ts, sdk-events.ts, claude-harness.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.
0 deducted task-comment markers across 182335 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.
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. 12 document(s) read across 6 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency9.6 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
1 API inconsistencies among 257 exposed members measured against a convention their peers follow.
`TenantConnectors.register` takes an options object where `TenantConnectors.test` takes the same values as positional parameterspackages/vendo/src/tenant-connectors.ts:71
What to do
Resolve the 1 `TenantConnectors.register` takes an options object where… finding(s) in Internal API Consistency — start with tenant-connectors.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
12 domain type(s) cross context boundaries across 15 contexts; they are measured and withheld (not published, not scored). Contexts: ai-sdk-agent, automations-e2e, demo-bank, existing-agents-e2e, express-host, genbench, harness, host-app, install-seam, integration, mastra-agent, mcp-e2e and 3 more.
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.
1 of 6 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionREDACTED:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — 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.
13 % of calls cross a namespace and 7 % go through an interface, but 74 % of collaborators are co-located — so following a call takes several hops. 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: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
70 finding(s): 0 critical, 6 high, 63 medium, 1 low. 2 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 73 file(s) — `examples/demo-bank/src/components/vendo/workbench/VendoWorkbench.tsx` (line 21), `examples/demo-bank/src/components/vendo/workbench/demo-feed.ts` (line 149), `examples/demo-bank/src/vendo/registry.tsx` (line 93), `REDACTED` (line 219, line 226), `packages/vendo/e2e/stress.spec.ts` (line 22), … (+68 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 1 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
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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 2 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 (2 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 17 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17). — One of this dimension's main actionable groups (17 issue-level).
Resolve the 6 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 653 of the 828 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with box.ts, doctor-codes.ts, agent-tools.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with memory-store-ops.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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 alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
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.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <div 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. — packages/vendo/src/ui/chrome/connect-dock.tsx:405
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. — packages/vendo/src/ui/chrome/vendo-toasts.tsx:260
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — packages/vendo/src/ui/kit/data/data-table.tsx:564
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.
`.mute` sets color: #7a746c on background-color: #211f1c — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:444
`.g th` sets color: #7a746c on background-color: #141312 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:977
`.avatar` sets color: #087f6f on background-color: #dcece8 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — corpus/hosts/express-host/src/client/brand.css:71
`.error` sets color: #dc2626 on background-color: #fff0ee — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — corpus/hosts/express-host/src/client/brand.css:72
`.ghostBtn` moves (`transition: color 120ms ease, transform 160ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:157
`.tsBtn` moves (`transition: transform 160ms var(--ease-out), background 120ms ease, color 120ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:188
`.pulseRun::after` moves (`animation: wb-ring 1.7s ease-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:279
`.prog > i` moves (`transition: width 260ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:310
`.chev` moves (`transition: transform 150ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:531
`.gaugeFill` moves (`transition: width 260ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:807
`.fchip` moves (`transition: color 120ms ease, border-color 120ms ease, background 120ms ease,
transform 160ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/components/vendo/workbench/workbench.module.css:1097
`.maple-modal-panel` moves (`transition: transform 260ms cubic-bezier(0.16, 1, 0.3, 1), opacity 180ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/app/globals.css:76
`.maple-modal[data-closing] .maple-modal-panel` moves (`transition: transform 160ms ease-out, opacity 140ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/app/globals.css:99
`.maple-approval-inflow .fl-approval` moves (`animation: maple-approval-in 0.28s cubic-bezier(0.16, 1, 0.3, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/demo-bank/src/app/globals.css:114
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 · 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.
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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`IFileSystem` declares 20 required operations: `readFile`, `readFileBuffer`, `writeFile`, `appendFile`, `exists`, `stat`, `mkdir`, `readdir`, `rm`, `cp`, `mv`, `resolvePath`, `getAllPaths`, `chmod`, `symlink`, `link`, `readlink`, `lstat`, `realpath`, `utimes`. 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/vendo/src/core/filesystem.ts:78
`AppsRuntime` declares 29 required operations: `create`, `authoredScreen`, `refusedScreen`, `commitSource`, `floor`, `takeReplaySource`, `toolShapeBrief`, `get`, `list`, `delete`, `fork`, `seen`, `place`, `unplace`, `placements`, `edit`, `remember`, `history`, `open`, `bundleDocument`, `call`, `exportApp`, `importApp`, `share`, `publish`, `agentTools`, `agentToolRisk`, `validate`, `schedule`. 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/vendo/src/apps/runtime/types.ts:398
`AppsRuntimeContext` declares 26 required operations: `updateAppDocument`, `holds`, `owned`, `requireOwned`, `grantedRecords`, `reportGuard`, `reportLifecycle`, `rungFor`, `failedEdit`, `persistEdit`, `reportDocumentEdit`, `discardVersion`, `pruneHistory`, `takeEditVersion`, `takeReplaySource`, `assembleEdit`, `generationToolContext`, `requireSlot`, `claimSlot`, `markUnbuilt`, `beginBuild`, `buildingNow`, `buildingFor`, `settleBuild`, `entryFor`, `runtime`. 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/vendo/src/apps/runtime/runtime-context.ts:53
`VendoComposition` declares 22 required operations: `resolvePrincipal`, `sweepNow`, `reportConfig`, `readSurfaceFile`, `memoizeOnce`, `startBackgroundSweep`, `startDevAutomationsTicker`, `enrolForCloudTicks`, `ready`, `themeProvider`, `briefing`, `hostSemanticsProvider`, `missSurface`, `doorBase`, `agentMenu`, `subjectHasToolkit`, `connectedToolkitsFor`, `serviceToolOwner`, `serviceToolRisk`, `channelInboundSecret`, `runSweep`, `bootReconcile`. 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/vendo/src/compose-context.ts:112
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
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. — packages/vendo/src/actions/presets/away-token.ts:86
What to do
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 · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
packages.vendo.src.core.app-document.AppDocument's [bundle, ui] are judged in packages.vendo.src.apps.persistence.open, packages.vendo.src.core.apps.app-validation — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
packages.vendo.src.core.grants.PermissionGrant's [expiresAt, revokedAt] are judged in packages.vendo.src.apps.testing.guard-fixture, packages.vendo.src.sync-impact — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
packages.vendo.src.core.run-context.Membership's [admin, org] are judged in packages.vendo.src.core.conformance.memory-app-access, packages.vendo.tests.apps.app-access-fixture — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
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.
A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. — packages/vendo/src/store/workspace-ops-rows.ts:74
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
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.
`detect` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/vendo/src/actions/sync/extractors.ts:70
`checkUserFiles` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/vendo/src/cli/doctor-config-checks.ts:116
`#revokeGrant` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/vendo/src/mcp/oauth/server.ts:827
`list` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/vendo/src/screen-agent.ts:867
`notWiredYet` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/vendo/src/store/workspace-ops-rows.ts:74
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×15) — fixtures/context-e2e/e2e/cache-ledger.spec.ts:37, fixtures/context-e2e/e2e/compaction-recall.spec.ts:51, fixtures/context-e2e/e2e/giant-first.spec.ts:50, …
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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 repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
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 · Observability4.3 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `corpus/hosts/express-host`, `fixtures/automations-e2e`, `fixtures/host-app`, `fixtures/install-seam`, `fixtures/install-seam/app` and 4 more.
`packages/vendo/src/compose-actions.ts` reports through `console.*` at line 73 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/vendo/src/compose-actions.ts:73
`packages/vendo/src/compose-discovery.ts` reports through `console.*` at line 88 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/vendo/src/compose-discovery.ts:88
`packages/vendo/src/compose-guard.ts` reports through `console.*` at line 149 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/vendo/src/compose-guard.ts:149
`packages/vendo/src/compose-mcp.ts` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/vendo/src/compose-mcp.ts:105
`packages/vendo/src/compose-store.ts` reports through `console.*` at line 177 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/vendo/src/compose-store.ts:177
`packages/vendo/src/config-keys.ts` reports through `console.*` at line 182 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/vendo/src/config-keys.ts:182
`packages/vendo/src/config-keys.ts` reports through `console.*` at line 197 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/vendo/src/config-keys.ts:197
`packages/vendo/src/screen-agent.ts` reports through `console.*` at line 629 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/vendo/src/screen-agent.ts:629
`packages/vendo/src/screen-agent.ts` reports through `console.*` at line 637 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/vendo/src/screen-agent.ts:637
`packages/vendo/src/surface-menu.ts` reports through `console.*` at line 22 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/vendo/src/surface-menu.ts:22
`packages/vendo/src/wire/apps.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/vendo/src/wire/apps.ts:117
`packages/vendo/src/store/db.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/vendo/src/store/db.ts:171
`packages/vendo/src/store/db.ts` reports through `console.*` at line 315 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/vendo/src/store/db.ts:315
`packages/vendo/src/store/hosted-store.ts` reports through `console.*` at line 490 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/vendo/src/store/hosted-store.ts:490
`packages/vendo/src/store/hosted-store.ts` reports through `console.*` at line 520 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/vendo/src/store/hosted-store.ts:520
`packages/vendo/src/store/secrets.ts` reports through `console.*` at line 27 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/vendo/src/store/secrets.ts:27
`packages/vendo/src/sandbox/edge/lib-source.ts` reports through `console.*` at line 35 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/vendo/src/sandbox/edge/lib-source.ts:35
`packages/vendo/src/harnesses/vendo/vendo.ts` reports through `console.*` at line 521 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/vendo/src/harnesses/vendo/vendo.ts:521
`packages/vendo/src/harnesses/claude-code/local.ts` reports through `console.*` at line 128 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/vendo/src/harnesses/claude-code/local.ts:128
`packages/vendo/src/core/fetch.ts` reports through `console.*` at line 22 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/vendo/src/core/fetch.ts:22
`packages/vendo/src/automations/ingestion-surface.ts` reports through `console.*` at line 151 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/vendo/src/automations/ingestion-surface.ts:151
`packages/vendo/src/auth-presets/auth-js.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/vendo/src/auth-presets/auth-js.ts:101
`packages/vendo/src/auth-presets/clerk.ts` reports through `console.*` at line 82 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/vendo/src/auth-presets/clerk.ts:82
`packages/vendo/src/apps/persistence/app-source.ts` reports through `console.*` at line 261 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/vendo/src/apps/persistence/app-source.ts:261
`packages/vendo/src/apps/generation/render-seam.ts` reports through `console.*` at line 237 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/vendo/src/apps/generation/render-seam.ts:237
`packages/vendo/src/apps/generation/render-seam.ts` reports through `console.*` at line 255 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/vendo/src/apps/generation/render-seam.ts:255
`packages/vendo/src/apps/generation/render-seam.ts` reports through `console.*` at line 325 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/vendo/src/apps/generation/render-seam.ts:325
`packages/vendo/src/apps/generation/validate-gate.ts` reports through `console.*` at line 72 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/vendo/src/apps/generation/validate-gate.ts:72
`packages/vendo/src/apps/generation/validate-gate.ts` reports through `console.*` at line 80 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/vendo/src/apps/generation/validate-gate.ts:80
`packages/vendo/src/apps/generation/validate-gate.ts` reports through `console.*` at line 132 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/vendo/src/apps/generation/validate-gate.ts:132
`packages/vendo/src/apps/doors/write-surface.ts` reports through `console.*` at line 402 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/vendo/src/apps/doors/write-surface.ts:402
`packages/vendo/src/apps/checking/component-screen.ts` reports through `console.*` at line 598 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/vendo/src/apps/checking/component-screen.ts:598
`packages/vendo/src/apps/checking/floor.ts` reports through `console.*` at line 183 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/vendo/src/apps/checking/floor.ts:183
`packages/vendo/src/actions/runtime/registry.ts` reports through `console.*` at line 638 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/vendo/src/actions/runtime/registry.ts:638
`packages/vendo/src/actions/runtime/registry.ts` reports through `console.*` at line 645 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/vendo/src/actions/runtime/registry.ts:645
`packages/vendo/src/actions/runtime/registry.ts` reports through `console.*` at line 822 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/vendo/src/actions/runtime/registry.ts:822
`packages/vendo/src/actions/runtime/registry.ts` reports through `console.*` at line 856 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/vendo/src/actions/runtime/registry.ts:856
`packages/vendo/src/actions/runtime/registry.ts` reports through `console.*` at line 931 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/vendo/src/actions/runtime/registry.ts:931
`packages/vendo/src/actions/runtime/registry.ts` reports through `console.*` at line 940 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/vendo/src/actions/runtime/registry.ts:940
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.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 6 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:5
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.
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.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — .github/workflows/release.yml:25
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download 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. (×7) — packages/vendo/scripts/build-onest-font.mjs:40, packages/vendo/src/actions/connectors/composio.ts:179, REDACTED:145, …
`fetcher(` 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. (×3) — packages/vendo/src/cli/cloud/auth.ts:93, packages/vendo/src/cli/cloud/auth.ts:96, packages/vendo/src/cli/cloud/auth.ts:126
`fetchImpl(` 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. (×3) — packages/vendo/src/cli/cloud/device-login.ts:158, packages/vendo/src/cloud-tools.ts:52, packages/vendo/src/core/heartbeat.ts:52
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.
`unzipSync` in `exportAndTamper` 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. — fixtures/redteam/src/harness.ts:373
`writeFileSync` in `handle` 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/vendo/box/harness.mjs:228, packages/vendo/box/turn-routes.mjs:430
`mkdirSync` in `handle` 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/vendo/box/turn-routes.mjs:420, packages/vendo/box/turn-routes.mjs:429
`readdirSync` in `handle` 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/vendo/box/turn-routes.mjs:421
`rmSync` in `handle` 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/vendo/box/turn-routes.mjs:422
`chmodSync` in `handle` 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/vendo/box/turn-routes.mjs:433
`readFileSync` in `handle` 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/vendo/box/turn-routes.mjs:461, packages/vendo/box/turn-routes.mjs:473
`statSync` in `handle` 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/vendo/box/turn-routes.mjs:472
`generateKeyPairSync` in `runVerifyDomain` 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/vendo/src/cli/mcp/verify-domain.ts:32
`readFileSync` in `anonymous function` 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/vendo/src/core/deployment-identity.ts:52
`chmodSync` in `materialize` 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/vendo/src/harnesses/claude-code/local.ts:288
`unzipSync` in `execute` 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/vendo/src/harnesses/vendo/shell/parsers/docx2txt.ts:104
`fs.writeFileSync` in `acquirePgliteDirLock` 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/vendo/src/store/db.ts:155
`fs.rmSync` in `acquirePgliteDirLock` 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/vendo/src/store/db.ts:165
`fs.utimesSync` in `callback to setInterval` 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/vendo/src/store/db.ts:182
`fs.rmSync` in `release` 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/vendo/src/store/db.ts:195
`fs.rmSync` in `createPgliteHealingStaleLock` 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/vendo/src/store/db.ts:318
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.9 / 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 — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
48 duplicated blocks under packages/vendo/src/ have copies in at least two of the sibling directories actions, apps, auth-presets, automations, capability, cli (+9 more sibling(s) not listed) — 34 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 48 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 48 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 48 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/vendo/src/core/conformance/memory-store.ts:88
8 duplicated blocks under the repository root have copies in at least two of the sibling directories corpus, docs-site, genbench, packages — 5 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — corpus/harness/src/layers/structural.ts:97
genbench/src/claude-code.ts:72 · genbench/src/codex.ts:59 — the two spans are one implementation copied and then locally edited — 617 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. — genbench/src/claude-code.ts:72
packages/vendo/src/ui/hooks/approvals-feed.ts:90 · packages/vendo/src/ui/hooks/apps-feed.ts:66 — the two spans are one implementation copied and then locally edited — 490 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/vendo/src/ui/hooks/approvals-feed.ts:90
packages/vendo/src/ui/kit/charts/bar.tsx:26 · packages/vendo/src/ui/kit/charts/line.tsx:34 — the two spans are one implementation copied and then locally edited — 586 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/vendo/src/ui/kit/charts/bar.tsx:26
genbench/src/honesty.ts:230 · REDACTED:255 — the two spans are one implementation copied and then locally edited — 337 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. — genbench/src/honesty.ts:230
packages/vendo/src/core/conformance/memory-store.ts:88 · packages/vendo/src/store/validate.ts:70 — the two spans are one implementation copied and then locally edited — 448 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/vendo/src/core/conformance/memory-store.ts:88
corpus/harness/src/layers/structural.ts:97 · REDACTED:43 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — corpus/harness/src/layers/structural.ts:97
packages/vendo/src/cli/extract/claude-cli-harness.ts:42 · packages/vendo/src/cli/extract/codex-cli-harness.ts:26 — the two spans are one implementation copied and then locally edited — 327 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/vendo/src/cli/extract/claude-cli-harness.ts:42
packages/vendo/src/cli/cloud/host-components.ts:165 · packages/vendo/src/cli/cloud/seed-baselines.ts:118 — the two spans are one implementation copied and then locally edited — 379 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/vendo/src/cli/cloud/host-components.ts:165
packages/vendo/src/ui/chrome/pin-chrome.tsx:90 · packages/vendo/src/ui/chrome/remixable.tsx:299 — the two spans are one implementation copied and then locally edited — 212 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/vendo/src/ui/chrome/pin-chrome.tsx:90
packages/vendo/src/ui/kit/layout.tsx:257 · packages/vendo/src/ui/kit/layout.tsx:312 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/ui/kit/layout.tsx:257
corpus/harness/src/install-command.ts:49 · corpus/harness/src/install-command.ts:88 — the two spans are one implementation copied and then locally edited — 314 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — corpus/harness/src/install-command.ts:49
packages/vendo/src/cli/cloud/host-components.ts:92 · packages/vendo/src/cli/cloud/seed-baselines.ts:53 — the two spans are one implementation copied and then locally edited — 269 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/vendo/src/cli/cloud/host-components.ts:92
packages/vendo/src/ui/hooks/approvals-feed.ts:18 · packages/vendo/src/ui/hooks/apps-feed.ts:19 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/vendo/src/ui/hooks/approvals-feed.ts:18
packages/vendo/src/actions/formats.ts:305 · packages/vendo/src/actions/formats.ts:429 — the two spans are one implementation copied and then locally edited — 215 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/vendo/src/actions/formats.ts:305
REDACTED:873 · REDACTED:900 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:873
packages/vendo/src/harnesses/claude-code/claude-turn.ts:275 · packages/vendo/src/harnesses/claude-code/index.ts:319 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/vendo/src/harnesses/claude-code/claude-turn.ts:275
packages/vendo/src/store/helpers/audit.ts:31 · packages/vendo/src/store/ops.ts:121 — the two spans are one implementation copied and then locally edited — 253 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/vendo/src/store/helpers/audit.ts:31
packages/vendo/src/store/helpers/runs.ts:28 · packages/vendo/src/store/records.ts:257 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/store/helpers/runs.ts:28
packages/vendo/src/actions/sync/common.ts:49 · packages/vendo/src/cli/theme/walk.ts:7 — the two spans are one implementation copied and then locally edited — 169 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/vendo/src/actions/sync/common.ts:49
packages/vendo/src/cli/cloud/pending-claim.ts:38 · packages/vendo/src/cli/cloud/session.ts:13 — the two spans are one implementation copied and then locally edited — 213 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/vendo/src/cli/cloud/pending-claim.ts:38
REDACTED:320 · REDACTED:467 — the two spans are one implementation copied and then locally edited — 228 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:320
packages/vendo/src/core/knowledge-wire.ts:130 · packages/vendo/src/core/store-wire.ts:775 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/core/knowledge-wire.ts:130
packages/vendo/src/automations/webhook-signature.ts:65 · packages/vendo/src/mcp/oauth/server.ts:1007 — the two spans are one implementation copied and then locally edited — 84 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/vendo/src/automations/webhook-signature.ts:65
packages/vendo/src/core/conformance/memory-app-access.ts:77 · packages/vendo/src/store/helpers/app-access.ts:134 — the two spans are one implementation copied and then locally edited — 152 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/vendo/src/core/conformance/memory-app-access.ts:77
packages/vendo/src/core/heartbeat.ts:80 · packages/vendo/src/turn-liveness.ts:237 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/vendo/src/core/heartbeat.ts:80
packages/vendo/src/ui/kit/data/card-list.tsx:47 · packages/vendo/src/ui/kit/data/timeline.tsx:51 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/ui/kit/data/card-list.tsx:47
packages/vendo/src/actions/connectors/composio.ts:569 · packages/vendo/src/cloud-tools.ts:149 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/vendo/src/actions/connectors/composio.ts:569
packages/vendo/src/cli/index.ts:108 · packages/vendo/src/cli/knowledge/index.ts:74 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/vendo/src/cli/index.ts:108
packages/vendo/src/apps/testing/adapter-conformance.ts:187 · packages/vendo/src/apps/testing/adapter-conformance.ts:209 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/apps/testing/adapter-conformance.ts:187
packages/vendo/src/cli/cloud/command.ts:41 · packages/vendo/src/cli/cloud/command.ts:63 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/cli/cloud/command.ts:41
packages/vendo/src/auth-presets/auth0.ts:115 · packages/vendo/src/auth-presets/clerk.ts:91 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/vendo/src/auth-presets/auth0.ts:115
corpus/harness/src/cli.ts:196 · corpus/harness/src/cli.ts:236 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — corpus/harness/src/cli.ts:196
packages/vendo/src/cli/extract/claude-harness.ts:32 · packages/vendo/src/harnesses/inference/model.ts:224 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/vendo/src/cli/extract/claude-harness.ts:32
packages/vendo/src/connector-discovery.ts:280 · packages/vendo/src/vendo-verbs.ts:157 — the two spans are one implementation copied and then locally edited — 55 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/vendo/src/connector-discovery.ts:280
corpus/harness/src/inject.ts:53 · corpus/harness/src/local-pack.ts:156 — the two spans are one implementation copied and then locally edited — 130 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. — corpus/harness/src/inject.ts:53
packages/vendo/src/guard/guard.ts:1425 · packages/vendo/src/knowledge/agent-tools.ts:129 — the two spans are one implementation copied and then locally edited — 127 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/vendo/src/guard/guard.ts:1425
packages/vendo/src/harnesses/turn-tools.ts:228 · packages/vendo/src/screen-agent.ts:1757 — the two spans are one implementation copied and then locally edited — 106 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/vendo/src/harnesses/turn-tools.ts:228
packages/vendo/src/store/routing.ts:394 · packages/vendo/src/store/routing.ts:536 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/vendo/src/store/routing.ts:394
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 · 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.
handler has cyclomatic complexity 208 and cognitive complexity 313; 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/vendo/tests/ui/wire-server.ts:438
(anonymous) has cyclomatic complexity 52 and cognitive complexity 59; 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/vendo/src/core/conformance/memory-store.ts:158
runInit has cyclomatic complexity 51 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1826
VendoThread has cyclomatic complexity 51 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/ui/chrome/thread/index.tsx:57
handle has cyclomatic complexity 49 and cognitive complexity 94; 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/vendo/box/turn-routes.mjs:374
(anonymous) has cyclomatic complexity 47 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/vendo/tests/sandbox.test.ts:71
VendoOverlay has cyclomatic complexity 47 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/ui/chrome/vendo-overlay.tsx:636
ThreadPart has cyclomatic complexity 45 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 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/vendo/src/ui/chrome/thread/parts.tsx:280
handler has cyclomatic complexity 44 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. — packages/vendo/src/mcp/door.ts:354
run has cyclomatic complexity 44 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/vendo/src/harnesses/claude-code/index.ts:364
run has cyclomatic complexity 43 and cognitive complexity 51; 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/vendo/src/harnesses/vendo/vendo.ts:418
runDeviceLogin has cyclomatic complexity 41 and cognitive complexity 60; 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/vendo/src/cli/cloud/device-login.ts:199
sync has cyclomatic complexity 41 and cognitive complexity 42; 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/vendo/src/cli/sync.ts:187
initCommand has cyclomatic complexity 40 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/cli/index.ts:157
schemaForCheckerType has cyclomatic complexity 38 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/actions/sync/route-schema.ts:530
cloudStep has cyclomatic complexity 38 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:276
vendoSync has cyclomatic complexity 37 and cognitive complexity 51; 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/vendo/src/actions/sync/index.ts:324
stream has cyclomatic complexity 34 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/harness-turn.ts:644
guardSql has cyclomatic complexity 32 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 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/vendo/src/apps/persistence/app-sql-guard.ts:280
(anonymous) has cyclomatic complexity 32 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/apps/automation/plan.ts:312
applyZodModifier has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/actions/sync/static-ts.ts:450
#checkWithMetadata has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/guard/guard.ts:1180
ThreadMessage has cyclomatic complexity 32 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/ui/chrome/thread/message.tsx:40
(anonymous) has cyclomatic complexity 31 and cognitive complexity 51; 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/vendo/src/actions/runtime/registry.ts:748
VendoSlot has cyclomatic complexity 31 and cognitive complexity 34; 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/vendo/src/ui/chrome/vendo-slot.tsx:248
planMcpScaffold has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:698
(anonymous) has cyclomatic complexity 28 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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) — packages/vendo/src/apps/checking/facts.ts:321, packages/vendo/src/apps/checking/screen-typecheck.ts:274
ConnectCard has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/ui/chrome/connect-card.tsx:74
checkComponentScreen has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/apps/checking/component-screen.ts:623
repairJson has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/cli/judge/parse.ts:58
scoreAiJudgments has cyclomatic complexity 27 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 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. — corpus/harness/src/ai/score.ts:206
(anonymous) has cyclomatic complexity 27 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/knowledge/cloud.test-util.ts:79
assembleScreen has cyclomatic complexity 27 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/screen-agent.ts:895
isDefaultSansSpread has cyclomatic complexity 27 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:369
(anonymous) has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/apps/checking/screen-typecheck.ts:211
localConstantJson has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/src/actions/sync/catalog-scan.ts:226
runTurn has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/vendo/tests/frozen/turn-frozen.ts:498
agent has cyclomatic complexity 26 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/turn/agent.ts:336
sha256Hex has cyclomatic complexity 26 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/vendo/src/core/sha256.ts:50
Do you agree with this assessment?
R3 · Large Files5.0 / 10Adequate✓ 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/vendo/src/guard/guard.ts has 2517 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/vendo/src/guard/guard.ts:1
packages/vendo/src/ui/chrome/chrome-css.ts has 2204 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/vendo/src/ui/chrome/chrome-css.ts:1
packages/vendo/src/core/conformance/store-ops.ts has 2074 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/vendo/src/core/conformance/store-ops.ts:1
REDACTED has 2014 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/vendo/src/mcp/door.ts has 1866 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/vendo/src/mcp/door.ts:1
packages/vendo/src/screen-agent.ts has 1722 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/vendo/src/screen-agent.ts:1
genbench/src/run.ts has 1349 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — genbench/src/run.ts:1
packages/vendo/src/core/apps/kit/specs.ts has 1254 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/vendo/src/core/apps/kit/specs.ts:1
packages/vendo/src/ui/chrome/vendo-overlay.tsx has 1171 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/vendo/src/ui/chrome/vendo-overlay.tsx:1
packages/vendo/src/mcp/oauth/server.ts has 1141 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/vendo/src/mcp/oauth/server.ts:1
packages/vendo/src/harnesses/runtime.ts has 1127 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/vendo/src/harnesses/runtime.ts:1
packages/vendo/src/apps/checking/component-screen.ts has 1081 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/vendo/src/apps/checking/component-screen.ts:1
packages/vendo/src/ui/chrome/thread/parts.tsx has 1077 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/vendo/src/ui/chrome/thread/parts.tsx:1
packages/vendo/src/harness-turn.ts has 1061 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/vendo/src/harness-turn.ts:1
packages/vendo/src/cli/judge/pass.ts has 1050 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/vendo/src/cli/judge/pass.ts:1
packages/vendo/src/cli/pretty.ts has 1044 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/vendo/src/cli/pretty.ts:1
genbench/src/report.ts has 1005 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — genbench/src/report.ts:1
packages/vendo/src/store/hosted-store.ts has 949 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/vendo/src/store/hosted-store.ts:1
packages/vendo/src/ui/tree/renderer.tsx has 948 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/vendo/src/ui/tree/renderer.tsx:1
packages/vendo/src/store/ops.ts has 936 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/vendo/src/store/ops.ts:1
packages/vendo/src/actions/runtime/registry.ts has 922 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/vendo/src/actions/runtime/registry.ts:1
packages/vendo/src/cli/sync-flow.ts has 912 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/vendo/src/cli/sync-flow.ts:1
packages/vendo/src/core/conformance/memory-store-ops.ts has 900 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/vendo/src/core/conformance/memory-store-ops.ts:1
genbench/src/probe.ts has 875 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — genbench/src/probe.ts:1
packages/vendo/src/actions/sync/catalog-scan.ts has 826 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/vendo/src/actions/sync/catalog-scan.ts:1
packages/vendo/src/turn/turn.ts has 814 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/vendo/src/turn/turn.ts:1
packages/vendo/src/actions/sync/split/carve.ts has 797 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/vendo/src/actions/sync/split/carve.ts:1
packages/vendo/src/actions/sync/route-scan.ts has 794 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/vendo/src/actions/sync/route-scan.ts:1
packages/vendo/src/core/store-wire.ts has 789 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/vendo/src/core/store-wire.ts:1
packages/vendo/src/apps/runtime/types.ts has 784 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/vendo/src/apps/runtime/types.ts:1
packages/vendo/src/harnesses/vendo/vendo.ts has 783 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/vendo/src/harnesses/vendo/vendo.ts:1
packages/vendo/src/core/apps/genui/component/vm-program.ts has 766 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/vendo/src/core/apps/genui/component/vm-program.ts:1
packages/vendo/src/actions/sync/route-schema.ts has 756 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/vendo/src/actions/sync/route-schema.ts:1
packages/vendo/src/harnesses/claude-code/box.ts has 749 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/vendo/src/harnesses/claude-code/box.ts:1
packages/vendo/src/store/routing.ts has 736 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/vendo/src/store/routing.ts:1
packages/vendo/src/apps/checking/screen-typings.ts has 729 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/vendo/src/apps/checking/screen-typings.ts:1
packages/vendo/src/harnesses/claude-code/index.ts has 725 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/vendo/src/harnesses/claude-code/index.ts:1
packages/vendo/src/ui/kit/data/data-table.tsx has 707 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/vendo/src/ui/kit/data/data-table.tsx:1
packages/vendo/src/harnesses/vendo/loop.ts has 706 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/vendo/src/harnesses/vendo/loop.ts:1
packages/vendo/src/actions/sync/seeds.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/vendo/src/actions/sync/seeds.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.8 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×13) — genbench/src/mount.tsx:1, packages/vendo/scripts/build-icons.mjs:1, corpus/scripts/corpus-trend.mjs:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 287 application, 42 tooling and 1186 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 (287 application, 42 tooling, 1186 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 (×4) — docs-site/snippets/agent-prompt.jsx, packages/vendo/src/theme-json-import.docs-check.ts, packages/vendo/src/server-api-imports.docs-check.ts, …
Nothing imports this binding — it is safe to review for removal. (×10) — corpus/harness/src/expectations.ts:16, corpus/harness/src/expectations.ts:17, corpus/harness/src/expectations.ts:121, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×2) — packages/vendo/src/config-keys.ts:87, packages/vendo/src/harnesses/vendo/vendo.ts:134
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.
Every import is type-only — move it to devDependencies. (×2) — packages/vendo/src/core/harness.ts:16, packages/vendo/src/harnesses/vendo/shell/parsers/pdftotext.ts:18
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. 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. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
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.
`server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/vendo/box/harness.mjs:254
What to do
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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 · 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 document1.5 / 10Critical✓ 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.
`requireJson` is exported, takes a document from its caller (line 92) and hands it to `isJson`, which calls itself at line 76 (`isJson`) with a piece of `value` (and at line 85) — and nowhere in `isJson` 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 `isJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/store/validate.ts:76
`jsonEqual` is exported and takes `left: unknown` from its caller, and it calls itself at line 20 (`jsonEqual`) with a piece of `left` (and at line 32) — and nowhere in `jsonEqual` 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 `jsonEqual` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/harnesses/json-equal.ts:20
`canonicalJson` is exported, takes a document from its caller (line 78) and hands it to `serialize`, which calls itself at line 48 (`serialize`) with a piece of `value` (and at line 64) — and nowhere in `serialize` 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 `serialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/core/jcs.ts:48
`findInvalidReshape` is exported and takes `value: unknown` from its caller, and it calls itself at line 187 (`findInvalidReshape`) with a piece of `value` (and at line 198) — and nowhere in `findInvalidReshape` 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 `findInvalidReshape` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/core/reshape.ts:187
`findInvalidActionReference` is exported and takes `value: unknown` from its caller, and it calls itself at line 17 (`findInvalidActionReference`) with a piece of `value` (and at line 30) — and nowhere in `findInvalidActionReference` 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 `findInvalidActionReference` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/core/apps/fn-references.ts:17
`flattenTree` is exported, takes a document from its caller (line 54) and hands it to `walk`, which calls itself at line 78 (`walk`) with a piece of `node` — and nowhere in `walk` 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 `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/core/apps/genui/component/flatten.ts:78
`amountUnitIssue` is exported, takes a document from its caller (line 76) and hands it to `walk`, which calls itself at line 86 (`walk`) with a piece of `value` — and nowhere in `walk` 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 `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/apps/persistence/call.ts:86
`extractOpenApiDocument` is exported, takes a document from its caller (line 147) and hands it to `resolveRefs`, which calls itself at line 24 (`resolveRefs`) with a piece of `node` (and at line 35, line 38) — and nowhere in `resolveRefs` 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 `resolveRefs` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/actions/openapi-document.ts:24
`stableJson` is exported, takes a document from its caller (line 87) and hands it to `canonical`, which calls itself at line 76 (`canonical`) with a piece of `value` (and at line 81) — and nowhere in `canonical` 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 `canonical` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vendo/src/actions/presets/shared.ts:76
`jsonSchemaFromExample` is exported and takes `value: unknown` from its caller, and it calls itself at line 144 (`jsonSchemaFromExample`) with a piece of `value` (and at line 151) — and nowhere in `jsonSchemaFromExample` 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 `jsonSchemaFromExample` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — genbench/src/world.ts:144
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 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 6/11 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.
`discoverJwksUri` 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/vendo/src/mcp/oauth/remote-as.ts:101
`loadWasm` 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/vendo/src/core/apps/genui/wasm-browser.ts:6
`googleFaces` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:143
`embedHostFonts` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:180
`composioFetch` 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/vendo/src/actions/connectors/composio.ts:172
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped7.0 / 10Strong✓ 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.
`escape(caseDir)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — genbench/src/report.ts:223
`markup` 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:44
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 element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×26) — packages/vendo/src/cloud-tools.ts:65, packages/vendo/src/turn-resume.ts:115, packages/vendo/src/ui/chrome/app-shape-cache.ts:109, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×9) — packages/vendo/src/harness-turn.ts:670, packages/vendo/src/harness-turn.ts:709, packages/vendo/src/harness-turn.ts:783, …
`.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — packages/vendo/src/ui/chrome/pin-ceremony.ts:272, packages/vendo/src/ui/chrome/vendo-slot.tsx:141
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×3) — packages/vendo/src/mcp/oauth/server.ts:990, packages/vendo/src/knowledge/ingest/index.ts:64, packages/vendo/src/harnesses/materialize.ts:195
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.
28/29 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~2.2 `!` null assertions per 1k TypeScript source lines — 378 assertion(s) across the 175182 source line(s) of the 810 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/vendo/src/cli/pretty.ts (26), packages/vendo/src/core/conformance/store-ops.ts (26), packages/vendo/src/apps/persistence/unified-diff.ts (16). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 — 2 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 — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'pg' (packages/vendo/src/store/db-postgres.ts:7) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'pg' (packages/vendo/src/store/db-postgres.ts:7) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'pg' (packages/vendo/src/store/db-postgres.ts:7) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 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).
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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 — docker build failed (exit 1) — ------ Dockerfile:13 -------------------- 11 | 12 | COPY . . 13 | >>> RUN pnpm install --frozen-lockfile 14 | RUN pnpm exec turbo run build --filter=demo-bank 15 | -------------------- ERROR: failed to solve: process "/bin/sh -c pnpm install --frozen-lockfile" did not complete successfully: exit code: 1; likely cause (the repository): a RUN step of the repository's Dockerfile exited with code 1 (`/bin/sh -c pnpm install --frozen-lockfile`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's Dockerfile exited with code 1 (`/bin/sh -c pnpm install --frozen-lockfile`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: this repository stores data through 'pg' (packages/vendo/src/store/db-postgres.ts:7) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
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.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 66 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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
DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 1923 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not 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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:2067— `@img/sharp-libvips-darwin-arm64` 1.3.2 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:2072— `@img/sharp-libvips-darwin-x64` 1.3.2 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:2083— `@img/sharp-libvips-linux-arm` 1.3.2 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:2077— `@img/sharp-libvips-linux-arm64` 1.3.2 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:2089— `@img/sharp-libvips-linux-ppc64` 1.3.2 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:2095— `@img/sharp-libvips-linux-riscv64` 1.3.2 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:2101— `@img/sharp-libvips-linux-s390x` 1.3.2 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:2107— `@img/sharp-libvips-linux-x64` 1.3.2 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:2113— `@img/sharp-libvips-linuxmusl-arm64` 1.3.2 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:2119— `@img/sharp-libvips-linuxmusl-x64` 1.3.2 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:2181— `@img/sharp-wasm32` 0.35.3 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:2190— `@img/sharp-win32-arm64` 0.35.3 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:2196— `@img/sharp-win32-ia32` 0.35.3 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:2202— `@img/sharp-win32-x64` 0.35.3 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: node-liblzma REDACTED:7205— `node-liblzma` 2.2.0 is published on registry.npmjs.org under `LGPL-3.0`, 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.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×1
Hover-only interaction on <div> packages/vendo/src/ui/chrome/vendo-toasts.tsx:260— 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <th> · ×1
Click handler on a non-interactive <th> packages/vendo/src/ui/kit/data/data-table.tsx:564— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): postgres leg configured packages/vendo/tests/store/postgres-gate.test.ts:4— Test method has an empty body — it asserts nothing and exercises no code.
D11 · Test Reliability· Test suite executes none of its 7 test cases · ×1
Test suite executes none of its 7 test cases: fixtures/install-seam/ — The vitest suite in fixtures/install-seam/ was launched successfully and reported 7 test case(s), every one of them skipped or pending — zero passed and zero failed. The suite is declared and committed but exercises none of the code it covers, so it cannot detect a regression and its presence overstates how much of this repository is tested. This is not a report that the tests FAIL: the runner never executed them.
Hotspot: REDACTED REDACTED:1826— REDACTED changed 107 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in init.runInit at line 1826. 28 of those changes were fix/bug commits, and the other 79 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vendo/src/ui/chrome/vendo-overlay.tsx packages/vendo/src/ui/chrome/vendo-overlay.tsx:636— packages/vendo/src/ui/chrome/vendo-overlay.tsx changed 44 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 98 in vendo-overlay.VendoOverlay at line 636. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/ui/chrome/vendo-overlay.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/vendo/src/ui/chrome/thread/index.tsx packages/vendo/src/ui/chrome/thread/index.tsx:57— packages/vendo/src/ui/chrome/thread/index.tsx changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in index.VendoThread at line 57. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/ui/chrome/thread/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: packages/vendo/src/ui/chrome/thread/parts.tsx packages/vendo/src/ui/chrome/thread/parts.tsx:280— packages/vendo/src/ui/chrome/thread/parts.tsx changed 58 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in parts.ThreadPart at line 280. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/ui/chrome/thread/parts.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/vendo/src/core/conformance/memory-store-ops.ts packages/vendo/src/core/conformance/memory-store-ops.ts:87— packages/vendo/src/core/conformance/memory-store-ops.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 131 in memory-store-ops.memoryStoreOps at line 87. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/core/conformance/memory-store-ops.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/vendo/src/store/hosted-store.ts packages/vendo/src/store/hosted-store.ts:415— packages/vendo/src/store/hosted-store.ts changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in hosted-store.storeWireClient at line 415. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/store/hosted-store.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vendo/src/mcp/door.ts packages/vendo/src/mcp/door.ts:354— packages/vendo/src/mcp/door.ts changed 57 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Door.handler at line 354. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/mcp/door.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/vendo/src/cli/index.ts packages/vendo/src/cli/index.ts:157— packages/vendo/src/cli/index.ts changed 54 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in index.initCommand at line 157. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/cli/index.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/vendo/src/guard/guard.ts packages/vendo/src/guard/guard.ts:1180— packages/vendo/src/guard/guard.ts changed 77 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in GuardImplementation.#checkWithMetadata at line 1180. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/guard/guard.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/vendo/src/harnesses/claude-code/index.ts packages/vendo/src/harnesses/claude-code/index.ts:343— packages/vendo/src/harnesses/claude-code/index.ts changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in index.claudeCode at line 343. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/harnesses/claude-code/index.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/vendo/src/harnesses/runtime.ts packages/vendo/src/harnesses/runtime.ts:413— packages/vendo/src/harnesses/runtime.ts changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in runtime.createHarnessRuntime.run at line 413. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/harnesses/runtime.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/vendo/src/screen-agent.ts packages/vendo/src/screen-agent.ts:895— packages/vendo/src/screen-agent.ts changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in screen-agent.assembleScreen at line 895. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/screen-agent.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/vendo/src/harness-turn.ts packages/vendo/src/harness-turn.ts:644— packages/vendo/src/harness-turn.ts changed 47 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in harness-turn.createHarnessTurns.stream at line 644. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/harness-turn.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/vendo/src/actions/runtime/registry.ts packages/vendo/src/actions/runtime/registry.ts:747— packages/vendo/src/actions/runtime/registry.ts changed 56 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in registry.createActions.buildRegistry at line 747. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/actions/runtime/registry.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/vendo/src/ui/tree/renderer.tsx packages/vendo/src/ui/tree/renderer.tsx:759— packages/vendo/src/ui/tree/renderer.tsx changed 60 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in renderer.StatefulTreeView at line 759. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/ui/tree/renderer.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/vendo/src/cli/sync.ts packages/vendo/src/cli/sync.ts:187— packages/vendo/src/cli/sync.ts changed 37 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in sync.sync at line 187. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/cli/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/vendo/src/store/ops.ts packages/vendo/src/store/ops.ts:278— packages/vendo/src/store/ops.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 61 in ops.createStoreOps at line 278. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/store/ops.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/vendo/src/core/conformance/store-ops.ts packages/vendo/src/core/conformance/store-ops.ts:198— packages/vendo/src/core/conformance/store-ops.ts changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in store-ops.storeOpsConformance at line 198. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/core/conformance/store-ops.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/vendo/box/turn-routes.mjs packages/vendo/box/turn-routes.mjs:374— packages/vendo/box/turn-routes.mjs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in turn-routes.createSessionRoutes.handle at line 374. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/box/turn-routes.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/vendo/src/apps/checking/facts.ts packages/vendo/src/apps/checking/facts.ts:231— packages/vendo/src/apps/checking/facts.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in facts.kitNestingIssues at line 231. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/apps/checking/facts.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/vendo/src/harnesses/vendo/vendo.ts packages/vendo/src/harnesses/vendo/vendo.ts:413— packages/vendo/src/harnesses/vendo/vendo.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in vendo.vendo at line 413. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/harnesses/vendo/vendo.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/vendo/src/ui/chrome/vendo-slot.tsx packages/vendo/src/ui/chrome/vendo-slot.tsx:248— packages/vendo/src/ui/chrome/vendo-slot.tsx changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in vendo-slot.VendoSlot at line 248. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/ui/chrome/vendo-slot.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/vendo/src/actions/sync/index.ts packages/vendo/src/actions/sync/index.ts:324— packages/vendo/src/actions/sync/index.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in index.vendoSync at line 324. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/actions/sync/index.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/vendo/src/cli/cloud/device-login.ts packages/vendo/src/cli/cloud/device-login.ts:199— packages/vendo/src/cli/cloud/device-login.ts changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in device-login.runDeviceLogin at line 199. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/cli/cloud/device-login.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/vendo/src/store/routing.ts packages/vendo/src/store/routing.ts:328— packages/vendo/src/store/routing.ts changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in routing.configFor at line 328. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/store/routing.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.
FunctionTooLong: store-ops.storeOpsConformance packages/vendo/src/core/conformance/store-ops.ts:198— FunctionTooLong — storeOpsConformance runs 1143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1043 over it, 11.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: memory-store-ops.memoryStoreOps packages/vendo/src/core/conformance/memory-store-ops.ts:87— FunctionTooLong — memoryStoreOps runs 510 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 410 over it, 5.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: report.escape genbench/src/report.ts:12— FunctionTooLong — escape runs 437 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 337 over it, 4.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.
FunctionTooLong: hosted-store.storeWireClient packages/vendo/src/store/hosted-store.ts:415— FunctionTooLong — storeWireClient runs 343 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 243 over it, 3.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: data-table.DataTable packages/vendo/src/ui/kit/data/data-table.tsx:197— FunctionTooLong — DataTable runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× 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: composio.composioConnector packages/vendo/src/actions/connectors/composio.ts:163— FunctionTooLong — composioConnector runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× 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: harness-turn.createHarnessTurns packages/vendo/src/harness-turn.ts:317— FunctionTooLong — createHarnessTurns runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× 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.VendoThread packages/vendo/src/ui/chrome/thread/index.tsx:57— FunctionTooLong — VendoThread runs 303 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 203 over it, 3.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: workspace-rows.workspaceRows packages/vendo/src/store/workspace-rows.ts:182— FunctionTooLong — workspaceRows runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: screen-agent.assembleScreen packages/vendo/src/screen-agent.ts:895— FunctionTooLong — assembleScreen runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: runtime.createHarnessRuntime packages/vendo/src/harnesses/runtime.ts:409— FunctionTooLong — createHarnessRuntime runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.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.
FunctionTooLong: runtime.createHarnessRuntime.run packages/vendo/src/harnesses/runtime.ts:413— FunctionTooLong — createHarnessRuntime.run runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× 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: routing.configFor packages/vendo/src/store/routing.ts:328— FunctionTooLong — configFor runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× 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: registry.createActions packages/vendo/src/actions/runtime/registry.ts:604— FunctionTooLong — createActions runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.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.
FunctionTooLong: connect-dock.ConnectTray packages/vendo/src/ui/chrome/connect-dock.tsx:203— FunctionTooLong — ConnectTray runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: box.boxMachine packages/vendo/src/harnesses/claude-code/box.ts:234— FunctionTooLong — boxMachine runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: vendo.vendo packages/vendo/src/harnesses/vendo/vendo.ts:413— FunctionTooLong — vendo runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: boot.bootScreen packages/vendo/src/core/apps/genui/component/boot.ts:296— FunctionTooLong — bootScreen runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.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: knowledge.knowledgeAdapterConformance packages/vendo/src/core/conformance/knowledge.ts:57— FunctionTooLong — knowledgeAdapterConformance runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: approval-modal.ApprovalModal packages/vendo/src/ui/chrome/approval-modal.tsx:122— FunctionTooLong — ApprovalModal runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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-access.appAccessConformance packages/vendo/src/core/conformance/app-access.ts:42— FunctionTooLong — appAccessConformance runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.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: index.storeAdapterConformance packages/vendo/src/core/conformance/index.ts:156— FunctionTooLong — storeAdapterConformance runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.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: sandbox.cloudSandbox packages/vendo/src/sandbox.ts:278— FunctionTooLong — cloudSandbox runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.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: mcp.mcpConnector packages/vendo/src/actions/connectors/mcp.ts:105— FunctionTooLong — mcpConnector runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.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: records.createRecordStore packages/vendo/src/store/records.ts:68— FunctionTooLong — createRecordStore runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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.
Swallowed exception (empty catch) packages/vendo/src/cloud-tools.ts:65— 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/vendo/src/harness-turn.ts:670— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/harness-turn.ts:709— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/harness-turn.ts:783— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/turn-resume.ts:115— 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/vendo/src/wire/apps.ts:94— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/ui/chrome/app-shape-cache.ts:109— 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/vendo/src/ui/chrome/app-shape-cache.ts:125— 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/vendo/src/ui/chrome/clipboard.ts:13— 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/vendo/src/ui/chrome/discoverability.ts:75— 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/vendo/src/ui/chrome/last-thread.ts:34— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/ui/chrome/last-thread.ts:43— 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/vendo/src/ui/chrome/pin-ceremony.ts:272— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/ui/chrome/vendo-slot.tsx:141— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/turn/turn.ts:806— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/telemetry/base-props.ts:110— 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/vendo/src/telemetry/base-props.ts:116— 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/vendo/src/telemetry/client.ts:262— 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/vendo/src/telemetry/client.ts:299— 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/vendo/src/telemetry/config.ts:41— 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/vendo/src/telemetry/config.ts:52— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/store/db-postgres.ts:111— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/vendo/src/store/db.ts:183— 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/vendo/src/store/db.ts:196— 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/vendo/src/store/workspace-ops-rows.ts:54— 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.
FileTooLong: guard/guard.ts packages/vendo/src/guard/guard.ts— FileTooLong — 1337 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: GuardImplementation (458-2643). The bar is 500 significant lines; this is 837 over it, 2.67× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: conformance/store-ops.ts packages/vendo/src/core/conformance/store-ops.ts— FileTooLong — 1238 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: storeOpsConformance (198-2245). The bar is 500 significant lines; this is 738 over it, 2.48× 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 — 1151 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 651 over it, 2.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mcp/door.ts packages/vendo/src/mcp/door.ts— FileTooLong — 977 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 477 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: oauth/server.ts packages/vendo/src/mcp/oauth/server.ts— FileTooLong — 840 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: OAuthServer (165-936). The bar is 500 significant lines; this is 340 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.
FileTooLong: chrome/vendo-overlay.tsx packages/vendo/src/ui/chrome/vendo-overlay.tsx— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 216 over it, 1.43× 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: cli/pretty.ts packages/vendo/src/cli/pretty.ts— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 174 over it, 1.35× 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/screen-agent.ts packages/vendo/src/screen-agent.ts— FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 167 over it, 1.33× 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/run.ts genbench/src/run.ts— FileTooLong — 657 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 157 over it, 1.31× 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: judge/pass.ts packages/vendo/src/cli/judge/pass.ts— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 156 over it, 1.31× 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: sync/catalog-scan.ts packages/vendo/src/actions/sync/catalog-scan.ts— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.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: thread/parts.tsx packages/vendo/src/ui/chrome/thread/parts.tsx— FileTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 118 over it, 1.24× 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/report.ts genbench/src/report.ts— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 70 over it, 1.14× 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: conformance/memory-store-ops.ts packages/vendo/src/core/conformance/memory-store-ops.ts— FileTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: memoryStoreOps (87-950). The bar is 500 significant lines; this is 59 over it, 1.12× 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: harnesses/runtime.ts packages/vendo/src/harnesses/runtime.ts— FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 56 over it, 1.11× 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: cli/sync-flow.ts packages/vendo/src/cli/sync-flow.ts— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× 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: split/carve.ts packages/vendo/src/actions/sync/split/carve.ts— FileTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 50 over it, 1.10× 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: tree/renderer.tsx packages/vendo/src/ui/tree/renderer.tsx— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 49 over it, 1.10× 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: runtime/registry.ts packages/vendo/src/actions/runtime/registry.ts— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 42 over it, 1.08× 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: checking/component-screen.ts packages/vendo/src/apps/checking/component-screen.ts— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× 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/cli.ts corpus/harness/src/cli.ts— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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: store/hosted-store.ts packages/vendo/src/store/hosted-store.ts— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: storeWireClient (415-997). The bar is 500 significant lines; this is 27 over it, 1.05× 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: store/ops.ts packages/vendo/src/store/ops.ts— FileTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: createStoreOps (278-973). The bar is 500 significant lines; this is 25 over it, 1.05× 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: store/routing.ts packages/vendo/src/store/routing.ts— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.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.
No assertions: auto-derives the dock from the wire catalog when no connectors prop is passed packages/vendo/tests/ui/chrome/affordances-eng225.test.tsx:292— 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: keeps the dock when the auto catalog resolves empty and the tray says so honestly packages/vendo/tests/ui/chrome/affordances-eng225.test.tsx:302— 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: keeps the dock when the auto catalog fetch FAILS and the tray offers a retry packages/vendo/tests/ui/chrome/affordances-eng225.test.tsx:325— 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: reopens on a toggle racing its own hide — no stale-closure toggle swallows it packages/vendo/tests/ui/chrome/overlay-toggle-slot.test.tsx:80— 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: cannot be answered through a different agent's registry packages/vendo/tests/turn/interruptions-adversarial.test.ts:223— 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: refuses an input answer given for an approval instead of silently denying it packages/vendo/tests/turn/interruptions-adversarial.test.ts:451— 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: a due schedule fires through the agent's own runner, as the code owner packages/vendo/tests/turn/serve.test.ts:80— 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: each agent brings its own runner, and a firing reaches the one it named packages/vendo/tests/turn/serve.test.ts:119— 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: postgres leg is required in CI packages/vendo/tests/store/postgres-gate.test.ts:6— 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: ensureSchema is idempotent packages/vendo/tests/store/schema.test.ts:44— 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: narrows on status: each arm carries its own fields and only its own packages/vendo/tests/core/turn-result.test.ts:61— 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: hands `resume` back whatever the second parameter binds — core never names a Turn packages/vendo/tests/core/turn-result.test.ts:69— 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: passes against the honest reference: ${conformanceCase.name} packages/vendo/tests/core/conformance/audit-tally-mutants.test.ts:74— 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: the Express composition parses as .mjs packages/vendo/tests/cli/init-scaffolds.test.ts:36— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: the runtime-neutral composition parses as .mjs packages/vendo/tests/cli/init-scaffolds.test.ts:40— 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: lands a FAILED commit as a flagged version while the previous keeps serving packages/vendo/tests/apps/checking/review-failure-protocol.test.ts:61— 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: gives a flagged version exactly one bounded fix round AFTER it lands packages/vendo/tests/apps/checking/review-failure-protocol.test.ts:71— 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: raises a plain-language card on the app naming the reason and the two choices packages/vendo/tests/apps/checking/review-failure-protocol.test.ts:78— 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: lets an `owner` accept a flagged version, recording the override in the audit trail packages/vendo/tests/apps/checking/review-failure-protocol.test.ts:86— 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: refuses an owner override of a HOST-check failure packages/vendo/tests/apps/checking/review-failure-protocol.test.ts:94— 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.
Sync-over-async blocking fixtures/redteam/src/harness.ts:373— `unzipSync` in `exportAndTamper` 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/vendo/box/harness.mjs:228— `writeFileSync` in `handle` 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/vendo/box/turn-routes.mjs:420— `mkdirSync` in `handle` 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/vendo/box/turn-routes.mjs:421— `readdirSync` in `handle` 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/vendo/box/turn-routes.mjs:422— `rmSync` in `handle` 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/vendo/box/turn-routes.mjs:429— `mkdirSync` in `handle` 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/vendo/box/turn-routes.mjs:430— `writeFileSync` in `handle` 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/vendo/box/turn-routes.mjs:433— `chmodSync` in `handle` 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/vendo/box/turn-routes.mjs:461— `readFileSync` in `handle` 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/vendo/box/turn-routes.mjs:472— `statSync` in `handle` 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/vendo/box/turn-routes.mjs:473— `readFileSync` in `handle` 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/vendo/src/cli/mcp/verify-domain.ts:32— `generateKeyPairSync` in `runVerifyDomain` 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/vendo/src/core/deployment-identity.ts:52— `readFileSync` in `anonymous function` 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/vendo/src/harnesses/claude-code/local.ts:288— `chmodSync` in `materialize` 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/vendo/src/harnesses/vendo/shell/parsers/docx2txt.ts:104— `unzipSync` in `execute` 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/vendo/src/store/db.ts:155— `fs.writeFileSync` in `acquirePgliteDirLock` 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/vendo/src/store/db.ts:165— `fs.rmSync` in `acquirePgliteDirLock` 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/vendo/src/store/db.ts:182— `fs.utimesSync` in `callback to setInterval` 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/vendo/src/store/db.ts:195— `fs.rmSync` in `release` 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/vendo/src/store/db.ts:318— `fs.rmSync` in `createPgliteHealingStaleLock` 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×15
Skipped test: dedupes every failed firing onto ONE card per missing grant per app packages/vendo/tests/audit-superset.e2e.test.ts:524— Skipped — switched off by it.skip
Skipped test: carries a skipped-run count on the standing card packages/vendo/tests/audit-superset.e2e.test.ts:537— Skipped — switched off by it.skip
Skipped test: kill-the-server durability is owned by PostgreSQL packages/vendo/tests/store/durability.drill.test.ts:36— Skipped — switched off by it.skip
Skipped test: ${conformanceCase.name} [pending: ${conformanceCase.pending}] packages/vendo/tests/store/ops.conformance.test.ts:40— Skipped — switched off by it.skip
Skipped test: postgres leg skipped — POSTGRES_URL not set packages/vendo/tests/store/postgres-gate.test.ts:10— Skipped — switched off by it.skip
Skipped test: skipped: ANTHROPIC_API_KEY not set packages/vendo/tests/guard/live/judge.live.test.ts:46— Skipped — switched off by it.skip
Skipped test: ${conformanceCase.name} [pending: ${conformanceCase.pending}] packages/vendo/tests/core/conformance/memory-store-ops.test.ts:57— Skipped — switched off by it.skip
Skipped test: raises an out-of-memory screen as a catchable failure, and the engine survives it packages/vendo/tests/core/apps/genui/component/screen-errors.test.ts:314— Skipped — switched off by it.skip
Skipped test: (unnamed test) packages/vendo/tests/actions/connectors/composio.live.test.ts:87— Skipped — switched off by test.skip
Skipped test: (unnamed test) fixtures/context-e2e/e2e/cache-ledger.spec.ts:37— Skipped — switched off by test.skip
Skipped test: (unnamed test) fixtures/context-e2e/e2e/compaction-recall.spec.ts:51— Skipped — switched off by test.skip
Skipped test: (unnamed test) fixtures/context-e2e/e2e/giant-first.spec.ts:50— Skipped — switched off by test.skip
Skipped test: (unnamed test) fixtures/context-e2e/e2e/overflow-recovery.spec.ts:29— Skipped — switched off by test.skip
Skipped test: (unnamed test) fixtures/context-e2e/e2e/parallel-hires.spec.ts:19— Skipped — switched off by test.skip
Outbound HTTP without resilience packages/vendo/scripts/build-onest-font.mjs:40— `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/vendo/src/actions/connectors/composio.ts:179— `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/vendo/src/cli/cloud/auth.ts:93— `fetcher(` 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/vendo/src/cli/cloud/auth.ts:96— `fetcher(` 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/vendo/src/cli/cloud/auth.ts:126— `fetcher(` 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/vendo/src/cli/cloud/device-login.ts:158— `fetchImpl(` 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 REDACTED:145— `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 REDACTED:198— `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/vendo/src/cloud-tools.ts:52— `fetchImpl(` 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/vendo/src/core/apps/genui/wasm-browser.ts:7— `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/vendo/src/core/heartbeat.ts:52— `fetchImpl(` 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/vendo/src/mcp/oauth/remote-as.ts:103— `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/vendo/src/ui/client-impl.ts:127— `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.
R4 · Test Coverage· No test reaches this file · ×13
No test reaches this file genbench/src/mount.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/scripts/build-icons.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file corpus/scripts/corpus-trend.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file docs-site/snippets/agent-prompt.jsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/scripts/generate-edge-lib-source.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/proofs/p2-harness-swap.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/src/ui/tree/mcp-shim/entry.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/scripts/build-onest-font.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file genbench/src/thesys-mount.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/src/theme-json-import.docs-check.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/src/store/crypto-edge.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/src/store/db-edge.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/vendo/src/core/apps/genui/wasm-node.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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×10
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:157— `.ghostBtn` moves (`transition: color 120ms ease, transform 160ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:188— `.tsBtn` moves (`transition: transform 160ms var(--ease-out), background 120ms ease, color 120ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:279— `.pulseRun::after` moves (`animation: wb-ring 1.7s ease-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:310— `.prog > i` moves (`transition: width 260ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:531— `.chev` moves (`transition: transform 150ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:807— `.gaugeFill` moves (`transition: width 260ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/components/vendo/workbench/workbench.module.css:1097— `.fchip` moves (`transition: color 120ms ease, border-color 120ms ease, background 120ms ease,
transform 160ms var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/app/globals.css:76— `.maple-modal-panel` moves (`transition: transform 260ms cubic-bezier(0.16, 1, 0.3, 1), opacity 180ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/app/globals.css:99— `.maple-modal[data-closing] .maple-modal-panel` moves (`transition: transform 160ms ease-out, opacity 140ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/demo-bank/src/app/globals.css:114— `.maple-approval-inflow .fl-approval` moves (`animation: maple-approval-in 0.28s cubic-bezier(0.16, 1, 0.3, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×10
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/store/validate.ts:76— `requireJson` is exported, takes a document from its caller (line 92) and hands it to `isJson`, which calls itself at line 76 (`isJson`) with a piece of `value` (and at line 85) — and nowhere in `isJson` 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 `isJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/harnesses/json-equal.ts:20— `jsonEqual` is exported and takes `left: unknown` from its caller, and it calls itself at line 20 (`jsonEqual`) with a piece of `left` (and at line 32) — and nowhere in `jsonEqual` 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 `jsonEqual` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/core/jcs.ts:48— `canonicalJson` is exported, takes a document from its caller (line 78) and hands it to `serialize`, which calls itself at line 48 (`serialize`) with a piece of `value` (and at line 64) — and nowhere in `serialize` 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 `serialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/core/reshape.ts:187— `findInvalidReshape` is exported and takes `value: unknown` from its caller, and it calls itself at line 187 (`findInvalidReshape`) with a piece of `value` (and at line 198) — and nowhere in `findInvalidReshape` 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 `findInvalidReshape` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/core/apps/fn-references.ts:17— `findInvalidActionReference` is exported and takes `value: unknown` from its caller, and it calls itself at line 17 (`findInvalidActionReference`) with a piece of `value` (and at line 30) — and nowhere in `findInvalidActionReference` 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 `findInvalidActionReference` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/core/apps/genui/component/flatten.ts:78— `flattenTree` is exported, takes a document from its caller (line 54) and hands it to `walk`, which calls itself at line 78 (`walk`) with a piece of `node` — and nowhere in `walk` 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 `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/apps/persistence/call.ts:86— `amountUnitIssue` is exported, takes a document from its caller (line 76) and hands it to `walk`, which calls itself at line 86 (`walk`) with a piece of `value` — and nowhere in `walk` 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 `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/actions/openapi-document.ts:24— `extractOpenApiDocument` is exported, takes a document from its caller (line 147) and hands it to `resolveRefs`, which calls itself at line 24 (`resolveRefs`) with a piece of `node` (and at line 35, line 38) — and nowhere in `resolveRefs` 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 `resolveRefs` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/vendo/src/actions/presets/shared.ts:76— `stableJson` is exported, takes a document from its caller (line 87) and hands it to `canonical`, which calls itself at line 76 (`canonical`) with a piece of `value` (and at line 81) — and nowhere in `canonical` 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 `canonical` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap genbench/src/world.ts:144— `jsonSchemaFromExample` is exported and takes `value: unknown` from its caller, and it calls itself at line 144 (`jsonSchemaFromExample`) with a piece of `value` (and at line 151) — and nowhere in `jsonSchemaFromExample` 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 `jsonSchemaFromExample` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D10 · Test Quality· Fixed-sleep synchronisation · ×6
Fixed-sleep synchronisation: never re-sends the same refused report on a later resolution cycle packages/vendo/tests/config-report-producer.seam.test.ts:203— This test starts work it did not wait for (`vendo`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 1_500))` — 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: a steer does NOT settle the caller's turn early packages/vendo/tests/harnesses/claude-code/claude-session.test.ts:436— This test starts work it did not wait for (`sending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — 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: a steer the engine FOLDS into the running turn still ends the caller's send() packages/vendo/tests/harnesses/claude-code/claude-session.test.ts:504— This test starts work it did not wait for (`sending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — 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: two steers and ONE result: idle clears the whole wait, not one steer of it packages/vendo/tests/harnesses/claude-code/claude-session.test.ts:542— This test starts work it did not wait for (`sending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — 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: leaves the replacement holding the slot when a place lands inside a stale unplace packages/vendo/tests/apps/placement-runtime.test.ts:345— This test starts work it did not wait for (`runtime`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — 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: leaves the replacement's POINTER standing when a place lands inside the same window packages/vendo/tests/apps/placement-runtime.test.ts:394— This test starts work it did not wait for (`runtime`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×5
Async function without AbortSignal: discoverJwksUri packages/vendo/src/mcp/oauth/remote-as.ts:101— `discoverJwksUri` 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: loadWasm packages/vendo/src/core/apps/genui/wasm-browser.ts:6— `loadWasm` 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: googleFaces REDACTED:143— `googleFaces` 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: embedHostFonts REDACTED:180— `embedHostFonts` 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: composioFetch packages/vendo/src/actions/connectors/composio.ts:172— `composioFetch` 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 })`.
Repeated repair: packages/vendo/src/capability-misses.ts packages/vendo/src/capability-misses.ts:105— packages/vendo/src/capability-misses.ts changed 10 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is capability-misses.createCapabilityMissCapture at line 105), AT OR 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(vendo): fifteen correctness bugs on the front door — two of them leak, one hangs, four answer wrong (#984)”; “fix(vendo): wire cloud overrides to tool ENABLEMENT (disabled/audience) (#557) (#600)”; “cloud: cloudSecrets adapter + selectSecrets seam; miss-capture adapter-rule fix (#548)”; “portability: the server runs on Web-standard runtimes — Workers fixes + CI gate (#513)”. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/capability-misses.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/vendo/src/sdk-events.ts packages/vendo/src/sdk-events.ts:57— packages/vendo/src/sdk-events.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is sdk-events.sdkRuntime at line 57), AT OR 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(vendo)!: validate what an allowlisted key HOLDS, not just its name (#1223)”; “fix(vendo)!: only a classification leaves the customer's servers (#1222)”; “fix(vendo)!: a failed snapshot ref is classified, never echoed into telemetry (#1217)”; “fix(vendo): sdk_error names the failing Vendo identifier, not just its type (#1216)”. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/sdk-events.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/vendo/src/cli/extract/claude-harness.ts packages/vendo/src/cli/extract/claude-harness.ts:116— packages/vendo/src/cli/extract/claude-harness.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 15 (its worst body is claude-harness.claudeHarness.run at line 116), AT OR 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(security): close verified critical findings from the Vega scan (#1648)”; “vendo: prune dead exports and CLI leftovers; fix env parsing (NaN/edge/quoted), cli option validation, refine maxMisses:0, cloud connections error masking, css-vars last-decl, doctor-live spawn error, init route wiring, doctor --yes non-TTY”; “fix(review): wake path owns its grade (no false refusals, never clobbers human risk); robust draft-JSON extraction; forward env to SDK”. 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-06-03..2026-09-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-03 19:48:26 +00:00' --until='2026-09-01 19:48:26 +00:00' --full-history --no-merges -- packages/vendo/src/cli/extract/claude-harness.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.
ClassTooLong: GuardImplementation packages/vendo/src/guard/guard.ts:458— ClassTooLong — 1113 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 713 over it, 2.78× 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: OAuthServer packages/vendo/src/mcp/oauth/server.ts:165— ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 132 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Door packages/vendo/src/mcp/door.ts:296— ClassTooLong — 472 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 72 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: box.ts ↔ local.ts packages/vendo/src/harnesses/claude-code/box.ts:1— `packages/vendo/src/harnesses/claude-code/box.ts` and `packages/vendo/src/harnesses/claude-code/local.ts` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `221c7459` fix(harnesses): pin every model slot the SDK reads, and stop blaming … (at that commit the files were still `packages/harnesses/src/claude-code/box.ts` and `packages/harnesses/src/claude-code/local.ts`); `5e584c84` fix(harnesses): every rung bounds a message, including machine: "loca… (at that commit the files were still `packages/harnesses/src/claude-code/box.ts` and `packages/harnesses/src/claude-code/local.ts`); `fb072fcc` feat(harnesses,ui): a build's own dev server is reachable from the br… (at that commit the files were still `packages/harnesses/src/claude-code/box.ts` and `packages/harnesses/src/claude-code/local.ts`) — run `git show` on any of them.
Change coupling: doctor-codes.ts ↔ doctor.ts packages/vendo/src/cli/doctor-codes.ts:1— `packages/vendo/src/cli/doctor-codes.ts` and `packages/vendo/src/cli/doctor.ts` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `545416ad` feat(store): warn when the store is writing to disk the platform wipe…; `2d52adbd` feat(core)!: env keys are credentials, config selects (#1209); `464dce8a` Broker mode is declared, not discovered (#1003) — run `git show` on any of them.
Change coupling: agent-tools.ts ↔ runtime.ts packages/vendo/src/apps/doors/agent-tools.ts:1— `packages/vendo/src/apps/doors/agent-tools.ts` and `packages/vendo/src/apps/runtime/runtime.ts` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `38a840de` refactor(apps,core)!: vendo_make has one engine — assembly that produ… (at that commit the files were still `packages/apps/src/agent-tools.ts` and `packages/apps/src/runtime.ts`); `3f98372a` feat(core,apps,harnesses): apps remember what they were asked for (#859) (at that commit the files were still `packages/apps/src/agent-tools.ts` and `packages/apps/src/runtime.ts`); `798b618f` UI-gen A1: the screen agent, its small loadout, and the seam that rou… (at that commit the files were still `packages/apps/src/agent-tools.ts` and `packages/apps/src/runtime.ts`) — run `git show` on any of them.
R10 · Code Duplication· Duplicated block with local edits (21 matched lines × 2 locations) · ×3
Duplicated block with local edits (21 matched lines × 2 locations) packages/vendo/src/actions/sync/common.ts:49— packages/vendo/src/actions/sync/common.ts:49 · packages/vendo/src/cli/theme/walk.ts:7 — the two spans are one implementation copied and then locally edited — 169 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (21 matched lines × 2 locations) packages/vendo/src/cli/cloud/pending-claim.ts:38— packages/vendo/src/cli/cloud/pending-claim.ts:38 · packages/vendo/src/cli/cloud/session.ts:13 — the two spans are one implementation copied and then locally edited — 213 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (21 matched lines × 2 locations) REDACTED:320— REDACTED:320 · REDACTED:467 — the two spans are one implementation copied and then locally edited — 228 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×3
Duplicated block with local edits (13 matched lines × 2 locations) corpus/harness/src/inject.ts:53— corpus/harness/src/inject.ts:53 · corpus/harness/src/local-pack.ts:156 — the two spans are one implementation copied and then locally edited — 130 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (13 matched lines × 2 locations) packages/vendo/src/guard/guard.ts:1425— packages/vendo/src/guard/guard.ts:1425 · packages/vendo/src/knowledge/agent-tools.ts:129 — the two spans are one implementation copied and then locally edited — 127 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (13 matched lines × 2 locations) packages/vendo/src/harnesses/turn-tools.ts:228— packages/vendo/src/harnesses/turn-tools.ts:228 · packages/vendo/src/screen-agent.ts:1757 — the two spans are one implementation copied and then locally edited — 106 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.
Swallowed exception (caught, then discarded) packages/vendo/src/mcp/oauth/server.ts:990— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/vendo/src/knowledge/ingest/index.ts:64— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/vendo/src/harnesses/materialize.ts:195— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Low contrast colour pair in CSS (4.0:1) examples/demo-bank/src/components/vendo/workbench/workbench.module.css:977— `.g th` sets color: #7a746c on background-color: #141312 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) corpus/hosts/express-host/src/client/brand.css:71— `.avatar` sets color: #087f6f on background-color: #dcece8 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
TooManyMethods: GuardImplementation packages/vendo/src/guard/guard.ts:458— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: WorkspaceStoreFs packages/vendo/src/store/workspace-fs.ts:194— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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.
Hollow method — returns a constant without doing the work packages/vendo/src/actions/sync/extractors.ts:70— `detect` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work packages/vendo/src/screen-agent.ts:867— `list` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Fake-async — async method never awaits packages/vendo/src/cli/doctor-config-checks.ts:116— `checkUserFiles` 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 packages/vendo/src/mcp/oauth/server.ts:827— `#revokeGrant` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R10 · Code Duplication· Duplicated block with local edits (63 matched lines × 2 locations) · ×2
Duplicated block with local edits (63 matched lines × 2 locations) packages/vendo/src/ui/hooks/approvals-feed.ts:90— packages/vendo/src/ui/hooks/approvals-feed.ts:90 · packages/vendo/src/ui/hooks/apps-feed.ts:66 — the two spans are one implementation copied and then locally edited — 490 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (63 matched lines × 2 locations) packages/vendo/src/ui/kit/charts/bar.tsx:26— packages/vendo/src/ui/kit/charts/bar.tsx:26 · packages/vendo/src/ui/kit/charts/line.tsx:34 — the two spans are one implementation copied and then locally edited — 586 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 (33 matched lines × 2 locations) · ×2
Duplicated block with local edits (33 matched lines × 2 locations) corpus/harness/src/install-command.ts:49— corpus/harness/src/install-command.ts:49 · corpus/harness/src/install-command.ts:88 — the two spans are one implementation copied and then locally edited — 314 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (33 matched lines × 2 locations) packages/vendo/src/cli/cloud/host-components.ts:92— packages/vendo/src/cli/cloud/host-components.ts:92 · packages/vendo/src/cli/cloud/seed-baselines.ts:53 — the two spans are one implementation copied and then locally edited — 269 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 (19 matched lines × 2 locations) · ×2
Duplicated block with local edits (19 matched lines × 2 locations) packages/vendo/src/automations/webhook-signature.ts:65— packages/vendo/src/automations/webhook-signature.ts:65 · packages/vendo/src/mcp/oauth/server.ts:1007 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (19 matched lines × 2 locations) packages/vendo/src/core/conformance/memory-app-access.ts:77— packages/vendo/src/core/conformance/memory-app-access.ts:77 · packages/vendo/src/store/helpers/app-access.ts:134 — the two spans are one implementation copied and then locally edited — 152 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (19 lines × 2 locations) packages/vendo/src/core/heartbeat.ts:80— packages/vendo/src/core/heartbeat.ts:80 · packages/vendo/src/turn-liveness.ts:237 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (19 lines × 2 locations) packages/vendo/src/ui/kit/data/card-list.tsx:47— packages/vendo/src/ui/kit/data/card-list.tsx:47 · packages/vendo/src/ui/kit/data/timeline.tsx:51 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) packages/vendo/src/actions/connectors/composio.ts:569— packages/vendo/src/actions/connectors/composio.ts:569 · packages/vendo/src/cloud-tools.ts:149 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (18 lines × 2 locations) packages/vendo/src/cli/index.ts:108— packages/vendo/src/cli/index.ts:108 · packages/vendo/src/cli/knowledge/index.ts:74 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (17 lines × 2 locations) packages/vendo/src/apps/testing/adapter-conformance.ts:187— packages/vendo/src/apps/testing/adapter-conformance.ts:187 · packages/vendo/src/apps/testing/adapter-conformance.ts:209 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) packages/vendo/src/cli/cloud/command.ts:41— packages/vendo/src/cli/cloud/command.ts:41 · packages/vendo/src/cli/cloud/command.ts:63 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) corpus/harness/src/cli.ts:196— corpus/harness/src/cli.ts:196 · corpus/harness/src/cli.ts:236 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) packages/vendo/src/cli/extract/claude-harness.ts:32— packages/vendo/src/cli/extract/claude-harness.ts:32 · packages/vendo/src/harnesses/inference/model.ts:224 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function (anonymous) (cyclomatic 28, cognitive 37) packages/vendo/src/apps/checking/facts.ts:321— (anonymous) has cyclomatic complexity 28 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 28, cognitive 37) packages/vendo/src/apps/checking/screen-typecheck.ts:274— (anonymous) has cyclomatic complexity 28 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped genbench/src/report.ts:223— `escape(caseDir)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped REDACTED:44— `markup` 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.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus packages/vendo/src/ui/chrome/connect-dock.tsx:405— 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.
Low contrast colour pair in CSS (3.6:1) examples/demo-bank/src/components/vendo/workbench/workbench.module.css:444— `.mute` sets color: #7a746c on background-color: #211f1c — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) corpus/hosts/express-host/src/client/brand.css:72— `.error` sets color: #dc2626 on background-color: #fff0ee — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
memory-store-ops.memoryStoreOps (cyclomatic 131) packages/vendo/src/core/conformance/memory-store-ops.ts:87— memory-store-ops.memoryStoreOps has cyclomatic complexity 131 (threshold 15). Of this number, 99 points are the body's own statements and 32 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.
vendo-overlay.VendoOverlay (cyclomatic 98) packages/vendo/src/ui/chrome/vendo-overlay.tsx:636— vendo-overlay.VendoOverlay has cyclomatic complexity 98 (threshold 15). Of this number, 40 points are the body's own statements and 58 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.VendoThread (cyclomatic 90) packages/vendo/src/ui/chrome/thread/index.tsx:57— index.VendoThread has cyclomatic complexity 90 (threshold 15). Of this number, 47 points are the body's own statements and 43 belong to 21 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.
data-table.DataTable (cyclomatic 63) packages/vendo/src/ui/kit/data/data-table.tsx:197— data-table.DataTable has cyclomatic complexity 63 (threshold 15). Of this number, 20 points are the body's own statements and 43 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.
ops.createStoreOps (cyclomatic 61) packages/vendo/src/store/ops.ts:278— ops.createStoreOps has cyclomatic complexity 61 (threshold 15). Of this number, 31 points are the body's own statements and 30 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
store-ops.storeOpsConformance (cyclomatic 57) packages/vendo/src/core/conformance/store-ops.ts:198— store-ops.storeOpsConformance has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 4 of the 57 points are its own statements and the rest belongs to 36 function literals inside it that branch (lines 1860, 283, 1649, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
hosted-store.storeWireClient (cyclomatic 56) packages/vendo/src/store/hosted-store.ts:415— hosted-store.storeWireClient has cyclomatic complexity 56 (threshold 15). Of this number, 18 points are the body's own statements and 38 belong to 21 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.claudeCode (cyclomatic 52) packages/vendo/src/harnesses/claude-code/index.ts:343— index.claudeCode has cyclomatic complexity 52 (threshold 15). Of this number, 38 points are the body's own statements and 14 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.
createSessionRoutes.handle (cyclomatic 52) packages/vendo/box/turn-routes.mjs:374— createSessionRoutes.handle has cyclomatic complexity 52 (threshold 15). Of this number, 49 points are the body's own statements and 3 belong to 6 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.
turn-routes.createSessionRoutes.handle (cyclomatic 51) packages/vendo/box/turn-routes.mjs:374— turn-routes.createSessionRoutes.handle has cyclomatic complexity 51 (threshold 15). Of this number, 48 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.
runtime.createHarnessRuntime.run (cyclomatic 51) packages/vendo/src/harnesses/runtime.ts:413— runtime.createHarnessRuntime.run has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 12 of the 51 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 589, a function literal at line 913, a function literal at line 857, …). 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.
vendo.vendo (cyclomatic 47) packages/vendo/src/harnesses/vendo/vendo.ts:413— vendo.vendo has cyclomatic complexity 47 (threshold 15). Of this number, 37 points are the body's own statements and 10 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.
init.runInit (cyclomatic 46) REDACTED:1826— init.runInit has cyclomatic complexity 46 (threshold 15). Of this number, 41 points are the body's own statements and 5 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.
memory-store.projectMemoryRecord (cyclomatic 44) packages/vendo/src/core/conformance/memory-store.ts:153— memory-store.projectMemoryRecord 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.
screen-agent.assembleScreen (cyclomatic 44) packages/vendo/src/screen-agent.ts:895— screen-agent.assembleScreen has cyclomatic complexity 44 (threshold 15). Of this number, 22 points are the body's own statements and 22 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.
connect-dock.ConnectTray (cyclomatic 43) packages/vendo/src/ui/chrome/connect-dock.tsx:203— connect-dock.ConnectTray has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 9 of the 43 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 279, item, connect, …). 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.
parts.ThreadPart (cyclomatic 43) packages/vendo/src/ui/chrome/thread/parts.tsx:280— parts.ThreadPart has cyclomatic complexity 43 (threshold 15). Of this number, 41 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.
lexical.vendoKnowledge (cyclomatic 43) packages/vendo/src/knowledge/local/lexical.ts:84— lexical.vendoKnowledge has cyclomatic complexity 43 (threshold 15). Of this number, 27 points are the body's own statements and 16 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.
use-placements.createPoller (cyclomatic 42) packages/vendo/src/ui/hooks/use-placements.ts:70— use-placements.createPoller has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 13 of the 42 points are its own statements and the rest belongs to 13 function items inside it that branch (flushReports, read, renew, …). 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.
sync.sync (cyclomatic 41) packages/vendo/src/cli/sync.ts:187— sync.sync has cyclomatic complexity 41 (threshold 15). Of this number, 39 points are the body's own statements and 2 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.
index.initCommand (cyclomatic 40) packages/vendo/src/cli/index.ts:157— index.initCommand 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.
connect-card.ConnectCard (cyclomatic 39) packages/vendo/src/ui/chrome/connect-card.tsx:74— connect-card.ConnectCard has cyclomatic complexity 39 (threshold 15). Of this number, 27 points are the body's own statements and 12 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.
Door.handler (cyclomatic 39) packages/vendo/src/mcp/door.ts:354— Door.handler 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.
index.vendoSync (cyclomatic 38) packages/vendo/src/actions/sync/index.ts:324— index.vendoSync has cyclomatic complexity 38 (threshold 15). Of this number, 34 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parts.ThreadAppCard (cyclomatic 37) packages/vendo/src/ui/chrome/thread/parts.tsx:745— parts.ThreadAppCard has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 766, 795, 839, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
harness-turn.createHarnessTurns.stream (cyclomatic 37) packages/vendo/src/harness-turn.ts:644— harness-turn.createHarnessTurns.stream has cyclomatic complexity 37 (threshold 15). Of this number, 25 points are the body's own statements and 12 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.
message.ThreadMessage (cyclomatic 36) packages/vendo/src/ui/chrome/thread/message.tsx:40— message.ThreadMessage has cyclomatic complexity 36 (threshold 15). Of this number, 33 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.
route-schema.schemaForCheckerType (cyclomatic 36) packages/vendo/src/actions/sync/route-schema.ts:530— route-schema.schemaForCheckerType has cyclomatic complexity 36 (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.
app-sql-guard.guardSql (cyclomatic 35) packages/vendo/src/apps/persistence/app-sql-guard.ts:280— app-sql-guard.guardSql has cyclomatic complexity 35 (threshold 15). Of this number, 31 points are the body's own statements and 4 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.
approval-modal.ApprovalModal (cyclomatic 34) packages/vendo/src/ui/chrome/approval-modal.tsx:122— approval-modal.ApprovalModal has cyclomatic complexity 34 (threshold 15). Of this number, 17 points are the body's own statements and 17 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.
cloud-init.cloudStep (cyclomatic 34) REDACTED:276— cloud-init.cloudStep has cyclomatic complexity 34 (threshold 15). Of this number, 30 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.
score.scoreAiJudgments (cyclomatic 32) corpus/harness/src/ai/score.ts:206— score.scoreAiJudgments has cyclomatic complexity 32 (threshold 15). Of this number, 26 points are the body's own statements and 6 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.
run.main (cyclomatic 32) genbench/src/run.ts:1154— run.main has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 14 of the 32 points are its own statements and the rest belongs to 4 function items inside it that branch (runOne, a function literal at line 1239, a function literal at line 1357, …). 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.
static-ts.applyZodModifier (cyclomatic 32) packages/vendo/src/actions/sync/static-ts.ts:450— static-ts.applyZodModifier 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.
composer.Composer (cyclomatic 31) packages/vendo/src/ui/chrome/thread/composer.tsx:324— composer.Composer has cyclomatic complexity 31 (threshold 15). Of this number, 19 points are the body's own statements and 12 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.
registry.createActions.buildRegistry (cyclomatic 31) packages/vendo/src/actions/runtime/registry.ts:747— registry.createActions.buildRegistry has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 748, 759, 855). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
vendo-slot.VendoSlot (cyclomatic 30) packages/vendo/src/ui/chrome/vendo-slot.tsx:248— vendo-slot.VendoSlot has cyclomatic complexity 30 (threshold 15). Of this number, 25 points are the body's own statements and 5 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.
route-scan.inferredPageVerbs (cyclomatic 30) packages/vendo/src/actions/sync/route-scan.ts:516— route-scan.inferredPageVerbs has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 528). 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.
plan.validatePlan (cyclomatic 30) packages/vendo/src/apps/automation/plan.ts:309— plan.validatePlan 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.
index.hostSignature (cyclomatic 30) packages/vendo/src/actions/sync/split/index.ts:190— index.hostSignature has cyclomatic complexity 30 (threshold 15). Of this number, 16 points are the body's own statements and 14 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.
turn.runTurn (cyclomatic 30) packages/vendo/src/turn/turn.ts:490— turn.runTurn has cyclomatic complexity 30 (threshold 15). Of this number, 18 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.
device-login.runDeviceLogin (cyclomatic 30) packages/vendo/src/cli/cloud/device-login.ts:199— device-login.runDeviceLogin 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. This shape REPEATS in the file: one other method here (device-login.runDeviceLogin::pollOnce) 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.
sync-flow.runGradingStages (cyclomatic 30) packages/vendo/src/cli/sync-flow.ts:640— sync-flow.runGradingStages has cyclomatic complexity 30 (threshold 15). Of this number, 21 points are the body's own statements and 9 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.
screen-tools-scan.blankNonCode (cyclomatic 29) packages/vendo/src/core/apps/screen-tools-scan.ts:84— screen-tools-scan.blankNonCode has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 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.
screen-typecheck.changeHandlerMessage (cyclomatic 29) packages/vendo/src/apps/checking/screen-typecheck.ts:206— screen-typecheck.changeHandlerMessage has cyclomatic complexity 29 (threshold 15). Of this number, 27 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.
morph-toast.MorphToast (cyclomatic 28) packages/vendo/src/ui/chrome/morph-toast.tsx:53— morph-toast.MorphToast has cyclomatic complexity 28 (threshold 15). Of this number, 21 points are the body's own statements and 7 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.
carve.proveHookCarve (cyclomatic 28) packages/vendo/src/actions/sync/split/carve.ts:396— carve.proveHookCarve has cyclomatic complexity 28 (threshold 15). 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: 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.splitSlot (cyclomatic 28) packages/vendo/src/actions/sync/split/index.ts:254— index.splitSlot has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 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.
GuardImplementation.#checkWithMetadata (cyclomatic 28) packages/vendo/src/guard/guard.ts:1180— GuardImplementation.#checkWithMetadata has cyclomatic complexity 28 (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.
turn-tools.createTurnTools.call (cyclomatic 28) packages/vendo/src/harnesses/turn-tools.ts:271— turn-tools.createTurnTools.call has cyclomatic complexity 28 (threshold 15). Of this number, 22 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.
renderer.StatefulTreeView (cyclomatic 27) packages/vendo/src/ui/tree/renderer.tsx:759— renderer.StatefulTreeView has cyclomatic complexity 27 (threshold 15). Of this number, 15 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.
catalog-scan.scanComponentCatalog (cyclomatic 27) packages/vendo/src/actions/sync/catalog-scan.ts:787— catalog-scan.scanComponentCatalog has cyclomatic complexity 27 (threshold 15). Of this number, 24 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.
screen-typecheck.typeIssue (cyclomatic 27) packages/vendo/src/apps/checking/screen-typecheck.ts:268— screen-typecheck.typeIssue 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.
parse.repairJson (cyclomatic 27) packages/vendo/src/cli/judge/parse.ts:58— parse.repairJson 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.
init.planMcpScaffold (cyclomatic 27) REDACTED:698— init.planMcpScaffold has cyclomatic complexity 27 (threshold 15). Of this number, 26 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.
embeds.VendoAppEmbed (cyclomatic 26) packages/vendo/src/ui/chrome/embeds.tsx:276— embeds.VendoAppEmbed has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 337, 325, 374, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
catalog-scan.localConstantJson (cyclomatic 26) packages/vendo/src/actions/sync/catalog-scan.ts:226— catalog-scan.localConstantJson 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.
component-screen.checkComponentScreen (cyclomatic 26) packages/vendo/src/apps/checking/component-screen.ts:623— component-screen.checkComponentScreen 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.
host-components.pushHostComponents (cyclomatic 26) packages/vendo/src/cli/cloud/host-components.ts:144— host-components.pushHostComponents has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, 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.
font-stack.isDefaultSansSpread (cyclomatic 26) REDACTED:369— font-stack.isDefaultSansSpread 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.
routing.configFor (cyclomatic 25) packages/vendo/src/store/routing.ts:328— routing.configFor 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.
facts.kitNestingIssues::checkKitElement (cyclomatic 25) packages/vendo/src/apps/checking/facts.ts:314— facts.kitNestingIssues::checkKitElement 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.
date-range.DateRange (cyclomatic 24) packages/vendo/src/ui/kit/forms/date-range.tsx:57— date-range.DateRange has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 103, pick, a function literal at line 81). 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.
composer.useComposer (cyclomatic 24) packages/vendo/src/ui/chrome/thread/composer.tsx:34— composer.useComposer 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 9 function literals inside it that branch (lines 61, 116, 250, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
screen-typings.zodTypeText (cyclomatic 24) packages/vendo/src/apps/checking/screen-typings.ts:181— screen-typings.zodTypeText has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
tool-bridge.guardedCall (cyclomatic 24) packages/vendo/src/harnesses/tool-bridge.ts:244— tool-bridge.guardedCall has cyclomatic complexity 24 (threshold 15). 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, 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.isPrivateAddress (cyclomatic 24) packages/vendo/src/mcp/oauth/server.ts:943— server.isPrivateAddress has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
agent.agent (cyclomatic 24) packages/vendo/src/turn/agent.ts:336— agent.agent has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
build-beat.toolPresentation (cyclomatic 23) packages/vendo/src/ui/chrome/build-beat.tsx:283— build-beat.toolPresentation 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, 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.
WorkspaceStoreFs.commit (cyclomatic 23) packages/vendo/src/store/workspace-fs.ts:566— WorkspaceStoreFs.commit has cyclomatic complexity 23 (threshold 15). Of this number, 22 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.
shared.verifyHs256 (cyclomatic 23) packages/vendo/src/actions/presets/shared.ts:157— shared.verifyHs256 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.
route-scan.exportedVerbs (cyclomatic 23) packages/vendo/src/actions/sync/route-scan.ts:325— route-scan.exportedVerbs 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 branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
GuardImplementation.bind (cyclomatic 23) packages/vendo/src/guard/guard.ts:730— GuardImplementation.bind has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 745, 741). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
screen-agent.screenAssembler.assemble (cyclomatic 23) packages/vendo/src/screen-agent.ts:1595— screen-agent.screenAssembler.assemble has cyclomatic complexity 23 (threshold 15). Of this number, 17 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.
extract-theme.collectCss (cyclomatic 23) packages/vendo/src/cli/theme/extract-theme.ts:230— extract-theme.collectCss 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 one function item inside it that branches (visit). 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.
index.runKnowledge (cyclomatic 23) packages/vendo/src/cli/knowledge/index.ts:369— index.runKnowledge has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: 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.
shape.shapeFromJsonSchemaAt (cyclomatic 22) packages/vendo/src/core/shape.ts:141— shape.shapeFromJsonSchemaAt 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.
static-ts.zodBase (cyclomatic 22) packages/vendo/src/actions/sync/static-ts.ts:411— static-ts.zodBase has cyclomatic complexity 22 (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.
catalog-scan.schemaForType (cyclomatic 22) packages/vendo/src/actions/sync/catalog-scan.ts:634— catalog-scan.schemaForType 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.
trpc.extractTrpc (cyclomatic 22) packages/vendo/src/actions/sync/trpc.ts:331— trpc.extractTrpc 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.
app-sql-guard.rewriteNamespaces (cyclomatic 22) packages/vendo/src/apps/persistence/app-sql-guard.ts:226— app-sql-guard.rewriteNamespaces 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.
screen-typings.jsonSchemaTypeText (cyclomatic 22) packages/vendo/src/apps/checking/screen-typings.ts:266— screen-typings.jsonSchemaTypeText 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.
component-screen.defaultComponent (cyclomatic 22) packages/vendo/src/apps/checking/component-screen.ts:370— component-screen.defaultComponent 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.
component-screen.scan (cyclomatic 22) packages/vendo/src/apps/checking/component-screen.ts:432— component-screen.scan has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 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.
port.portComponent (cyclomatic 22) packages/vendo/src/actions/sync/split/port.ts:124— port.portComponent has cyclomatic complexity 22 (threshold 15). Of this number, 19 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.
consent.createDecisionSubscriber.handleDecision (cyclomatic 22) packages/vendo/src/automations/consent.ts:184— consent.createDecisionSubscriber.handleDecision 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.
user-files.createUserFilesTools.execute (cyclomatic 22) packages/vendo/src/user-files.ts:292— user-files.createUserFilesTools.execute 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.
boot-summary.bootSummaryFor (cyclomatic 22) packages/vendo/src/boot-summary.ts:231— boot-summary.bootSummaryFor 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.
pass.reportNarrative (cyclomatic 22) packages/vendo/src/cli/judge/pass.ts:1022— pass.reportNarrative 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.
inject.assertLocalVendoResolution (cyclomatic 21) corpus/harness/src/inject.ts:269— inject.assertLocalVendoResolution 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.
structural.checkExpectedFiles (cyclomatic 21) corpus/harness/src/layers/structural.ts:504— structural.checkExpectedFiles 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.
steps.walkSteps (cyclomatic 21) packages/vendo/src/actions/runtime/steps.ts:109— steps.walkSteps has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
capture.importSpecifiers (cyclomatic 21) packages/vendo/src/actions/sync/capture.ts:166— capture.importSpecifiers has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
static-ts.resolveExport (cyclomatic 21) packages/vendo/src/actions/sync/static-ts.ts:150— static-ts.resolveExport 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.
server-actions.typeNodeSchema (cyclomatic 21) packages/vendo/src/actions/sync/server-actions.ts:247— server-actions.typeNodeSchema 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.
app-sql.createAppSql.run (cyclomatic 21) packages/vendo/src/apps/persistence/app-sql.ts:176— app-sql.createAppSql.run 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.
ingestion-surface.createWebhookDoor.webhook (cyclomatic 21) packages/vendo/src/automations/ingestion-surface.ts:218— ingestion-surface.createWebhookDoor.webhook 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.
fake-console.fakeConsole.route (cyclomatic 21) packages/vendo/src/store/fake-console.ts:378— fake-console.fakeConsole.route 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.
index.createRelayServer (cyclomatic 20) corpus/hosts/express-host/src/server/index.ts:35— index.createRelayServer 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 7 function literals inside it that branch (lines 66, 53, 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.
vendo.run (cyclomatic 20) genbench/src/vendo.ts:225— vendo.run has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
jcs.serialize (cyclomatic 20) packages/vendo/src/core/jcs.ts:23— jcs.serialize 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.
build-beat.BuildBeat (cyclomatic 20) packages/vendo/src/ui/chrome/build-beat.tsx:545— build-beat.BuildBeat 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.
turn-citations.CitationChip (cyclomatic 20) packages/vendo/src/ui/chrome/thread/turn-citations.tsx:52— turn-citations.CitationChip 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 10 function items inside it that branch (a function literal at line 95, a function literal at line 111, show, …). 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.
component-screen.literalValue (cyclomatic 20) packages/vendo/src/apps/checking/component-screen.ts:276— component-screen.literalValue 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.
claude-turn.createClaudeSession (cyclomatic 20) packages/vendo/src/harnesses/claude-code/claude-turn.ts:459— claude-turn.createClaudeSession 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 one function literal inside it that branches (line 540). 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.
OAuthServer.authorize (cyclomatic 20) packages/vendo/src/mcp/oauth/server.ts:231— OAuthServer.authorize 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.
OAuthServer.revoke (cyclomatic 20) packages/vendo/src/mcp/oauth/server.ts:479— OAuthServer.revoke 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, 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.
ingestion-surface.createTickDoor.runTick (cyclomatic 20) packages/vendo/src/automations/ingestion-surface.ts:38— ingestion-surface.createTickDoor.runTick 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.
agent-tools.parseInput (cyclomatic 20) packages/vendo/src/knowledge/agent-tools.ts:155— agent-tools.parseInput 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.
sandbox.decodeSnapshotRef (cyclomatic 20) packages/vendo/src/sandbox.ts:155— sandbox.decodeSnapshotRef 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.
connector-discovery.connectorDiscoveryRegistry.execute (cyclomatic 20) packages/vendo/src/connector-discovery.ts:218— connector-discovery.connectorDiscoveryRegistry.execute 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.
font-stack.exportedConfigObject (cyclomatic 20) REDACTED:448— font-stack.exportedConfigObject 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.
font-stack.tailwindConfigSansStack (cyclomatic 20) REDACTED:486— font-stack.tailwindConfigSansStack 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.
sync-flow.printSyncReport (cyclomatic 20) packages/vendo/src/cli/sync-flow.ts:230— sync-flow.printSyncReport 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.
matrix.runAiRepoMatrix (cyclomatic 19) corpus/harness/src/ai/matrix.ts:328— matrix.runAiRepoMatrix 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.
probe.press (cyclomatic 19) genbench/src/probe.ts:676— probe.press 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.
reshape.reshapeShape (cyclomatic 19) packages/vendo/src/core/reshape.ts:673— reshape.reshapeShape 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.
sample-props.generate (cyclomatic 19) packages/vendo/src/actions/sync/sample-props.ts:168— sample-props.generate 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.
server-actions.collectInlineActions (cyclomatic 19) packages/vendo/src/actions/sync/server-actions.ts:546— server-actions.collectInlineActions 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 3 function items inside it that branch (inlineName, visit, a function literal at line 574). 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.
carve.pruneDeadHomeStatements (cyclomatic 19) packages/vendo/src/actions/sync/split/carve.ts:665— carve.pruneDeadHomeStatements has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 683, keptOut). 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.inputNarrowed (cyclomatic 19) packages/vendo/src/actions/sync/index.ts:122— index.inputNarrowed 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.
GuardImplementation.#queryAudit (cyclomatic 19) packages/vendo/src/guard/guard.ts:2578— GuardImplementation.#queryAudit 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.
loop.turnModelMessages (cyclomatic 19) packages/vendo/src/harnesses/vendo/loop.ts:348— loop.turnModelMessages has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 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.
run-execution.createStepsRunner.continueSteps (cyclomatic 19) packages/vendo/src/automations/run-execution.ts:79— run-execution.createStepsRunner.continueSteps 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.
device-login.runDeviceLogin::pollOnce (cyclomatic 19) packages/vendo/src/cli/cloud/device-login.ts:365— device-login.runDeviceLogin::pollOnce has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (device-login.runDeviceLogin) 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.
pretty.createPrettyOutput.select (cyclomatic 19) packages/vendo/src/cli/pretty.ts:950— pretty.createPrettyOutput.select has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 990, optionLine, draw). 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.
provenance.mergeExtraction (cyclomatic 19) packages/vendo/src/cli/theme/provenance.ts:173— provenance.mergeExtraction has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.main (cyclomatic 19) packages/vendo/src/cli/index.ts:297— index.main 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.
local.localMachine.send (cyclomatic 19) packages/vendo/src/harnesses/claude-code/local.ts:327— local.localMachine.send 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.
vendo-root-paste.mountSpan (cyclomatic 18) corpus/harness/src/vendo-root-paste.ts:120— vendo-root-paste.mountSpan has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (visit, isReturned, isChildren, …). 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.
reshape.invalidStep (cyclomatic 18) packages/vendo/src/core/reshape.ts:139— reshape.invalidStep 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.
catalog-prompt.typeText (cyclomatic 18) packages/vendo/src/core/apps/kit/catalog-prompt.ts:81— catalog-prompt.typeText has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
client-impl.createVendoClient (cyclomatic 18) packages/vendo/src/ui/client-impl.ts:108— client-impl.createVendoClient 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 8 function literals inside it that branch (lines 273, 288, 206, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
split-view.splitViewReducer (cyclomatic 18) packages/vendo/src/ui/chrome/split-view.tsx:72— split-view.splitViewReducer 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.
mcp.mcpConnector.descriptors (cyclomatic 18) packages/vendo/src/actions/connectors/mcp.ts:234— mcp.mcpConnector.descriptors 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.
common.declaresExport (cyclomatic 18) packages/vendo/src/actions/sync/common.ts:239— common.declaresExport 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.
common.exportOrigin::follow (cyclomatic 18) packages/vendo/src/actions/sync/common.ts:413— common.exportOrigin::follow 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.
capture.captureClosure (cyclomatic 18) packages/vendo/src/actions/sync/capture.ts:241— capture.captureClosure has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
access-surface.createAccessSurface (cyclomatic 18) packages/vendo/src/apps/doors/access-surface.ts:17— access-surface.createAccessSurface has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (promoteBeforeSharing, require, requireMembership, …). 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.
render-seam.wrapWorkspaceForRender (cyclomatic 18) packages/vendo/src/apps/generation/render-seam.ts:281— render-seam.wrapWorkspaceForRender has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (persistSource, a function literal at line 348, emitFor). 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.
carve.jsonTypeText (cyclomatic 18) packages/vendo/src/actions/sync/split/carve.ts:306— carve.jsonTypeText has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
seeds.wrapperSites (cyclomatic 18) packages/vendo/src/actions/sync/seeds.ts:237— seeds.wrapperSites has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 252, 270). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GuardImplementation.#runOnce (cyclomatic 18) packages/vendo/src/guard/guard.ts:1722— GuardImplementation.#runOnce has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
GuardImplementation.#decideApprovals (cyclomatic 18) packages/vendo/src/guard/guard.ts:2220— GuardImplementation.#decideApprovals has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
OAuthServer.#decideConsent (cyclomatic 18) packages/vendo/src/mcp/oauth/server.ts:323— OAuthServer.#decideConsent 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.
OAuthServer.#exchangeCode (cyclomatic 18) packages/vendo/src/mcp/oauth/server.ts:560— OAuthServer.#exchangeCode 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.
Door.#handleMcp (cyclomatic 18) packages/vendo/src/mcp/door.ts:501— Door.#handleMcp 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.
Door.#callTool (cyclomatic 18) packages/vendo/src/mcp/door.ts:874— Door.#callTool 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.
seed-baselines.pushSeedBaselines (cyclomatic 18) packages/vendo/src/cli/cloud/seed-baselines.ts:101— seed-baselines.pushSeedBaselines has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
extract-theme.readExact (cyclomatic 18) packages/vendo/src/cli/theme/extract-theme.ts:369— extract-theme.readExact has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
claude-code.run (cyclomatic 17) genbench/src/claude-code.ts:159— claude-code.run has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 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.
renderer.validateWalkTree (cyclomatic 17) packages/vendo/src/ui/tree/renderer.tsx:134— renderer.validateWalkTree 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.
remixable.RemixedFork (cyclomatic 17) packages/vendo/src/ui/chrome/remixable.tsx:125— remixable.RemixedFork has cyclomatic complexity 17 (threshold 15). 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: 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.
records.createRecordStore.compareAndMutate (cyclomatic 17) packages/vendo/src/store/records.ts:103— records.createRecordStore.compareAndMutate 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.
static-ts.zodFromExpression (cyclomatic 17) packages/vendo/src/actions/sync/static-ts.ts:274— static-ts.zodFromExpression 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.
catalog-scan.registeredComponentMaps (cyclomatic 17) packages/vendo/src/actions/sync/catalog-scan.ts:145— catalog-scan.registeredComponentMaps 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 one function item inside it that branches (visit). 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.
sample-props.stringFor (cyclomatic 17) packages/vendo/src/actions/sync/sample-props.ts:50— sample-props.stringFor 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.
server-actions.typeLiteralSchema (cyclomatic 17) packages/vendo/src/actions/sync/server-actions.ts:183— server-actions.typeLiteralSchema 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.
trpc.evaluateRouterExpression (cyclomatic 17) packages/vendo/src/actions/sync/trpc.ts:175— trpc.evaluateRouterExpression 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.
tool-bridge.knowledgeCitationsPart (cyclomatic 17) packages/vendo/src/harnesses/tool-bridge.ts:182— tool-bridge.knowledgeCitationsPart has cyclomatic complexity 17 (threshold 15). 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: 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.
OAuthServer.#rotateRefresh (cyclomatic 17) packages/vendo/src/mcp/oauth/server.ts:607— OAuthServer.#rotateRefresh 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.
arming-surface.createDryRunDoor.dryRun (cyclomatic 17) packages/vendo/src/automations/arming-surface.ts:87— arming-surface.createDryRunDoor.dryRun has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
byo-approvals.createByoApprovals.read (cyclomatic 17) packages/vendo/src/byo-approvals.ts:256— byo-approvals.createByoApprovals.read 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.
channel-turn.cronProse (cyclomatic 17) packages/vendo/src/channel-turn.ts:148— channel-turn.cronProse 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.
sync-flow.pushComponentsToCloud (cyclomatic 17) packages/vendo/src/cli/sync-flow.ts:840— sync-flow.pushComponentsToCloud 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.
local-pack.rewritePackageJsonForLocalVendo (cyclomatic 16) corpus/harness/src/local-pack.ts:271— local-pack.rewritePackageJsonForLocalVendo 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.
repaint-motion.diffPaints (cyclomatic 16) packages/vendo/src/ui/tree/repaint-motion.ts:127— repaint-motion.diffPaints has cyclomatic complexity 16 (threshold 15). Of this number, 13 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.
steps.Steps (cyclomatic 16) packages/vendo/src/ui/kit/feedback/steps.tsx:24— steps.Steps 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 one function literal inside it that branches (line 41). 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.
db.createPgliteDb (cyclomatic 16) packages/vendo/src/store/db.ts:335— db.createPgliteDb has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WorkspaceStoreFs.readdirWithFileTypes (cyclomatic 16) packages/vendo/src/store/workspace-fs.ts:373— WorkspaceStoreFs.readdirWithFileTypes has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 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.
composio.composioConnector.searchTools (cyclomatic 16) packages/vendo/src/actions/connectors/composio.ts:466— composio.composioConnector.searchTools 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.
composio.composioConnector.descriptors (cyclomatic 16) packages/vendo/src/actions/connectors/composio.ts:544— composio.composioConnector.descriptors 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.
registry.hostHeaders (cyclomatic 16) packages/vendo/src/actions/runtime/registry.ts:476— registry.hostHeaders 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.
common.importReferenceFor (cyclomatic 16) packages/vendo/src/actions/sync/common.ts:462— common.importReferenceFor 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.
route-schema.methodHandlerBody (cyclomatic 16) packages/vendo/src/actions/sync/route-schema.ts:183— route-schema.methodHandlerBody 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, 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.
route-scan.reExportTargets (cyclomatic 16) packages/vendo/src/actions/sync/route-scan.ts:441— route-scan.reExportTargets 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.
route-scan.scanRoutes (cyclomatic 16) packages/vendo/src/actions/sync/route-scan.ts:756— route-scan.scanRoutes 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.
server-actions.extractServerActions (cyclomatic 16) packages/vendo/src/actions/sync/server-actions.ts:629— server-actions.extractServerActions 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.
build-messages.buildFailureReason (cyclomatic 16) packages/vendo/src/apps/doors/build-messages.ts:163— build-messages.buildFailureReason 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.
plan.stepsIssues (cyclomatic 16) packages/vendo/src/apps/automation/plan.ts:250— plan.stepsIssues 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.
seed-surface.seedFrom (cyclomatic 16) packages/vendo/src/apps/remix/seed-surface.ts:118— seed-surface.seedFrom 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, 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.
carve.scanElement (cyclomatic 16) packages/vendo/src/actions/sync/split/carve.ts:350— carve.scanElement has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 360). 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.
wiring.remixWiringSource (cyclomatic 16) packages/vendo/src/actions/sync/split/wiring.ts:47— wiring.remixWiringSource has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (localFor, a function literal at line 82, propertiesOf, …). 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.
GuardImplementation.#commitPreviewed (cyclomatic 16) packages/vendo/src/guard/guard.ts:1085— GuardImplementation.#commitPreviewed 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.
materialize.checkoutWorkspace.apply (cyclomatic 16) packages/vendo/src/harnesses/materialize.ts:211— materialize.checkoutWorkspace.apply 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.
runs-surface.createRunReadDoors.list (cyclomatic 16) packages/vendo/src/automations/runs-surface.ts:38— runs-surface.createRunReadDoors.list 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.
memory-store.memoryStoreAdapter.records.list (cyclomatic 16) packages/vendo/src/core/conformance/memory-store.ts:445— memory-store.memoryStoreAdapter.records.list has cyclomatic complexity 16 (threshold 15). Of this number, 10 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.
supabase.supabase (cyclomatic 16) packages/vendo/src/auth-presets/supabase.ts:210— supabase.supabase has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (sessionClaims, a function literal at line 258, 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.
registry.validateRegistryServer (cyclomatic 16) packages/vendo/src/cli/mcp/registry.ts:67— registry.validateRegistryServer 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.
pass.ingestProposal (cyclomatic 16) packages/vendo/src/cli/judge/pass.ts:649— pass.ingestProposal 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.
pass.routeProposal (cyclomatic 16) packages/vendo/src/cli/judge/pass.ts:872— pass.routeProposal has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, 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.
sync-flow.chooseEngine (cyclomatic 16) packages/vendo/src/cli/sync-flow.ts:495— sync-flow.chooseEngine 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.
init.buildPlan (cyclomatic 16) REDACTED:1021— init.buildPlan 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.
index.syncCommand (cyclomatic 16) packages/vendo/src/cli/index.ts:252— index.syncCommand 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.
Deprecated: eslint REDACTED:31— eslint 9.39.5, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
memory-store-ops.memoryStoreOps (cognitive 172) packages/vendo/src/core/conformance/memory-store-ops.ts:87— memory-store-ops.memoryStoreOps has cognitive complexity 172 (threshold 15). Drivers by points: if/else 55 (85 pts), ternaries 35 (39 pts), loops 17 (27 pts), boolean chains 21 (nesting depth added 44). Of this number, 138 points are the body's own statements and 34 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.
vendo-overlay.VendoOverlay (cognitive 112) packages/vendo/src/ui/chrome/vendo-overlay.tsx:636— vendo-overlay.VendoOverlay has cognitive complexity 112 (threshold 15). Drivers by points: if/else 38 (45 pts), ternaries 28 (41 pts), boolean chains 24, loops 1 (2 pts) (nesting depth added 21). Of this number, 49 points are the body's own statements and 63 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
createSessionRoutes.handle (cognitive 97) packages/vendo/box/turn-routes.mjs:374— createSessionRoutes.handle has cognitive complexity 97 (threshold 15). Drivers by points: if/else 26 (49 pts), loops 5 (14 pts), boolean chains 13, ternaries 5 (12 pts), error handling 3 (9 pts) (nesting depth added 45). Of this number, 94 points are the body's own statements and 3 belong to 6 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.
turn-routes.createSessionRoutes.handle (cognitive 96) packages/vendo/box/turn-routes.mjs:374— turn-routes.createSessionRoutes.handle has cognitive complexity 96 (threshold 15). Drivers by points: if/else 26 (49 pts), loops 5 (14 pts), boolean chains 13, ternaries 5 (12 pts), error handling 2 (8 pts) (nesting depth added 45). Of this number, 93 points are the body's own statements and 3 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.
index.VendoThread (cognitive 92) packages/vendo/src/ui/chrome/thread/index.tsx:57— index.VendoThread has cognitive complexity 92 (threshold 15). Drivers by points: ternaries 21 (36 pts), if/else 25 (30 pts), boolean chains 24, loops 2 (nesting depth added 20). Of this number, 48 points are the body's own statements and 44 belong to 21 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.
data-table.DataTable (cognitive 91) packages/vendo/src/ui/kit/data/data-table.tsx:197— data-table.DataTable has cognitive complexity 91 (threshold 15). Drivers by points: ternaries 25 (55 pts), boolean chains 16, if/else 11 (16 pts), loops 3 (4 pts) (nesting depth added 36). Most of this is not in the body itself: 15 of the 91 points are its own statements and the rest belongs to 19 function literals inside it that branch (lines 622, 329, 418, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
runtime.createHarnessRuntime.run (cognitive 64) packages/vendo/src/harnesses/runtime.ts:413— runtime.createHarnessRuntime.run has cognitive complexity 64 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 16 (23 pts), error handling 5 (6 pts), loops 4 (6 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 18). Of this number, 18 points are the body's own statements and 46 belong to 9 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
connect-card.ConnectCard (cognitive 60) packages/vendo/src/ui/chrome/connect-card.tsx:74— connect-card.ConnectCard has cognitive complexity 60 (threshold 15). Drivers by points: ternaries 19 (40 pts), if/else 8 (11 pts), boolean chains 8, error handling 1 (nesting depth added 24). Of this number, 42 points are the body's own statements and 18 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.
hosted-store.storeWireClient (cognitive 59) packages/vendo/src/store/hosted-store.ts:415— hosted-store.storeWireClient has cognitive complexity 59 (threshold 15). Drivers by points: if/else 17 (24 pts), ternaries 15 (16 pts), boolean chains 12, error handling 4 (6 pts), loops 1 (nesting depth added 10). Of this number, 19 points are the body's own statements and 40 belong to 21 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.
index.claudeCode (cognitive 58) packages/vendo/src/harnesses/claude-code/index.ts:343— index.claudeCode has cognitive complexity 58 (threshold 15). Drivers by points: if/else 24 (34 pts), ternaries 12, boolean chains 8, error handling 2, loops 2 (nesting depth added 10). Of this number, 43 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
connect-dock.ConnectTray (cognitive 57) packages/vendo/src/ui/chrome/connect-dock.tsx:203— connect-dock.ConnectTray has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 21 (32 pts), if/else 13 (17 pts), boolean chains 4, loops 3, error handling 1 (nesting depth added 15). Most of this is not in the body itself: 14 of the 57 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 279, item, connect, …). 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.
parts.ThreadPart (cognitive 57) packages/vendo/src/ui/chrome/thread/parts.tsx:280— parts.ThreadPart has cognitive complexity 57 (threshold 15). Drivers by points: if/else 25 (38 pts), ternaries 5 (10 pts), boolean chains 9 (nesting depth added 18). Of this number, 56 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.
lexical.vendoKnowledge (cognitive 56) packages/vendo/src/knowledge/local/lexical.ts:84— lexical.vendoKnowledge has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (31 pts), loops 10 (15 pts), boolean chains 9, ternaries 1 (nesting depth added 17). Of this number, 40 points are the body's own statements and 16 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.
store-ops.storeOpsConformance (cognitive 56) packages/vendo/src/core/conformance/store-ops.ts:198— store-ops.storeOpsConformance has cognitive complexity 56 (threshold 15). Drivers by points: loops 25 (26 pts), if/else 17 (19 pts), boolean chains 9, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 56 points are its own statements and the rest belongs to 36 function literals inside it that branch (lines 283, 1860, 1236, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ops.createStoreOps (cognitive 54) packages/vendo/src/store/ops.ts:278— ops.createStoreOps has cognitive complexity 54 (threshold 15). Drivers by points: if/else 24 (29 pts), ternaries 17, boolean chains 4, loops 3, error handling 1 (nesting depth added 5). Of this number, 32 points are the body's own statements and 22 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
memory-store.projectMemoryRecord (cognitive 53) packages/vendo/src/core/conformance/memory-store.ts:153— memory-store.projectMemoryRecord has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 18 (36 pts), boolean chains 8, if/else 4 (8 pts), match/switch 1 (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
init.runInit (cognitive 53) REDACTED:1826— init.runInit has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 14 (21 pts), if/else 16 (18 pts), boolean chains 10, error handling 2, loops 1 (2 pts) (nesting depth added 10). Of this number, 47 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
screen-tools-scan.blankNonCode (cognitive 52) packages/vendo/src/core/apps/screen-tools-scan.ts:84— screen-tools-scan.blankNonCode has cognitive complexity 52 (threshold 15). Drivers by points: if/else 16 (31 pts), ternaries 3 (9 pts), boolean chains 6, loops 4 (6 pts) (nesting depth added 23). Of this number, 41 points are the body's own statements and 11 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.
trpc.extractTrpc (cognitive 52) packages/vendo/src/actions/sync/trpc.ts:331— trpc.extractTrpc has cognitive complexity 52 (threshold 15). Drivers by points: if/else 13 (34 pts), ternaries 4 (12 pts), boolean chains 3, loops 2 (3 pts) (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.
index.vendoSync (cognitive 52) packages/vendo/src/actions/sync/index.ts:324— index.vendoSync has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 15 (23 pts), if/else 10 (18 pts), boolean chains 6, loops 4 (5 pts) (nesting depth added 17). Of this number, 46 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vendo.vendo (cognitive 52) packages/vendo/src/harnesses/vendo/vendo.ts:413— vendo.vendo has cognitive complexity 52 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 11 (16 pts), error handling 4 (6 pts), loops 4 (5 pts), boolean chains 4, match/switch 1 (3 pts) (nesting depth added 16). Of this number, 46 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.
Door.handler (cognitive 52) packages/vendo/src/mcp/door.ts:354— Door.handler has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 12, ternaries 5 (10 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.
registry.createActions.buildRegistry (cognitive 49) packages/vendo/src/actions/runtime/registry.ts:747— registry.createActions.buildRegistry has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 13 (17 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 20). None of this is in the body itself: all 49 points belong to 3 function literals inside it that branch (lines 748, 759, 855). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
app-sql-guard.guardSql (cognitive 49) packages/vendo/src/apps/persistence/app-sql-guard.ts:280— app-sql-guard.guardSql has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 11, ternaries 3 (6 pts), loops 4 (5 pts) (nesting depth added 17). Of this number, 44 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.
device-login.runDeviceLogin (cognitive 49) packages/vendo/src/cli/cloud/device-login.ts:199— device-login.runDeviceLogin has cognitive complexity 49 (threshold 15). Drivers by points: if/else 30 (50 pts), ternaries 9 (14 pts), boolean chains 7, error handling 3 (6 pts), loops 2 (3 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (device-login.runDeviceLogin::pollOnce) 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.
score.scoreAiJudgments (cognitive 48) corpus/harness/src/ai/score.ts:206— score.scoreAiJudgments has cognitive complexity 48 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 8 (15 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 19). Of this number, 39 points are the body's own statements and 9 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.
steps.walkSteps (cognitive 46) packages/vendo/src/actions/runtime/steps.ts:109— steps.walkSteps has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 5 (12 pts), error handling 2 (5 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 24). Of this number, 45 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.
parse.repairJson (cognitive 46) packages/vendo/src/cli/judge/parse.ts:58— parse.repairJson has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 3 (9 pts), loops 4 (8 pts), boolean chains 7 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
catalog-scan.scanComponentCatalog (cognitive 45) packages/vendo/src/actions/sync/catalog-scan.ts:787— catalog-scan.scanComponentCatalog has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 7, loops 3 (7 pts), ternaries 1 (3 pts) (nesting depth added 22). Of this number, 43 points are the body's own statements and 2 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.
use-placements.createPoller (cognitive 44) packages/vendo/src/ui/hooks/use-placements.ts:70— use-placements.createPoller has cognitive complexity 44 (threshold 15). Drivers by points: if/else 25 (30 pts), loops 6 (7 pts), boolean chains 5, error handling 1, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 13 of the 44 points are its own statements and the rest belongs to 13 function items inside it that branch (flushReports, read, renew, …). 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.
WorkspaceStoreFs.commit (cognitive 44) packages/vendo/src/store/workspace-fs.ts:566— WorkspaceStoreFs.commit has cognitive complexity 44 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 9 (15 pts), error handling 2 (6 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 22). Of this number, 43 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.
capture.captureClosure (cognitive 44) packages/vendo/src/actions/sync/capture.ts:241— capture.captureClosure has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (34 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 26). Of this number, 43 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.
route-schema.schemaForCheckerType (cognitive 44) packages/vendo/src/actions/sync/route-schema.ts:530— route-schema.schemaForCheckerType has cognitive complexity 44 (threshold 15). Drivers by points: if/else 24 (31 pts), ternaries 5 (9 pts), boolean chains 3, 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.
structural.checkExpectedFiles (cognitive 43) corpus/harness/src/layers/structural.ts:504— structural.checkExpectedFiles has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (33 pts), boolean chains 7, ternaries 1 (2 pts), loops 1 (nesting depth added 21). 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.
sync.sync (cognitive 43) packages/vendo/src/cli/sync.ts:187— sync.sync has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 20 (22 pts), if/else 10 (12 pts), boolean chains 5, loops 1 (3 pts), error handling 1 (nesting depth added 6). Of this number, 39 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, 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.
approval-modal.ApprovalModal (cognitive 42) packages/vendo/src/ui/chrome/approval-modal.tsx:122— approval-modal.ApprovalModal has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 17 (26 pts), if/else 12, boolean chains 3, error handling 1 (nesting depth added 9). Of this number, 23 points are the body's own statements and 19 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.
build-beat.BuildBeat (cognitive 41) packages/vendo/src/ui/chrome/build-beat.tsx:545— build-beat.BuildBeat has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 16 (38 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.
composer.Composer (cognitive 41) packages/vendo/src/ui/chrome/thread/composer.tsx:324— composer.Composer has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 7, if/else 6 (7 pts) (nesting depth added 11). Of this number, 22 points are the body's own statements and 19 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.
message.ThreadMessage (cognitive 41) packages/vendo/src/ui/chrome/thread/message.tsx:40— message.ThreadMessage has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 13 (25 pts), boolean chains 14, if/else 2 (nesting depth added 12). Of this number, 37 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.
static-ts.resolveExport (cognitive 41) packages/vendo/src/actions/sync/static-ts.ts:150— static-ts.resolveExport has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 21). 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.initCommand (cognitive 41) packages/vendo/src/cli/index.ts:157— index.initCommand has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 13 (15 pts), boolean chains 13, if/else 13 (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.
component-screen.checkComponentScreen (cognitive 39) packages/vendo/src/apps/checking/component-screen.ts:623— component-screen.checkComponentScreen has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 8 (12 pts), error handling 4 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
host-components.pushHostComponents (cognitive 39) packages/vendo/src/cli/cloud/host-components.ts:144— host-components.pushHostComponents has cognitive complexity 39 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 8 (11 pts), ternaries 6 (10 pts), boolean chains 3, error handling 1 (nesting depth added 14). Of this number, 31 points are the body's own statements and 8 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.
common.exportOrigin::follow (cognitive 38) packages/vendo/src/actions/sync/common.ts:413— common.exportOrigin::follow has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (25 pts), ternaries 2 (6 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harness-turn.createHarnessTurns.stream (cognitive 38) packages/vendo/src/harness-turn.ts:644— harness-turn.createHarnessTurns.stream has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 22 (24 pts), boolean chains 8, if/else 4 (6 pts) (nesting depth added 4). Of this number, 22 points are the body's own statements and 16 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.
run.main (cognitive 37) genbench/src/run.ts:1154— run.main has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 13 (17 pts), if/else 9 (11 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 7). Of this number, 18 points are the body's own statements and 19 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.
route-scan.scanRoutes (cognitive 37) packages/vendo/src/actions/sync/route-scan.ts:756— route-scan.scanRoutes has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 6 (19 pts), if/else 6 (14 pts), loops 2 (3 pts), boolean chains 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.
port.portComponent (cognitive 37) packages/vendo/src/actions/sync/split/port.ts:124— port.portComponent has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 5 (11 pts), loops 5 (7 pts), boolean chains 3 (nesting depth added 16). Of this number, 28 points are the body's own statements and 9 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.hostSignature (cognitive 37) packages/vendo/src/actions/sync/split/index.ts:190— index.hostSignature has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 9, loops 3 (4 pts), ternaries 3 (4 pts) (nesting depth added 9). Of this number, 22 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.
OAuthServer.revoke (cognitive 37) packages/vendo/src/mcp/oauth/server.ts:479— OAuthServer.revoke has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (26 pts), ternaries 4 (8 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 18). Of this number, 35 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.
run-execution.createStepsRunner.continueSteps (cognitive 37) packages/vendo/src/automations/run-execution.ts:79— run-execution.createStepsRunner.continueSteps has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (25 pts), error handling 2 (5 pts), loops 2 (3 pts), ternaries 2 (3 pts), boolean chains 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.
mcp.mcpConnector.descriptors (cognitive 36) packages/vendo/src/actions/connectors/mcp.ts:234— mcp.mcpConnector.descriptors has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (15 pts), ternaries 5 (15 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
claude-turn.createClaudeSession (cognitive 36) packages/vendo/src/harnesses/claude-code/claude-turn.ts:459— claude-turn.createClaudeSession has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 3, loops 1 (nesting depth added 19). None of this is in the body itself: all 36 points belong to one function literal inside it that branches (line 540). 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.
parts.ThreadAppCard (cognitive 35) packages/vendo/src/ui/chrome/thread/parts.tsx:745— parts.ThreadAppCard has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 12, ternaries 11 (12 pts), if/else 10 (11 pts) (nesting depth added 2). 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 766, 795, 839, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
static-ts.applyZodModifier (cognitive 35) packages/vendo/src/actions/sync/static-ts.ts:450— static-ts.applyZodModifier has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 6 (12 pts), boolean chains 4, match/switch 1 (nesting depth added 15). 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.
catalog-scan.localConstantJson (cognitive 35) packages/vendo/src/actions/sync/catalog-scan.ts:226— catalog-scan.localConstantJson has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
facts.kitNestingIssues::checkKitElement (cognitive 35) packages/vendo/src/apps/checking/facts.ts:314— facts.kitNestingIssues::checkKitElement has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 5 (10 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
component-screen.literalValue (cognitive 35) packages/vendo/src/apps/checking/component-screen.ts:276— component-screen.literalValue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (22 pts), ternaries 3 (6 pts), loops 2 (4 pts), boolean chains 3 (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.
component-screen.defaultComponent (cognitive 35) packages/vendo/src/apps/checking/component-screen.ts:370— component-screen.defaultComponent has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 5 (7 pts), boolean chains 3 (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.
screen-typecheck.typeIssue (cognitive 35) packages/vendo/src/apps/checking/screen-typecheck.ts:268— screen-typecheck.typeIssue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 5 (11 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.
vendo-slot.VendoSlot (cognitive 34) packages/vendo/src/ui/chrome/vendo-slot.tsx:248— vendo-slot.VendoSlot has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 9 (12 pts), boolean chains 9 (nesting depth added 7). Of this number, 29 points are the body's own statements and 5 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.
trpc.routerFromObjectLiteral (cognitive 34) packages/vendo/src/actions/sync/trpc.ts:140— trpc.routerFromObjectLiteral has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 3 (10 pts), loops 2 (5 pts), boolean chains 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.
plan.validatePlan (cognitive 34) packages/vendo/src/apps/automation/plan.ts:309— plan.validatePlan has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 6 (9 pts), boolean chains 7, 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.
index.splitSlot (cognitive 34) packages/vendo/src/actions/sync/split/index.ts:254— index.splitSlot has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (18 pts), ternaries 10 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). Of this number, 18 points are the body's own statements and 16 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.
font-stack.isDefaultSansSpread (cognitive 34) REDACTED:369— font-stack.isDefaultSansSpread has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 7, ternaries 2 (7 pts) (nesting depth added 14). 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.
inject.assertLocalVendoResolution (cognitive 33) corpus/harness/src/inject.ts:269— inject.assertLocalVendoResolution has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 6 (8 pts), boolean chains 6, ternaries 2 (3 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.
app-sql-guard.rewriteNamespaces (cognitive 33) packages/vendo/src/apps/persistence/app-sql-guard.ts:226— app-sql-guard.rewriteNamespaces has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 9, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tool-bridge.guardedCall (cognitive 33) packages/vendo/src/harnesses/tool-bridge.ts:244— tool-bridge.guardedCall has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 6, ternaries 3 (6 pts), error handling 1 (2 pts) (nesting depth added 10). Of this number, 31 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.
loop.turnModelMessages (cognitive 33) packages/vendo/src/harnesses/vendo/loop.ts:348— loop.turnModelMessages has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 7 (18 pts), if/else 8 (11 pts), boolean chains 4 (nesting depth added 14). Of this number, 31 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.
ingestion-surface.createTickDoor.runTick (cognitive 33) packages/vendo/src/automations/ingestion-surface.ts:38— ingestion-surface.createTickDoor.runTick has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 4 (7 pts), boolean chains 2, 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.
claude-harness.claudeHarness.run (cognitive 33) packages/vendo/src/cli/extract/claude-harness.ts:116— claude-harness.claudeHarness.run has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 4 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 19). 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.
morph-toast.MorphToast (cognitive 32) packages/vendo/src/ui/chrome/morph-toast.tsx:53— morph-toast.MorphToast has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 18 (23 pts), boolean chains 5, if/else 3, loops 1 (nesting depth added 5). Of this number, 25 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
route-scan.exportedVerbs (cognitive 32) packages/vendo/src/actions/sync/route-scan.ts:325— route-scan.exportedVerbs has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (11 pts), boolean chains 5 (nesting depth added 15). Of this number, 21 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.
turn-tools.createTurnTools.call (cognitive 32) packages/vendo/src/harnesses/turn-tools.ts:271— turn-tools.createTurnTools.call has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 8 (13 pts), boolean chains 3, error handling 1 (nesting depth added 10). Of this number, 26 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.
cloud-init.cloudStep (cognitive 32) REDACTED:276— cloud-init.cloudStep has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 8, loops 2 (7 pts) (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.
font-stack.tailwindConfigSansStack (cognitive 32) REDACTED:486— font-stack.tailwindConfigSansStack has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 3, loops 2 (3 pts), ternaries 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.
extract-theme.collectCss (cognitive 32) packages/vendo/src/cli/theme/extract-theme.ts:230— extract-theme.collectCss has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 5, loops 3 (5 pts), ternaries 2 (5 pts) (nesting depth added 12). Of this number, 17 points are the body's own statements and 15 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
init.buildPlan (cognitive 32) REDACTED:1021— init.buildPlan has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 7 (17 pts), if/else 8 (15 pts) (nesting depth added 17). 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.
shape.shapeFromJsonSchemaAt (cognitive 31) packages/vendo/src/core/shape.ts:141— shape.shapeFromJsonSchemaAt has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 9 (15 pts), if/else 8 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
routing.configFor (cognitive 31) packages/vendo/src/store/routing.ts:328— routing.configFor has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 9 (18 pts), if/else 6 (12 pts), match/switch 1 (nesting depth added 15). 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.
sample-props.stringFor (cognitive 31) packages/vendo/src/actions/sync/sample-props.ts:50— sample-props.stringFor has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (26 pts), if/else 4, 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.
route-schema.destructuredSearchParamsInitializer (cognitive 31) packages/vendo/src/actions/sync/route-schema.ts:706— route-schema.destructuredSearchParamsInitializer has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (14 pts), ternaries 2 (9 pts), loops 3 (6 pts), boolean chains 2 (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.
app-sql.createAppSql.run (cognitive 31) packages/vendo/src/apps/persistence/app-sql.ts:176— app-sql.createAppSql.run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 6 (9 pts), boolean chains 5, 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.
turn.runTurn (cognitive 31) packages/vendo/src/turn/turn.ts:490— turn.runTurn has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 13 (15 pts), if/else 11 (12 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 3). Of this number, 20 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.
consent.createDecisionSubscriber.handleDecision (cognitive 31) packages/vendo/src/automations/consent.ts:184— consent.createDecisionSubscriber.handleDecision has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 12). 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.
sync-flow.runGradingStages (cognitive 31) packages/vendo/src/cli/sync-flow.ts:640— sync-flow.runGradingStages has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 14 (18 pts), boolean chains 7, if/else 5, error handling 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 12 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.
matrix.runAiRepoMatrix (cognitive 30) corpus/harness/src/ai/matrix.ts:328— matrix.runAiRepoMatrix has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5 (10 pts), error handling 2 (4 pts), loops 2 (3 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.
embeds.VendoAppEmbed (cognitive 30) packages/vendo/src/ui/chrome/embeds.tsx:276— embeds.VendoAppEmbed has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 7 (11 pts), boolean chains 5, error handling 2 (nesting depth added 6). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 337, 325, 374, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
trpc.handlerOptions::visit (cognitive 30) packages/vendo/src/actions/sync/trpc.ts:245— trpc.handlerOptions::visit has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 4, loops 1 (4 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.
connector-discovery.connectorDiscoveryRegistry.execute (cognitive 30) packages/vendo/src/connector-discovery.ts:218— connector-discovery.connectorDiscoveryRegistry.execute has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 4 (8 pts), error handling 1, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provenance.mergeExtraction (cognitive 30) packages/vendo/src/cli/theme/provenance.ts:173— provenance.mergeExtraction has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 6, loops 2 (4 pts), ternaries 2 (3 pts) (nesting depth added 12). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
composio.composioConnector.searchTools (cognitive 29) packages/vendo/src/actions/connectors/composio.ts:466— composio.composioConnector.searchTools has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (9 pts), loops 5 (8 pts), boolean chains 2 (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.
component-screen.scan (cognitive 29) packages/vendo/src/apps/checking/component-screen.ts:432— component-screen.scan has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 3, ternaries 2 (3 pts), boolean chains 2, error handling 1 (nesting depth added 8). Most of this is not in the body itself: 13 of the 29 points are its own statements and the rest belongs to 2 function items inside it that branch (visit, a function literal at line 449). 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.
GuardImplementation.#checkWithMetadata (cognitive 29) packages/vendo/src/guard/guard.ts:1180— GuardImplementation.#checkWithMetadata has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 6 (9 pts), boolean chains 8 (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.
byo-approvals.createByoApprovals.read (cognitive 29) packages/vendo/src/byo-approvals.ts:256— byo-approvals.createByoApprovals.read has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 3 (7 pts), boolean chains 2, 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.
init.planMcpScaffold (cognitive 29) REDACTED:698— init.planMcpScaffold has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 10, ternaries 3, loops 1 (nesting depth added 4). Of this number, 28 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.
catalog-scan.schemaForType (cognitive 28) packages/vendo/src/actions/sync/catalog-scan.ts:634— catalog-scan.schemaForType has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (23 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (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.
route-scan.inferredPageVerbs (cognitive 28) packages/vendo/src/actions/sync/route-scan.ts:516— route-scan.inferredPageVerbs has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 8 (nesting depth added 4). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 528). 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.
screen-typecheck.changeHandlerMessage (cognitive 28) packages/vendo/src/apps/checking/screen-typecheck.ts:206— screen-typecheck.changeHandlerMessage has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 8, ternaries 4 (5 pts), loops 1 (nesting depth added 3). Of this number, 26 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.
carve.homeImportLines (cognitive 28) packages/vendo/src/actions/sync/split/carve.ts:705— carve.homeImportLines has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 4 (10 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 14). Of this number, 25 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.
Door.#callTool (cognitive 28) packages/vendo/src/mcp/door.ts:874— Door.#callTool has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2 (5 pts), boolean chains 4 (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.
screen-agent.assembleScreen (cognitive 28) packages/vendo/src/screen-agent.ts:895— screen-agent.assembleScreen has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (26 pts), ternaries 12 (21 pts), boolean chains 9, 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. This shape REPEATS in the file: one other method here (screen-agent.assembleScreen::landApp) 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.
message-data.sourcesFor (cognitive 27) packages/vendo/src/ui/chrome/thread/message-data.ts:180— message-data.sourcesFor has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 4, loops 2 (3 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.
composer.useComposer (cognitive 27) packages/vendo/src/ui/chrome/thread/composer.tsx:34— composer.useComposer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 5, boolean chains 4, ternaries 1 (nesting depth added 5). None of this is in the body itself: all 27 points belong to 9 function literals inside it that branch (lines 61, 116, 115, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
common.declaresExport (cognitive 27) packages/vendo/src/actions/sync/common.ts:239— common.declaresExport has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 5, 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.
capture.defaultExportOf (cognitive 27) packages/vendo/src/actions/sync/capture.ts:205— capture.defaultExportOf has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (8 pts), boolean chains 4, loops 2 (4 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.
server-actions.extractServerActions (cognitive 27) packages/vendo/src/actions/sync/server-actions.ts:629— server-actions.extractServerActions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 4 (10 pts), error handling 1 (2 pts), loops 2, boolean chains 1 (nesting depth added 12). Of this number, 26 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.
carve.pruneDeadHomeStatements (cognitive 27) packages/vendo/src/actions/sync/split/carve.ts:665— carve.pruneDeadHomeStatements has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 13). Of this number, 14 points are the body's own statements and 13 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.
wiring.remixWiringSource (cognitive 27) packages/vendo/src/actions/sync/split/wiring.ts:47— wiring.remixWiringSource has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 10 (20 pts), loops 3 (4 pts), if/else 2 (3 pts) (nesting depth added 12). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (localFor, a function literal at line 82, propertiesOf, …). 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.inputNarrowed (cognitive 27) packages/vendo/src/actions/sync/index.ts:122— index.inputNarrowed has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 7, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuardImplementation.#decideApprovals (cognitive 27) packages/vendo/src/guard/guard.ts:2220— GuardImplementation.#decideApprovals has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (6 pts), ternaries 4 (5 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 10). Of this number, 24 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.
GuardImplementation.#queryAudit (cognitive 27) packages/vendo/src/guard/guard.ts:2578— GuardImplementation.#queryAudit has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 6 (9 pts), boolean chains 3, loops 2 (3 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.
box.boxMachine.send (cognitive 27) packages/vendo/src/harnesses/claude-code/box.ts:504— box.boxMachine.send has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (9 pts), error handling 1 (4 pts), loops 2 (3 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.
boot-summary.bootSummaryFor (cognitive 27) packages/vendo/src/boot-summary.ts:231— boot-summary.bootSummaryFor has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (19 pts), ternaries 3 (6 pts), boolean chains 1, match/switch 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.
device-login.runDeviceLogin::pollOnce (cognitive 27) packages/vendo/src/cli/cloud/device-login.ts:365— device-login.runDeviceLogin::pollOnce has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 4 (7 pts), error handling 2 (5 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. This shape REPEATS in the file: one other method here (device-login.runDeviceLogin) 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.
pretty.createPrettyOutput.select (cognitive 27) packages/vendo/src/cli/pretty.ts:950— pretty.createPrettyOutput.select has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4, ternaries 3, loops 2 (nesting depth added 9). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 990, optionLine, draw). 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.
local-pack.rewritePackageJsonForLocalVendo (cognitive 26) corpus/harness/src/local-pack.ts:271— local-pack.rewritePackageJsonForLocalVendo has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 7 (10 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.
judge.traceText (cognitive 26) genbench/src/judge.ts:354— judge.traceText has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10 (25 pts), if/else 1 (nesting depth added 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 357). 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.
route-scan.reExportTargets (cognitive 26) packages/vendo/src/actions/sync/route-scan.ts:441— route-scan.reExportTargets has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (4 pts), boolean chains 2, 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.
carve.jsonTypeText (cognitive 26) packages/vendo/src/actions/sync/split/carve.ts:306— carve.jsonTypeText has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 4 (9 pts), boolean chains 1 (nesting depth added 9). Of this number, 22 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.
GuardImplementation.#commitPreviewed (cognitive 26) packages/vendo/src/guard/guard.ts:1085— GuardImplementation.#commitPreviewed has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 5, ternaries 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.
consent.createGrantCapture.captureGrants (cognitive 26) packages/vendo/src/automations/consent.ts:434— consent.createGrantCapture.captureGrants has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 3 (7 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ingestion-surface.createWebhookDoor.webhook (cognitive 26) packages/vendo/src/automations/ingestion-surface.ts:218— ingestion-surface.createWebhookDoor.webhook has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 4, loops 3 (4 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.
renderer.StatefulTreeView (cognitive 25) packages/vendo/src/ui/tree/renderer.tsx:759— renderer.StatefulTreeView has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (15 pts), if/else 5 (6 pts), boolean chains 3, error handling 1 (nesting depth added 2). Of this number, 14 points are the body's own statements and 11 belong to 7 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
use-app.useApp.refresh (cognitive 25) packages/vendo/src/ui/hooks/use-app.ts:62— use-app.useApp.refresh has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 1 (4 pts), error handling 1 (2 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.
composio.composioConnector.descriptors (cognitive 25) packages/vendo/src/actions/connectors/composio.ts:544— composio.composioConnector.descriptors has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (16 pts), if/else 3 (5 pts), boolean chains 3, 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.
app-sql-guard.tokenize (cognitive 25) packages/vendo/src/apps/persistence/app-sql-guard.ts:168— app-sql-guard.tokenize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (4 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.
screen-typings.jsonSchemaTypeText (cognitive 25) packages/vendo/src/apps/checking/screen-typings.ts:266— screen-typings.jsonSchemaTypeText has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 5, ternaries 3 (5 pts), loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
render-seam.wrapWorkspaceForRender (cognitive 25) packages/vendo/src/apps/generation/render-seam.ts:281— render-seam.wrapWorkspaceForRender has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (7 pts), error handling 2 (3 pts), loops 3 (nesting depth added 8). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (persistSource, a function literal at line 348, emitFor). 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.
seeds.remixableBindings (cognitive 25) packages/vendo/src/actions/sync/seeds.ts:138— seeds.remixableBindings has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (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.
materialize.checkoutWorkspace.apply (cognitive 25) packages/vendo/src/harnesses/materialize.ts:211— materialize.checkoutWorkspace.apply has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 4 (5 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.
unified-diff.unifiedDiff (cognitive 25) packages/vendo/src/apps/persistence/unified-diff.ts:61— unified-diff.unifiedDiff has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2, ternaries 2 (nesting depth added 11). Of this number, 21 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
seed-baselines.pushSeedBaselines (cognitive 25) packages/vendo/src/cli/cloud/seed-baselines.ts:101— seed-baselines.pushSeedBaselines has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 3 (6 pts), loops 4 (5 pts), boolean chains 3, error handling 1 (nesting depth added 8). Of this number, 17 points are the body's own statements and 8 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.
structural.mountReachesVendoReact (cognitive 24) corpus/harness/src/layers/structural.ts:479— structural.mountReachesVendoReact has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 12). Of this number, 22 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.
index.createRelayServer (cognitive 24) corpus/hosts/express-host/src/server/index.ts:35— index.createRelayServer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12, ternaries 8 (9 pts), boolean chains 3 (nesting depth added 1). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 66, 45, 53, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
build-beat.toolPresentation (cognitive 24) packages/vendo/src/ui/chrome/build-beat.tsx:283— build-beat.toolPresentation has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 7 (10 pts), boolean chains 7, if/else 5 (7 pts) (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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
records.createRecordStore.compareAndMutate (cognitive 24) packages/vendo/src/store/records.ts:103— records.createRecordStore.compareAndMutate has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 8 (11 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.
registry.hostHeaders (cognitive 24) packages/vendo/src/actions/runtime/registry.ts:476— registry.hostHeaders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 2, ternaries 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.
sample-props.generate (cognitive 24) packages/vendo/src/actions/sync/sample-props.ts:168— sample-props.generate has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3, ternaries 2 (3 pts), 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.
carve.proveHookCarve (cognitive 24) packages/vendo/src/actions/sync/split/carve.ts:396— carve.proveHookCarve has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (8 pts), if/else 7, loops 1 (nesting depth added 2). Of this number, 12 points are the body's own statements and 12 belong to 4 function literals inside it that branch. To reduce it, split the body: 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.agent (cognitive 24) packages/vendo/src/turn/agent.ts:336— agent.agent has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 18 (19 pts), if/else 3, boolean chains 2 (nesting depth added 1). Of this number, 19 points are the body's own statements and 5 belong to 2 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.
runs-surface.createRunReadDoors.list (cognitive 24) packages/vendo/src/automations/runs-surface.ts:38— runs-surface.createRunReadDoors.list has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 4 (5 pts), boolean chains 4, loops 2 (3 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.
sync-flow.printSyncReport (cognitive 24) packages/vendo/src/cli/sync-flow.ts:230— sync-flow.printSyncReport has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (11 pts), loops 5 (7 pts), if/else 6 (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.
probe.probe (cognitive 23) genbench/src/probe.ts:846— probe.probe has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 4 (8 pts), loops 1 (nesting depth added 12). Of this number, 21 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
shape.intersectSchemas (cognitive 23) packages/vendo/src/core/shape.ts:188— shape.intersectSchemas has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts), ternaries 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
screen-tools-scan.scanIslandTools (cognitive 23) packages/vendo/src/core/apps/screen-tools-scan.ts:188— screen-tools-scan.scanIslandTools has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (21 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.
renderer.validateWalkTree (cognitive 23) packages/vendo/src/ui/tree/renderer.tsx:134— renderer.validateWalkTree has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 6, 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.
catalog-scan.catalogCandidates (cognitive 23) packages/vendo/src/actions/sync/catalog-scan.ts:355— catalog-scan.catalogCandidates has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThreadRepository.persist (cognitive 23) packages/vendo/src/threads.ts:195— ThreadRepository.persist has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 3 (5 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
user-files.createUserFilesTools.execute (cognitive 23) packages/vendo/src/user-files.ts:292— user-files.createUserFilesTools.execute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4, ternaries 2, error handling 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.
screen-agent.screenAssembler.assemble (cognitive 23) packages/vendo/src/screen-agent.ts:1595— screen-agent.screenAssembler.assemble has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (12 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 2). 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, 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.
pass.reviewPendingLoosenings (cognitive 23) packages/vendo/src/cli/judge/pass.ts:974— pass.reviewPendingLoosenings has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (7 pts), ternaries 2 (4 pts), boolean chains 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.
vendo.run (cognitive 22) genbench/src/vendo.ts:225— vendo.run has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 13 (16 pts), if/else 5, boolean chains 1 (nesting depth added 3). Of this number, 17 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
jcs.serialize (cognitive 22) packages/vendo/src/core/jcs.ts:23— jcs.serialize has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 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.
date-range.DateRange (cognitive 22) packages/vendo/src/ui/kit/forms/date-range.tsx:57— date-range.DateRange has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 12 (13 pts), boolean chains 6, if/else 3 (nesting depth added 1). Most of this is not in the body itself: 7 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 103, pick, a function literal at line 81). 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.
http-dispatch.hostRequest (cognitive 22) packages/vendo/src/actions/runtime/http-dispatch.ts:163— http-dispatch.hostRequest has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (7 pts), ternaries 1 (2 pts), error handling 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.
shared.verifyHs256 (cognitive 22) packages/vendo/src/actions/presets/shared.ts:157— shared.verifyHs256 has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 9, error handling 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
route-schema.methodHandlerBody (cognitive 22) packages/vendo/src/actions/sync/route-schema.ts:183— route-schema.methodHandlerBody has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (12 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
access-checks.createAccessChecks.grantedRecords (cognitive 22) packages/vendo/src/apps/doors/access-checks.ts:83— access-checks.createAccessChecks.grantedRecords has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 6 (8 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.
GuardImplementation.bind (cognitive 22) packages/vendo/src/guard/guard.ts:730— GuardImplementation.bind has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 6, ternaries 2 (nesting depth added 2). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 745, 741). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
OAuthServer.authorize (cognitive 22) packages/vendo/src/mcp/oauth/server.ts:231— OAuthServer.authorize has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3, 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.
threads.deriveTitle (cognitive 22) packages/vendo/src/threads.ts:73— threads.deriveTitle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 1 (4 pts), loops 2 (3 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.
pass.ingestProposal (cognitive 22) packages/vendo/src/cli/judge/pass.ts:649— pass.ingestProposal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (5 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tree.queriesError (cognitive 21) packages/vendo/src/core/apps/genui/tree.ts:80— tree.queriesError has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, 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.
repaint-motion.diffPaints (cognitive 21) packages/vendo/src/ui/tree/repaint-motion.ts:127— repaint-motion.diffPaints has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (6 pts), boolean chains 4 (nesting depth added 6). Of this number, 18 points are the body's own statements and 3 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.
markdown.splitSections (cognitive 21) packages/vendo/src/ui/chrome/markdown.tsx:102— markdown.splitSections has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 9). 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.
compound.validateCapabilities (cognitive 21) packages/vendo/src/actions/runtime/compound.ts:48— compound.validateCapabilities has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (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.
common.importReferenceFor (cognitive 21) packages/vendo/src/actions/sync/common.ts:462— common.importReferenceFor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
route-scan.mergeRouteInput (cognitive 21) packages/vendo/src/actions/sync/route-scan.ts:682— route-scan.mergeRouteInput has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (8 pts), boolean chains 2, ternaries 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.
server-actions.typeLiteralSchema (cognitive 21) packages/vendo/src/actions/sync/server-actions.ts:183— server-actions.typeLiteralSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 3 (5 pts), boolean chains 4, 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.
trpc.evaluateRouterExpression (cognitive 21) packages/vendo/src/actions/sync/trpc.ts:175— trpc.evaluateRouterExpression has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (7 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
screen-typings.componentScreenTypings (cognitive 21) packages/vendo/src/apps/checking/screen-typings.ts:710— screen-typings.componentScreenTypings has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (14 pts), if/else 2 (4 pts), loops 2, boolean chains 1 (nesting depth added 8). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plan.stepsIssues (cognitive 21) packages/vendo/src/apps/automation/plan.ts:250— plan.stepsIssues has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, 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.
arming-surface.createDryRunDoor.dryRun (cognitive 21) packages/vendo/src/automations/arming-surface.ts:87— arming-surface.createDryRunDoor.dryRun has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (5 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 6). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vendo-verbs.vendoVerbsRegistry.execute (cognitive 21) packages/vendo/src/vendo-verbs.ts:116— vendo-verbs.vendoVerbsRegistry.execute has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 3 (6 pts), boolean chains 1, error handling 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
channel-turn.cronProse (cognitive 21) packages/vendo/src/channel-turn.ts:148— channel-turn.cronProse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 4 (7 pts), boolean chains 2 (nesting depth added 6). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
font-stack.exportedConfigObject (cognitive 21) REDACTED:448— font-stack.exportedConfigObject has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1, 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.
extract-theme.readExact (cognitive 21) packages/vendo/src/cli/theme/extract-theme.ts:369— extract-theme.readExact has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 4, if/else 3, loops 2 (nesting depth added 4). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pass.reportNarrative (cognitive 21) packages/vendo/src/cli/judge/pass.ts:1022— pass.reportNarrative has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, loops 4 (5 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.
reshape.invalidStep (cognitive 20) packages/vendo/src/core/reshape.ts:139— reshape.invalidStep has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 2 (5 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.
reshape.reshapeShape (cognitive 20) packages/vendo/src/core/reshape.ts:673— reshape.reshapeShape has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, ternaries 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.
message-data.approvalByCall (cognitive 20) packages/vendo/src/ui/chrome/thread/message-data.ts:104— message-data.approvalByCall has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 2 (6 pts), loops 2 (3 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.
turn-citations.CitationChip (cognitive 20) packages/vendo/src/ui/chrome/thread/turn-citations.tsx:52— turn-citations.CitationChip has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, ternaries 4 (6 pts), boolean chains 4 (nesting depth added 2). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 111, a function literal at line 95, show, …). 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.
openapi-document.extractOpenApiDocument (cognitive 20) packages/vendo/src/actions/openapi-document.ts:147— openapi-document.extractOpenApiDocument has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 1 (3 pts), loops 2 (3 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.
server-actions.typeNodeSchema (cognitive 20) packages/vendo/src/actions/sync/server-actions.ts:247— server-actions.typeNodeSchema has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
screen-program.translate (cognitive 20) packages/vendo/src/apps/checking/screen-program.ts:347— screen-program.translate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuardImplementation.#runOnce (cognitive 20) packages/vendo/src/guard/guard.ts:1722— GuardImplementation.#runOnce has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 6 (7 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 3). Of this number, 17 points are the body's own statements and 3 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.
harness.balancedObjectSpans (cognitive 20) packages/vendo/src/cli/extract/harness.ts:68— harness.balancedObjectSpans has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (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.
index.runKnowledge (cognitive 20) packages/vendo/src/cli/knowledge/index.ts:369— index.runKnowledge has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9, ternaries 4 (6 pts), boolean chains 4, error handling 1 (nesting depth added 2). Of this number, 13 points are the body's own statements and 7 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.
local-pack.detectPackageManager (cognitive 19) corpus/harness/src/local-pack.ts:221— local-pack.detectPackageManager has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4, ternaries 1 (3 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.
cli.parseAiArgs (cognitive 19) corpus/harness/src/cli.ts:220— cli.parseAiArgs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, loops 1, ternaries 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.
reshape.applyTemplate (cognitive 19) packages/vendo/src/core/reshape.ts:336— reshape.applyTemplate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 8). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderer.hasRenderableTreeContent (cognitive 19) packages/vendo/src/ui/tree/renderer.tsx:493— renderer.hasRenderableTreeContent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, 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.
aggregates.groupBy (cognitive 19) packages/vendo/src/ui/kit/aggregates.ts:132— aggregates.groupBy has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (5 pts), loops 2, boolean chains 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceStoreFs.readdirWithFileTypes (cognitive 19) packages/vendo/src/store/workspace-fs.ts:373— WorkspaceStoreFs.readdirWithFileTypes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, loops 4 (6 pts), ternaries 3 (4 pts), boolean chains 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 8 belong to 2 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.
catalog-scan.registeredComponentMaps::visit (cognitive 19) packages/vendo/src/actions/sync/catalog-scan.ts:156— catalog-scan.registeredComponentMaps::visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 8). 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.
catalog-scan.exportedObjectCandidates (cognitive 19) packages/vendo/src/actions/sync/catalog-scan.ts:487— catalog-scan.exportedObjectCandidates has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
route-scan.isInRejectedMethodBranch (cognitive 19) packages/vendo/src/actions/sync/route-scan.ts:291— route-scan.isInRejectedMethodBranch has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 3, 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.
route-scan.verbsFromSource (cognitive 19) packages/vendo/src/actions/sync/route-scan.ts:575— route-scan.verbsFromSource has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 4 (9 pts), ternaries 1 (nesting depth added 7). 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.
seed-surface.seedFrom (cognitive 19) packages/vendo/src/apps/remix/seed-surface.ts:118— seed-surface.seedFrom has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 3 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 4). Of this number, 17 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.
carve.computeCutSet (cognitive 19) packages/vendo/src/actions/sync/split/carve.ts:246— carve.computeCutSet has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (nesting depth added 6). Of this number, 11 points are the body's own statements and 8 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.declaredBody (cognitive 19) packages/vendo/src/actions/sync/split/index.ts:112— index.declaredBody has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (3 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.
agent-tools.parseInput (cognitive 19) packages/vendo/src/knowledge/agent-tools.ts:155— agent-tools.parseInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, ternaries 2 (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.
memory-store.memoryStoreAdapter.records.list (cognitive 19) packages/vendo/src/core/conformance/memory-store.ts:445— memory-store.memoryStoreAdapter.records.list has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (7 pts), if/else 4 (6 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 4). Of this number, 12 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, 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.
supabase.supabase (cognitive 19) packages/vendo/src/auth-presets/supabase.ts:210— supabase.supabase has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (7 pts), boolean chains 4, error handling 2 (4 pts), if/else 4 (nesting depth added 4). None of this is in the body itself: all 19 points belong to 3 function items inside it that branch (sessionClaims, a function literal at line 258, 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.
host-components.readLocal (cognitive 19) packages/vendo/src/cli/cloud/host-components.ts:95— host-components.readLocal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 4 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider-deps.installCommandFor (cognitive 19) REDACTED:163— provider-deps.installCommandFor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
embed-fonts.embedHostFonts (cognitive 19) REDACTED:180— embed-fonts.embedHostFonts has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 3 (6 pts), loops 2 (3 pts) (nesting depth added 10). Of this number, 15 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.
sync-flow.pushComponentsToCloud (cognitive 19) packages/vendo/src/cli/sync-flow.ts:840— sync-flow.pushComponentsToCloud has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (5 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.
matrix.renderAiScoreboardMarkdown (cognitive 18) corpus/harness/src/ai/matrix.ts:484— matrix.renderAiScoreboardMarkdown has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), loops 3 (5 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.
render.wideTables (cognitive 18) REDACTED:444— render.wideTables has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 446, 488). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
registry.createActions.surfaceMenu (cognitive 18) packages/vendo/src/actions/runtime/registry.ts:910— registry.createActions.surfaceMenu has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 8). Of this number, 16 points are the body's own statements and 2 belong to 2 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.
capture.importSpecifiers (cognitive 18) packages/vendo/src/actions/sync/capture.ts:166— capture.importSpecifiers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, loops 1 (nesting depth added 5). Of this number, 12 points are the body's own statements and 6 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.
static-ts.zodFromExpression (cognitive 18) packages/vendo/src/actions/sync/static-ts.ts:274— static-ts.zodFromExpression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4 (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.
route-scan.hasInlineDefaultFunctionBody (cognitive 18) packages/vendo/src/actions/sync/route-scan.ts:496— route-scan.hasInlineDefaultFunctionBody has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 1 (nesting depth added 7). Of this number, 13 points are the body's own statements and 5 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.
server-actions.collectInlineActions (cognitive 18) packages/vendo/src/actions/sync/server-actions.ts:546— server-actions.collectInlineActions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 1 (3 pts) (nesting depth added 4). None of this is in the body itself: all 18 points belong to 3 function items inside it that branch (inlineName, visit, a function literal at line 574). 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.
lane.runAutomationLane (cognitive 18) packages/vendo/src/apps/automation/lane.ts:202— lane.runAutomationLane has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 6 (7 pts), 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, 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.
call.amountUnitIssue::walk (cognitive 18) packages/vendo/src/apps/persistence/call.ts:81— call.amountUnitIssue::walk has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.importOf (cognitive 18) packages/vendo/src/actions/sync/split/index.ts:84— index.importOf has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, loops 2 (3 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.
seeds.captureRootStyles (cognitive 18) packages/vendo/src/actions/sync/seeds.ts:329— seeds.captureRootStyles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), error handling 1 (3 pts), loops 2 (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.
GuardImplementation.#matchingGrant (cognitive 18) packages/vendo/src/guard/guard.ts:2079— GuardImplementation.#matchingGrant has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
permission-wire.handlePermissionRequest (cognitive 18) REDACTED:70— permission-wire.handlePermissionRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5 (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.
run-execution.createRunLauncher.launchRun (cognitive 18) packages/vendo/src/automations/run-execution.ts:267— run-execution.createRunLauncher.launchRun has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 5, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 294). 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.
batched-uploader.createBatchedUploader.send (cognitive 18) packages/vendo/src/batched-uploader.ts:77— batched-uploader.createBatchedUploader.send has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 2 (4 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pretty.wrapRail (cognitive 18) packages/vendo/src/cli/pretty.ts:309— pretty.wrapRail has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
framework.detectVendoWiring (cognitive 18) packages/vendo/src/cli/framework.ts:272— framework.detectVendoWiring has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
registry.validateRegistryServer (cognitive 18) packages/vendo/src/cli/mcp/registry.ts:67— registry.validateRegistryServer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
font-stack.fontFactoryCall (cognitive 18) REDACTED:308— font-stack.fontFactoryCall has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 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.
shim-core.resolveQueries (cognitive 18) packages/vendo/src/ui/tree/mcp-shim/shim-core.ts:162— shim-core.resolveQueries has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 4 (5 pts), loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
structural.checkCommand (cognitive 17) corpus/harness/src/layers/structural.ts:616— structural.checkCommand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 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.
floor.wiredActions.bindings (cognitive 17) genbench/src/floor.ts:188— floor.wiredActions.bindings has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 2 (nesting depth added 10). 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, 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.
client-impl.createVendoClient (cognitive 17) packages/vendo/src/ui/client-impl.ts:108— client-impl.createVendoClient has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8, if/else 7, boolean chains 2. None of this is in the body itself: all 17 points belong to 8 function literals inside it that branch (lines 273, 288, 206, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
select.Select (cognitive 17) packages/vendo/src/ui/kit/forms/select.tsx:39— select.Select has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 1 (nesting depth added 4). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parked-approvals.useParkedApprovals (cognitive 17) packages/vendo/src/ui/tree/parked-approvals.ts:32— parked-approvals.useParkedApprovals has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 1 (nesting depth added 3). None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 48, 70, 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.
split-view.splitViewReducer (cognitive 17) packages/vendo/src/ui/chrome/split-view.tsx:72— split-view.splitViewReducer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 3 (6 pts), boolean chains 4, match/switch 1 (nesting depth added 6). 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.
workspace-ops-rows.workspaceOpsRows.commitAll (cognitive 17) packages/vendo/src/store/workspace-ops-rows.ts:246— workspace-ops-rows.workspaceOpsRows.commitAll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1, 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.
composio.composioConnector.listConnectable (cognitive 17) packages/vendo/src/actions/connectors/composio.ts:373— composio.composioConnector.listConnectable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 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.
static-ts.importMap (cognitive 17) packages/vendo/src/actions/sync/static-ts.ts:110— static-ts.importMap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), boolean chains 3 (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.
components.prune (cognitive 17) packages/vendo/src/actions/sync/components.ts:438— components.prune has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 5 (7 pts) (nesting depth added 6). 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.
facts.catalogIssues (cognitive 17) packages/vendo/src/apps/checking/facts.ts:157— facts.catalogIssues has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 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.
component-screen.paintedEvidence (cognitive 17) packages/vendo/src/apps/checking/component-screen.ts:1065— component-screen.paintedEvidence has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 4 (6 pts), boolean chains 1 (nesting depth added 7). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
build-messages.buildFailureReason (cognitive 17) packages/vendo/src/apps/doors/build-messages.ts:163— build-messages.buildFailureReason has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6, ternaries 4 (6 pts), boolean chains 5 (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.
app-source.commitApp (cognitive 17) packages/vendo/src/apps/persistence/app-source.ts:229— app-source.commitApp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3, error handling 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 6). Of this number, 11 points are the body's own statements and 6 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.
access-surface.createAccessSurface (cognitive 17) packages/vendo/src/apps/doors/access-surface.ts:17— access-surface.createAccessSurface has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 5, ternaries 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (require, requireMembership, promoteBeforeSharing, …). 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.
seeds.wrapperSites (cognitive 17) packages/vendo/src/actions/sync/seeds.ts:237— seeds.wrapperSites has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 252, 270). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GuardImplementation.#pipeline (cognitive 17) packages/vendo/src/guard/guard.ts:1478— GuardImplementation.#pipeline has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 5, boolean chains 2, error handling 1 (2 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuardImplementation.#compensateDecidedMembers (cognitive 17) packages/vendo/src/guard/guard.ts:2416— GuardImplementation.#compensateDecidedMembers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 3 (5 pts), ternaries 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
handler.agentHandler.<returned closure> (cognitive 17) packages/vendo/src/turn/handler.ts:162— handler.agentHandler.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (6 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
knowledge.knowledgeAdapterConformance (cognitive 17) packages/vendo/src/core/conformance/knowledge.ts:57— knowledge.knowledgeAdapterConformance has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 8 function items inside it that branch (adapterCase, a function literal at line 114, a function literal at line 119, …). 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.
screen-agent.assembleScreen::landApp (cognitive 17) packages/vendo/src/screen-agent.ts:990— screen-agent.assembleScreen::landApp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 5 (7 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. This shape REPEATS in the file: one other method here (screen-agent.assembleScreen) 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.
sandbox.decodeSnapshotRef (cognitive 17) packages/vendo/src/sandbox.ts:155— sandbox.decodeSnapshotRef has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 2, error handling 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.
doctor-wiring-checks.checkServerActionsWiring (cognitive 17) packages/vendo/src/cli/doctor-wiring-checks.ts:65— doctor-wiring-checks.checkServerActionsWiring has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 5, boolean chains 2 (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.
font-stack.propertyValue (cognitive 17) REDACTED:426— font-stack.propertyValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pass.runJudgmentPass (cognitive 17) packages/vendo/src/cli/judge/pass.ts:395— pass.runJudgmentPass has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 4 (7 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.
index.syncCommand (cognitive 17) packages/vendo/src/cli/index.ts:252— index.syncCommand has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (7 pts), boolean chains 5, if/else 5 (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.
index.main (cognitive 17) packages/vendo/src/cli/index.ts:297— index.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 4. 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.
mastra.unwrapOpenArgs (cognitive 17) packages/vendo/src/mastra.ts:95— mastra.unwrapOpenArgs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, error handling 1 (3 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.
fake-console.fakeConsole.route (cognitive 17) packages/vendo/src/store/fake-console.ts:378— fake-console.fakeConsole.route has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 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.
local-pack.discoverLocalPackages (cognitive 16) corpus/harness/src/local-pack.ts:126— local-pack.discoverLocalPackages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), error handling 1 (3 pts), loops 2 (3 pts), ternaries 1 (2 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.
local-pack.installLocalVendoPackages (cognitive 16) corpus/harness/src/local-pack.ts:362— local-pack.installLocalVendoPackages has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 3 (4 pts), boolean chains 2, loops 2, 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.
vendo-root-paste.directivePrologueEnd (cognitive 16) corpus/harness/src/vendo-root-paste.ts:32— vendo-root-paste.directivePrologueEnd has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vendo-root-paste.localFunction (cognitive 16) corpus/harness/src/vendo-root-paste.ts:61— vendo-root-paste.localFunction has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 3, loops 2 (3 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.
probe.supply (cognitive 16) genbench/src/probe.ts:547— probe.supply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (4 pts), boolean chains 2, loops 2 (nesting depth added 6). Of this number, 11 points are the body's own statements and 5 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.
claude-code.run (cognitive 16) genbench/src/claude-code.ts:159— claude-code.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3, boolean chains 2, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 189, observe). 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.
mount.opened (cognitive 16) genbench/src/mount.tsx:106— mount.opened has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (4 pts), error handling 1 (2 pts), loops 2, boolean chains 1 (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.
sha256.utf8Bytes (cognitive 16) packages/vendo/src/core/sha256.ts:15— sha256.utf8Bytes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 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.
shape.walkShapePointer (cognitive 16) packages/vendo/src/core/shape.ts:46— shape.walkShapePointer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tree.nodeError (cognitive 16) packages/vendo/src/core/apps/genui/tree.ts:117— tree.nodeError has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5 (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.
expr.evaluateExpr (cognitive 16) packages/vendo/src/core/apps/genui/expr.ts:319— expr.evaluateExpr has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 5, boolean chains 2, 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.
kit-prompt.renderSpec (cognitive 16) packages/vendo/src/core/apps/kit/kit-prompt.ts:159— kit-prompt.renderSpec has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), loops 3 (5 pts), if/else 3 (4 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.
composer.useComposer.send (cognitive 16) packages/vendo/src/ui/chrome/thread/composer.tsx:209— composer.useComposer.send has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 7). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markdown.MarkdownImpl (cognitive 16) packages/vendo/src/ui/chrome/markdown.tsx:222— markdown.MarkdownImpl has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 3, if/else 2 (nesting depth added 3). 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.
remixable.RemixedFork (cognitive 16) packages/vendo/src/ui/chrome/remixable.tsx:125— remixable.RemixedFork has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 5 (6 pts), if/else 4 (nesting depth added 1). Of this number, 10 points are the body's own statements and 6 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.
server-actions.collectModuleActions (cognitive 16) packages/vendo/src/actions/sync/server-actions.ts:451— server-actions.collectModuleActions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (nesting depth added 5). Of this number, 15 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.
trpc.procedureFromChain (cognitive 16) packages/vendo/src/actions/sync/trpc.ts:86— trpc.procedureFromChain has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, ternaries 2, 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.
screen-typings.zodTypeText (cognitive 16) packages/vendo/src/apps/checking/screen-typings.ts:181— screen-typings.zodTypeText has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (5 pts), match/switch 1 (nesting depth added 7). Of this number, 12 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.
loop.wellFormed (cognitive 16) packages/vendo/src/harnesses/vendo/loop.ts:216— loop.wellFormed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (3 pts) (nesting depth added 6). Of this number, 12 points are the body's own statements and 4 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.
OAuthServer.#decideConsent (cognitive 16) packages/vendo/src/mcp/oauth/server.ts:323— OAuthServer.#decideConsent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 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.
Door.#handleMcp (cognitive 16) packages/vendo/src/mcp/door.ts:501— Door.#handleMcp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 4, ternaries 4. 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.
consent.createPermissionMiss.needsPermission (cognitive 16) packages/vendo/src/automations/consent.ts:583— consent.createPermissionMiss.needsPermission has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 3 (6 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
merge.mergeCapability (cognitive 16) packages/vendo/src/capability/merge.ts:154— merge.mergeCapability has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 4 (8 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.
context.createContextResolver.<returned closure> (cognitive 16) packages/vendo/src/wire/context.ts:25— context.createContextResolver.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 5 (6 pts), boolean chains 1, 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.
client.cloudFetch (cognitive 16) packages/vendo/src/cli/cloud/client.ts:191— client.cloudFetch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 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.
pretty.createPrettyOutput.rowsWritten (cognitive 16) packages/vendo/src/cli/pretty.ts:737— pretty.createPrettyOutput.rowsWritten has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pass.routeProposal (cognitive 16) packages/vendo/src/cli/judge/pass.ts:872— pass.routeProposal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 3, ternaries 2 (3 pts), boolean chains 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sync-flow.chooseEngine (cognitive 16) packages/vendo/src/cli/sync-flow.ts:495— sync-flow.chooseEngine has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, ternaries 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.
createHarness.handle (cognitive 16) packages/vendo/box/harness.mjs:190— createHarness.handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), error handling 2 (4 pts), boolean chains 3, ternaries 1 (2 pts), other 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.
D22 · Internal API Consistency· `TenantConnectors.register` takes an options object where `TenantConnectors.test` takes the same values as positional parameters · ×1
`TenantConnectors.register` takes an options object where `TenantConnectors.test` takes the same values as positional parameters packages/vendo/src/tenant-connectors.ts:71— `test` takes (org, name) positionally; `register` takes them as properties of `TenantConnectorInput` (1 of 2). Siblings: TenantConnectors.test (packages/vendo/src/tenant-connectors.ts:74). Use one form for the same values across the type. [rule A7]
Change coupling clique: memory-store-ops.ts, store-ops.ts, hosted-store.ts, ops.ts packages/vendo/src/core/conformance/memory-store-ops.ts— 4 files — `packages/vendo/src/core/conformance/memory-store-ops.ts`, `packages/vendo/src/core/conformance/store-ops.ts`, `packages/vendo/src/store/hosted-store.ts`, `packages/vendo/src/store/ops.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Unfinished stub — throws a "not implemented" error packages/vendo/src/store/workspace-ops-rows.ts:74— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception packages/vendo/src/store/workspace-ops-rows.ts:74— `notWiredYet` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Duplication concentrated across 15 sibling directories (48 clone groups) packages/vendo/src/core/conformance/memory-store.ts:88— 48 duplicated blocks under packages/vendo/src/ have copies in at least two of the sibling directories actions, apps, auth-presets, automations, capability, cli (+9 more sibling(s) not listed) — 34 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 48 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 48 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 48 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 (8 clone groups) corpus/harness/src/layers/structural.ts:97— 8 duplicated blocks under the repository root have copies in at least two of the sibling directories corpus, docs-site, genbench, packages — 5 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (71 matched lines × 2 locations) · ×1
Duplicated block with local edits (71 matched lines × 2 locations) genbench/src/claude-code.ts:72— genbench/src/claude-code.ts:72 · genbench/src/codex.ts:59 — the two spans are one implementation copied and then locally edited — 617 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) genbench/src/honesty.ts:230— genbench/src/honesty.ts:230 · REDACTED:255 — the two spans are one implementation copied and then locally edited — 337 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 (47 matched lines × 2 locations) · ×1
Duplicated block with local edits (47 matched lines × 2 locations) packages/vendo/src/core/conformance/memory-store.ts:88— packages/vendo/src/core/conformance/memory-store.ts:88 · packages/vendo/src/store/validate.ts:70 — the two spans are one implementation copied and then locally edited — 448 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (46 lines × 2 locations) corpus/harness/src/layers/structural.ts:97— corpus/harness/src/layers/structural.ts:97 · REDACTED:43 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (44 matched lines × 2 locations) · ×1
Duplicated block with local edits (44 matched lines × 2 locations) packages/vendo/src/cli/extract/claude-cli-harness.ts:42— packages/vendo/src/cli/extract/claude-cli-harness.ts:42 · packages/vendo/src/cli/extract/codex-cli-harness.ts:26 — the two spans are one implementation copied and then locally edited — 327 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (38 matched lines × 2 locations) · ×1
Duplicated block with local edits (38 matched lines × 2 locations) packages/vendo/src/cli/cloud/host-components.ts:165— packages/vendo/src/cli/cloud/host-components.ts:165 · packages/vendo/src/cli/cloud/seed-baselines.ts:118 — the two spans are one implementation copied and then locally edited — 379 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (34 matched lines × 2 locations) · ×1
Duplicated block with local edits (34 matched lines × 2 locations) packages/vendo/src/ui/chrome/pin-chrome.tsx:90— packages/vendo/src/ui/chrome/pin-chrome.tsx:90 · packages/vendo/src/ui/chrome/remixable.tsx:299 — the two spans are one implementation copied and then locally edited — 212 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (34 lines × 2 locations) packages/vendo/src/ui/kit/layout.tsx:257— packages/vendo/src/ui/kit/layout.tsx:257 · packages/vendo/src/ui/kit/layout.tsx:312 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (28 lines × 2 locations) packages/vendo/src/ui/hooks/approvals-feed.ts:18— packages/vendo/src/ui/hooks/approvals-feed.ts:18 · packages/vendo/src/ui/hooks/apps-feed.ts:19 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (25 matched lines × 2 locations) · ×1
Duplicated block with local edits (25 matched lines × 2 locations) packages/vendo/src/actions/formats.ts:305— packages/vendo/src/actions/formats.ts:305 · packages/vendo/src/actions/formats.ts:429 — the two spans are one implementation copied and then locally edited — 215 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (24 lines × 2 locations) REDACTED:873— REDACTED:873 · REDACTED:900 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2 locations) packages/vendo/src/harnesses/claude-code/claude-turn.ts:275— packages/vendo/src/harnesses/claude-code/claude-turn.ts:275 · packages/vendo/src/harnesses/claude-code/index.ts:319 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (23 matched lines × 2 locations) · ×1
Duplicated block with local edits (23 matched lines × 2 locations) packages/vendo/src/store/helpers/audit.ts:31— packages/vendo/src/store/helpers/audit.ts:31 · packages/vendo/src/store/ops.ts:121 — the two spans are one implementation copied and then locally edited — 253 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 2 locations) packages/vendo/src/store/helpers/runs.ts:28— packages/vendo/src/store/helpers/runs.ts:28 · packages/vendo/src/store/records.ts:257 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) packages/vendo/src/core/knowledge-wire.ts:130— packages/vendo/src/core/knowledge-wire.ts:130 · packages/vendo/src/core/store-wire.ts:775 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) packages/vendo/src/auth-presets/auth0.ts:115— packages/vendo/src/auth-presets/auth0.ts:115 · packages/vendo/src/auth-presets/clerk.ts:91 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) packages/vendo/src/connector-discovery.ts:280— packages/vendo/src/connector-discovery.ts:280 · packages/vendo/src/vendo-verbs.ts:157 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (13 lines × 2 locations) packages/vendo/src/store/routing.ts:394— packages/vendo/src/store/routing.ts:394 · packages/vendo/src/store/routing.ts:536 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Complex function handler (cyclomatic 208, cognitive 313) packages/vendo/tests/ui/wire-server.ts:438— handler has cyclomatic complexity 208 and cognitive complexity 313; 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 52, cognitive 59) packages/vendo/src/core/conformance/memory-store.ts:158— (anonymous) has cyclomatic complexity 52 and cognitive complexity 59; 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 runInit (cyclomatic 51, cognitive 57) REDACTED:1826— runInit has cyclomatic complexity 51 and cognitive complexity 57; 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 VendoThread (cyclomatic 51, cognitive 44) packages/vendo/src/ui/chrome/thread/index.tsx:57— VendoThread has cyclomatic complexity 51 and cognitive complexity 44; 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 handle (cyclomatic 49, cognitive 94) packages/vendo/box/turn-routes.mjs:374— handle has cyclomatic complexity 49 and cognitive complexity 94; 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 47, cognitive 56) packages/vendo/tests/sandbox.test.ts:71— (anonymous) has cyclomatic complexity 47 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 VendoOverlay (cyclomatic 47, cognitive 44) packages/vendo/src/ui/chrome/vendo-overlay.tsx:636— VendoOverlay has cyclomatic complexity 47 and cognitive complexity 44; 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 ThreadPart (cyclomatic 45, cognitive 62) packages/vendo/src/ui/chrome/thread/parts.tsx:280— ThreadPart has cyclomatic complexity 45 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 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 handler (cyclomatic 44, cognitive 58) packages/vendo/src/mcp/door.ts:354— handler has cyclomatic complexity 44 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.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 44, cognitive 55) · ×1
Complex function run (cyclomatic 44, cognitive 55) packages/vendo/src/harnesses/claude-code/index.ts:364— run has cyclomatic complexity 44 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.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 43, cognitive 51) · ×1
Complex function run (cyclomatic 43, cognitive 51) packages/vendo/src/harnesses/vendo/vendo.ts:418— run has cyclomatic complexity 43 and cognitive complexity 51; 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 runDeviceLogin (cyclomatic 41, cognitive 60) packages/vendo/src/cli/cloud/device-login.ts:199— runDeviceLogin has cyclomatic complexity 41 and cognitive complexity 60; 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 sync (cyclomatic 41, cognitive 42) packages/vendo/src/cli/sync.ts:187— sync has cyclomatic complexity 41 and cognitive complexity 42; 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 initCommand (cyclomatic 40, cognitive 40) packages/vendo/src/cli/index.ts:157— initCommand has cyclomatic complexity 40 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 schemaForCheckerType (cyclomatic 38, cognitive 47) packages/vendo/src/actions/sync/route-schema.ts:530— schemaForCheckerType has cyclomatic complexity 38 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cloudStep (cyclomatic 38, cognitive 44) REDACTED:276— cloudStep has cyclomatic complexity 38 and cognitive complexity 44; 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 vendoSync (cyclomatic 37, cognitive 51) packages/vendo/src/actions/sync/index.ts:324— vendoSync has cyclomatic complexity 37 and cognitive complexity 51; 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 stream (cyclomatic 34, cognitive 32) packages/vendo/src/harness-turn.ts:644— stream has cyclomatic complexity 34 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function guardSql (cyclomatic 32, cognitive 45) packages/vendo/src/apps/persistence/app-sql-guard.ts:280— guardSql has cyclomatic complexity 32 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 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 32, cognitive 37) packages/vendo/src/apps/automation/plan.ts:312— (anonymous) has cyclomatic complexity 32 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 applyZodModifier (cyclomatic 32, cognitive 35) packages/vendo/src/actions/sync/static-ts.ts:450— applyZodModifier has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 #checkWithMetadata (cyclomatic 32, cognitive 35) packages/vendo/src/guard/guard.ts:1180— #checkWithMetadata has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ThreadMessage (cyclomatic 32, cognitive 25) packages/vendo/src/ui/chrome/thread/message.tsx:40— ThreadMessage has cyclomatic complexity 32 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 51) packages/vendo/src/actions/runtime/registry.ts:748— (anonymous) has cyclomatic complexity 31 and cognitive complexity 51; 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 VendoSlot (cyclomatic 31, cognitive 34) packages/vendo/src/ui/chrome/vendo-slot.tsx:248— VendoSlot has cyclomatic complexity 31 and cognitive complexity 34; 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 planMcpScaffold (cyclomatic 29, cognitive 34) REDACTED:698— planMcpScaffold has cyclomatic complexity 29 and cognitive complexity 34; 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 ConnectCard (cyclomatic 28, cognitive 25) packages/vendo/src/ui/chrome/connect-card.tsx:74— ConnectCard has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkComponentScreen (cyclomatic 27, cognitive 46) packages/vendo/src/apps/checking/component-screen.ts:623— checkComponentScreen has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 repairJson (cyclomatic 27, cognitive 46) packages/vendo/src/cli/judge/parse.ts:58— repairJson has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 scoreAiJudgments (cyclomatic 27, cognitive 45) corpus/harness/src/ai/score.ts:206— scoreAiJudgments has cyclomatic complexity 27 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 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 27, cognitive 36) packages/vendo/src/knowledge/cloud.test-util.ts:79— (anonymous) has cyclomatic complexity 27 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 assembleScreen (cyclomatic 27, cognitive 36) packages/vendo/src/screen-agent.ts:895— assembleScreen has cyclomatic complexity 27 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 isDefaultSansSpread (cyclomatic 27, cognitive 34) REDACTED:369— isDefaultSansSpread has cyclomatic complexity 27 and cognitive complexity 34; 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 27, cognitive 26) packages/vendo/src/apps/checking/screen-typecheck.ts:211— (anonymous) has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function localConstantJson (cyclomatic 26, cognitive 35) packages/vendo/src/actions/sync/catalog-scan.ts:226— localConstantJson has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 runTurn (cyclomatic 26, cognitive 26) packages/vendo/tests/frozen/turn-frozen.ts:498— runTurn has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 agent (cyclomatic 26, cognitive 25) packages/vendo/src/turn/agent.ts:336— agent has cyclomatic complexity 26 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function sha256Hex (cyclomatic 26, cognitive 23) packages/vendo/src/core/sha256.ts:50— sha256Hex has cyclomatic complexity 26 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/vendo/src/guard/guard.ts · ×1
packages/vendo/src/guard/guard.ts: 2517 lines of code packages/vendo/src/guard/guard.ts:1— packages/vendo/src/guard/guard.ts has 2517 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/vendo/src/ui/chrome/chrome-css.ts · ×1
packages/vendo/src/ui/chrome/chrome-css.ts: 2204 lines of code packages/vendo/src/ui/chrome/chrome-css.ts:1— packages/vendo/src/ui/chrome/chrome-css.ts has 2204 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/vendo/src/core/conformance/store-ops.ts · ×1
packages/vendo/src/core/conformance/store-ops.ts: 2074 lines of code packages/vendo/src/core/conformance/store-ops.ts:1— packages/vendo/src/core/conformance/store-ops.ts has 2074 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: 2014 lines of code REDACTED:1— REDACTED has 2014 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/vendo/src/mcp/door.ts · ×1
packages/vendo/src/mcp/door.ts: 1866 lines of code packages/vendo/src/mcp/door.ts:1— packages/vendo/src/mcp/door.ts has 1866 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/vendo/src/screen-agent.ts · ×1
packages/vendo/src/screen-agent.ts: 1722 lines of code packages/vendo/src/screen-agent.ts:1— packages/vendo/src/screen-agent.ts has 1722 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
genbench/src/run.ts: 1349 lines of code genbench/src/run.ts:1— genbench/src/run.ts has 1349 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/vendo/src/core/apps/kit/specs.ts · ×1
packages/vendo/src/core/apps/kit/specs.ts: 1254 lines of code packages/vendo/src/core/apps/kit/specs.ts:1— packages/vendo/src/core/apps/kit/specs.ts has 1254 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/vendo/src/ui/chrome/vendo-overlay.tsx · ×1
packages/vendo/src/ui/chrome/vendo-overlay.tsx: 1171 lines of code packages/vendo/src/ui/chrome/vendo-overlay.tsx:1— packages/vendo/src/ui/chrome/vendo-overlay.tsx has 1171 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/vendo/src/mcp/oauth/server.ts · ×1
packages/vendo/src/mcp/oauth/server.ts: 1141 lines of code packages/vendo/src/mcp/oauth/server.ts:1— packages/vendo/src/mcp/oauth/server.ts has 1141 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/vendo/src/harnesses/runtime.ts · ×1
packages/vendo/src/harnesses/runtime.ts: 1127 lines of code packages/vendo/src/harnesses/runtime.ts:1— packages/vendo/src/harnesses/runtime.ts has 1127 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/vendo/src/apps/checking/component-screen.ts · ×1
packages/vendo/src/apps/checking/component-screen.ts: 1081 lines of code packages/vendo/src/apps/checking/component-screen.ts:1— packages/vendo/src/apps/checking/component-screen.ts has 1081 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/vendo/src/ui/chrome/thread/parts.tsx · ×1
packages/vendo/src/ui/chrome/thread/parts.tsx: 1077 lines of code packages/vendo/src/ui/chrome/thread/parts.tsx:1— packages/vendo/src/ui/chrome/thread/parts.tsx has 1077 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/vendo/src/harness-turn.ts · ×1
packages/vendo/src/harness-turn.ts: 1061 lines of code packages/vendo/src/harness-turn.ts:1— packages/vendo/src/harness-turn.ts has 1061 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/vendo/src/cli/judge/pass.ts · ×1
packages/vendo/src/cli/judge/pass.ts: 1050 lines of code packages/vendo/src/cli/judge/pass.ts:1— packages/vendo/src/cli/judge/pass.ts has 1050 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/vendo/src/cli/pretty.ts · ×1
packages/vendo/src/cli/pretty.ts: 1044 lines of code packages/vendo/src/cli/pretty.ts:1— packages/vendo/src/cli/pretty.ts has 1044 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
genbench/src/report.ts: 1005 lines of code genbench/src/report.ts:1— genbench/src/report.ts has 1005 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/vendo/src/store/hosted-store.ts · ×1
packages/vendo/src/store/hosted-store.ts: 949 lines of code packages/vendo/src/store/hosted-store.ts:1— packages/vendo/src/store/hosted-store.ts has 949 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/vendo/src/ui/tree/renderer.tsx · ×1
packages/vendo/src/ui/tree/renderer.tsx: 948 lines of code packages/vendo/src/ui/tree/renderer.tsx:1— packages/vendo/src/ui/tree/renderer.tsx has 948 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/vendo/src/store/ops.ts · ×1
packages/vendo/src/store/ops.ts: 936 lines of code packages/vendo/src/store/ops.ts:1— packages/vendo/src/store/ops.ts has 936 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/vendo/src/actions/runtime/registry.ts · ×1
packages/vendo/src/actions/runtime/registry.ts: 922 lines of code packages/vendo/src/actions/runtime/registry.ts:1— packages/vendo/src/actions/runtime/registry.ts has 922 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/vendo/src/cli/sync-flow.ts · ×1
packages/vendo/src/cli/sync-flow.ts: 912 lines of code packages/vendo/src/cli/sync-flow.ts:1— packages/vendo/src/cli/sync-flow.ts has 912 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/vendo/src/core/conformance/memory-store-ops.ts · ×1
packages/vendo/src/core/conformance/memory-store-ops.ts: 900 lines of code packages/vendo/src/core/conformance/memory-store-ops.ts:1— packages/vendo/src/core/conformance/memory-store-ops.ts has 900 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
genbench/src/probe.ts: 875 lines of code genbench/src/probe.ts:1— genbench/src/probe.ts has 875 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/vendo/src/actions/sync/catalog-scan.ts · ×1
packages/vendo/src/actions/sync/catalog-scan.ts: 826 lines of code packages/vendo/src/actions/sync/catalog-scan.ts:1— packages/vendo/src/actions/sync/catalog-scan.ts has 826 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/vendo/src/turn/turn.ts · ×1
packages/vendo/src/turn/turn.ts: 814 lines of code packages/vendo/src/turn/turn.ts:1— packages/vendo/src/turn/turn.ts has 814 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/vendo/src/actions/sync/split/carve.ts · ×1
packages/vendo/src/actions/sync/split/carve.ts: 797 lines of code packages/vendo/src/actions/sync/split/carve.ts:1— packages/vendo/src/actions/sync/split/carve.ts has 797 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/vendo/src/actions/sync/route-scan.ts · ×1
packages/vendo/src/actions/sync/route-scan.ts: 794 lines of code packages/vendo/src/actions/sync/route-scan.ts:1— packages/vendo/src/actions/sync/route-scan.ts has 794 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/vendo/src/core/store-wire.ts · ×1
packages/vendo/src/core/store-wire.ts: 789 lines of code packages/vendo/src/core/store-wire.ts:1— packages/vendo/src/core/store-wire.ts has 789 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/vendo/src/apps/runtime/types.ts · ×1
packages/vendo/src/apps/runtime/types.ts: 784 lines of code packages/vendo/src/apps/runtime/types.ts:1— packages/vendo/src/apps/runtime/types.ts has 784 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/vendo/src/harnesses/vendo/vendo.ts · ×1
packages/vendo/src/harnesses/vendo/vendo.ts: 783 lines of code packages/vendo/src/harnesses/vendo/vendo.ts:1— packages/vendo/src/harnesses/vendo/vendo.ts has 783 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/vendo/src/core/apps/genui/component/vm-program.ts · ×1
packages/vendo/src/core/apps/genui/component/vm-program.ts: 766 lines of code packages/vendo/src/core/apps/genui/component/vm-program.ts:1— packages/vendo/src/core/apps/genui/component/vm-program.ts has 766 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/vendo/src/actions/sync/route-schema.ts · ×1
packages/vendo/src/actions/sync/route-schema.ts: 756 lines of code packages/vendo/src/actions/sync/route-schema.ts:1— packages/vendo/src/actions/sync/route-schema.ts has 756 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/vendo/src/harnesses/claude-code/box.ts · ×1
packages/vendo/src/harnesses/claude-code/box.ts: 749 lines of code packages/vendo/src/harnesses/claude-code/box.ts:1— packages/vendo/src/harnesses/claude-code/box.ts has 749 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/vendo/src/store/routing.ts · ×1
packages/vendo/src/store/routing.ts: 736 lines of code packages/vendo/src/store/routing.ts:1— packages/vendo/src/store/routing.ts has 736 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/vendo/src/apps/checking/screen-typings.ts · ×1
packages/vendo/src/apps/checking/screen-typings.ts: 729 lines of code packages/vendo/src/apps/checking/screen-typings.ts:1— packages/vendo/src/apps/checking/screen-typings.ts has 729 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/vendo/src/harnesses/claude-code/index.ts · ×1
packages/vendo/src/harnesses/claude-code/index.ts: 725 lines of code packages/vendo/src/harnesses/claude-code/index.ts:1— packages/vendo/src/harnesses/claude-code/index.ts has 725 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/vendo/src/ui/kit/data/data-table.tsx · ×1
packages/vendo/src/ui/kit/data/data-table.tsx: 707 lines of code packages/vendo/src/ui/kit/data/data-table.tsx:1— packages/vendo/src/ui/kit/data/data-table.tsx has 707 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/vendo/src/harnesses/vendo/loop.ts · ×1
packages/vendo/src/harnesses/vendo/loop.ts: 706 lines of code packages/vendo/src/harnesses/vendo/loop.ts:1— packages/vendo/src/harnesses/vendo/loop.ts has 706 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/vendo/src/actions/sync/seeds.ts · ×1
packages/vendo/src/actions/sync/seeds.ts: 699 lines of code packages/vendo/src/actions/sync/seeds.ts:1— packages/vendo/src/actions/sync/seeds.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~93 LoC) docs-site/snippets/agent-prompt.jsx— no import path from any entry point (287 application, 42 tooling, 1186 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 (~39 LoC) packages/vendo/src/theme-json-import.docs-check.ts— no import path from any entry point (287 application, 42 tooling, 1186 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 (~36 LoC) packages/vendo/src/server-api-imports.docs-check.ts— no import path from any entry point (287 application, 42 tooling, 1186 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 (~33 LoC) packages/vendo/src/store/workspace-fs.parity.ts— no import path from any entry point (287 application, 42 tooling, 1186 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
Duplicated predicate packages/vendo/src/actions/presets/shared.ts:98— `!/^[A-Za-z0-9_-]+$/.test(value) || value.length % 4 === 1` appears character-identically in 2 files — packages/vendo/src/actions/presets/shared.ts, packages/vendo/src/auth-presets/supabase.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/vendo/src/core/conformance/memory-store-ops.ts:48— `!Array.isArray(parsed) || typeof parsed[0] !== "string" || typeof parsed[1] !== "string"` appears character-identically in 3 files — packages/vendo/src/core/conformance/memory-store-ops.ts, packages/vendo/src/store/fake-console.ts, packages/vendo/src/store/routing.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/vendo/src/actions/sync/route-scan.ts:394— `!argument || !ts.isObjectLiteralExpression(argument)` appears character-identically in 2 files — packages/vendo/src/actions/sync/route-scan.ts, packages/vendo/src/actions/sync/static-ts.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 corpus/harness/src/layers/structural.ts:190— `!entry.name.startsWith(".") && !SKIP_DIRECTORIES.has(entry.name)` appears character-identically in 2 files — corpus/harness/src/layers/structural.ts, packages/vendo/src/cli/theme/walk.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/vendo/src/apps/checking/component-screen.ts:449— `!isMutatingTool(tool) || tool.name === VENDO_APPS_SQL_TOOL` appears character-identically in 2 files — packages/vendo/src/apps/checking/component-screen.ts, packages/vendo/src/apps/checking/screen-typings.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/vendo/src/ui/chrome/thread/index.tsx:206— `!isToolUIPart(part) || part.state !== "approval-requested"` appears character-identically in 2 files — packages/vendo/src/ui/chrome/thread/index.tsx, packages/vendo/src/ui/use-vendo-chat.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/vendo/src/actions/sync/common.ts:273— `!ts.isExportDeclaration(statement) || !statement.moduleSpecifier || !ts.isStringLiteral(statement.moduleSpecifier)` appears character-identically in 2 files — packages/vendo/src/actions/sync/common.ts, packages/vendo/src/actions/sync/static-ts.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 corpus/harness/src/layers/structural.ts:381— `!ts.isImportDeclaration(statement) || !ts.isStringLiteral(statement.moduleSpecifier)` appears character-identically in 8 files — corpus/harness/src/layers/structural.ts, packages/vendo/src/actions/sync/common.ts, packages/vendo/src/actions/sync/route-scan.ts, packages/vendo/src/actions/sync/seeds.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/vendo/src/apps/checking/screen-typings.ts:285— `Array.isArray(schema.allOf) && schema.allOf.length > 0` appears character-identically in 2 files — packages/vendo/src/apps/checking/screen-typings.ts, packages/vendo/src/core/shape.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/vendo/src/core/apps/build-deadlines.ts:43— `Number.isFinite(configured) && configured > 0` appears character-identically in 3 files — packages/vendo/src/core/apps/build-deadlines.ts, packages/vendo/src/knowledge/agent-tools.ts, packages/vendo/src/turn-liveness.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/vendo/src/apps/testing/fake-sandbox.ts:62— `Number.isInteger(port) && port > 0 && port <= 65_535` appears character-identically in 2 files — packages/vendo/src/apps/testing/fake-sandbox.ts, packages/vendo/src/sandbox.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/vendo/src/cli/doctor-deps-checks.ts:19— `aiVersion !== null && aiBelowPeerFloor(aiVersion)` appears character-identically in 2 files — packages/vendo/src/cli/doctor-deps-checks.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate corpus/harness/src/layers/structural.ts:383— `bindings === undefined || !ts.isNamedImports(bindings)` appears character-identically in 2 files — corpus/harness/src/layers/structural.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/vendo/src/cloud-directory.ts:60— `cached !== undefined && Date.now() - cached.at < ttlMs` appears character-identically in 2 files — packages/vendo/src/cloud-directory.ts, packages/vendo/src/compose-discovery.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/vendo/src/ui/chrome/thread/index.tsx:150— `card && typeof card.scrollIntoView === "function"` appears character-identically in 2 files — packages/vendo/src/ui/chrome/thread/index.tsx, packages/vendo/src/ui/chrome/thread/parts.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/vendo/src/actions/sync/split/index.ts:88— `clause === undefined || clause.isTypeOnly` appears character-identically in 2 files — packages/vendo/src/actions/sync/split/index.ts, packages/vendo/src/actions/sync/split/port.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/vendo/src/ui/kit/charts/bar.tsx:115— `clean.length === 0 || seriesIsEmpty(clean, keys)` appears character-identically in 2 files — packages/vendo/src/ui/kit/charts/bar.tsx, packages/vendo/src/ui/kit/charts/line.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/vendo/src/ui/chrome/thread/parts.tsx:600— `code !== "conflict" && code !== "not-found"` appears character-identically in 2 files — packages/vendo/src/ui/chrome/thread/parts.tsx, packages/vendo/src/ui/chrome/vendo-approval.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/vendo/src/cli/banner.ts:178— `colorterm === "truecolor" || colorterm === "24bit"` appears character-identically in 2 files — packages/vendo/src/cli/banner.ts, packages/vendo/src/core/style.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/vendo/src/cli/index.ts:299— `command === undefined || command === "--help" || command === "-h"` appears character-identically in 3 files — packages/vendo/src/cli/index.ts, packages/vendo/src/cli/knowledge/index.ts, packages/vendo/src/cli/mcp/index.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/vendo/src/cli/cloud/index.ts:40— `command === undefined || command === "--help" || command === "-h" || command === "help"` appears character-identically in 2 files — packages/vendo/src/cli/cloud/index.ts, packages/vendo/src/cli/config.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/vendo/src/apps/persistence/placements.ts:86— `data === null || typeof data !== "object"` appears character-identically in 2 files — packages/vendo/src/apps/persistence/placements.ts, packages/vendo/src/apps/persistence/slots.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/vendo/src/actions/sync/catalog.ts:13— `error && typeof error === "object" && "issues" in error` appears character-identically in 2 files — packages/vendo/src/actions/sync/catalog.ts, packages/vendo/src/actions/sync/index.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/vendo/src/actions/connectors/mcp.ts:189— `error instanceof Error && error.name === "AbortError"` appears character-identically in 2 files — packages/vendo/src/actions/connectors/mcp.ts, packages/vendo/src/apps/doors/build-messages.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/vendo/src/cli/cloud/host-components.ts:176— `init?.signal === undefined || init.signal === null` appears character-identically in 2 files — packages/vendo/src/cli/cloud/host-components.ts, packages/vendo/src/cli/cloud/seed-baselines.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.
+ 15 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel packages/vendo/src/compose-actions.ts:73— `packages/vendo/src/compose-actions.ts` reports through `console.*` at line 73 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/vendo/src/compose-discovery.ts:88— `packages/vendo/src/compose-discovery.ts` reports through `console.*` at line 88 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/vendo/src/compose-guard.ts:149— `packages/vendo/src/compose-guard.ts` reports through `console.*` at line 149 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/vendo/src/compose-mcp.ts:105— `packages/vendo/src/compose-mcp.ts` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/vendo/src/compose-store.ts:177— `packages/vendo/src/compose-store.ts` reports through `console.*` at line 177 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/vendo/src/config-keys.ts:182— `packages/vendo/src/config-keys.ts` reports through `console.*` at line 182 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/vendo/src/config-keys.ts:197— `packages/vendo/src/config-keys.ts` reports through `console.*` at line 197 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/vendo/src/screen-agent.ts:629— `packages/vendo/src/screen-agent.ts` reports through `console.*` at line 629 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/vendo/src/screen-agent.ts:637— `packages/vendo/src/screen-agent.ts` reports through `console.*` at line 637 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/vendo/src/surface-menu.ts:22— `packages/vendo/src/surface-menu.ts` reports through `console.*` at line 22 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/vendo/src/wire/apps.ts:117— `packages/vendo/src/wire/apps.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/vendo/src/store/db.ts:171— `packages/vendo/src/store/db.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/vendo/src/store/db.ts:315— `packages/vendo/src/store/db.ts` reports through `console.*` at line 315 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/vendo/src/store/hosted-store.ts:490— `packages/vendo/src/store/hosted-store.ts` reports through `console.*` at line 490 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/vendo/src/store/hosted-store.ts:520— `packages/vendo/src/store/hosted-store.ts` reports through `console.*` at line 520 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/vendo/src/store/secrets.ts:27— `packages/vendo/src/store/secrets.ts` reports through `console.*` at line 27 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/vendo/src/sandbox/edge/lib-source.ts:35— `packages/vendo/src/sandbox/edge/lib-source.ts` reports through `console.*` at line 35 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/vendo/src/harnesses/vendo/vendo.ts:521— `packages/vendo/src/harnesses/vendo/vendo.ts` reports through `console.*` at line 521 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/vendo/src/harnesses/claude-code/local.ts:128— `packages/vendo/src/harnesses/claude-code/local.ts` reports through `console.*` at line 128 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/vendo/src/core/fetch.ts:22— `packages/vendo/src/core/fetch.ts` reports through `console.*` at line 22 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/vendo/src/automations/ingestion-surface.ts:151— `packages/vendo/src/automations/ingestion-surface.ts` reports through `console.*` at line 151 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/vendo/src/auth-presets/auth-js.ts:101— `packages/vendo/src/auth-presets/auth-js.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/vendo/src/auth-presets/clerk.ts:82— `packages/vendo/src/auth-presets/clerk.ts` reports through `console.*` at line 82 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/vendo/src/apps/persistence/app-source.ts:261— `packages/vendo/src/apps/persistence/app-source.ts` reports through `console.*` at line 261 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/vendo/src/apps/generation/render-seam.ts:237— `packages/vendo/src/apps/generation/render-seam.ts` reports through `console.*` at line 237 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Silent fallback default in catch corpus/harness/src/layers/structural.ts:336— `sourceTreeText` 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/vendo/src/core/store-wire.ts:851— `bodySnippet` 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/vendo/src/core/apps/genui/component/boot.ts:428— `bootScreen.pendingMisses` 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/vendo/src/store/hosted-store.ts:170— `hostedStore.postJson.<returned closure>` 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/vendo/src/actions/sync/common.ts:99— `loadAliases` 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/vendo/src/apps/checking/toolchain.ts:206— `esbuildEntry` swallows every exception into `return "esbuild"` — 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/vendo/src/capability/host-collision.ts:44— `hostToolNamesIn` 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/vendo/src/sandbox.ts:325— `cloudSandbox.sendJson` 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/vendo/src/compose-wire.ts:46— `wireDepsFor` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/vendo/src/apps/testing/guard-fixture.ts:35— `inputPreview` swallows every exception into `return "[unserializable input]"` — 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/vendo/src/cli/init-scaffolds.ts:322— `requiredServerActions` 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/vendo/src/cli/init-scaffolds.ts:661— `devPort` swallows every exception into `return 3000` — 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/vendo/src/cli/init-judgment.ts:61— `judgedSummaries` 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/vendo/src/cli/sync-flow.ts:373— `readCatalog` 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/vendo/src/cli/sync-flow.ts:749— `declaredMount` 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/vendo/src/harnesses/claude-code/index.ts:231— `readState` 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/vendo/src/telemetry/scrub.ts:52— `scrubErrorDetail` 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.
Disabled test fixtures/context-e2e/e2e/cache-ledger.spec.ts:37— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test fixtures/context-e2e/e2e/compaction-recall.spec.ts:51— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test fixtures/context-e2e/e2e/giant-first.spec.ts:50— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test fixtures/context-e2e/e2e/overflow-recovery.spec.ts:29— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test fixtures/context-e2e/e2e/parallel-hires.spec.ts:19— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/actions/connectors/composio.live.test.ts:87— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/apps/checking/review-failure-protocol.test.ts:60— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/audit-superset.e2e.test.ts:524— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/audit-superset.e2e.test.ts:537— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/core/apps/genui/component/screen-errors.test.ts:314— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/core/conformance/memory-store-ops.test.ts:57— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/guard/live/judge.live.test.ts:46— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/store/durability.drill.test.ts:36— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/store/ops.conformance.test.ts:40— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/vendo/tests/store/postgres-gate.test.ts:10— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Fat interface: IFileSystem (20 required operations) packages/vendo/src/core/filesystem.ts:78— `IFileSystem` declares 20 required operations: `readFile`, `readFileBuffer`, `writeFile`, `appendFile`, `exists`, `stat`, `mkdir`, `readdir`, `rm`, `cp`, `mv`, `resolvePath`, `getAllPaths`, `chmod`, `symlink`, `link`, `readlink`, `lstat`, `realpath`, `utimes`. 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: AppsRuntime (29 required operations) packages/vendo/src/apps/runtime/types.ts:398— `AppsRuntime` declares 29 required operations: `create`, `authoredScreen`, `refusedScreen`, `commitSource`, `floor`, `takeReplaySource`, `toolShapeBrief`, `get`, `list`, `delete`, `fork`, `seen`, `place`, `unplace`, `placements`, `edit`, `remember`, `history`, `open`, `bundleDocument`, `call`, `exportApp`, `importApp`, `share`, `publish`, `agentTools`, `agentToolRisk`, `validate`, `schedule`. 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: AppsRuntimeContext (26 required operations) packages/vendo/src/apps/runtime/runtime-context.ts:53— `AppsRuntimeContext` declares 26 required operations: `updateAppDocument`, `holds`, `owned`, `requireOwned`, `grantedRecords`, `reportGuard`, `reportLifecycle`, `rungFor`, `failedEdit`, `persistEdit`, `reportDocumentEdit`, `discardVersion`, `pruneHistory`, `takeEditVersion`, `takeReplaySource`, `assembleEdit`, `generationToolContext`, `requireSlot`, `claimSlot`, `markUnbuilt`, `beginBuild`, `buildingNow`, `buildingFor`, `settleBuild`, `entryFor`, `runtime`. 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: VendoComposition (22 required operations) packages/vendo/src/compose-context.ts:112— `VendoComposition` declares 22 required operations: `resolvePrincipal`, `sweepNow`, `reportConfig`, `readSurfaceFile`, `memoizeOnce`, `startBackgroundSweep`, `startDevAutomationsTicker`, `enrolForCloudTicks`, `ready`, `themeProvider`, `briefing`, `hostSemanticsProvider`, `missSurface`, `doorBase`, `agentMenu`, `subjectHasToolkit`, `connectedToolkitsFor`, `serviceToolOwner`, `serviceToolRisk`, `channelInboundSecret`, `runSweep`, `bootReconcile`. 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.
Deprecated: glob REDACTED:6073— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6078— glob 11.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: prebuild-install REDACTED:7572— prebuild-install 7.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "No longer maintained. Please contact the author of the relevant native addon; alternatives are available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: recharts REDACTED:7862— recharts 2.15.4 is resolved in REDACTED and 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". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
redundant comment fixtures/integration/tests/chat-generates-app.e2e.test.ts:89— "Wire GET /apps lists it for ADA." repeats the code it sits on: 4 of its 5 words (wire, apps, lists, ada) are already in `const adaList = (await (await stack.wireFetch("/apps", {}, ADA)).json()) as Array<{ id: string }>;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/vendo/src/core/conformance/memory-store-ops.ts:88— "records: Map<collection, Map<id, record>>" repeats the code it sits on: 4 of its 5 words (records, map, collection, record) are already in `const collections = new Map<string, Map<string, VendoRecord & { seq: number }>>();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/vendo/tests/actions/sync/server-actions.test.ts:76— "Default export + FormData parameter." repeats the code it sits on: 4 of its 5 words (default, export, form, data) are already in `await writeFile(root, "src/actions/report.ts", ``. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/vendo/tests/guard/security/breakers.test.ts:50— "The breaker is tripped for writes…" repeats the code it sits on: 3 of its 3 words (breaker, tripped, writes) are already in `await expect(guard.check(call(write.name, {}, "w_tripped"), write, run)).resolves.toMatchObject({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Mock-dominated test: renders a tagged open-in-product result exactly once with the %s ordering packages/vendo/tests/ui/mcp-shim-core.test.ts:132— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: renders the invalid-result notice for non-payload structured content packages/vendo/tests/ui/mcp-shim-core.test.ts:158— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies packages/vendo/src/actions/presets/away-token.ts:86— 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.
No ADRs found packages/vendoai/package.json:30— 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/`. ADRs are expected here because `packages/vendoai/package.json` makes this repository a deployable product (line 30).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion REDACTED:1— `packages/vendo` (154906 LoC, 1758 module-visible types across 70 directories) overshoots its size bounds. 1 of 6 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 6.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
DM9 · Scattered domain decisions· Rule about [bundle, ui] decided in 2 places · ×1
Rule about [bundle, ui] decided in 2 places — packages.vendo.src.core.app-document.AppDocument's [bundle, ui] are judged in packages.vendo.src.apps.persistence.open, packages.vendo.src.core.apps.app-validation — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions· Rule about [expiresAt, revokedAt] decided in 2 places · ×1
Rule about [expiresAt, revokedAt] decided in 2 places — packages.vendo.src.core.grants.PermissionGrant's [expiresAt, revokedAt] are judged in packages.vendo.src.apps.testing.guard-fixture, packages.vendo.src.sync-impact — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions· Rule about [admin, org] decided in 2 places · ×1
Rule about [admin, org] decided in 2 places — packages.vendo.src.core.run-context.Membership's [admin, org] are judged in packages.vendo.src.core.conformance.memory-app-access, packages.vendo.tests.apps.app-access-fixture — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
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 1/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `corpus/hosts/express-host`, `fixtures/automations-e2e`, `fixtures/host-app`, `fixtures/install-seam`, `fixtures/install-seam/app` and 4 more.
No SAST REDACTED:5— 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 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate .github/workflows/release.yml:25— The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Unused export 'CardByline' packages/vendo/src/ui/chrome/card-shell.tsx:145— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration '_NoMissingKeys' · ×1
Unused module-local declaration '_NoMissingKeys' packages/vendo/src/config-keys.ts:87— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '_NoKnobLeftBehind' · ×1
Unused module-local declaration '_NoKnobLeftBehind' packages/vendo/src/harnesses/vendo/vendo.ts:134— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene· Type-only dependency '@standard-schema/spec' in production deps · ×1
Type-only dependency '@standard-schema/spec' in production deps packages/vendo/src/core/harness.ts:16— Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene· Type-only dependency 'unpdf' in production deps · ×1
Type-only dependency 'unpdf' in production deps packages/vendo/src/harnesses/vendo/shell/parsers/pdftotext.ts:18— Every import is type-only — move it to devDependencies.
No app-layer HTTPS enforcement detected packages/vendo/box/harness.mjs:254— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
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 6/11 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.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 28/29 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~2.2 `!` null assertions per 1k TypeScript source lines — 378 assertion(s) across the 175182 source line(s) of the 810 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/vendo/src/cli/pretty.ts (26), packages/vendo/src/core/conformance/store-ops.ts (26), packages/vendo/src/apps/persistence/unified-diff.ts (16). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated (npm): @ai-sdk/anthropic — @ai-sdk/anthropic is pinned at 3.0.12; registry.npmjs.org publishes 4.0.105 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): @ai-sdk/openai — @ai-sdk/openai is pinned at 3.0.9; registry.npmjs.org publishes 4.0.118 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): @ai-sdk/react — @ai-sdk/react is pinned at 3.0.230; registry.npmjs.org publishes 4.0.177 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): @anthropic-ai/claude-agent-sdk — @anthropic-ai/claude-agent-sdk is pinned at 0.3.214; registry.npmjs.org publishes 0.3.326 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): @base-ui/react — @base-ui/react is pinned at 1.7.0; registry.npmjs.org publishes 1.9.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): @electric-sql/pglite — @electric-sql/pglite is pinned at 0.5.4; registry.npmjs.org publishes 0.5.16 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): @mastra/ai-sdk — @mastra/ai-sdk is pinned at 1.6.2; registry.npmjs.org publishes 1.12.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mastra/core — @mastra/core is pinned at 1.51.0; registry.npmjs.org publishes 1.83.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): @mastra/duckdb — @mastra/duckdb is pinned at 1.5.1; registry.npmjs.org publishes 1.19.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): @mastra/libsql — @mastra/libsql is pinned at 1.16.0; registry.npmjs.org publishes 1.30.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): @mastra/loggers — @mastra/loggers is pinned at 1.2.0; registry.npmjs.org publishes 1.3.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): @mastra/memory — @mastra/memory is pinned at 1.26.2; registry.npmjs.org publishes 1.41.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): @mastra/observability — @mastra/observability is pinned at 1.16.1; registry.npmjs.org publishes 1.24.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): @modelcontextprotocol/ext-apps — @modelcontextprotocol/ext-apps is pinned at 1.7.4; registry.npmjs.org publishes 2.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @modelcontextprotocol/sdk — @modelcontextprotocol/sdk is pinned at 1.29.0; registry.npmjs.org publishes 1.32.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @radix-ui/react-dropdown-menu — @radix-ui/react-dropdown-menu is pinned at 2.1.20; 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-switch — @radix-ui/react-switch is pinned at 1.3.3; 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): @radix-ui/react-tabs — @radix-ui/react-tabs is pinned at 1.1.17; 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-tooltip — @radix-ui/react-tooltip is pinned at 1.2.12; 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-table — @tanstack/react-table is pinned at 8.21.3; registry.npmjs.org publishes 9.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): acorn — acorn is pinned at 8.17.0; registry.npmjs.org publishes 8.19.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): ai — ai is pinned at 6.0.230; registry.npmjs.org publishes 7.0.173 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): croner — croner is pinned at 9.1.0; registry.npmjs.org publishes 11.0.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): e2b — e2b is pinned at 2.32.0; registry.npmjs.org publishes 2.64.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): express — express is pinned at 5.2.1; registry.npmjs.org publishes 5.3.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.
Skipped (documented): (unnamed test) packages/vendo/tests/store/postgres-entry.test.ts:28— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/vendo/tests/store/schema.test.ts:261— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vendo/tests/store/thread-messages.batch.test.ts:196— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): SIMULTANEOUS (Promise.all over two whole tool calls): the second write is blocked packages/vendo/tests/guard/security/preview-reuse-round2.test.ts:71— Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
Skipped (documented): takes a directory, then throws — the removal must not depend on the test passing corpus/harness/tests/temp-dir.test.ts:24— Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
Skipped (documented): removes a directory taken by a fixture that then throws mid-setup corpus/harness/tests/temp-dir.test.ts:35— Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
doc comments repeat the names packages/vendo/src/ui/kit/charts/line.tsx:51— 0 of 13 documented parameters and 1 of 8834 summaries in `@vendoai/vendo` only repeat the member or parameter name (e.g. "One or more value series." for `series`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 66 file(s) — `packages/vendo/src/actions/formats.ts`, `packages/vendo/src/actions/openapi-document.ts`, `packages/vendo/src/actions/sync/route-scan.ts`, `packages/vendo/src/actions/sync/schema-patch.ts`, `packages/vendo/src/actions/sync/server-actions.ts`, … (+61 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 01a1e917-44c8-77f1-8a17-5042566cae77 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 63 · Warnings: 1648 · Recommendations: 163 · Info: 51 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 10:39 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.