Public report of DioxusLabs/dioxus, published 25 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 25 October 2026, 22:59 UTC · Survey ID cd_14880fd8a1804cd7a91d7cf5008bc603
DioxusLabs/dioxus
Measured 25 October 2026, 22:54 UTC, at code version d358d58
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 153,189 lines of product code in 81 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Code Health, 49
Findings by how serious they are
93 critical731 serious77 minor
12 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
25 October 2026, 22:54 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
79of 79 dimensions measured by tools.
863of 901 findings point to an exact file and line, so you can open each one in the code. The other 38 concern the repository as a whole, such as missing documentation.
79dimensions across 7 lenses, read from 153,189 lines of product code in 81 projects.
DioxusLabs/dioxus falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 57 out of 100 and is rated Adequate, and 81 of its 93 critical findings are security problems.
Code Health, at 49, is the weakest lens and counts most in the score. The best first step is writing log messages as searchable templates, worth about 4 points. Adding type checking comes next, worth about 3 points. Raising Code Health to 67 would lift the score to about 63.
Sixty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen known security holes in the packages the code depends on can be used by attackers, and three parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, updating the vulnerable packages and having someone learn the forgotten files would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first. The six pages that don't say their language need their language set.
The product code is 153,189 lines, about €180,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.
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/assets/calculator.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/assets/todomvc.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement examples/assets/weatherapp.css
Visual & motion safety · Animation without a prefers-reduced-motion guard examples/assets/radio.css
Visual & motion safety · Animation without a prefers-reduced-motion guard examples/assets/visible.css
Visual & motion safety · Animation without a prefers-reduced-motion guard examples/01-app-demos/hackernews/assets/hackernews.css
Visual & motion safety · Animation without a prefers-reduced-motion guard examples/01-app-demos/ecommerce-site/public/loading.css
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 50 findings
These 50 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one.
Outbound HTTP resilience · Outbound HTTP without resilience packages/cli/src/bundler/tools.rs
Outbound HTTP resilience · Outbound HTTP without resilience packages/cli/src/cli/create.rs
Outbound HTTP resilience · Outbound HTTP without resilience packages/cli/src/esbuild.rs
Outbound HTTP resilience · Outbound HTTP without resilience packages/cli/src/tailwind.rs
Outbound HTTP resilience · Outbound HTTP without resilience packages/cli/src/wasm_bindgen.rs
Outbound HTTP resilience · Outbound HTTP without resilience packages/cli/src/wasm_opt.rs
Rebuild cost: about €180,000 · Estimate
Cost to rebuild
€61,000 to €310,000, for 1,021 to 3,239 hours of work, about 1.3 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 57. 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: 153,189 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
Migrate the remaining .js/.jsx files to TypeScript.
Raises the score by about 3 points · Medium effort · Type Safety
3
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 `?`).
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.3 person-years of work. Its weakest lens is Code Health, at 49 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Interpolated log message defeats structured logging. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph 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.
584 modules, with 1282 dependencies between them. 14 loops run through 93 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 544 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.
dioxus_cli.serve.runner uses dioxus_cli.build.request, so a change to dioxus_cli.build.request can break dioxus_cli.serve.runner, while a change to dioxus_cli.serve.runner can't break dioxus_cli.build.request.
Position
Below the diagonal: dioxus_cli.serve.runner uses a module listed above it, which is the healthy direction.
8→13 dioxus_html.events uses dioxus_core.eventspart of a loop✕
Connections
1 pair of types, where a type in dioxus_html.events uses a type in dioxus_core.events.
dioxus_html.events uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_html.events, while a change to dioxus_html.events can't break dioxus_core.events.
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.
8→26 dioxus_html.events uses dioxus_core.nodespart of a loop✕
Connections
1 pair of types, where a type in dioxus_html.events uses a type in dioxus_core.nodes.
dioxus_html.events uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_html.events, while a change to dioxus_html.events can't break dioxus_core.nodes.
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.
dioxus_rsx.template_body uses dioxus_cli.check.metadata, so a change to dioxus_cli.check.metadata can break dioxus_rsx.template_body, while a change to dioxus_rsx.template_body can't break dioxus_cli.check.metadata.
Position
Below the diagonal: dioxus_rsx.template_body uses a module listed above it, which is the healthy direction.
9→11 dioxus_rsx.template_body uses dioxus_rsx.elementpart of a loop✕
Connections
4 pairs of types, where a type in dioxus_rsx.template_body uses a type in dioxus_rsx.element.
dioxus_rsx.template_body uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_rsx.template_body, while a change to dioxus_rsx.template_body can't break dioxus_rsx.element.
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.
9→26 dioxus_rsx.template_body uses dioxus_core.nodespart of a loop✕
Connections
3 pairs of types, where a type in dioxus_rsx.template_body uses a type in dioxus_core.nodes.
dioxus_rsx.template_body uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_rsx.template_body, while a change to dioxus_rsx.template_body can't break dioxus_core.nodes.
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.
dioxus_rsx.element uses dioxus_cli.check.metadata, so a change to dioxus_cli.check.metadata can break dioxus_rsx.element, while a change to dioxus_rsx.element can't break dioxus_cli.check.metadata.
Position
Below the diagonal: dioxus_rsx.element uses a module listed above it, which is the healthy direction.
dioxus_rsx.element uses dioxus_rsx.template_body, so a change to dioxus_rsx.template_body can break dioxus_rsx.element, while a change to dioxus_rsx.element can't break dioxus_rsx.template_body.
Position
Below the diagonal: dioxus_rsx.element uses a module listed above it, which is the healthy direction.
11→26 dioxus_rsx.element uses dioxus_core.nodespart of a loop✕
Connections
6 pairs of types, where a type in dioxus_rsx.element uses a type in dioxus_core.nodes.
dioxus_rsx.element uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_rsx.element, while a change to dioxus_rsx.element can't break dioxus_core.nodes.
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.
dioxus_core.events uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_core.events, while a change to dioxus_core.events can't break dioxus_html.events.
Position
Below the diagonal: dioxus_core.events uses a module listed above it, which is the healthy direction.
dioxus_core.events uses generational_box, so a change to generational_box can break dioxus_core.events, while a change to dioxus_core.events can't break generational_box.
Position
Below the diagonal: dioxus_core.events uses a module listed above it, which is the healthy direction.
13→19 dioxus_core.events uses dioxus_core.scopespart of a loop✕
Connections
2 pairs of types, where a type in dioxus_core.events uses a type in dioxus_core.scopes.
dioxus_core.events uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.events, while a change to dioxus_core.events can't break dioxus_core.scopes.
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.
13→26 dioxus_core.events uses dioxus_core.nodespart of a loop✕
Connections
2 pairs of types, where a type in dioxus_core.events uses a type in dioxus_core.nodes.
dioxus_core.events uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_core.events, while a change to dioxus_core.events can't break dioxus_core.nodes.
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.
dioxus_core.scope_context uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_core.scope_context, while a change to dioxus_core.scope_context can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_core.scope_context uses a module listed above it, which is the healthy direction.
dioxus_core.scope_context uses generational_box, so a change to generational_box can break dioxus_core.scope_context, while a change to dioxus_core.scope_context can't break generational_box.
Position
Below the diagonal: dioxus_core.scope_context uses a module listed above it, which is the healthy direction.
14→15 dioxus_core.scope_context uses dioxus_core.runtimepart of a loop✕
Connections
1 pair of types, where a type in dioxus_core.scope_context uses a type in dioxus_core.runtime.
dioxus_core.scope_context uses dioxus_core.runtime, so a change to dioxus_core.runtime can break dioxus_core.scope_context, while a change to dioxus_core.scope_context can't break dioxus_core.runtime.
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.
14→19 dioxus_core.scope_context uses dioxus_core.scopespart of a loop✕
Connections
1 pair of types, where a type in dioxus_core.scope_context uses a type in dioxus_core.scopes.
dioxus_core.scope_context uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.scope_context, while a change to dioxus_core.scope_context can't break dioxus_core.scopes.
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.
dioxus_core.runtime uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_core.runtime, while a change to dioxus_core.runtime can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_core.runtime uses a module listed above it, which is the healthy direction.
dioxus_core.runtime uses generational_box, so a change to generational_box can break dioxus_core.runtime, while a change to dioxus_core.runtime can't break generational_box.
Position
Below the diagonal: dioxus_core.runtime uses a module listed above it, which is the healthy direction.
dioxus_core.runtime uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_core.runtime, while a change to dioxus_core.runtime can't break dioxus_core.events.
Position
Below the diagonal: dioxus_core.runtime uses a module listed above it, which is the healthy direction.
dioxus_core.runtime uses dioxus_core.scope_context, so a change to dioxus_core.scope_context can break dioxus_core.runtime, while a change to dioxus_core.runtime can't break dioxus_core.scope_context.
Position
Below the diagonal: dioxus_core.runtime uses a module listed above it, which is the healthy direction.
15→19 dioxus_core.runtime uses dioxus_core.scopespart of a loop✕
Connections
1 pair of types, where a type in dioxus_core.runtime uses a type in dioxus_core.scopes.
dioxus_core.runtime uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.runtime, while a change to dioxus_core.runtime can't break dioxus_core.scopes.
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.
15→26 dioxus_core.runtime uses dioxus_core.nodespart of a loop✕
Connections
1 pair of types, where a type in dioxus_core.runtime uses a type in dioxus_core.nodes.
dioxus_core.runtime uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_core.runtime, while a change to dioxus_core.runtime can't break dioxus_core.nodes.
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.
dioxus_web.events uses dioxus_document.document, so a change to dioxus_document.document can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_document.document.
Position
Below the diagonal: dioxus_web.events uses a module listed above it, which is the healthy direction.
dioxus_web.events uses dioxus_html.file_data, so a change to dioxus_html.file_data can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_html.file_data.
Position
Below the diagonal: dioxus_web.events uses a module listed above it, which is the healthy direction.
dioxus_web.events uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_html.events.
Position
Below the diagonal: dioxus_web.events uses a module listed above it, which is the healthy direction.
dioxus_web.events uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_rsx.element.
Position
Below the diagonal: dioxus_web.events uses a module listed above it, which is the healthy direction.
dioxus_web.events uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_core.events.
Position
Below the diagonal: dioxus_web.events uses a module listed above it, which is the healthy direction.
16→18 dioxus_web.events uses dioxus_html.events.mousepart of a loop✕
Connections
1 pair of types, where a type in dioxus_web.events uses a type in dioxus_html.events.mouse.
dioxus_web.events uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_html.events.mouse.
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.
16→20 dioxus_web.events uses dioxus_html.events.dragpart of a loop✕
Connections
1 pair of types, where a type in dioxus_web.events uses a type in dioxus_html.events.drag.
dioxus_web.events uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_web.events, while a change to dioxus_web.events can't break dioxus_html.events.drag.
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.
dioxus_core.reactive_context uses wasm_used, so a change to wasm_used can break dioxus_core.reactive_context, while a change to dioxus_core.reactive_context can't break wasm_used.
Position
Below the diagonal: dioxus_core.reactive_context uses a module listed above it, which is the healthy direction.
dioxus_core.reactive_context uses generational_box, so a change to generational_box can break dioxus_core.reactive_context, while a change to dioxus_core.reactive_context can't break generational_box.
Position
Below the diagonal: dioxus_core.reactive_context uses a module listed above it, which is the healthy direction.
dioxus_core.reactive_context uses dioxus_core.scope_context, so a change to dioxus_core.scope_context can break dioxus_core.reactive_context, while a change to dioxus_core.reactive_context can't break dioxus_core.scope_context.
Position
Below the diagonal: dioxus_core.reactive_context uses a module listed above it, which is the healthy direction.
dioxus_core.reactive_context uses dioxus_core.runtime, so a change to dioxus_core.runtime can break dioxus_core.reactive_context, while a change to dioxus_core.reactive_context can't break dioxus_core.runtime.
Position
Below the diagonal: dioxus_core.reactive_context uses a module listed above it, which is the healthy direction.
17→19 dioxus_core.reactive_context uses dioxus_core.scopespart of a loop✕
Connections
2 pairs of types, where a type in dioxus_core.reactive_context uses a type in dioxus_core.scopes.
dioxus_core.reactive_context uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.reactive_context, while a change to dioxus_core.reactive_context can't break dioxus_core.scopes.
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.
dioxus_html.events.mouse uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_html.events.mouse, while a change to dioxus_html.events.mouse can't break dioxus_html.events.
Position
Below the diagonal: dioxus_html.events.mouse uses a module listed above it, which is the healthy direction.
dioxus_html.events.mouse uses dioxus_web.events, so a change to dioxus_web.events can break dioxus_html.events.mouse, while a change to dioxus_html.events.mouse can't break dioxus_web.events.
Position
Below the diagonal: dioxus_html.events.mouse uses a module listed above it, which is the healthy direction.
dioxus_core.scopes uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_core.scopes, while a change to dioxus_core.scopes can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_core.scopes uses a module listed above it, which is the healthy direction.
dioxus_core.scopes uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_core.scopes, while a change to dioxus_core.scopes can't break dioxus_rsx.element.
Position
Below the diagonal: dioxus_core.scopes uses a module listed above it, which is the healthy direction.
dioxus_core.scopes uses dioxus_core.runtime, so a change to dioxus_core.runtime can break dioxus_core.scopes, while a change to dioxus_core.scopes can't break dioxus_core.runtime.
Position
Below the diagonal: dioxus_core.scopes uses a module listed above it, which is the healthy direction.
dioxus_core.scopes uses dioxus_core.reactive_context, so a change to dioxus_core.reactive_context can break dioxus_core.scopes, while a change to dioxus_core.scopes can't break dioxus_core.reactive_context.
Position
Below the diagonal: dioxus_core.scopes uses a module listed above it, which is the healthy direction.
19→26 dioxus_core.scopes uses dioxus_core.nodespart of a loop✕
Connections
5 pairs of types, where a type in dioxus_core.scopes uses a type in dioxus_core.nodes.
dioxus_core.scopes uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_core.scopes, while a change to dioxus_core.scopes can't break dioxus_core.nodes.
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.
dioxus_html.events.drag uses dioxus_html.file_data, so a change to dioxus_html.file_data can break dioxus_html.events.drag, while a change to dioxus_html.events.drag can't break dioxus_html.file_data.
Position
Below the diagonal: dioxus_html.events.drag uses a module listed above it, which is the healthy direction.
dioxus_html.events.drag uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_html.events.drag, while a change to dioxus_html.events.drag can't break dioxus_html.events.
Position
Below the diagonal: dioxus_html.events.drag uses a module listed above it, which is the healthy direction.
dioxus_html.events.drag uses dioxus_web.events, so a change to dioxus_web.events can break dioxus_html.events.drag, while a change to dioxus_html.events.drag can't break dioxus_web.events.
Position
Below the diagonal: dioxus_html.events.drag uses a module listed above it, which is the healthy direction.
dioxus_html.events.drag uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_html.events.drag, while a change to dioxus_html.events.drag can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_html.events.drag uses a module listed above it, which is the healthy direction.
dioxus_signals.read uses dioxus_core.reactive_context, so a change to dioxus_core.reactive_context can break dioxus_signals.read, while a change to dioxus_signals.read can't break dioxus_core.reactive_context.
Position
Below the diagonal: dioxus_signals.read uses a module listed above it, which is the healthy direction.
21→40 dioxus_signals.read uses dioxus_signals.boxedpart of a loop✕
Connections
1 pair of types, where a type in dioxus_signals.read uses a type in dioxus_signals.boxed.
dioxus_signals.read uses dioxus_signals.boxed, so a change to dioxus_signals.boxed can break dioxus_signals.read, while a change to dioxus_signals.read can't break dioxus_signals.boxed.
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.
dioxus_core.virtual_dom uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_core.virtual_dom, while a change to dioxus_core.virtual_dom can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_core.virtual_dom uses a module listed above it, which is the healthy direction.
dioxus_core.virtual_dom uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_core.virtual_dom, while a change to dioxus_core.virtual_dom can't break dioxus_rsx.element.
Position
Below the diagonal: dioxus_core.virtual_dom uses a module listed above it, which is the healthy direction.
dioxus_core.virtual_dom uses dioxus_core.scope_context, so a change to dioxus_core.scope_context can break dioxus_core.virtual_dom, while a change to dioxus_core.virtual_dom can't break dioxus_core.scope_context.
Position
Below the diagonal: dioxus_core.virtual_dom uses a module listed above it, which is the healthy direction.
dioxus_core.virtual_dom uses dioxus_core.runtime, so a change to dioxus_core.runtime can break dioxus_core.virtual_dom, while a change to dioxus_core.virtual_dom can't break dioxus_core.runtime.
Position
Below the diagonal: dioxus_core.virtual_dom uses a module listed above it, which is the healthy direction.
dioxus_core.virtual_dom uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.virtual_dom, while a change to dioxus_core.virtual_dom can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_core.virtual_dom uses a module listed above it, which is the healthy direction.
22→26 dioxus_core.virtual_dom uses dioxus_core.nodespart of a loop✕
Connections
2 pairs of types, where a type in dioxus_core.virtual_dom uses a type in dioxus_core.nodes.
dioxus_core.virtual_dom uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_core.virtual_dom, while a change to dioxus_core.virtual_dom can't break dioxus_core.nodes.
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.
dioxus_desktop.file_upload uses dioxus_html.file_data, so a change to dioxus_html.file_data can break dioxus_desktop.file_upload, while a change to dioxus_desktop.file_upload can't break dioxus_html.file_data.
Position
Below the diagonal: dioxus_desktop.file_upload uses a module listed above it, which is the healthy direction.
dioxus_desktop.file_upload uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_desktop.file_upload, while a change to dioxus_desktop.file_upload can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_desktop.file_upload uses a module listed above it, which is the healthy direction.
dioxus_desktop.file_upload uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_desktop.file_upload, while a change to dioxus_desktop.file_upload can't break dioxus_html.events.drag.
Position
Below the diagonal: dioxus_desktop.file_upload uses a module listed above it, which is the healthy direction.
dioxus_html.events.generated uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_html.events.generated, while a change to dioxus_html.events.generated can't break dioxus_html.events.
Position
Below the diagonal: dioxus_html.events.generated uses a module listed above it, which is the healthy direction.
dioxus_html.events.generated uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_html.events.generated, while a change to dioxus_html.events.generated can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_html.events.generated uses a module listed above it, which is the healthy direction.
dioxus_html.events.generated uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_html.events.generated, while a change to dioxus_html.events.generated can't break dioxus_html.events.drag.
Position
Below the diagonal: dioxus_html.events.generated uses a module listed above it, which is the healthy direction.
dioxus_signals.write uses dioxus_signals.read, so a change to dioxus_signals.read can break dioxus_signals.write, while a change to dioxus_signals.write can't break dioxus_signals.read.
Position
Below the diagonal: dioxus_signals.write uses a module listed above it, which is the healthy direction.
25→40 dioxus_signals.write uses dioxus_signals.boxedpart of a loop✕
Connections
1 pair of types, where a type in dioxus_signals.write uses a type in dioxus_signals.boxed.
dioxus_signals.write uses dioxus_signals.boxed, so a change to dioxus_signals.boxed can break dioxus_signals.write, while a change to dioxus_signals.write can't break dioxus_signals.boxed.
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.
dioxus_core.nodes uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_core.nodes, while a change to dioxus_core.nodes can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_core.nodes uses a module listed above it, which is the healthy direction.
dioxus_core.nodes uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_core.nodes, while a change to dioxus_core.nodes can't break dioxus_rsx.element.
Position
Below the diagonal: dioxus_core.nodes uses a module listed above it, which is the healthy direction.
dioxus_core.nodes uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.nodes, while a change to dioxus_core.nodes can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_core.nodes uses a module listed above it, which is the healthy direction.
dioxus_core.nodes uses dioxus_core.virtual_dom, so a change to dioxus_core.virtual_dom can break dioxus_core.nodes, while a change to dioxus_core.nodes can't break dioxus_core.virtual_dom.
Position
Below the diagonal: dioxus_core.nodes uses a module listed above it, which is the healthy direction.
dioxus_desktop.desktop_state uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_desktop.desktop_state, while a change to dioxus_desktop.desktop_state can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_desktop.desktop_state uses a module listed above it, which is the healthy direction.
dioxus_desktop.desktop_state uses dioxus_desktop.file_upload, so a change to dioxus_desktop.file_upload can break dioxus_desktop.desktop_state, while a change to dioxus_desktop.desktop_state can't break dioxus_desktop.file_upload.
Position
Below the diagonal: dioxus_desktop.desktop_state uses a module listed above it, which is the healthy direction.
dioxus_desktop.events uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_desktop.events, while a change to dioxus_desktop.events can't break dioxus_html.events.
Position
Below the diagonal: dioxus_desktop.events uses a module listed above it, which is the healthy direction.
dioxus_desktop.events uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_desktop.events, while a change to dioxus_desktop.events can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_desktop.events uses a module listed above it, which is the healthy direction.
dioxus_desktop.events uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_desktop.events, while a change to dioxus_desktop.events can't break dioxus_html.events.drag.
Position
Below the diagonal: dioxus_desktop.events uses a module listed above it, which is the healthy direction.
dioxus_desktop.events uses dioxus_html.events.generated, so a change to dioxus_html.events.generated can break dioxus_desktop.events, while a change to dioxus_desktop.events can't break dioxus_html.events.generated.
Position
Below the diagonal: dioxus_desktop.events uses a module listed above it, which is the healthy direction.
dioxus_html.transit uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_html.transit, while a change to dioxus_html.transit can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_html.transit uses a module listed above it, which is the healthy direction.
dioxus_html.transit uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_html.transit, while a change to dioxus_html.transit can't break dioxus_html.events.
Position
Below the diagonal: dioxus_html.transit uses a module listed above it, which is the healthy direction.
dioxus_html.transit uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_html.transit, while a change to dioxus_html.transit can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_html.transit uses a module listed above it, which is the healthy direction.
dioxus_html.transit uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_html.transit, while a change to dioxus_html.transit can't break dioxus_html.events.drag.
Position
Below the diagonal: dioxus_html.transit uses a module listed above it, which is the healthy direction.
dioxus_html.transit uses dioxus_html.events.generated, so a change to dioxus_html.events.generated can break dioxus_html.transit, while a change to dioxus_html.transit can't break dioxus_html.events.generated.
Position
Below the diagonal: dioxus_html.transit uses a module listed above it, which is the healthy direction.
dioxus_liveview.events uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_liveview.events, while a change to dioxus_liveview.events can't break dioxus_html.events.
Position
Below the diagonal: dioxus_liveview.events uses a module listed above it, which is the healthy direction.
dioxus_liveview.events uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_liveview.events, while a change to dioxus_liveview.events can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_liveview.events uses a module listed above it, which is the healthy direction.
dioxus_liveview.events uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_liveview.events, while a change to dioxus_liveview.events can't break dioxus_html.events.drag.
Position
Below the diagonal: dioxus_liveview.events uses a module listed above it, which is the healthy direction.
dioxus_liveview.events uses dioxus_html.events.generated, so a change to dioxus_html.events.generated can break dioxus_liveview.events, while a change to dioxus_liveview.events can't break dioxus_html.events.generated.
Position
Below the diagonal: dioxus_liveview.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses dioxus_html.file_data, so a change to dioxus_html.file_data can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break dioxus_html.file_data.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses dioxus_html.events, so a change to dioxus_html.events can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break dioxus_html.events.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses wasm_used, so a change to wasm_used can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break wasm_used.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses dioxus_html.events.mouse, so a change to dioxus_html.events.mouse can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break dioxus_html.events.mouse.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses dioxus_html.events.drag, so a change to dioxus_html.events.drag can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break dioxus_html.events.drag.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses dioxus_html.events.generated, so a change to dioxus_html.events.generated can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break dioxus_html.events.generated.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_signals.copy_value uses wasm_used, so a change to wasm_used can break dioxus_signals.copy_value, while a change to dioxus_signals.copy_value can't break wasm_used.
Position
Below the diagonal: dioxus_signals.copy_value uses a module listed above it, which is the healthy direction.
dioxus_signals.copy_value uses generational_box, so a change to generational_box can break dioxus_signals.copy_value, while a change to dioxus_signals.copy_value can't break generational_box.
Position
Below the diagonal: dioxus_signals.copy_value uses a module listed above it, which is the healthy direction.
dioxus_signals.copy_value uses dioxus_core.reactive_context, so a change to dioxus_core.reactive_context can break dioxus_signals.copy_value, while a change to dioxus_signals.copy_value can't break dioxus_core.reactive_context.
Position
Below the diagonal: dioxus_signals.copy_value uses a module listed above it, which is the healthy direction.
dioxus_signals.copy_value uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_signals.copy_value, while a change to dioxus_signals.copy_value can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_signals.copy_value uses a module listed above it, which is the healthy direction.
dioxus_signals.copy_value uses dioxus_signals.read, so a change to dioxus_signals.read can break dioxus_signals.copy_value, while a change to dioxus_signals.copy_value can't break dioxus_signals.read.
Position
Below the diagonal: dioxus_signals.copy_value uses a module listed above it, which is the healthy direction.
dioxus_signals.copy_value uses dioxus_signals.write, so a change to dioxus_signals.write can break dioxus_signals.copy_value, while a change to dioxus_signals.copy_value can't break dioxus_signals.write.
Position
Below the diagonal: dioxus_signals.copy_value uses a module listed above it, which is the healthy direction.
dioxus_autofmt.writer uses dioxus_cli.check.metadata, so a change to dioxus_cli.check.metadata can break dioxus_autofmt.writer, while a change to dioxus_autofmt.writer can't break dioxus_cli.check.metadata.
Position
Below the diagonal: dioxus_autofmt.writer uses a module listed above it, which is the healthy direction.
dioxus_autofmt.writer uses dioxus_rsx.template_body, so a change to dioxus_rsx.template_body can break dioxus_autofmt.writer, while a change to dioxus_autofmt.writer can't break dioxus_rsx.template_body.
Position
Below the diagonal: dioxus_autofmt.writer uses a module listed above it, which is the healthy direction.
dioxus_autofmt.writer uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_autofmt.writer, while a change to dioxus_autofmt.writer can't break dioxus_rsx.element.
Position
Below the diagonal: dioxus_autofmt.writer uses a module listed above it, which is the healthy direction.
dioxus_autofmt.writer uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_autofmt.writer, while a change to dioxus_autofmt.writer can't break dioxus_core.nodes.
Position
Below the diagonal: dioxus_autofmt.writer uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_rsx.element, so a change to dioxus_rsx.element can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_rsx.element.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses generational_box, so a change to generational_box can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break generational_box.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_core.events.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_core.scope_context, so a change to dioxus_core.scope_context can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_core.scope_context.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_core.virtual_dom, so a change to dioxus_core.virtual_dom can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_core.virtual_dom.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_core.suspense.component uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_core.suspense.component, while a change to dioxus_core.suspense.component can't break dioxus_core.nodes.
Position
Below the diagonal: dioxus_core.suspense.component uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses wasm_used, so a change to wasm_used can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break wasm_used.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses generational_box, so a change to generational_box can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break generational_box.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses dioxus_core.reactive_context, so a change to dioxus_core.reactive_context can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_core.reactive_context.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses dioxus_signals.read, so a change to dioxus_signals.read can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_signals.read.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses dioxus_signals.write, so a change to dioxus_signals.write can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_signals.write.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_core.nodes.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
dioxus_signals.signal uses dioxus_signals.copy_value, so a change to dioxus_signals.copy_value can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_signals.copy_value.
Position
Below the diagonal: dioxus_signals.signal uses a module listed above it, which is the healthy direction.
35→39 dioxus_signals.signal uses dioxus_signals.memopart of a loop✕
Connections
1 pair of types, where a type in dioxus_signals.signal uses a type in dioxus_signals.memo.
dioxus_signals.signal uses dioxus_signals.memo, so a change to dioxus_signals.memo can break dioxus_signals.signal, while a change to dioxus_signals.signal can't break dioxus_signals.memo.
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.
dioxus_web.dom uses dioxus_core.arena, so a change to dioxus_core.arena can break dioxus_web.dom, while a change to dioxus_web.dom can't break dioxus_core.arena.
Position
Below the diagonal: dioxus_web.dom uses a module listed above it, which is the healthy direction.
dioxus_web.dom uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_web.dom, while a change to dioxus_web.dom can't break dioxus_core.events.
Position
Below the diagonal: dioxus_web.dom uses a module listed above it, which is the healthy direction.
dioxus_web.dom uses dioxus_core.runtime, so a change to dioxus_core.runtime can break dioxus_web.dom, while a change to dioxus_web.dom can't break dioxus_core.runtime.
Position
Below the diagonal: dioxus_web.dom uses a module listed above it, which is the healthy direction.
dioxus_web.dom uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_web.dom, while a change to dioxus_web.dom can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_web.dom uses a module listed above it, which is the healthy direction.
dioxus_web.dom uses dioxus_core.virtual_dom, so a change to dioxus_core.virtual_dom can break dioxus_web.dom, while a change to dioxus_web.dom can't break dioxus_core.virtual_dom.
Position
Below the diagonal: dioxus_web.dom uses a module listed above it, which is the healthy direction.
dioxus_web.dom uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_web.dom, while a change to dioxus_web.dom can't break dioxus_core.nodes.
Position
Below the diagonal: dioxus_web.dom uses a module listed above it, which is the healthy direction.
dioxus_cli.logging uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_cli.logging, while a change to dioxus_cli.logging can't break dioxus_core.events.
Position
Below the diagonal: dioxus_cli.logging uses a module listed above it, which is the healthy direction.
dioxus_cli.logging uses dioxus_autofmt.writer, so a change to dioxus_autofmt.writer can break dioxus_cli.logging, while a change to dioxus_cli.logging can't break dioxus_autofmt.writer.
Position
Below the diagonal: dioxus_cli.logging uses a module listed above it, which is the healthy direction.
dioxus_cli.serve.output uses dioxus_cli.serve.runner, so a change to dioxus_cli.serve.runner can break dioxus_cli.serve.output, while a change to dioxus_cli.serve.output can't break dioxus_cli.serve.runner.
Position
Below the diagonal: dioxus_cli.serve.output uses a module listed above it, which is the healthy direction.
dioxus_cli.serve.output uses dioxus_core.events, so a change to dioxus_core.events can break dioxus_cli.serve.output, while a change to dioxus_cli.serve.output can't break dioxus_core.events.
Position
Below the diagonal: dioxus_cli.serve.output uses a module listed above it, which is the healthy direction.
dioxus_cli.serve.output uses dioxus_cli.logging, so a change to dioxus_cli.logging can break dioxus_cli.serve.output, while a change to dioxus_cli.serve.output can't break dioxus_cli.logging.
Position
Below the diagonal: dioxus_cli.serve.output uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in dioxus_signals.memo uses a type in wasm_used.
The types involved
dioxus_signals.memo.Memo → wasm_used.Location
Direction
dioxus_signals.memo uses wasm_used, so a change to wasm_used can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break wasm_used.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses generational_box, so a change to generational_box can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break generational_box.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_core.reactive_context, so a change to dioxus_core.reactive_context can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_core.reactive_context.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_core.scopes, so a change to dioxus_core.scopes can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_core.scopes.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_signals.read, so a change to dioxus_signals.read can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_signals.read.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_signals.write, so a change to dioxus_signals.write can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_signals.write.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_core.nodes.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_signals.copy_value, so a change to dioxus_signals.copy_value can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_signals.copy_value.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_signals.signal, so a change to dioxus_signals.signal can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_signals.signal.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.memo uses dioxus_cli.serve.output, so a change to dioxus_cli.serve.output can break dioxus_signals.memo, while a change to dioxus_signals.memo can't break dioxus_cli.serve.output.
Position
Below the diagonal: dioxus_signals.memo uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses generational_box, so a change to generational_box can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break generational_box.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_core.reactive_context, so a change to dioxus_core.reactive_context can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_core.reactive_context.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_signals.read, so a change to dioxus_signals.read can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_signals.read.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_signals.write, so a change to dioxus_signals.write can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_signals.write.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_core.nodes, so a change to dioxus_core.nodes can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_core.nodes.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_signals.copy_value, so a change to dioxus_signals.copy_value can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_signals.copy_value.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_signals.signal, so a change to dioxus_signals.signal can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_signals.signal.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
dioxus_signals.boxed uses dioxus_signals.memo, so a change to dioxus_signals.memo can break dioxus_signals.boxed, while a change to dioxus_signals.boxed can't break dioxus_signals.memo.
Position
Below the diagonal: dioxus_signals.boxed uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49% · Adequate · gated by R1, X4, X5 ·
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
69
High / Critical
A03:2025 — Software Supply Chain Failures
38
High / Critical
A02:2025 — Security Misconfiguration
4
Medium
Roadmap
First, fix the 451 instances of interpolated log messages to restore structured logging, and migrate the remaining plain JavaScript files to TypeScript to improve type safety. Next, enable strict null checking across all TypeScript configurations and resolve existing null assertions to prevent runtime errors. Finally, correct page structure issues such as missing landmarks and titles, and enforce accessibility standards by integrating checks into the UI test suite and CI pipeline.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
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 `?`).
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
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.
Per-file score 0–10 — a quality signature. Of 200 files carrying findings, judged against the Preview bar: 1% slop · 23% mixed · 76% near-clean.
File
Score
Band
Worst signal
REDACTED
0.0
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Dependency Vulnerabilities: Medium CVE: REDACTED
packages/desktop/src/document.rs
5.6
Mixed
Code Duplication: Duplicated block (6 lines × 2)
packages/cli/src/build/request.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/fullstack-macro/src/lib.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/autofmt/src/writer.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/serve/runner.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/build/link.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/build/patch.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/build/builder.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/build/apple.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/interpreter/src/ts/serialize.ts
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/logging.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/fullstack-server/src/ssr.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/serve/output.rs
6.0
Mixed
Explicit Debt: FixmeComment
packages/core-macro/src/props/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/rsx/src/rsx_block.rs
6.0
Mixed
Explicit Debt: TodoComment
packages/cli/src/cli/link.rs
6.0
Mixed
Explicit Debt: TodoComment
How the grades work
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 — 93
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 — 731
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 — 77
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 79 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 79 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, 863 of 901 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — packages/playwright-tests/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 81 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 278 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .js) and this repository declares a Cargo test suite (repository root, 177 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 2 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (examples/01-app-demos/hotdog/Dockerfile). docker build failed (exit 1) — > [internal] load metadata for docker.io/library/rust:1: ------ REDACTED:1 -------------------- 1 | >>> FROM rust:1 AS chef 2 | RUN cargo install cargo-chef 3 | WORKDIR /app -------------------- ERROR: failed to solve: rust:1: failed to resolve source metadata for docker.io/library/rust:1: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1": Forbidden; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read 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.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read 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.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 411 further occurrence(s) are not listed individually; the score already reflects all 451.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
74 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BuildRequest::new at 85. A further 21 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 KeyCode::from_raw_code at 99 — they are counted neither in the figure above nor in this dimension's score. 14 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: packages/html/src/events/keyboard.rs (KeyCode::from_raw_code at 99), packages/desktop/src/shortcut.rs (KeyCode::into_key_code at 97), packages/core-types/src/bubbles.rs (dioxus_core_types::bubbles::event_bubbles at 92), packages/html/src/events/before_input.rs (InputType::as_str at 47), packages/web/src/events/mod.rs (dioxus_web::events::event_type_matches at 24), and 9 more not listed here. 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.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with BuildRequest::new (cyclomatic 85). — Refactoring it lifts Cyclomatic Complexity from 6.2 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 68 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with Writer::write_partial_expr (cognitive 147), ServerFnArgs::parse (cognitive 125), BuildRequest::new (cognitive 116). — 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 8 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 31 MethodTooLong finding(s) in God Classes — start with lib.rs (3), mod.rs (3), android.rs (2). — One of this dimension's main actionable groups (31 warning-level).
Resolve the 28 FileTooLong finding(s) in God Classes — start with lib.rs (2), mod.rs (2), request.rs. — One of this dimension's main actionable groups (28 warning-level).
Resolve the 14 TooManyMethods finding(s) in God Classes — start with request.rs, virtual_dom.rs, runtime.rs. — One of this dimension's main actionable groups (14 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
148 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 23 of the 152 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 44 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 25 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with mutation_writer.rs (6), btreemap.rs (3), link.rs (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 14 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), lib.rs (2), print.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mutation_writer.rs (3), windows.rs (2), node.rs. — One of this dimension's main actionable groups (13 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.9 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
81 production modules (Gradle+Cargo+npm), 0 dependency cycle(s), 7 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 13 module(s) off the main sequence, with abstractness counted on 45 of the 81 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: depinfo · ×13
Unstable project dioxus-desktop
Unstable project dioxus-fullstack
Unstable project dioxus-liveview
Unstable project dioxus-native
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 1 Unstable project dioxus-desktop finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project dioxus-fullstack finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with magic.rs (2), document.rs (2), desktop_context.rs. — One of this dimension's main actionable groups (9 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
874 test methods: 534 unit, 340 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 81 `it`/`test` case(s) across 23 test file(s) declaring at least one beside 1 .NET test method(s); its tier split is read from package names and paths only. The Rust suite contributes 792 `#[test]` function(s) across 177 file(s) declaring at least one; its unit/integration split is Cargo's own — 93 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 81 tests. Measured on the JavaScript/TypeScript suite only — at least 278 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
1 of 1370 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
Banned license: imagequant
What to do
Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with mutation_writer.rs, webview.rs, update.rs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/cli/src/bundler/macos.rs. Counted over 415 of the 616 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
173 deducted task-comment markers across 153189 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 159 TodoComment finding(s) in Explicit Debt — start with request.rs (16), lib.rs (14), runner.rs (11). — One of this dimension's main actionable groups (159 warning-level).
Resolve the 13 FixmeComment finding(s) in Explicit Debt — start with elements.rs (9), mutation_writer.rs (2), element.rs. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with native.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 57 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
71 finding(s): 0 critical, 67 high, 4 medium, 0 low. 63 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 9 file(s) — `.devin/skills/release-alpha/publish-with-retry.sh` (line 8), `packages/cli/assets/android/gen/gradlew` (line 74, line 178), `packages/cli/assets/web/dev.loading.html` (line 282), `packages/core/src/diff/placement.rs` (line 90), `packages/fuzz/fuzz/fuzz_parallel_cmin.sh`, … (+4 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
What to do
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 63 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (64 issue-level, 1 of them charged here).
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).
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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
16 of 415 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/cli/src/config/manifest.rs. Counted over 415 of the 616 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with manifest.rs, manifest_mapper.rs, mod.rs. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with visible.rs (2), css_module_parser.rs, issues.rs. — One of this dimension's main actionable groups (13 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 5 Change coupling finding(s) in Change Coupling — start with sync.rs, impls.rs, fragment.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
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.
Do you agree with this assessment?
AC3 · Page structure3.7 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×6) — packages/cli/assets/web/dev.index.html:2, packages/cli/assets/web/dev.loading.html:2, packages/cli/assets/web/prod.index.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="main">, so there is no content here to wrap — render the <main> from the component mounted into it. (×5) — packages/cli/assets/web/dev.index.html:2, packages/cli/assets/web/prod.index.html:2, packages/desktop/src/assets/dev.index.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/cli/assets/web/dev.loading.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — packages/cli/assets/web/dev.loading.html:268
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×2) — packages/desktop/src/assets/dev.index.html:5, packages/desktop/src/assets/prod.index.html:5
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether 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.
`/* header` sets color: white on background-color: #2196F3 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/01-app-demos/file-explorer/assets/fileexplorer.css:14
`button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/assets/calculator.css:26
`:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/assets/todomvc.css:37
`.focus\:outline-none:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/assets/weatherapp.css:1182
`.bounce` moves (`animation: boomBox 0.5s 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/assets/radio.css:28
`.animated-text` moves (`transition: opacity 1s ease, transform 1s 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/assets/visible.css:21
`.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — examples/01-app-demos/hackernews/assets/hackernews.css:16, examples/01-app-demos/ecommerce-site/public/loading.css:16
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
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.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
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.
What to do
Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 85 of 125 project(s) that lack one — worth up to 1.4 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability5.2 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 26/66 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/autofmt`, `packages/cli-config`, `packages/cli-harnesses/harness-default-to-non-default`, `packages/cli-harnesses/harness-fullstack-desktop`, `packages/cli-harnesses/harness-fullstack-desktop-with-default` and 35 more.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Dependabot is configured but does not watch `npm`, `cargo`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
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.
`reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — packages/cli/src/build/builder.rs:2135, packages/cli/src/http_client.rs:31, packages/fullstack/src/client.rs:145
`reqwest::blocking::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — packages/cli/src/http_client.rs:43
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`run` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — packages/cli/src/test_harnesses.rs:404
What to do
Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
Do you agree with this assessment?
R1 · Type Safety2.9 / 10Weak✓ 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.
13 typed · 32 plain JS — the untyped files are packages/document/assets/script.js, packages/document/src/js/head.js, packages/interpreter/src/js/hydrate.js, packages/interpreter/src/js/initialize_streaming.js, packages/liveview/src/main.js, packages/manganis/manganis-core/assets/script.js (+26 more). 0 production file(s) opt out entirely with @ts-nocheck · 29 @ts-ignore suppression(s).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
packages/interpreter/src/ts/core.ts:111 · packages/interpreter/src/ts/core.ts:134 — 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/interpreter/src/ts/core.ts:111
packages/interpreter/src/ts/patch_console.ts:10 · packages/interpreter/src/ts/patch_console.ts:19 · packages/interpreter/src/ts/patch_console.ts:28 · packages/interpreter/src/ts/patch_console.ts:37 · +1 more site(s) not listed — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/interpreter/src/ts/patch_console.ts:10
packages/interpreter/src/ts/core.ts:331 · packages/interpreter/src/ts/core.ts:340 — 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/interpreter/src/ts/core.ts:331
packages/interpreter/src/ts/core.ts:247 · packages/interpreter/src/ts/core.ts:254 · packages/interpreter/src/ts/core.ts:267 · packages/interpreter/src/ts/core.ts:274 — all 4 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/interpreter/src/ts/core.ts:247
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.
serializeEvent has cyclomatic complexity 33 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/interpreter/src/ts/serialize.ts:15
setAttributeInner has cyclomatic complexity 20 and cognitive complexity 22; 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/interpreter/src/ts/set_attribute.ts:4
fmtSelection has cyclomatic complexity 15 and cognitive complexity 14; 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/extension/src/main.ts:121
serializeInputEvent has cyclomatic complexity 13 and cognitive complexity 16; 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/interpreter/src/ts/serialize.ts:187
handleEvent has cyclomatic complexity 11 and cognitive complexity 16; 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/interpreter/src/ts/native.ts:328
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.4 / 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/interpreter/src/ts/native.ts has 509 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/interpreter/src/ts/native.ts:1
packages/interpreter/src/ts/serialize.ts has 496 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/interpreter/src/ts/serialize.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.8 / 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.
24 file(s) (~1923 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/playwright-tests
Nothing imports this binding — it is safe to review for removal. (×3) — packages/interpreter/src/ts/serialize.ts:7, packages/interpreter/src/ts/serialize.ts:555, packages/interpreter/src/ts/serialize.ts:556
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in packages/extension/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`axum::serve(` (packages/liveview/src/adapters/axum_adapter.rs:92)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — packages/cli/src/bundler/linux.rs:1079, packages/cli/src/bundler/tools.rs:239
Set: Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy. Missing: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−2.0 on this card.) The server: `axum::serve(` (packages/liveview/src/adapters/axum_adapter.rs:92).
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `packages/cli/src/bundler/linux.rs:1079` (`md5::compute`), `packages/cli/src/bundler/tools.rs:239` (`Sha1::new`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Add Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options beside the headers the Rust server already sets.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped1.7 / 10Critical✓ 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.
`raw_manifest` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output 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:17
`plist_entries` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — packages/cli/assets/ios/ios.plist.hbs:90, packages/cli/assets/macos/mac.plist.hbs:57
`raw_plist` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — packages/cli/assets/ios/ios.plist.hbs:93, packages/cli/assets/macos/mac.plist.hbs:60
`value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/interpreter/src/ts/set_attribute.ts:64
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error!` at line 43 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/web/src/hydration/hydrate.rs:43
`warn!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/web/src/events/mod.rs:233
`error!` at line 197 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-used/src/lib.rs:197
`error!` at line 205 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-used/src/lib.rs:205
`info!` at line 235 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/lib.rs:235
`info!` at line 298 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/lib.rs:298
`error!` at line 1339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/lib.rs:1339
`info!` at line 55 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/main.rs:55
`info!` at line 69 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/main.rs:69
`info!` at line 85 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/main.rs:85
`debug!` at line 117 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/main.rs:117
`error!` at line 171 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/main.rs:171
`debug!` at line 175 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/wasm-split/wasm-split-cli/src/main.rs:175
`trace!` at line 191 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/signals/src/memo.rs:191
`trace!` at line 412 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/signals/src/signal.rs:412
`trace!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/signals/src/signal.rs:531
`error!` at line 163 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/router/src/routable.rs:163
`error!` at line 184 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/router/src/routable.rs:184
`error!` at line 383 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/router/src/routable.rs:383
`error!` at line 70 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/router/src/components/history_buttons.rs:70
`error!` at line 142 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/router/src/components/history_buttons.rs:142
`error!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/router/src/components/link.rs:159
`trace!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/native/src/assets.rs:48
`warn!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/native/src/assets.rs:53
`warn!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/native/src/assets.rs:60
`error!` at line 15 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/native/src/link_handler.rs:15
`warn!` at line 132 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/liveview/src/query.rs:132
`trace!` at line 385 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/generational-box/src/sync.rs:385
`trace!` at line 381 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/generational-box/src/unsync.rs:381
`info!` at line 136 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/server.rs:136
`error!` at line 364 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/server.rs:364
`error!` at line 85 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/ssr.rs:85
`error!` at line 71 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/isrg/fs_cache.rs:71
`error!` at line 81 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/isrg/fs_cache.rs:81
`trace!` at line 96 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/isrg/fs_cache.rs:96
`error!` at line 119 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-server/src/isrg/fs_cache.rs:119
`trace!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-core/src/transport.rs:276
`error!` at line 299 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-core/src/transport.rs:299
`error!` at line 306 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack-core/src/transport.rs:306
`error!` at line 203 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/fullstack/src/client.rs:203
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.
1/5 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.
~1.3 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 2261 source line(s) of the 13 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/interpreter/src/ts/native.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 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.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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) — > [internal] load metadata for docker.io/library/rust:1: ------ REDACTED:1 -------------------- 1 | >>> FROM rust:1 AS chef 2 | RUN cargo install cargo-chef 3 | WORKDIR /app -------------------- ERROR: failed to solve: rust:1: failed to resolve source metadata for docker.io/library/rust:1: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 2 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Kotlin, Rust, Swift, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust, Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .kt, .rs, .swift, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (139 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — 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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — 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
M4 Documentation accuracy — Not applicable: the 57 current-state document(s) make no claim of a kind M4 checks. 12 claim(s) of kinds M4 does not check were not checked (path 11, command argument 1); M4 checks only links and versions.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 24 test file(s) reach none of 21 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
<html> without a lang packages/cli/assets/web/dev.index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/cli/assets/web/dev.loading.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/cli/assets/web/prod.index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/desktop/src/assets/dev.index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/desktop/src/assets/prod.index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/liveview/src/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
Orphaned knowledge packages/cli/src/config/manifest.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge packages/cli/src/config/manifest_mapper.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge packages/cli/src/check/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Viewport restricts zoom packages/desktop/src/assets/dev.index.html:5— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom packages/desktop/src/assets/prod.index.html:5— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Banned license: imagequant — `imagequant` 4.4.1 is published on crates.io under `GPL-3.0-or-later`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
TodoComment packages/web/src/devtools.rs:75— // todo: we want to throw a screen here that shows the user that the devserver has disconnected — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web/src/lib.rs:246— // Todo: This is currently disabled because it has a negative impact on response times for events but it could be re-enabled for tasks — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web/src/events/mod.rs:71— // todo: special case more input types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web/src/events/mod.rs:270— // todo: some of these events are being casted to the wrong event type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/wasm-split/wasm-split-cli/src/lib.rs:284— // todo(jon): prefer to delete the items as we go so we don't need to run a gc pass. it/it's quite slow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/wasm-split/wasm-split-cli/src/lib.rs:884— /// Todo: we could chunk up the main module itself! Not going to now but it would enable parallel downloads of the main chunk — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/wasm-split/wasm-split-cli/src/lib.rs:899— // todo: break down this chunk if it exceeds a certain size (100kb?) by identifying different groups — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stores/src/impls/btreemap.rs:137— // TODO: This method was released in 0.7 without the hash bound so we don't have a way — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx-rosetta/src/lib.rs:61— // todo(jon): apply the namespaces to the attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/attribute.rs:84— // todo: make this cleaner please — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/component.rs:114— // todo: ensure going through the trait actually works — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/component.rs:214— /// todo: don't create the tokenstream from scratch and instead dump it into the existing streama — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/diagnostics.rs:63— // TODO: Ideally this would be integrated into the existing diagnostics struct, but currently all fields are public so adding — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/forloop.rs:18— // todo: better partial parsing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/literal.rs:219— // todo: hmmmmmmmmmmmm might not always work — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/rsx_block.rs:166— // todo: this might cause complications with partial expansion... think more about the cases — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/rsx_block.rs:201— // todo: maybe make this a method such that the rsxblock is lossless — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/rsx_block.rs:232— // todo: we would've pushed a warning here but proc-macro-2 emits them as errors, which we — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/rsx_call.rs:86— // todo: actually throw warnings if there are any — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/template_body.rs:849— /// todo: we want to allow arbitrary exprs for keys provided they impl hash / eq — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/rsx/src/text_node.rs:33— // todo: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/router/src/components/link.rs:221— // todo(jon): this is extra hacky for no reason - we should fix prevent default on Links — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/playwright-tests/cli-optimization/src/lib.rs:85— // todo: test monaco more.... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/native-dom/src/dioxus_document.rs:105— // TODO: Support arbitrary "index.html" templates — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/native-dom/src/dioxus_document.rs:329— // TODO: Implement IME handling — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: BuildRequest.new packages/cli/src/build/request.rs:359— MethodTooLong — new runs 333 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 233 over it, 3.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.build_android_app_dir packages/cli/src/build/android.rs:81— MethodTooLong — build_android_app_dir runs 235 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 135 over it, 2.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.run_fat_link packages/cli/src/build/link.rs:847— MethodTooLong — run_fat_link runs 204 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebviewInstance.new packages/desktop/src/webview.rs:318— MethodTooLong — new runs 199 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ServerFnArgs.parse packages/fullstack-macro/src/lib.rs:1513— MethodTooLong — parse runs 190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StructInfo.build_method_impl packages/core-macro/src/props/mod.rs:1395— MethodTooLong — build_method_impl runs 181 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Doctor.doctor packages/cli/src/cli/doctor.rs:11— MethodTooLong — doctor runs 180 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.android_env_vars packages/cli/src/build/android.rs:661— MethodTooLong — android_env_vars runs 179 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppServer.handle_file_change packages/cli/src/serve/runner.rs:387— MethodTooLong — handle_file_change runs 163 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BundleContext.bundle_linux_rpm packages/cli/src/bundler/linux.rs:229— MethodTooLong — bundle_linux_rpm runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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.
MethodTooLong: HotpatchModuleCache.new packages/cli/src/build/patch.rs:120— MethodTooLong — new runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Writer.write_partial_expr packages/autofmt/src/writer.rs:956— MethodTooLong — write_partial_expr runs 143 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.auto_provision_entitlements packages/cli/src/build/apple.rs:618— MethodTooLong — auto_provision_entitlements runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SelfUpdate.self_update packages/cli/src/cli/update.rs:34— MethodTooLong — self_update runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RouteTreeSegmentData.to_tokens packages/router-macro/src/route_tree.rs:278— MethodTooLong — to_tokens runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ElementDef.to_tokens_with_paths packages/html-internal-macro/src/elements.rs:389— MethodTooLong — to_tokens_with_paths runs 137 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.bundle_web packages/cli/src/build/web.rs:74— MethodTooLong — bundle_web runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TraceController.main packages/cli/src/logging.rs:133— MethodTooLong — main runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FfiBridgeParser.generate_android_function packages/manganis/manganis-macro/src/ffi.rs:471— MethodTooLong — generate_android_function runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BundleContext.bundle_macos_app packages/cli/src/bundler/macos.rs:44— MethodTooLong — bundle_macos_app runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RouteEnum.parse packages/router-macro/src/lib.rs:283— MethodTooLong — parse runs 132 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ImplExtensionAttributes.to_tokens packages/html-internal-macro/src/extension_attributes.rs:39— MethodTooLong — to_tokens runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.enrich_entitlements_from_config packages/cli/src/build/apple.rs:396— MethodTooLong — enrich_entitlements_from_config runs 123 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuildRequest.compile_workspace_hotpatch packages/cli/src/build/link.rs:135— MethodTooLong — compile_workspace_hotpatch runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StructInfo.field_impl packages/core-macro/src/props/mod.rs:1111— MethodTooLong — field_impl runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: build/request.rs packages/cli/src/build/request.rs— FileTooLong — 1551 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 97% of them inside a single declaration: BuildRequest (2 blocks, 243-3211). The bar is 500 significant lines; this is 1051 over it, 3.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs packages/fullstack-macro/src/lib.rs— FileTooLong — 1277 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 777 over it, 2.55× 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: props/mod.rs packages/core-macro/src/props/mod.rs— FileTooLong — 1261 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 761 over it, 2.52× 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: build/builder.rs packages/cli/src/build/builder.rs— FileTooLong — 1257 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 757 over it, 2.51× 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: serve/runner.rs packages/cli/src/serve/runner.rs— FileTooLong — 1256 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: AppServer (2 blocks, 42-1795). The bar is 500 significant lines; this is 756 over it, 2.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: build/apple.rs packages/cli/src/build/apple.rs— FileTooLong — 1205 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 705 over it, 2.41× 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: payloads/websocket.rs packages/fullstack/src/payloads/websocket.rs— FileTooLong — 947 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 447 over it, 1.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: build/patch.rs packages/cli/src/build/patch.rs— FileTooLong — 925 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 425 over it, 1.85× 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: bundler/windows.rs packages/cli/src/bundler/windows.rs— FileTooLong — 890 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 390 over it, 1.78× 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/writer.rs packages/autofmt/src/writer.rs— FileTooLong — 881 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: Writer (2 blocks, 14-1413). The bar is 500 significant lines; this is 381 over it, 1.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/logging.rs packages/cli/src/logging.rs— FileTooLong — 880 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 75% of them inside a single declaration: TraceController (3 blocks, 82-1162). The bar is 500 significant lines; this is 380 over it, 1.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs packages/wasm-split/wasm-split-cli/src/lib.rs— FileTooLong — 870 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: Splitter (2 blocks, 27-1155). The bar is 500 significant lines; this is 370 over it, 1.74× 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: build/android.rs packages/cli/src/build/android.rs— FileTooLong — 850 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: BuildRequest (75-1034). The bar is 500 significant lines; this is 350 over it, 1.70× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/attribute_groups.rs packages/html/src/attribute_groups.rs— FileTooLong — 845 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 345 over it, 1.69× 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: build/link.rs packages/cli/src/build/link.rs— FileTooLong — 779 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: BuildRequest (42-1467). The bar is 500 significant lines; this is 279 over it, 1.56× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/renderer.rs packages/oracle/src/renderer.rs— FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 278 over it, 1.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bundler/linux.rs packages/cli/src/bundler/linux.rs— FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 80% of them inside a single declaration: BundleContext (17-946). The bar is 500 significant lines; this is 249 over it, 1.50× 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: diff/node.rs packages/core/src/diff/node.rs— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 86% of them inside a single declaration: VNode (2 blocks, 133-1008). The bar is 500 significant lines; this is 209 over it, 1.42× 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: suspense/component.rs packages/core/src/suspense/component.rs— FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 175 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: serve/output.rs packages/cli/src/serve/output.rs— FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: Output (3 blocks, 46-1067). The bar is 500 significant lines; this is 163 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/ffi.rs packages/manganis/manganis-macro/src/ffi.rs— FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: FfiBridgeParser (2 blocks, 254-1084). The bar is 500 significant lines; this is 163 over it, 1.33× 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: config/manifest.rs packages/cli/src/config/manifest.rs— FileTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 146 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bundler/macos.rs packages/cli/src/bundler/macos.rs— FileTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 135 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bundler/mod.rs packages/cli/src/bundler/mod.rs— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 102 over it, 1.20× 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/template_body.rs packages/rsx/src/template_body.rs— FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (5 lines × 2) packages/cli/src/build/builder.rs:1031— packages/cli/src/build/builder.rs:1031-1035 | packages/cli/src/build/builder.rs:1714-1718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/cli/src/cli/link.rs:262— packages/cli/src/cli/link.rs:262-266 | packages/cli/src/rustcwrapper.rs:161-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) packages/const-serialize/src/str.rs:344— packages/const-serialize/src/str.rs:344-348 | packages/const-serialize/src/str.rs:349-353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/stores/src/impls/slice.rs:136— packages/stores/src/impls/slice.rs:136-140 | packages/stores/src/impls/slice.rs:147-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/hooks/src/use_future.rs:110— packages/hooks/src/use_future.rs:110-114 | packages/hooks/src/use_resource.rs:192-196 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/native-dom/src/mutation_writer.rs:151— packages/native-dom/src/mutation_writer.rs:151-155 | packages/oracle/src/renderer.rs:149-153 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/native-dom/src/mutation_writer.rs:171— packages/native-dom/src/mutation_writer.rs:171-175 | packages/oracle/src/renderer.rs:169-173 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/native-dom/src/mutation_writer.rs:177— packages/native-dom/src/mutation_writer.rs:177-181 | packages/oracle/src/renderer.rs:175-179 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/native-dom/src/mutation_writer.rs:190— packages/native-dom/src/mutation_writer.rs:190-194 | packages/oracle/src/renderer.rs:188-192 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/native-dom/src/mutation_writer.rs:196— packages/native-dom/src/mutation_writer.rs:196-200 | packages/oracle/src/renderer.rs:194-198 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/native-dom/src/mutation_writer.rs:230— packages/native-dom/src/mutation_writer.rs:230-234 | packages/oracle/src/renderer.rs:228-232 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/web/src/events/resize.rs:16— packages/web/src/events/resize.rs:16-20 | packages/web/src/events/visible.rs:24-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/cli/src/build/windows.rs:618— packages/cli/src/build/windows.rs:618-622 | packages/cli/src/build/windows.rs:631-638 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/cli/src/cli/doctor.rs:67— packages/cli/src/cli/doctor.rs:67-71 | packages/cli/src/cli/doctor.rs:72-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/cli/src/build/link.rs:1011— packages/cli/src/build/link.rs:1011-1015 | packages/cli/src/build/link.rs:1020-1024 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/manganis/manganis-macro/src/ffi.rs:497— packages/manganis/manganis-macro/src/ffi.rs:497-501 | packages/manganis/manganis-macro/src/ffi.rs:900-904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/core/src/hotreload_utils.rs:187— packages/core/src/hotreload_utils.rs:187-191 | packages/core/src/hotreload_utils.rs:193-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/core/src/nodes.rs:565— packages/core/src/nodes.rs:565-569 | packages/core/src/nodes.rs:618-622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/stores/src/impls/btreemap.rs:113— packages/stores/src/impls/btreemap.rs:113-117 | packages/stores/src/impls/hashmap.rs:117-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/stores/src/impls/btreemap.rs:319— packages/stores/src/impls/btreemap.rs:319-323 | packages/stores/src/impls/hashmap.rs:326-330 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/stores/src/impls/btreemap.rs:329— packages/stores/src/impls/btreemap.rs:329-333 | packages/stores/src/impls/hashmap.rs:336-340 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/fuzz/src/harness.rs:790— packages/fuzz/src/harness.rs:790-794 | packages/fuzz/src/harness.rs:798-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/fuzz/src/ops.rs:336— packages/fuzz/src/ops.rs:336-340 | packages/fuzz/src/ops.rs:354-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/fuzz/src/warmup.rs:565— packages/fuzz/src/warmup.rs:565-571 | packages/fuzz/src/warmup.rs:599-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/fuzz/src/warmup.rs:557— packages/fuzz/src/warmup.rs:557-561 | packages/fuzz/src/warmup.rs:591-595 — 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.
dioxus_cli::serve::serve_all (cognitive 75) packages/cli/src/serve/mod.rs:42— dioxus_cli::serve::serve_all has cognitive complexity 75 (threshold 15). Drivers by points: if/else 15 (52 pts), match/switch 6 (17 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 50). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::build::patch::create_wasm_jump_table (cognitive 46) packages/cli/src/build/patch.rs:479— dioxus_cli::build::patch::create_wasm_jump_table has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 8, match/switch 3 (5 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::build::patch::create_undefined_symbol_stub (cognitive 44) packages/cli/src/build/patch.rs:873— dioxus_cli::build::patch::create_undefined_symbol_stub has cognitive complexity 44 (threshold 15). Drivers by points: match/switch 13 (27 pts), if/else 9 (15 pts), loops 2 (nesting depth added 20). 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.
dioxus_cli::build::patch::prepare_wasm_base_module (cognitive 32) packages/cli/src/build/patch.rs:1336— dioxus_cli::build::patch::prepare_wasm_base_module has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 4 (6 pts), boolean chains 3, match/switch 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.
dioxus_cli::opt::js::lexer::has_module_syntax (cognitive 31) packages/cli/src/opt/js.rs:158— dioxus_cli::opt::js::lexer::has_module_syntax has cognitive complexity 31 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 4 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::build::windows::get_sdk (cognitive 29) packages/cli/src/build/windows.rs:678— dioxus_cli::build::windows::get_sdk has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 2 (5 pts) (nesting depth added 18). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
dioxus_cli::config::manifest::simplify_schema (cognitive 29) packages/cli/src/config/manifest.rs:1476— dioxus_cli::config::manifest::simplify_schema has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 4 (9 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::cli::component::copy_component_files (cognitive 28) packages/cli/src/cli/component.rs:632— dioxus_cli::cli::component::copy_component_files has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 4 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 15). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::serve::runner::analyze_cargo_value (cognitive 28) packages/cli/src/serve/runner.rs:2006— dioxus_cli::serve::runner::analyze_cargo_value has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::build::apple::compile_swift_sources (cognitive 26) packages/cli/src/build/apple.rs:1049— dioxus_cli::build::apple::compile_swift_sources has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 5 (6 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.
dioxus_cli::build::apple::extract_swift_from_bytes (cognitive 26) packages/cli/src/build/apple.rs:1447— dioxus_cli::build::apple::extract_swift_from_bytes has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (22 pts), match/switch 2 (3 pts), loops 1 (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.
dioxus_cli::build::assets::find_wasm_symbol_offsets (cognitive 26) packages/cli/src/build/assets.rs:319— dioxus_cli::build::assets::find_wasm_symbol_offsets has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3 (4 pts), match/switch 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.
dioxus_cli::build::assets::extract_symbols_from_file (cognitive 26) packages/cli/src/build/assets.rs:487— dioxus_cli::build::assets::extract_symbols_from_file has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (9 pts), loops 3, 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.
dioxus_cli::bundler::linux::find_icon_in_appdir (cognitive 26) packages/cli/src/bundler/linux.rs:949— dioxus_cli::bundler::linux::find_icon_in_appdir has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 1 (2 pts), boolean chains 1 (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.
dioxus_cli::cargo_toml::merge_profiles (cognitive 24) packages/cli/src/cargo_toml.rs:68— dioxus_cli::cargo_toml::merge_profiles has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (23 pts), 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.
dioxus_cli::config::inline_config::extract_module_doc_comments (cognitive 23) packages/cli/src/config/inline_config.rs:66— dioxus_cli::config::inline_config::extract_module_doc_comments has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 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.
dioxus_cli::bundler::macos::find_identity_in_keychain (cognitive 20) packages/cli/src/bundler/macos.rs:762— dioxus_cli::bundler::macos::find_identity_in_keychain has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (17 pts), boolean chains 2, loops 1 (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.
dioxus_cli::serve::runner::analyze_dioxus_value (cognitive 19) packages/cli/src/serve/runner.rs:2196— dioxus_cli::serve::runner::analyze_dioxus_value has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::build::patch::parse_bytes_to_data_segment (cognitive 18) packages/cli/src/build/patch.rs:1639— dioxus_cli::build::patch::parse_bytes_to_data_segment has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dioxus_cli::build::patch::collect_func_ifuncs (cognitive 17) packages/cli/src/build/patch.rs:825— dioxus_cli::build::patch::collect_func_ifuncs has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (7 pts), if/else 2 (6 pts), loops 2 (4 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.
BuildRequest::new (cognitive 116) packages/cli/src/build/request.rs:359— BuildRequest::new has cognitive complexity 116 (threshold 15). Drivers by points: if/else 53 (83 pts), boolean chains 19, match/switch 7 (13 pts), loops 1 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuildRequest::run_fat_link (cognitive 71) packages/cli/src/build/link.rs:847— BuildRequest::run_fat_link has cognitive complexity 71 (threshold 15). Drivers by points: if/else 20 (38 pts), loops 8 (23 pts), match/switch 4 (7 pts), boolean chains 3 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuildRequest::enrich_entitlements_from_config (cognitive 52) packages/cli/src/build/apple.rs:396— BuildRequest::enrich_entitlements_from_config has cognitive complexity 52 (threshold 15). Drivers by points: if/else 29 (38 pts), loops 5 (13 pts), match/switch 1 (nesting depth added 17). 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.
BuildRequest::thin_link_args (cognitive 30) packages/cli/src/build/link.rs:344— BuildRequest::thin_link_args has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (6 pts), boolean chains 4, 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.
BuildRequest::auto_provision_entitlements (cognitive 27) packages/cli/src/build/apple.rs:618— BuildRequest::auto_provision_entitlements has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 4 (6 pts), boolean chains 4, loops 1 (nesting depth added 7). Of this number, 23 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.
BuildRequest::find_rlib_for_crate (cognitive 27) packages/cli/src/build/link.rs:1344— BuildRequest::find_rlib_for_crate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (25 pts), boolean chains 1, loops 1 (nesting depth added 16). 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.
BuildRequest::cargo_build (cognitive 27) packages/cli/src/build/request.rs:1033— BuildRequest::cargo_build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 4 (8 pts), 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.
BuildRequest::write_winres (cognitive 27) packages/cli/src/build/windows.rs:67— BuildRequest::write_winres has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (21 pts), match/switch 4, loops 1 (2 pts) (nesting depth added 6). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
BuildRequest::inject_resources (cognitive 26) packages/cli/src/build/web.rs:418— BuildRequest::inject_resources has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 3, match/switch 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.
BuildRequest::compile_dep_crate (cognitive 23) packages/cli/src/build/link.rs:521— BuildRequest::compile_dep_crate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuildRequest::enabled_cargo_toml_default_features_renderers (cognitive 21) packages/cli/src/build/renderer.rs:47— BuildRequest::enabled_cargo_toml_default_features_renderers has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (4 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. This shape REPEATS in the file: one other method here (BuildRequest::rendererless_features) 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.
BuildRequest::rendererless_features (cognitive 21) packages/cli/src/build/renderer.rs:100— BuildRequest::rendererless_features has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (4 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. This shape REPEATS in the file: one other method here (BuildRequest::enabled_cargo_toml_default_features_renderers) 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.
BuildRequest::cargo_build_arguments (cognitive 21) packages/cli/src/build/request.rs:1689— BuildRequest::cargo_build_arguments has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 3, match/switch 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
BuildRequest::load_rustc_argset (cognitive 21) packages/cli/src/build/request.rs:2446— BuildRequest::load_rustc_argset has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 1 (2 pts) (nesting depth added 15). 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.
BuildRequest::compile_workspace_hotpatch (cognitive 19) packages/cli/src/build/link.rs:135— BuildRequest::compile_workspace_hotpatch has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuildRequest::start_ios_sim (cognitive 16) packages/cli/src/build/apple.rs:85— BuildRequest::start_ios_sim has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (4 pts) (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.
BuildRequest::feature_for_platform_and_renderer (cognitive 16) packages/cli/src/build/renderer.rs:144— BuildRequest::feature_for_platform_and_renderer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 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.
BuildRequest::write_frameworks (cognitive 16) packages/cli/src/build/request.rs:1358— BuildRequest::write_frameworks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 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.
TooManyMethods: BuildRequest packages/cli/src/build/request.rs:243— TooManyMethods — 140 methods, declared across 7 files: build/request.rs (72), build/web.rs (18), build/android.rs (17), build/link.rs (13), +3 more file(s). The bar is 30 methods; this is 110 over it, 4.67× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VirtualDom packages/core/src/virtual_dom.rs:206— TooManyMethods — 102 methods, declared across 7 files: src/mount.rs (41), src/virtual_dom.rs (34), src/scheduler.rs (10), src/arena.rs (7), +3 more file(s). The bar is 30 methods; this is 72 over it, 3.40× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Runtime packages/core/src/runtime.rs:31— TooManyMethods — 61 methods, declared across 2 files: src/runtime.rs (49), src/tasks.rs (12). The bar is 30 methods; this is 31 over it, 2.03× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VNode packages/core/src/nodes.rs:138— TooManyMethods — 59 methods, declared across 5 files: diff/node.rs (31), diff/template.rs (10), src/nodes.rs (8), diff/attributes.rs (6), +1 more file(s). The bar is 30 methods; this is 29 over it, 1.97× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BundleContext packages/cli/src/bundler/mod.rs:26— TooManyMethods — 52 methods, declared across 6 files: bundler/mod.rs (27), bundler/linux.rs (14), bundler/macos.rs (4), bundler/windows.rs (4), +2 more file(s). The bar is 30 methods; this is 22 over it, 1.73× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Writer packages/autofmt/src/writer.rs:14— TooManyMethods — 48 methods, declared across 2 files: src/writer.rs (46), src/prettier_please.rs (2). The bar is 30 methods; this is 18 over it, 1.60× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AppServer packages/cli/src/serve/runner.rs:42— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: Store packages/stores/src/store.rs:110— TooManyMethods — 44 methods, declared across 8 files: impls/btreemap.rs (11), impls/option.rs (11), impls/result.rs (9), impls/vec.rs (4), +4 more file(s). The bar is 30 methods; this is 14 over it, 1.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BaseInterpreter packages/interpreter/src/ts/core.ts:18— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AppBuilder packages/cli/src/build/builder.rs:51— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: App packages/desktop/src/app.rs:25— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HttpError packages/fullstack-core/src/httperror.rs:7— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Workspace packages/cli/src/workspace.rs:15— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Scope packages/core/src/scope_context.rs:56— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (9 lines × 2) packages/cli/src/cli/print.rs:68— packages/cli/src/cli/print.rs:68-76 | packages/cli/src/cli/print.rs:85-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/core-macro/src/props/mod.rs:997— packages/core-macro/src/props/mod.rs:997-1005 | packages/core-macro/src/props/mod.rs:1140-1148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/fullstack-core/src/loader.rs:43— packages/fullstack-core/src/loader.rs:43-51 | packages/fullstack-core/src/server_future.rs:75-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) packages/fullstack-macro/src/lib.rs:672— packages/fullstack-macro/src/lib.rs:672-680 | packages/fullstack-macro/src/lib.rs:682-690 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/router-macro/src/lib.rs:648— packages/router-macro/src/lib.rs:648-656 | packages/router-macro/src/segment.rs:319-327 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) packages/router/src/routable.rs:763— packages/router/src/routable.rs:763-771 | packages/router/src/routable.rs:773-781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/rsx-hotreload/src/extensions.rs:78— packages/rsx-hotreload/src/extensions.rs:78-86 | packages/rsx/src/template_body.rs:43-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) packages/web/src/files.rs:43— packages/web/src/files.rs:43-51 | packages/web/src/files.rs:76-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/manganis/manganis/src/android/mod.rs:20— packages/manganis/manganis/src/android/mod.rs:20-28 | packages/manganis/manganis/src/macro_helpers.rs:13-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) packages/native-dom/src/mutation_writer.rs:59— packages/native-dom/src/mutation_writer.rs:59-67 | packages/oracle/src/renderer.rs:57-65 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) packages/cli/src/build/windows.rs:632— packages/cli/src/build/windows.rs:632-643 | packages/cli/src/build/windows.rs:666-674 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/cli/src/build/apple.rs:225— packages/cli/src/build/apple.rs:225-233 | packages/cli/src/build/apple.rs:259-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/playwright-tests/liveview/src/main.rs:14— packages/playwright-tests/liveview/src/main.rs:14-22 | packages/playwright-tests/web/src/main.rs:16-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:120— examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:120-128 | examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:144-152 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
FixmeComment packages/rsx/src/element.rs:177— // FIXME: I don't want to special case anything - but our delimiter is special cased to a space — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/native-dom/src/mutation_writer.rs:481— // FIXME: support all attribute types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/native-dom/src/mutation_writer.rs:509— // FIXME: more principled handling of special case attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:44— // FIXME media query — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:77— // FIXME media query — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:46— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:47— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:79— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:505— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:63— // FIXME IANA standard names — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:501— // FIXME this is much more complicated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/html/src/elements.rs:502— // FIXME should be a fragment starting with '#' — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/cli/src/serve/output.rs:404— // FIXME(jon): why are we pulling only the first message here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (8 lines × 2) packages/core/src/diff/node.rs:257— packages/core/src/diff/node.rs:257-264 | packages/core/src/diff/node.rs:282-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/oracle/src/renderer.rs:395— packages/oracle/src/renderer.rs:395-402 | packages/oracle/src/renderer.rs:419-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/wasm-split/wasm-split-cli/src/lib.rs:241— packages/wasm-split/wasm-split-cli/src/lib.rs:241-250 | packages/wasm-split/wasm-split-cli/src/lib.rs:316-323 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/native-dom/src/mutation_writer.rs:119— packages/native-dom/src/mutation_writer.rs:119-126 | packages/oracle/src/renderer.rs:117-124 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) packages/native-dom/src/mutation_writer.rs:212— packages/native-dom/src/mutation_writer.rs:212-219 | packages/oracle/src/renderer.rs:210-217 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) packages/native-dom/src/mutation_writer.rs:221— packages/native-dom/src/mutation_writer.rs:221-228 | packages/oracle/src/renderer.rs:219-226 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) packages/generational-box/src/sync.rs:329— packages/generational-box/src/sync.rs:329-336 | packages/generational-box/src/unsync.rs:325-332 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) packages/cli/src/bundler/windows.rs:149— packages/cli/src/bundler/windows.rs:149-156 | packages/cli/src/bundler/windows.rs:157-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/cli/src/bundler/windows.rs:504— packages/cli/src/bundler/windows.rs:504-511 | packages/cli/src/bundler/windows.rs:520-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/desktop/headless_tests/events.rs:500— packages/desktop/headless_tests/events.rs:500-508 | packages/desktop/headless_tests/events.rs:552-559 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/playwright-tests/suspense-carousel/src/main.rs:62— packages/playwright-tests/suspense-carousel/src/main.rs:62-71 | packages/playwright-tests/suspense-carousel/src/main.rs:93-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:231— examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:231-238 | examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:275-282 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:230` calls `LocationPermissionAttributes` and `examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:273` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:203— examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:203-210 | examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationWidget.swift:305-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Off the main sequence: depinfo — depinfo: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: dioxus-cli-telemetry — dioxus-cli-telemetry: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: dioxus-component-manifest — dioxus-component-manifest: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: dioxus-const-vec — dioxus-const-vec: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: lazy-js-bundle — lazy-js-bundle: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: subsecond-types — subsecond-types: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: wasm-used — wasm-used: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: generational-box — generational-box: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
Off the main sequence: dioxus-rsx — dioxus-rsx: abstractness 0.04, instability 0.14, distance 0.82 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: dioxus-asset-resolver — dioxus-asset-resolver: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: dioxus-autofmt — dioxus-autofmt: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: dioxus-core-template — dioxus-core-template: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: subsecond — subsecond: abstractness 0.07, instability 0.20, distance 0.73 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Duplicated block (6 lines × 2) packages/fullstack/src/payloads/msgpack.rs:33— packages/fullstack/src/payloads/msgpack.rs:33-38 | packages/fullstack/src/payloads/msgpack.rs:86-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) packages/stores/src/impls/btreemap.rs:358— packages/stores/src/impls/btreemap.rs:358-363 | packages/stores/src/impls/hashmap.rs:366-371 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) packages/desktop/src/document.rs:43— packages/desktop/src/document.rs:43-48 | packages/liveview/src/document.rs:102-107 — before extracting anything, compare `packages/desktop/src/document.rs` and `packages/liveview/src/document.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) packages/desktop/src/document.rs:75— packages/desktop/src/document.rs:75-80 | packages/liveview/src/document.rs:134-139 — before extracting anything, compare `packages/desktop/src/document.rs` and `packages/liveview/src/document.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) packages/desktop/src/document.rs:114— packages/desktop/src/document.rs:114-119 | packages/liveview/src/document.rs:46-51 — before extracting anything, compare `packages/desktop/src/document.rs` and `packages/liveview/src/document.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) packages/html-internal-macro/src/common.rs:106— packages/html-internal-macro/src/common.rs:106-111 | packages/html-internal-macro/src/elements.rs:591-596 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) packages/liveview/src/document.rs:94— packages/liveview/src/document.rs:94-99 | packages/web/src/document.rs:123-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) packages/native-dom/src/mutation_writer.rs:183— packages/native-dom/src/mutation_writer.rs:183-188 | packages/oracle/src/renderer.rs:181-186 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) packages/router-macro/src/lib.rs:588— packages/router-macro/src/lib.rs:588-593 | packages/router-macro/src/lib.rs:622-628 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) packages/core/src/diff/node.rs:758— packages/core/src/diff/node.rs:758-764 | packages/core/src/diff/node.rs:767-772 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) packages/cli/src/cli/doctor.rs:129— packages/cli/src/cli/doctor.rs:129-134 | packages/cli/src/cli/doctor.rs:187-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) packages/cli/src/bundler/updater.rs:93— packages/cli/src/bundler/updater.rs:93-98 | packages/cli/src/bundler/updater.rs:113-118 — 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.
BuildRequest::new (cyclomatic 85) packages/cli/src/build/request.rs:359— BuildRequest::new has cyclomatic complexity 85 (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.
BuildRequest::run_fat_link (cyclomatic 43) packages/cli/src/build/link.rs:847— BuildRequest::run_fat_link has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BuildRequest::enrich_entitlements_from_config (cyclomatic 36) packages/cli/src/build/apple.rs:396— BuildRequest::enrich_entitlements_from_config has cyclomatic complexity 36 (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.
BuildRequest::cargo_build_arguments (cyclomatic 24) packages/cli/src/build/request.rs:1689— BuildRequest::cargo_build_arguments has cyclomatic complexity 24 (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.
BuildRequest::linker_flavor (cyclomatic 23) packages/cli/src/build/link.rs:1249— BuildRequest::linker_flavor has cyclomatic complexity 23 (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.
BuildRequest::write_winres (cyclomatic 21) packages/cli/src/build/windows.rs:67— BuildRequest::write_winres has cyclomatic complexity 21 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
BuildRequest::auto_provision_entitlements (cyclomatic 20) packages/cli/src/build/apple.rs:618— BuildRequest::auto_provision_entitlements has cyclomatic complexity 20 (threshold 15). Of this number, 16 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.
BuildRequest::thin_link_args (cyclomatic 20) packages/cli/src/build/link.rs:344— BuildRequest::thin_link_args 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.
BuildRequest::cargo_build (cyclomatic 18) packages/cli/src/build/request.rs:1033— BuildRequest::cargo_build 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.
BuildRequest::compile_dep_crate (cyclomatic 17) packages/cli/src/build/link.rs:521— BuildRequest::compile_dep_crate 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.
BuildRequest::android_env_vars (cyclomatic 16) packages/cli/src/build/android.rs:661— BuildRequest::android_env_vars has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function items inside it that branch. 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.
FunctionTooLong: dioxus_fullstack_macro::route_impl_with_route packages/fullstack-macro/src/lib.rs:198— FunctionTooLong — dioxus_fullstack_macro::route_impl_with_route runs 249 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 149 over it, 2.49× 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: dioxus_cli::build::patch::create_undefined_symbol_stub packages/cli/src/build/patch.rs:873— FunctionTooLong — dioxus_cli::build::patch::create_undefined_symbol_stub runs 212 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dioxus_cli::serve::serve_all packages/cli/src/serve/mod.rs:42— FunctionTooLong — dioxus_cli::serve::serve_all runs 163 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dioxus_core::suspense::component::suspense_diff packages/core/src/suspense/component.rs:618— FunctionTooLong — dioxus_core::suspense::component::suspense_diff runs 163 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: const_serialize_macro::derive_parse packages/const-serialize-macro/src/lib.rs:23— FunctionTooLong — const_serialize_macro::derive_parse runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dioxus_cli::build::apple::compile_apple_widget packages/cli/src/build/apple.rs:1557— FunctionTooLong — dioxus_cli::build::apple::compile_apple_widget runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: dioxus_cli::build::patch::create_wasm_jump_table packages/cli/src/build/patch.rs:479— FunctionTooLong — dioxus_cli::build::patch::create_wasm_jump_table runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dioxus_cli::build::apple::compile_swift_sources packages/cli/src/build/apple.rs:1049— FunctionTooLong — dioxus_cli::build::apple::compile_swift_sources runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dioxus_stores_macro::derive::derive_store_enum packages/stores-macro/src/derive.rs:412— FunctionTooLong — dioxus_stores_macro::derive::derive_store_enum runs 121 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dioxus_cli::build::apple::create_framework_bundle packages/cli/src/build/apple.rs:1792— FunctionTooLong — dioxus_cli::build::apple::create_framework_bundle runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: dioxus_cli::build::assets::extract_symbols_from_file packages/cli/src/build/assets.rs:487— FunctionTooLong — dioxus_cli::build::assets::extract_symbols_from_file runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.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.
Duplicated block (10 lines × 2) packages/cli/src/build/patch.rs:138— packages/cli/src/build/patch.rs:138-147 | packages/cli/src/build/patch.rs:162-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) packages/cli/src/build/patch.rs:1694— packages/cli/src/build/patch.rs:1694-1703 | packages/wasm-split/wasm-split-cli/src/lib.rs:1526-1535 — before extracting anything, compare `packages/cli/src/build/patch.rs` and `packages/wasm-split/wasm-split-cli/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) packages/fullstack-core/src/loader.rs:57— packages/fullstack-core/src/loader.rs:57-66 | packages/fullstack-core/src/server_future.rs:85-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) packages/wasm-split/wasm-split-cli/src/lib.rs:1253— packages/wasm-split/wasm-split-cli/src/lib.rs:1253-1262 | packages/wasm-split/wasm-split-cli/src/lib.rs:1287-1296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) packages/desktop/src/document.rs:51— packages/desktop/src/document.rs:51-60 | packages/liveview/src/document.rs:110-119 — before extracting anything, compare `packages/desktop/src/document.rs` and `packages/liveview/src/document.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) packages/desktop/src/document.rs:63— packages/desktop/src/document.rs:63-72 | packages/liveview/src/document.rs:122-131 — before extracting anything, compare `packages/desktop/src/document.rs` and `packages/liveview/src/document.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) packages/html/src/events/mounted.rs:230— packages/html/src/events/mounted.rs:230-239 | packages/html/src/events/resize.rs:149-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) packages/cli/src/config/manifest_mapper.rs:299— packages/cli/src/config/manifest_mapper.rs:299-308 | packages/cli/src/config/manifest_mapper.rs:338-347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) packages/cli/src/bundler/linux.rs:660— packages/cli/src/bundler/linux.rs:660-669 | packages/cli/src/bundler/linux.rs:676-685 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) packages/cli/src/build/apple.rs:1146— packages/cli/src/build/apple.rs:1146-1155 | packages/cli/src/build/apple.rs:1686-1695 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) packages/playwright-tests/fullstack/src/main.rs:158— packages/playwright-tests/fullstack/src/main.rs:158-167 | packages/playwright-tests/web/src/main.rs:147-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
dioxus_cli::serve::serve_all (cyclomatic 46) packages/cli/src/serve/mod.rs:42— dioxus_cli::serve::serve_all has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dioxus_cli::build::patch::create_undefined_symbol_stub (cyclomatic 40) packages/cli/src/build/patch.rs:873— dioxus_cli::build::patch::create_undefined_symbol_stub has cyclomatic complexity 40 (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.
dioxus_cli::build::patch::create_wasm_jump_table (cyclomatic 33) packages/cli/src/build/patch.rs:479— dioxus_cli::build::patch::create_wasm_jump_table has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dioxus_cli::opt::js::lexer::has_module_syntax (cyclomatic 26) packages/cli/src/opt/js.rs:158— dioxus_cli::opt::js::lexer::has_module_syntax has cyclomatic complexity 26 (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.
dioxus_cli::build::patch::prepare_wasm_base_module (cyclomatic 20) packages/cli/src/build/patch.rs:1336— dioxus_cli::build::patch::prepare_wasm_base_module 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.
dioxus_cli::build::apple::compile_swift_sources (cyclomatic 17) packages/cli/src/build/apple.rs:1049— dioxus_cli::build::apple::compile_swift_sources 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.
dioxus_cli::build::assets::find_wasm_symbol_offsets (cyclomatic 17) packages/cli/src/build/assets.rs:319— dioxus_cli::build::assets::find_wasm_symbol_offsets 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.
dioxus_cli::serve::runner::analyze_cargo_value (cyclomatic 17) packages/cli/src/serve/runner.rs:2006— dioxus_cli::serve::runner::analyze_cargo_value 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.
dioxus_cli::build::assets::extract_symbols_from_file (cyclomatic 16) packages/cli/src/build/assets.rs:487— dioxus_cli::build::assets::extract_symbols_from_file 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.
dioxus_cli::config::manifest::simplify_schema (cyclomatic 16) packages/cli/src/config/manifest.rs:1476— dioxus_cli::config::manifest::simplify_schema 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.
Duplicated block (7 lines × 2) packages/cli/src/build/patch.rs:1657— packages/cli/src/build/patch.rs:1657-1663 | packages/wasm-split/wasm-split-cli/src/lib.rs:1500-1506 — before extracting anything, compare `packages/cli/src/build/patch.rs` and `packages/wasm-split/wasm-split-cli/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) packages/cli/src/serve/runner.rs:1759— packages/cli/src/serve/runner.rs:1759-1765 | packages/cli/src/serve/runner.rs:1783-1789 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) packages/fullstack/src/magic.rs:535— packages/fullstack/src/magic.rs:535-541 | packages/fullstack/src/magic.rs:572-578 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) packages/html-internal-macro/src/common.rs:121— packages/html-internal-macro/src/common.rs:121-127 | packages/html-internal-macro/src/elements.rs:649-655 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/native-dom/src/mutation_writer.rs:78— packages/native-dom/src/mutation_writer.rs:78-84 | packages/oracle/src/renderer.rs:76-82 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) packages/native-dom/src/mutation_writer.rs:86— packages/native-dom/src/mutation_writer.rs:86-92 | packages/oracle/src/renderer.rs:84-90 — before extracting anything, compare `packages/native-dom/src/mutation_writer.rs` and `packages/oracle/src/renderer.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) packages/cli/src/esbuild.rs:86— packages/cli/src/esbuild.rs:86-92 | packages/cli/src/tailwind.rs:205-212 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/cli/src/bundler/linux.rs:491— packages/cli/src/bundler/linux.rs:491-497 | packages/cli/src/bundler/macos.rs:79-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/html/src/events/drag.rs:32— packages/html/src/events/drag.rs:32-38 | packages/html/src/events/mouse.rs:24-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) packages/fuzz/src/mutator.rs:392— packages/fuzz/src/mutator.rs:392-398 | packages/fuzz/src/mutator.rs:438-444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: ServerFnDecoder (LCOM4 13) packages/fullstack/src/magic.rs:63— ServerFnDecoder's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DesktopService (LCOM4 7) packages/desktop/src/desktop_context.rs:102— DesktopService's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Element (LCOM4 6) packages/rsx/src/element.rs:16— Element's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DesktopDocument (LCOM4 5) packages/desktop/src/document.rs:15— DesktopDocument's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ServerFnEncoder (LCOM4 5) packages/fullstack/src/magic.rs:54— ServerFnEncoder's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: VNodeSpec (LCOM4 5) packages/fuzz/src/model.rs:90— VNodeSpec's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LiveviewDocument (LCOM4 5) packages/liveview/src/document.rs:84— LiveviewDocument's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WasmLayer (LCOM4 5) packages/logger/src/wasm.rs:53— WasmLayer's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Scope (LCOM4 4) packages/core/src/scope_context.rs:56— Scope's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
BundleContext::bundle_macos_app (cyclomatic 22) packages/cli/src/bundler/macos.rs:44— BundleContext::bundle_macos_app 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.
BundleContext::bundle_project (cyclomatic 22) packages/cli/src/bundler/mod.rs:134— BundleContext::bundle_project has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: AppCategory::freedesktop_categories (cyclomatic 40) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
BundleContext::bundle_linux_rpm (cyclomatic 19) packages/cli/src/bundler/linux.rs:229— BundleContext::bundle_linux_rpm 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.
BundleContext::bundle_windows_msi (cyclomatic 17) packages/cli/src/bundler/windows.rs:36— BundleContext::bundle_windows_msi 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.
BundleContext::generate_linux_control_file (cyclomatic 16) packages/cli/src/bundler/linux.rs:860— BundleContext::generate_linux_control_file 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.
BundleContext::new (cyclomatic 16) packages/cli/src/bundler/mod.rs:40— BundleContext::new has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: AppCategory::freedesktop_categories (cyclomatic 40) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
BundleContext::bundle_windows_nsis (cyclomatic 16) packages/cli/src/bundler/windows.rs:373— BundleContext::bundle_windows_nsis 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.
BundleContext::bundle_macos_app (cognitive 53) packages/cli/src/bundler/macos.rs:44— BundleContext::bundle_macos_app has cognitive complexity 53 (threshold 15). Drivers by points: if/else 24 (42 pts), loops 3 (7 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BundleContext::bundle_linux_rpm (cognitive 29) packages/cli/src/bundler/linux.rs:229— BundleContext::bundle_linux_rpm has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 5 (6 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BundleContext::generate_linux_control_file (cognitive 25) packages/cli/src/bundler/linux.rs:860— BundleContext::generate_linux_control_file has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 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.
BundleContext::bundle_project (cognitive 23) packages/cli/src/bundler/mod.rs:134— BundleContext::bundle_project has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (7 pts), match/switch 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.
BundleContext::new (cognitive 20) packages/cli/src/bundler/mod.rs:40— BundleContext::new has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 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.
BundleContext::bundle_windows_msi (cognitive 19) packages/cli/src/bundler/windows.rs:36— BundleContext::bundle_windows_msi has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (16 pts), loops 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BundleContext::bundle_windows_nsis (cognitive 18) packages/cli/src/bundler/windows.rs:373— BundleContext::bundle_windows_nsis has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, boolean chains 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.
ClassTooLong: BuildRequest packages/cli/src/build/request.rs:243— ClassTooLong — 1498 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 140 methods, 2 blocks, lines 243-3211. The bar is 400 significant lines; this is 1098 over it, 3.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppServer packages/cli/src/serve/runner.rs:42— ClassTooLong — 933 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 2 blocks, lines 42-1795. The bar is 400 significant lines; this is 533 over it, 2.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: Writer packages/autofmt/src/writer.rs:14— ClassTooLong — 870 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 48 methods, 2 blocks, lines 14-1413. The bar is 400 significant lines; this is 470 over it, 2.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.
ClassTooLong: TraceController packages/cli/src/logging.rs:82— ClassTooLong — 657 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 3 blocks, lines 82-1162. The bar is 400 significant lines; this is 257 over it, 1.64× 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: Output packages/cli/src/serve/output.rs:46— ClassTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 3 blocks, lines 46-1067. The bar is 400 significant lines; this is 230 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Splitter packages/wasm-split/wasm-split-cli/src/lib.rs:27— ClassTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 27-1155. The bar is 400 significant lines; this is 189 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FfiBridgeParser packages/manganis/manganis-macro/src/ffi.rs:254— ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 2 blocks, lines 254-1084. The bar is 400 significant lines; this is 70 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.
AC3 · Page structure· Page without a main landmark · ×6
Page without a main landmark packages/cli/assets/web/dev.index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="main">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/cli/assets/web/dev.loading.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/cli/assets/web/prod.index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="main">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/desktop/src/assets/dev.index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="main">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/desktop/src/assets/prod.index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="main">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/liveview/src/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="main">, so there is no content here to wrap — render the <main> from the component mounted into it.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×6
Duplicated block (15 lines × 2) packages/cli/src/serve/output.rs:441— packages/cli/src/serve/output.rs:441-455 | packages/cli/src/serve/output.rs:1041-1055 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) packages/core-macro/src/props/mod.rs:1595— packages/core-macro/src/props/mod.rs:1595-1609 | packages/core-macro/src/props/mod.rs:1625-1639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) packages/fullstack/src/magic.rs:737— packages/fullstack/src/magic.rs:737-751 | packages/fullstack/src/magic.rs:788-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) packages/router-macro/src/lib.rs:360— packages/router-macro/src/lib.rs:360-374 | packages/router-macro/src/lib.rs:455-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) packages/web/src/history.rs:137— packages/web/src/history.rs:137-151 | packages/web/src/history.rs:291-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/LocationActivityAttributes.swift:27— examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/LocationActivityAttributes.swift:27-41 | examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationActivityAttributes.swift:27-41 — before extracting anything, compare `examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/LocationActivityAttributes.swift` and `examples/01-app-demos/geolocation-native-plugin/src/ios/widget/Sources/LocationActivityAttributes.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) packages/cli/src/build/builder.rs:1010— packages/cli/src/build/builder.rs:1010-1023 | packages/cli/src/build/builder.rs:1072-1085 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) packages/cli/src/bundler/mod.rs:77— packages/cli/src/bundler/mod.rs:77-90 | packages/cli/src/bundler/mod.rs:320-333 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) packages/fullstack-core/src/error.rs:218— packages/fullstack-core/src/error.rs:218-231 | packages/fullstack-core/src/error.rs:239-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) packages/cli/src/bundler/linux.rs:761— packages/cli/src/bundler/linux.rs:761-774 | packages/cli/src/bundler/linux.rs:783-796 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) packages/desktop/headless_tests/events.rs:561— packages/desktop/headless_tests/events.rs:561-574 | packages/desktop/headless_tests/forms.rs:84-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) packages/playwright-tests/web-hash-routing/src/main.rs:28— packages/playwright-tests/web-hash-routing/src/main.rs:28-41 | packages/playwright-tests/web-routing/src/main.rs:24-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×6
Untrusted text written into markup unescaped REDACTED:17— `raw_manifest` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/cli/assets/ios/ios.plist.hbs:90— `plist_entries` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/cli/assets/ios/ios.plist.hbs:93— `raw_plist` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/cli/assets/macos/mac.plist.hbs:57— `plist_entries` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/cli/assets/macos/mac.plist.hbs:60— `raw_plist` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/interpreter/src/ts/set_attribute.ts:64— `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Change coupling: sync.rs ↔ unsync.rs packages/generational-box/src/sync.rs:1— `packages/generational-box/src/sync.rs` and `packages/generational-box/src/unsync.rs` change together 91% of the time (10 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 10 shared commits counted here, the most recent 3 are `f48aec7e` fix: use floats for pointer events (#4708); `f95d8e46` Fix empty borrow location warnings (#4593); `47c87568` Fix event handler memory leak (#2298) — run `git show` on any of them.
Change coupling: impls.rs ↔ signal.rs packages/signals/src/impls.rs:1— `packages/signals/src/impls.rs` and `packages/signals/src/signal.rs` change together 59% of the time (13 of the 22 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 13 shared commits counted here, the most recent 3 are `24ebc1e6` added better documentation and code snipppets for the use_resource, u…; `df0d45be` added better documentation and code snipppets for the use_resource, u…; `94c0c2e5` remove some old manual implementations of helpers — run `git show` on any of them.
Change coupling: fragment.rs ↔ virtual_dom.rs packages/core/src/fragment.rs:1— `packages/core/src/fragment.rs` and `packages/core/src/virtual_dom.rs` change together 57% of the time (13 of the 23 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 13 shared commits counted here, the most recent 3 are `3267ddec` more consistent naming of the root component in core; `fd0a53ab` make all core tests compile; `1794debf` fix components that take no arguments — run `git show` on any of them.
Change coupling: desktop_context.rs ↔ document.rs packages/desktop/src/desktop_context.rs:1— `packages/desktop/src/desktop_context.rs` and `packages/desktop/src/document.rs` change together 50% of the time (7 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 7 shared commits counted here, the most recent 3 are `25a64d97` Fixed the multiple window closing issue, where the two multiwindow ex…; `3865f440` make desktop compile (at that commit the file was still `packages/desktop/src/eval.rs`); `06049089` Clean up desktop even more (at that commit the file was still `packages/desktop/src/eval.rs`) — run `git show` on any of them.
Change coupling: lib.rs ↔ lib.rs packages/core/src/lib.rs:1— `packages/core/src/lib.rs` and `packages/html-internal-macro/src/lib.rs` change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `36e9eb11` partially restore spreading attributes; `b60671e0` fix non extending attributes; `7b51bb80` WIP: add extends to the props macro — run `git show` on any of them.
Duplicated block (12 lines × 2) packages/cli/src/build/patch.rs:807— packages/cli/src/build/patch.rs:807-818 | packages/wasm-split/wasm-split-cli/src/lib.rs:823-834 — before extracting anything, compare `packages/cli/src/build/patch.rs` and `packages/wasm-split/wasm-split-cli/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) packages/const-serialize/src/array.rs:53— packages/const-serialize/src/array.rs:53-64 | packages/const-serialize/src/list.rs:107-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) packages/core-macro/src/props/mod.rs:1009— packages/core-macro/src/props/mod.rs:1009-1020 | packages/core-macro/src/props/mod.rs:1152-1163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) packages/manganis/manganis-macro/src/ffi.rs:477— packages/manganis/manganis-macro/src/ffi.rs:477-488 | packages/manganis/manganis-macro/src/ffi.rs:886-897 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) packages/desktop/headless_tests/events.rs:97— packages/desktop/headless_tests/events.rs:97-108 | packages/desktop/headless_tests/events.rs:263-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard examples/assets/radio.css:28— `.bounce` moves (`animation: boomBox 0.5s 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/assets/visible.css:21— `.animated-text` moves (`transition: opacity 1s ease, transform 1s 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/01-app-demos/hackernews/assets/hackernews.css:16— `.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/01-app-demos/ecommerce-site/public/loading.css:16— `.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Hotspot: packages/native-dom/src/mutation_writer.rs packages/native-dom/src/mutation_writer.rs:404— packages/native-dom/src/mutation_writer.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in BlitzBackend::set_attribute_impl at line 404. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:32:28 +00:00' --until='2026-10-25 15:32:28 +00:00' --full-history --no-merges -- packages/native-dom/src/mutation_writer.rs`: 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/desktop/src/webview.rs packages/desktop/src/webview.rs:318— packages/desktop/src/webview.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in WebviewInstance::new at line 318. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:32:28 +00:00' --until='2026-10-25 15:32:28 +00:00' --full-history --no-merges -- packages/desktop/src/webview.rs`: 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/cli/src/cli/update.rs packages/cli/src/cli/update.rs:34— packages/cli/src/cli/update.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SelfUpdate::self_update at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:32:28 +00:00' --until='2026-10-25 15:32:28 +00:00' --full-history --no-merges -- packages/cli/src/cli/update.rs`: 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/desktop/src/app.rs packages/desktop/src/app.rs:317— packages/desktop/src/app.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in App::handle_hot_reload_msg at line 317. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:32:28 +00:00' --until='2026-10-25 15:32:28 +00:00' --full-history --no-merges -- packages/desktop/src/app.rs`: 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.
Writer::write_partial_expr (cognitive 147) packages/autofmt/src/writer.rs:956— Writer::write_partial_expr has cognitive complexity 147 (threshold 15). Drivers by points: if/else 31 (105 pts), loops 9 (33 pts), boolean chains 9 (nesting depth added 98). 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.
Writer::write_rsx_block (cognitive 42) packages/autofmt/src/writer.rs:299— Writer::write_rsx_block has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (28 pts), boolean chains 11, loops 1 (2 pts), match/switch 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.
Writer::write_attributes (cognitive 23) packages/autofmt/src/writer.rs:477— Writer::write_attributes has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, match/switch 3 (5 pts), 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.
Writer::is_short_attrs (cognitive 18) packages/autofmt/src/writer.rs:868— Writer::is_short_attrs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), match/switch 2 (6 pts), loops 3 (5 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.
AppServer::handle_file_change (cognitive 114) packages/cli/src/serve/runner.rs:387— AppServer::handle_file_change has cognitive complexity 114 (threshold 15). Drivers by points: if/else 32 (90 pts), loops 5 (15 pts), boolean chains 5, match/switch 2 (4 pts) (nesting depth added 70). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppServer::workspace_dep_chain (cognitive 26) packages/cli/src/serve/runner.rs:1370— AppServer::workspace_dep_chain has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (5 pts), match/switch 2 (5 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.
AppServer::wait (cognitive 20) packages/cli/src/serve/runner.rs:306— AppServer::wait has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 3 (7 pts), match/switch 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AppServer::watch_filesystem (cognitive 19) packages/cli/src/serve/runner.rs:1190— AppServer::watch_filesystem has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (5 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.
Splitter::build_call_graph (cognitive 40) packages/wasm-split/wasm-split-cli/src/lib.rs:927— Splitter::build_call_graph has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 11 (16 pts), match/switch 2 (3 pts) (nesting depth added 17). Of this number, 30 points are the body's own statements and 10 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.
Splitter::create_ifunc_initializers (cognitive 29) packages/wasm-split/wasm-split-cli/src/lib.rs:557— Splitter::create_ifunc_initializers has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 6 (10 pts), match/switch 1 (2 pts) (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.
Splitter::replace_segments_with_holes (cognitive 22) packages/wasm-split/wasm-split-cli/src/lib.rs:532— Splitter::replace_segments_with_holes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 3 (13 pts), loops 3 (7 pts), match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Splitter::clear_data_segments (cognitive 21) packages/wasm-split/wasm-split-cli/src/lib.rs:739— Splitter::clear_data_segments has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (18 pts), 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
Duplicated block (11 lines × 2) packages/cli/src/logging.rs:812— packages/cli/src/logging.rs:812-822 | packages/cli/src/logging.rs:834-844 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) packages/manganis/manganis-macro/src/ffi.rs:688— packages/manganis/manganis-macro/src/ffi.rs:688-698 | packages/manganis/manganis-macro/src/ffi.rs:1039-1049 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) packages/subsecond/subsecond/src/lib.rs:412— packages/subsecond/subsecond/src/lib.rs:412-422 | packages/subsecond/subsecond/src/lib.rs:459-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) packages/cli/src/build/apple.rs:1811— packages/cli/src/build/apple.rs:1811-1821 | packages/cli/src/build/apple.rs:1871-1881 — 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.
Outbound HTTP without resilience packages/cli/src/build/builder.rs:2135— `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/cli/src/http_client.rs:31— `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/cli/src/http_client.rs:43— `reqwest::blocking::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/fullstack/src/client.rs:145— `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement examples/assets/calculator.css:26— `button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/assets/todomvc.css:37— `:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/assets/weatherapp.css:1182— `.focus\:outline-none:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Writer::write_partial_expr (cyclomatic 46) packages/autofmt/src/writer.rs:956— Writer::write_partial_expr has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Writer::write_rsx_block (cyclomatic 31) packages/autofmt/src/writer.rs:299— Writer::write_rsx_block has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Writer::write_attributes (cyclomatic 19) packages/autofmt/src/writer.rs:477— Writer::write_attributes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TraceController::command_anonymized (cyclomatic 31) packages/cli/src/logging.rs:805— TraceController::command_anonymized has cyclomatic complexity 31 (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.
TraceController::main (cyclomatic 17) packages/cli/src/logging.rs:133— TraceController::main 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.
TraceController::on_event (cyclomatic 16) packages/cli/src/logging.rs:1051— TraceController::on_event 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.
DiffState::diff_keyed_children (cognitive 27) packages/core/src/diff/iterator.rs:231— DiffState::diff_keyed_children has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 8 (11 pts), boolean chains 4 (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.
DiffState::create_or_diff_placed_range (cognitive 20) packages/core/src/diff/iterator.rs:465— DiffState::create_or_diff_placed_range has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffState::execute_fragment_plan (cognitive 16) packages/core/src/diff/iterator.rs:372— DiffState::execute_fragment_plan has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (7 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppBuilder::get_android_device_transport_id (cognitive 24) packages/cli/src/build/builder.rs:1861— AppBuilder::get_android_device_transport_id has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 1 (3 pts) (nesting depth added 16). 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.
AppBuilder::wait (cognitive 23) packages/cli/src/build/builder.rs:192— AppBuilder::wait has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 6 (10 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AppBuilder::get_ios_device_uuid (cognitive 18) packages/cli/src/build/builder.rs:1138— AppBuilder::get_ios_device_uuid has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Duplicated block (16 lines × 2) packages/fullstack/src/payloads/websocket.rs:182— packages/fullstack/src/payloads/websocket.rs:182-197 | packages/fullstack/src/payloads/websocket.rs:226-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) packages/cli/src/bundler/windows.rs:330— packages/cli/src/bundler/windows.rs:330-345 | packages/cli/src/bundler/windows.rs:595-610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) packages/cli/src/tailwind.rs:182— packages/cli/src/tailwind.rs:182-197 | packages/cli/src/wasm_bindgen.rs:247-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
AppBuilder::wait (cyclomatic 39) packages/cli/src/build/builder.rs:192— AppBuilder::wait has cyclomatic complexity 39 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AppBuilder::finish_build (cyclomatic 18) packages/cli/src/build/builder.rs:501— AppBuilder::finish_build has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Output::render_gauges (cyclomatic 27) packages/cli/src/serve/output.rs:518— Output::render_gauges has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Output::tracemsg_to_lines (cyclomatic 23) packages/cli/src/serve/output.rs:940— Output::tracemsg_to_lines has cyclomatic complexity 23 (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.
FieldBuilderAttr::apply_meta (cognitive 42) packages/core-macro/src/props/mod.rs:351— FieldBuilderAttr::apply_meta has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (31 pts), match/switch 5 (11 pts) (nesting depth added 23). 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.
FieldBuilderAttr::with (cognitive 17) packages/core-macro/src/props/mod.rs:304— FieldBuilderAttr::with has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), boolean chains 2, match/switch 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.
Output::tracemsg_to_lines (cognitive 27) packages/cli/src/serve/output.rs:940— Output::tracemsg_to_lines has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 4 (11 pts), loops 3 (7 pts), if/else 2 (6 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.
Output::push_stdio (cognitive 16) packages/cli/src/serve/output.rs:339— Output::push_stdio has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ConstStr::rsplit_once (cognitive 26) packages/const-serialize/src/str.rs:160— ConstStr::rsplit_once has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConstStr::split_once (cognitive 24) packages/const-serialize/src/str.rs:214— ConstStr::split_once has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TraceController::on_event (cognitive 24) packages/cli/src/logging.rs:1051— TraceController::on_event has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 2 (5 pts), 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.
TraceController::main (cognitive 17) packages/cli/src/logging.rs:133— TraceController::main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 3, match/switch 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.
const_serialize::list::deserialize_const_list (cognitive 21) packages/const-serialize/src/list.rs:68— const_serialize::list::deserialize_const_list has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (4 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.
const_serialize::cbor::item_length (cognitive 17) packages/const-serialize/src/cbor.rs:66— const_serialize::cbor::item_length has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (2 pts), match/switch 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.
App::persist_window_state (cognitive 19) packages/desktop/src/app.rs:601— App::persist_window_state has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 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.
App::handle_hot_reload_msg (cognitive 18) packages/desktop/src/app.rs:317— App::handle_hot_reload_msg has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (4 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (18 lines × 2) packages/cli/src/build/patch.rs:1748— packages/cli/src/build/patch.rs:1748-1765 | packages/wasm-split/wasm-split-cli/src/lib.rs:1162-1179 — before extracting anything, compare `packages/cli/src/build/patch.rs` and `packages/wasm-split/wasm-split-cli/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) packages/fullstack/src/payloads/msgpack.rs:49— packages/fullstack/src/payloads/msgpack.rs:49-66 | packages/fullstack/src/payloads/msgpack.rs:102-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–14 lines × 2) packages/cli/src/bundler/windows.rs:80— packages/cli/src/bundler/windows.rs:80-91 | packages/cli/src/bundler/windows.rs:411-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–14 lines × 2) packages/core-macro/src/props/mod.rs:388— packages/core-macro/src/props/mod.rs:388-401 | packages/core-macro/src/props/mod.rs:1711-1722 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) packages/cli/src/build/apple.rs:1823— packages/cli/src/build/apple.rs:1823-1835 | packages/cli/src/build/apple.rs:1883-1895 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) packages/desktop/headless_tests/events.rs:523— packages/desktop/headless_tests/events.rs:523-535 | packages/desktop/headless_tests/events.rs:568-580 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 3) packages/html/src/events/drag.rs:42— packages/html/src/events/drag.rs:42-47 | packages/html/src/events/mouse.rs:34-39 | packages/html/src/events/mouse.rs:110-115 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) packages/router-macro/src/lib.rs:588— packages/router-macro/src/lib.rs:588-593 | packages/router-macro/src/lib.rs:604-609 | packages/router-macro/src/lib.rs:623-628 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) packages/cli/src/bundler/linux.rs:180— packages/cli/src/bundler/linux.rs:180-184 | packages/cli/src/bundler/linux.rs:187-191 | packages/cli/src/bundler/linux.rs:194-198 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) packages/document/src/elements/link.rs:62— packages/document/src/elements/link.rs:62-66 | packages/document/src/elements/meta.rs:23-27 | packages/document/src/elements/style.rs:23-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Weak hash algorithm packages/cli/src/bundler/linux.rs:1079— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/cli/src/bundler/tools.rs:239— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×1
Heading level jumps from h1 to h4 packages/cli/assets/web/dev.loading.html:268— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast colour pair in CSS (3.1:1) examples/01-app-demos/file-explorer/assets/fileexplorer.css:14— `/* header` sets color: white on background-color: #2196F3 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
ServerFnArgs::parse (cyclomatic 52) packages/fullstack-macro/src/lib.rs:1513— ServerFnArgs::parse has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppServer::handle_file_change (cyclomatic 46) packages/cli/src/serve/runner.rs:387— AppServer::handle_file_change has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RunArgs::run (cyclomatic 44) packages/cli/src/cli/run.rs:23— RunArgs::run has cyclomatic complexity 44 (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.
Doctor::doctor (cyclomatic 41) packages/cli/src/cli/doctor.rs:11— Doctor::doctor has cyclomatic complexity 41 (threshold 15). Of this number, 39 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.
Used::new (cyclomatic 41) packages/wasm-split/wasm-used/src/lib.rs:121— Used::new has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
serialize.serializeEvent (cyclomatic 33) packages/interpreter/src/ts/serialize.ts:15— serialize.serializeEvent has cyclomatic complexity 33 (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.
dioxus_desktop::launch::launch_virtual_dom_blocking (cyclomatic 29) packages/desktop/src/launch.rs:60— dioxus_desktop::launch::launch_virtual_dom_blocking has cyclomatic complexity 29 (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.
SsrRendererPool::render_to (cyclomatic 28) packages/fullstack-server/src/ssr.rs:96— SsrRendererPool::render_to has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Renderer::render_template (cyclomatic 28) packages/ssr/src/renderer.rs:103— Renderer::render_template has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FieldBuilderAttr::apply_meta (cyclomatic 26) packages/core-macro/src/props/mod.rs:351— FieldBuilderAttr::apply_meta 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.
ForeignType::from_type (cyclomatic 26) packages/manganis/manganis-macro/src/ffi.rs:54— ForeignType::from_type 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.
RouteEnum::parse (cyclomatic 26) packages/router-macro/src/lib.rs:283— RouteEnum::parse has cyclomatic complexity 26 (threshold 15). Of this number, 25 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.
RsxBlock::parse_inner (cyclomatic 26) packages/rsx/src/rsx_block.rs:69— RsxBlock::parse_inner 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.
LinkAction::run_link_inner (cyclomatic 24) packages/cli/src/cli/link.rs:131— LinkAction::run_link_inner has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Splitter::build_call_graph (cyclomatic 23) packages/wasm-split/wasm-split-cli/src/lib.rs:927— Splitter::build_call_graph has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebviewInstance::new (cyclomatic 22) packages/desktop/src/webview.rs:318— WebviewInstance::new 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.
FfiBridgeParser::generate_android_function (cyclomatic 22) packages/manganis/manganis-macro/src/ffi.rs:471— FfiBridgeParser::generate_android_function 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.
const_serialize_macro::derive_parse (cyclomatic 21) packages/const-serialize-macro/src/lib.rs:23— const_serialize_macro::derive_parse 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.
BlitzBackend::set_attribute_impl (cyclomatic 20) packages/native-dom/src/mutation_writer.rs:404— BlitzBackend::set_attribute_impl has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to one function item 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.
dioxus_router::components::link::Link (cyclomatic 20) packages/router/src/components/link.rs:139— dioxus_router::components::link::Link 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.
set_attribute.setAttributeInner (cyclomatic 20) packages/interpreter/src/ts/set_attribute.ts:4— set_attribute.setAttributeInner has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: set_attribute.isBoolAttr (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
dioxus_autofmt::prettier_please::unparse_expr (cyclomatic 19) packages/autofmt/src/prettier_please.rs:20— dioxus_autofmt::prettier_please::unparse_expr 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.
Workspace::find_main_package (cyclomatic 19) packages/cli/src/workspace.rs:315— Workspace::find_main_package 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.
SelfUpdate::self_update (cyclomatic 18) packages/cli/src/cli/update.rs:34— SelfUpdate::self_update 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.
ManifestMapper::map_background_modes (cyclomatic 18) packages/cli/src/config/manifest_mapper.rs:552— ManifestMapper::map_background_modes 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.
DiffState::diff_keyed_children (cyclomatic 18) packages/core/src/diff/iterator.rs:231— DiffState::diff_keyed_children has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
dioxus_fullstack_macro::route_impl_with_route (cyclomatic 18) packages/fullstack-macro/src/lib.rs:198— dioxus_fullstack_macro::route_impl_with_route has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
prune (cyclomatic 18) .github/actions/prune-cargo-target/lib.js:70— prune 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.
HotpatchModuleCache::new (cyclomatic 17) packages/cli/src/build/patch.rs:120— HotpatchModuleCache::new 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.
ComponentCommand::run (cyclomatic 17) packages/cli/src/cli/component.rs:88— ComponentCommand::run has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CompiledRoute::from_route (cyclomatic 17) packages/fullstack-macro/src/lib.rs:630— CompiledRoute::from_route has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
manganis_core::css_module::collect_css_idents (cyclomatic 17) packages/manganis/manganis-core/src/css_module.rs:120— manganis_core::css_module::collect_css_idents 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.
dioxus_web::run (cyclomatic 17) packages/web/src/lib.rs:53— dioxus_web::run 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.
LinkProps::attributes (cyclomatic 16) packages/document/src/elements/link.rs:60— LinkProps::attributes 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.
RouteParser::new (cyclomatic 16) packages/fullstack-macro/src/lib.rs:976— RouteParser::new 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.
dioxus_liveview::pool::run (cyclomatic 16) packages/liveview/src/pool.rs:123— dioxus_liveview::pool::run has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HackComment packages/interpreter/src/ts/native.ts:552— // hack for android since we CANT SEND BODIES (because wry is using shouldInterceptRequest) — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
ServerFnArgs::parse (cognitive 125) packages/fullstack-macro/src/lib.rs:1513— ServerFnArgs::parse has cognitive complexity 125 (threshold 15). Drivers by points: if/else 45 (116 pts), match/switch 2 (5 pts), boolean chains 2, loops 2 (nesting depth added 74). 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.
RouteEnum::parse (cognitive 78) packages/router-macro/src/lib.rs:283— RouteEnum::parse has cognitive complexity 78 (threshold 15). Drivers by points: if/else 17 (48 pts), loops 7 (20 pts), match/switch 3 (10 pts) (nesting depth added 51). Of this number, 73 points are the body's own statements and 5 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.
Used::new (cognitive 77) packages/wasm-split/wasm-used/src/lib.rs:121— Used::new has cognitive complexity 77 (threshold 15). Drivers by points: if/else 12 (34 pts), loops 13 (26 pts), match/switch 5 (15 pts), boolean chains 2 (nesting depth added 45). To reduce it, split the body into named stages: move each independent 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::render_template (cognitive 60) packages/ssr/src/renderer.rs:103— Renderer::render_template has cognitive complexity 60 (threshold 15). Drivers by points: if/else 14 (39 pts), loops 4 (12 pts), match/switch 3 (9 pts) (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SsrRendererPool::render_to (cognitive 52) packages/fullstack-server/src/ssr.rs:96— SsrRendererPool::render_to has cognitive complexity 52 (threshold 15). Drivers by points: if/else 24 (41 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Workspace::find_main_package (cognitive 48) packages/cli/src/workspace.rs:315— Workspace::find_main_package has cognitive complexity 48 (threshold 15). Drivers by points: if/else 13 (37 pts), loops 3 (6 pts), match/switch 2 (5 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.
Doctor::doctor (cognitive 47) packages/cli/src/cli/doctor.rs:11— Doctor::doctor has cognitive complexity 47 (threshold 15). Drivers by points: if/else 34 (39 pts), match/switch 5 (7 pts), loops 1 (nesting depth added 7). Of this number, 44 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
IfmtInput::from_raw (cognitive 46) packages/rsx/src/ifmt.rs:128— IfmtInput::from_raw has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (37 pts), loops 3 (9 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
const_serialize_macro::derive_parse (cognitive 46) packages/const-serialize-macro/src/lib.rs:23— const_serialize_macro::derive_parse has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (32 pts), match/switch 5 (9 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RsxBlock::parse_inner (cognitive 39) packages/rsx/src/rsx_block.rs:69— RsxBlock::parse_inner has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 12, loops 2, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prune (cognitive 34) .github/actions/prune-cargo-target/lib.js:70— prune has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 6 (12 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.
dioxus_autofmt::prettier_please::unparse_expr (cognitive 33) packages/autofmt/src/prettier_please.rs:20— dioxus_autofmt::prettier_please::unparse_expr has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParseRouteTree::construct (cognitive 33) packages/router-macro/src/route_tree.rs:117— ParseRouteTree::construct has cognitive complexity 33 (threshold 15). Drivers by points: match/switch 5 (15 pts), loops 4 (11 pts), if/else 1 (6 pts), boolean chains 1 (nesting depth added 22). 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.
serialize.serializeEvent (cognitive 33) packages/interpreter/src/ts/serialize.ts:15— serialize.serializeEvent has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
HotpatchModuleCache::new (cognitive 32) packages/cli/src/build/patch.rs:120— HotpatchModuleCache::new has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 4 (8 pts), match/switch 3 (6 pts) (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
IssueReport::fmt (cognitive 31) packages/cli/src/check/issues.rs:55— IssueReport::fmt has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 4 (13 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComponentCommand::run (cognitive 31) packages/cli/src/cli/component.rs:88— ComponentCommand::run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 5 (11 pts), match/switch 2 (5 pts) (nesting depth added 17). 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.
dioxus_web::run (cognitive 31) packages/web/src/lib.rs:53— dioxus_web::run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 3 (7 pts), loops 2 (3 pts), boolean chains 2 (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.
dioxus_liveview::pool::run (cognitive 28) packages/liveview/src/pool.rs:123— dioxus_liveview::pool::run has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 4 (13 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForeignType::from_type (cognitive 28) packages/manganis/manganis-macro/src/ffi.rs:54— ForeignType::from_type has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (23 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
StructInfo::build_method_impl (cognitive 27) packages/core-macro/src/props/mod.rs:1395— StructInfo::build_method_impl has cognitive complexity 27 (threshold 15). Drivers by points: if/else 19 (24 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RouteParser::new (cognitive 27) packages/fullstack-macro/src/lib.rs:976— RouteParser::new has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 3 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manganis_core::css_module::collect_css_idents (cognitive 27) packages/manganis/manganis-core/src/css_module.rs:120— manganis_core::css_module::collect_css_idents has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 3 (10 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelfUpdate::self_update (cognitive 26) packages/cli/src/cli/update.rs:34— SelfUpdate::self_update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 3, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WebviewInstance::new (cognitive 26) packages/desktop/src/webview.rs:318— WebviewInstance::new has cognitive complexity 26 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dioxus_asset_resolver::native::get_asset_root (cognitive 24) packages/asset-resolver/src/native.rs:152— dioxus_asset_resolver::native::get_asset_root has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 15). 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.
dioxus_fullstack_macro::route_impl_with_route (cognitive 24) packages/fullstack-macro/src/lib.rs:198— dioxus_fullstack_macro::route_impl_with_route has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 13 (18 pts), if/else 6 (nesting depth added 5). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
dioxus_router_macro::segment::parse_route_segments (cognitive 24) packages/router-macro/src/segment.rs:130— dioxus_router_macro::segment::parse_route_segments has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RustcDepInfo::new (cognitive 23) packages/depinfo/src/lib.rs:66— RustcDepInfo::new has cognitive complexity 23 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 4 (8 pts), match/switch 3 (6 pts) (nesting depth added 12). Of this number, 18 points are the body's own statements and 5 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.
FileSystemCache::find_file (cognitive 23) packages/fullstack-server/src/isrg/fs_cache.rs:103— FileSystemCache::find_file has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 1 (3 pts), boolean chains 1 (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.
dioxus_ssr::cache::from_template_element (cognitive 23) packages/ssr/src/cache.rs:175— dioxus_ssr::cache::from_template_element has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 2 (3 pts), match/switch 1 (2 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.
set_attribute.setAttributeInner (cognitive 22) packages/interpreter/src/ts/set_attribute.ts:4— set_attribute.setAttributeInner has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (7 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.
NativeInterpreter.initialize (cognitive 22) packages/interpreter/src/ts/native.ts:42— NativeInterpreter.initialize has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, loops 1 (4 pts) (nesting depth added 10). None of this is in the body itself: all 22 points belong to 4 function literals inside it that branch (lines 75, 108, 50, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FieldInfo::new (cognitive 21) packages/core-macro/src/props/mod.rs:196— FieldInfo::new has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 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.
dioxus_router::components::link::Link (cognitive 21) packages/router/src/components/link.rs:139— dioxus_router::components::link::Link has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 5, match/switch 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.
WebFormData::values (cognitive 21) packages/web/src/events/form.rs:35— WebFormData::values has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RunArgs::run (cognitive 20) packages/cli/src/cli/run.rs:23— RunArgs::run has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 2 (8 pts), loops 1 (nesting depth added 13). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WebSocketResponse::into_stream_and_protocol (cognitive 20) packages/fullstack/src/payloads/websocket.rs:1326— WebSocketResponse::into_stream_and_protocol has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 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.
BlitzBackend::set_attribute_impl (cognitive 20) packages/native-dom/src/mutation_writer.rs:404— BlitzBackend::set_attribute_impl has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 9). Of this number, 19 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.
VisitHooks::visit_expr_call (cognitive 19) packages/cli/src/check/mod.rs:102— VisitHooks::visit_expr_call has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 1 (5 pts), loops 1 (4 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Print::print_as_unified_command (cognitive 19) packages/cli/src/cli/print.rs:101— Print::print_as_unified_command has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 4 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 7). 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.
ManifestMapper::map_background_modes (cognitive 19) packages/cli/src/config/manifest_mapper.rs:552— ManifestMapper::map_background_modes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (17 pts), loops 2 (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.
Runtime::handle_bubbling_event (cognitive 19) packages/core/src/runtime.rs:564— Runtime::handle_bubbling_event has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (5 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.
QuerySegment::parse_from_str (cognitive 19) packages/router-macro/src/query.rs:51— QuerySegment::parse_from_str has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 1 (2 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.
Element::merge_attributes (cognitive 19) packages/rsx/src/element.rs:139— Element::merge_attributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (4 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.
dioxus_rsx_rosetta::rsx_node_from_html (cognitive 19) packages/rsx-rosetta/src/lib.rs:32— dioxus_rsx_rosetta::rsx_node_from_html has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LinkAction::run_link_inner (cognitive 18) packages/cli/src/cli/link.rs:131— LinkAction::run_link_inner has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 6 (11 pts), if/else 4 (6 pts), boolean chains 1 (nesting depth added 7). 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.
dioxus_desktop::launch::launch_virtual_dom_blocking (cognitive 18) packages/desktop/src/launch.rs:60— dioxus_desktop::launch::launch_virtual_dom_blocking has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 4 (8 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.
ServerEvents::from_response (cognitive 18) packages/fullstack/src/payloads/sse.rs:92— ServerEvents::from_response has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 1 (2 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.
dioxus_stores_macro::extend::extend_store (cognitive 18) packages/stores-macro/src/extend.rs:7— dioxus_stores_macro::extend::extend_store has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebsysDom::collect_suspense_in_vnode (cognitive 18) packages/web/src/hydration/suspense.rs:117— WebsysDom::collect_suspense_in_vnode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 2 (8 pts), loops 3 (7 pts), match/switch 1 (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.
Synthetic::files (cognitive 18) packages/web/src/events/drag.rs:94— Synthetic::files has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (4 pts), boolean chains 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.
VNode::prepare_node_removal (cognitive 17) packages/core/src/diff/node.rs:493— VNode::prepare_node_removal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), 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.
ServerFnDecoder::decode_client_response (cognitive 17) packages/fullstack/src/magic.rs:257— ServerFnDecoder::decode_client_response has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (6 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DioxusNativeApplication::handle_dioxus_native_event (cognitive 17) packages/native/src/dioxus_application.rs:58— DioxusNativeApplication::handle_dioxus_native_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 2 (7 pts), match/switch 2 (3 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
dioxus_core_macro::props::strip_option (cognitive 16) packages/core-macro/src/props/mod.rs:1808— dioxus_core_macro::props::strip_option has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 2, loops 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.
DefineElements::parse (cognitive 16) packages/html-internal-macro/src/elements.rs:42— DefineElements::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (5 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.
FfiBridgeParser::generate_ios_function (cognitive 16) packages/manganis/manganis-macro/src/ffi.rs:879— FfiBridgeParser::generate_ios_function has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), match/switch 3 (5 pts), loops 3 (4 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.
Route::parse (cognitive 16) packages/router-macro/src/route.rs:67— Route::parse has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 3 (5 pts), boolean chains 2 (nesting depth added 7). 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.
TooManyFields: BuildRequest packages/cli/src/build/request.rs:243— TooManyFields — 31 stored fields beside 140 methods. The bar is 30 stored fields; this is 1 over it, 1.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
Near-duplicate member pair (38 shared lines) packages/core-macro/src/props/mod.rs:984— packages/core-macro/src/props/mod.rs:984-1109 | packages/core-macro/src/props/mod.rs:1111-1271 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (28 shared lines) packages/cli/src/build/patch.rs:1639— packages/cli/src/build/patch.rs:1639-1720 | packages/wasm-split/wasm-split-cli/src/lib.rs:1484-1550 — These two members are variants of one another: 28 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) packages/desktop/src/element.rs:83— packages/desktop/src/element.rs:83-105 | packages/desktop/src/element.rs:111-135 | packages/desktop/src/element.rs:140-163 | packages/liveview/src/element.rs:76-95 | packages/liveview/src/element.rs:101-122 | packages/liveview/src/element.rs:127-147 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) packages/fullstack/src/magic.rs:627— packages/fullstack/src/magic.rs:627-641 | packages/fullstack/src/magic.rs:669-689 | packages/fullstack/src/magic.rs:693-751 | packages/fullstack/src/magic.rs:755-802 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (36 lines × 2) packages/const-serialize/src/str.rs:170— packages/const-serialize/src/str.rs:170-205 | packages/const-serialize/src/str.rs:224-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (32–34 lines × 2) packages/stores-macro/src/derive.rs:222— packages/stores-macro/src/derive.rs:222-255 | packages/stores-macro/src/derive.rs:423-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–26 lines × 2) packages/cli/src/cli/create.rs:72— packages/cli/src/cli/create.rs:72-97 | packages/cli/src/cli/init.rs:69-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (22–24 lines × 2) packages/desktop/src/file_upload.rs:118— packages/desktop/src/file_upload.rs:118-141 | packages/desktop/src/file_upload.rs:170-191 — 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 (22 lines × 2) packages/core/src/events.rs:575— packages/core/src/events.rs:575-596 | packages/signals/src/read.rs:262-283 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) packages/generational-box/src/sync.rs:376— packages/generational-box/src/sync.rs:376-395 | packages/generational-box/src/unsync.rs:372-391 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) packages/core-macro/src/props/mod.rs:313— packages/core-macro/src/props/mod.rs:313-331 | packages/core-macro/src/props/mod.rs:1671-1689 — 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 (17–18 lines × 2) packages/core-macro/src/props/mod.rs:1033— packages/core-macro/src/props/mod.rs:1033-1049 | packages/core-macro/src/props/mod.rs:1171-1188 — 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 (17 lines × 2) packages/web/src/history.rs:170— packages/web/src/history.rs:170-186 | packages/web/src/history.rs:324-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–15 lines × 3) packages/html/src/events/keyboard.rs:196— packages/html/src/events/keyboard.rs:196-210 | packages/html/src/events/touch.rs:104-117 | packages/html/src/point_interaction.rs:175-189 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (14–15 lines × 2) packages/rsx/src/rsx_block.rs:122— packages/rsx/src/rsx_block.rs:122-135 | packages/rsx/src/rsx_block.rs:176-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–14 lines × 2) packages/oracle/src/renderer.rs:532— packages/oracle/src/renderer.rs:532-545 | packages/oracle/src/vdom_snapshot.rs:153-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12–13 lines × 3) packages/desktop/src/element.rs:88— packages/desktop/src/element.rs:88-99 | packages/desktop/src/element.rs:118-129 | packages/desktop/src/element.rs:145-157 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11–13 lines × 2) packages/cli/src/build/patch.rs:1640— packages/cli/src/build/patch.rs:1640-1652 | packages/wasm-split/wasm-split-cli/src/lib.rs:1485-1495 — before extracting anything, compare `packages/cli/src/build/patch.rs` and `packages/wasm-split/wasm-split-cli/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 6) packages/desktop/src/element.rs:94— packages/desktop/src/element.rs:94-105 | packages/desktop/src/element.rs:124-135 | packages/desktop/src/element.rs:152-163 | packages/liveview/src/element.rs:84-95 | packages/liveview/src/element.rs:111-122 | packages/liveview/src/element.rs:136-147 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (11 lines × 3) packages/router-macro/src/hash.rs:50— packages/router-macro/src/hash.rs:50-60 | packages/router-macro/src/query.rs:58-68 | packages/router-macro/src/query.rs:84-94 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7–9 lines × 2) packages/cli/src/bundler/windows.rs:126— packages/cli/src/bundler/windows.rs:126-134 | packages/cli/src/bundler/windows.rs:452-458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) packages/cli/src/bundler/linux.rs:307— packages/cli/src/bundler/linux.rs:307-312 | packages/cli/src/bundler/linux.rs:690-697 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 3) packages/fullstack/src/magic.rs:678— packages/fullstack/src/magic.rs:678-684 | packages/fullstack/src/magic.rs:739-746 | packages/fullstack/src/magic.rs:790-797 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) packages/fullstack/src/magic.rs:630— packages/fullstack/src/magic.rs:630-635 | packages/fullstack/src/magic.rs:679-684 | packages/fullstack/src/magic.rs:741-746 | packages/fullstack/src/magic.rs:792-797 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) packages/router/src/components/history_buttons.rs:65— packages/router/src/components/history_buttons.rs:65-72 | packages/router/src/components/history_buttons.rs:137-144 | packages/router/src/components/link.rs:151-161 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 3) packages/cli/src/bundler/windows.rs:265— packages/cli/src/bundler/windows.rs:265-274 | packages/cli/src/bundler/windows.rs:325-334 | packages/cli/src/bundler/windows.rs:590-599 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) packages/cli/src/bundler/linux.rs:83— packages/cli/src/bundler/linux.rs:83-89 | packages/cli/src/bundler/windows.rs:262-268 | packages/cli/src/bundler/windows.rs:322-328 | packages/cli/src/bundler/windows.rs:587-593 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (15–16 lines × 3) packages/desktop/headless_tests/events.rs:157— packages/desktop/headless_tests/events.rs:157-171 | packages/desktop/headless_tests/events.rs:196-211 | packages/desktop/headless_tests/events.rs:231-245 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–10 lines × 2) packages/fuzz/src/mutator.rs:271— packages/fuzz/src/mutator.rs:271-278 | packages/fuzz/src/mutator.rs:296-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) packages/desktop/headless_tests/events.rs:522— packages/desktop/headless_tests/events.rs:522-530 | packages/desktop/headless_tests/events.rs:567-575 | packages/desktop/headless_tests/forms.rs:90-98 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (3–8 lines × 3) packages/desktop/headless_tests/events.rs:361— packages/desktop/headless_tests/events.rs:361-363 | packages/desktop/headless_tests/events.rs:401-408 | packages/desktop/headless_tests/events.rs:438-445 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) packages/playwright-tests/fullstack/src/main.rs:60— packages/playwright-tests/fullstack/src/main.rs:60-71 | packages/playwright-tests/liveview/src/main.rs:28-39 | packages/playwright-tests/web/src/main.rs:88-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9–10 lines × 2) examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:249— examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:249-258 | examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:294-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Sources/GeolocationPlugin.swift:249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Sync-over-async blocking packages/cli/src/test_harnesses.rs:404— `run` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
Duplicated block (9 lines × 2 locations) packages/interpreter/src/ts/core.ts:111— packages/interpreter/src/ts/core.ts:111 · packages/interpreter/src/ts/core.ts:134 — 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 (8 lines × 5 locations) packages/interpreter/src/ts/patch_console.ts:10— packages/interpreter/src/ts/patch_console.ts:10 · packages/interpreter/src/ts/patch_console.ts:19 · packages/interpreter/src/ts/patch_console.ts:28 · packages/interpreter/src/ts/patch_console.ts:37 · +1 more site(s) not listed — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 2 locations) packages/interpreter/src/ts/core.ts:331— packages/interpreter/src/ts/core.ts:331 · packages/interpreter/src/ts/core.ts:340 — 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 (6 lines × 4 locations) packages/interpreter/src/ts/core.ts:247— packages/interpreter/src/ts/core.ts:247 · packages/interpreter/src/ts/core.ts:254 · packages/interpreter/src/ts/core.ts:267 · packages/interpreter/src/ts/core.ts:274 — all 4 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.
Complex function serializeEvent (cyclomatic 33, cognitive 33) packages/interpreter/src/ts/serialize.ts:15— serializeEvent has cyclomatic complexity 33 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 setAttributeInner (cyclomatic 20, cognitive 22) packages/interpreter/src/ts/set_attribute.ts:4— setAttributeInner has cyclomatic complexity 20 and cognitive complexity 22; 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 fmtSelection (cyclomatic 15, cognitive 14) packages/extension/src/main.ts:121— fmtSelection has cyclomatic complexity 15 and cognitive complexity 14; 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 serializeInputEvent (cyclomatic 13, cognitive 16) packages/interpreter/src/ts/serialize.ts:187— serializeInputEvent has cyclomatic complexity 13 and cognitive complexity 16; 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 handleEvent (cyclomatic 11, cognitive 16) packages/interpreter/src/ts/native.ts:328— handleEvent has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/interpreter/src/ts/native.ts · ×1
packages/interpreter/src/ts/native.ts: 509 lines of code packages/interpreter/src/ts/native.ts:1— packages/interpreter/src/ts/native.ts has 509 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/interpreter/src/ts/serialize.ts · ×1
packages/interpreter/src/ts/serialize.ts: 496 lines of code packages/interpreter/src/ts/serialize.ts:1— packages/interpreter/src/ts/serialize.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency 'ovsx' — Declared in packages/extension/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'tslib' — Declared in packages/extension/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Interpolated log message defeats structured logging packages/web/src/hydration/hydrate.rs:43— `error!` at line 43 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/web/src/events/mod.rs:233— `warn!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-used/src/lib.rs:197— `error!` at line 197 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-used/src/lib.rs:205— `error!` at line 205 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/lib.rs:235— `info!` at line 235 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/lib.rs:298— `info!` at line 298 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/lib.rs:1339— `error!` at line 1339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/main.rs:55— `info!` at line 55 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/main.rs:69— `info!` at line 69 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/main.rs:85— `info!` at line 85 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/main.rs:117— `debug!` at line 117 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/main.rs:171— `error!` at line 171 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/wasm-split/wasm-split-cli/src/main.rs:175— `debug!` at line 175 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/signals/src/memo.rs:191— `trace!` at line 191 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/signals/src/signal.rs:412— `trace!` at line 412 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/signals/src/signal.rs:531— `trace!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/router/src/routable.rs:163— `error!` at line 163 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/router/src/routable.rs:184— `error!` at line 184 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/router/src/routable.rs:383— `error!` at line 383 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/router/src/components/history_buttons.rs:70— `error!` at line 70 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/router/src/components/history_buttons.rs:142— `error!` at line 142 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/router/src/components/link.rs:159— `error!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/native/src/assets.rs:48— `trace!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/native/src/assets.rs:53— `warn!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/native/src/assets.rs:60— `warn!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Orphaned file packages/manganis/manganis-core/src/css_module_parser.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cli/src/check/issues.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cli/src/config/inline_config.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/html/src/events/visible.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/html/src/geometry.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cli/src/check/metadata.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/html/src/events/resize.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/html/src/input_data.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/core-macro/src/utils.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/manganis/manganis-core/src/ffi.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/manganis/manganis/src/android/java.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/web/src/events/scroll.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/web/src/events/visible.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/stores-macro/src/derive.rs, packages/stores/src/impls/hashmap.rs, packages/stores/src/impls/btreemap.rs, packages/stores/src/impls/slice.rs, packages/html/src/events/selection.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/cli/src/bundler/macos.rs, packages/native-dom/src/dioxus_document.rs, packages/wasm-split/wasm-used/src/lib.rs, packages/native/src/dioxus_renderer.rs, packages/native/src/config.rs. Pair on, review, or document these before any departure.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — 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.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (14 single-owned of 415 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 415 of the 616 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/hooks/src/use_action.rs, packages/fullstack-server/src/index_html.rs, packages/core/src/diff/placement.rs, packages/manganis/manganis/src/android/callback.rs.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 77 project(s) overshoot their size bounds, lowering Project Cohesion to 9.3/10. The most over is `packages/cli` (37525 LoC, 144 module-visible types across 9 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 13 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/manganis/manganis-core/src/css_module_parser.rs, packages/cli/src/check/issues.rs, packages/html/src/events/visible.rs, packages/cli/src/config/inline_config.rs, packages/html/src/geometry.rs, packages/cli/src/check/metadata.rs, packages/html/src/events/resize.rs, packages/html/src/input_data.rs (and 5 more) (16 orphaned of 415 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 415 of the 616 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 26/66 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/autofmt`, `packages/cli-config`, `packages/cli-harnesses/harness-default-to-non-default`, `packages/cli-harnesses/harness-fullstack-desktop`, `packages/cli-harnesses/harness-fullstack-desktop-with-default` and 35 more.
Changelog looks stale/thin — The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
R7 · Dead Code· Unused export 'AppTouchEvent' · ×1
Unused export 'AppTouchEvent' packages/interpreter/src/ts/serialize.ts:7— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SerializedDataTransfer' · ×1
Unused export 'SerializedDataTransfer' packages/interpreter/src/ts/serialize.ts:555— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SerializedDataTransferItem' · ×1
Unused export 'SerializedDataTransferItem' packages/interpreter/src/ts/serialize.ts:556— Nothing imports this binding — it is safe to review for removal.
Security headers incomplete — Set: Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy. Missing: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−2.0 on this card.) The server: `axum::serve(` (packages/liveview/src/adapters/axum_adapter.rs:92).
Duplicated predicate packages/html/src/events/drag.rs:43— `self.coordinates() == other.coordinates() && self.modifiers() == other.modifiers() && self.held_buttons() == other.held_buttons() && self.tr…` appears character-identically in 2 files — packages/html/src/events/drag.rs, packages/html/src/events/mouse.rs. 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.
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 — 1/5 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~1.3 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 2261 source line(s) of the 13 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/interpreter/src/ts/native.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Silent fallback default on Err packages/html-internal-macro/src/extension_attributes.rs:215— `detect_builtin_gated_attributes_for` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 01a17545-e247-71fe-938b-7bc6a7172f6e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 93 · Warnings: 731 · Recommendations: 77 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 25-10-2026 @ 22:54 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.