Public report of leptos-rs/leptos, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 04:08 UTC · Survey ID cd_9223dd308c4b42708d78b8404a512bd0
leptos-rs/leptos
Measured 26 October 2026, 04:05 UTC, at code version bc1cc5a
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 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: 105,208 lines of product code in 50 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Code Health, 35
Findings by how serious they are
45 critical461 serious119 minor
13 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 04:05 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 ▸
84of 84 dimensions measured by tools.
592of 625 findings point to an exact file and line, so you can open each one in the code. The other 33 concern the repository as a whole, such as missing documentation.
84dimensions across 7 lenses, read from 105,208 lines of product code in 50 projects.
leptos-rs/leptos 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 49 out of 100 and is rated Adequate, and 44 of its 45 critical findings are security problems.
Code Health, at 35, is the weakest lens and counts most in the score. The best first step is simplifying the most tangled functions, worth about 6 points. Splitting the oversized files comes next, worth about 4 points. Raising Code Health to 67 would lift the score to about 60.
Thirty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, updating the vulnerable packages and setting a waiting period for automatic updates would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the unsafe setting in infrastructure or container files needs changing to safe values. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 105,208 lines, about €120,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.
Outbound HTTP resilience · Outbound HTTP without resilience projects/ory-kratos/app/src/auth/login.rs
Outbound HTTP resilience · Outbound HTTP without resilience projects/ory-kratos/app/src/auth/recovery.rs
Outbound HTTP resilience · Outbound HTTP without resilience projects/ory-kratos/app/src/auth/registration.rs
Outbound HTTP resilience · Outbound HTTP without resilience projects/ory-kratos/app/src/auth/settings.rs
Outbound HTTP resilience · Outbound HTTP without resilience projects/ory-kratos/app/src/auth/verification.rs
Outbound HTTP resilience · Outbound HTTP without resilience projects/sso_auth_axum/src/sign_in_sign_up.rs
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: 20 findings
These 20 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one.
€41,000 to €200,000, for 676 to 2,144 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 49. 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: 105,208 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 4 points · Medium effort · Large Files
3
Bring the 34 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with patch.patch (cyclomatic 48), patch (cyclomatic 48), ServerFnArgs::parse (cyclomatic 46).
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 €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Code Health, at 35 (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
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5. Of all the actions in this report, it raises the score most for the work it takes: about 6 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, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
372 modules, with 1012 dependencies between them. 4 loops run through 85 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 332 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.
reactive_graph.owner.arena_item uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.owner.arena_item, while a change to reactive_graph.owner.arena_item can't break reactive_graph.traits.
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.
5→9 tachys.hydration uses tachys.viewpart of a loop✕
Connections
1 pair of types, where a type in tachys.hydration uses a type in tachys.view.
tachys.hydration uses leptos_router.location, so a change to leptos_router.location can break tachys.hydration, while a change to tachys.hydration can't break leptos_router.location.
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.
5→18 tachys.hydration uses tachys.renderer.mock_dompart of a loop✕
Connections
6 pairs of types, where a type in tachys.hydration uses a type in tachys.renderer.mock_dom.
tachys.hydration uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.hydration, while a change to tachys.hydration can't break tachys.renderer.mock_dom.
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.
leptos.into_view uses tachys.view.add_attr, so a change to tachys.view.add_attr can break leptos.into_view, while a change to leptos.into_view can't break tachys.view.add_attr.
Position
Below the diagonal: leptos.into_view uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in leptos.into_view uses a type in tachys.hydration.
The types involved
leptos.into_view.View → tachys.hydration.Cursor
Direction
leptos.into_view uses tachys.hydration, so a change to tachys.hydration can break leptos.into_view, while a change to leptos.into_view can't break tachys.hydration.
Position
Below the diagonal: leptos.into_view uses a module listed above it, which is the healthy direction.
6→8 leptos.into_view uses tachys.ssrpart of a loop✕
Connections
1 pair of types, where a type in leptos.into_view uses a type in tachys.ssr.
The types involved
leptos.into_view.View → tachys.ssr.StreamBuilder
Direction
leptos.into_view uses tachys.ssr, so a change to tachys.ssr can break leptos.into_view, while a change to leptos.into_view can't break tachys.ssr.
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.
6→9 leptos.into_view uses tachys.viewpart of a loop✕
Connections
6 pairs of types, where a type in leptos.into_view uses a type in tachys.view.
The types involved
leptos.into_view.View → tachys.view.Position
leptos.into_view.View → tachys.view.PositionState
leptos.into_view.View → tachys.view.Render
leptos.into_view.View → tachys.view.RenderFlags
leptos.into_view.View → tachys.view.RenderHtml
leptos.into_view.View → tachys.view.ToTemplate
Direction
leptos.into_view uses tachys.view, so a change to tachys.view can break leptos.into_view, while a change to leptos.into_view can't break tachys.view.
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.
6→20 leptos.into_view uses tachys.html.attribute.any_attributepart of a loop✕
Connections
1 pair of types, where a type in leptos.into_view uses a type in tachys.html.attribute.any_attribute.
leptos.into_view uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break leptos.into_view, while a change to leptos.into_view can't break tachys.html.attribute.any_attribute.
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.
reactive_graph.owner.stored_value uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_graph.owner.stored_value, while a change to reactive_graph.owner.stored_value can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_graph.owner.stored_value uses a module listed above it, which is the healthy direction.
7→16 reactive_graph.owner.stored_value uses leptos_router.locationpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.owner.stored_value uses a type in leptos_router.location.
reactive_graph.owner.stored_value uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.owner.stored_value, while a change to reactive_graph.owner.stored_value can't break leptos_router.location.
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.
7→17 reactive_graph.owner.stored_value uses reactive_graph.traitspart of a loop✕
Connections
6 pairs of types, where a type in reactive_graph.owner.stored_value uses a type in reactive_graph.traits.
reactive_graph.owner.stored_value uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.owner.stored_value, while a change to reactive_graph.owner.stored_value can't break reactive_graph.traits.
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.
7→22 reactive_graph.owner.stored_value uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.owner.stored_value uses a type in leptos_meta.title.
reactive_graph.owner.stored_value uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.owner.stored_value, while a change to reactive_graph.owner.stored_value can't break leptos_meta.title.
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.
tachys.ssr uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break tachys.ssr, while a change to tachys.ssr can't break tachys.html.attribute.any_attribute.
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→22 tachys.ssr uses leptos_meta.titlepart of a loop✕
Connections
2 pairs of types, where a type in tachys.ssr uses a type in leptos_meta.title.
tachys.view uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.view, while a change to tachys.view can't break tachys.renderer.mock_dom.
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→20 tachys.view uses tachys.html.attribute.any_attributepart of a loop✕
Connections
1 pair of types, where a type in tachys.view uses a type in tachys.html.attribute.any_attribute.
tachys.view uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break tachys.view, while a change to tachys.view can't break tachys.html.attribute.any_attribute.
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.
tachys.html.property uses tachys.view, so a change to tachys.view can break tachys.html.property, while a change to tachys.html.property can't break tachys.view.
Position
Below the diagonal: tachys.html.property uses a module listed above it, which is the healthy direction.
10→18 tachys.html.property uses tachys.renderer.mock_dompart of a loop✕
Connections
2 pairs of types, where a type in tachys.html.property uses a type in tachys.renderer.mock_dom.
tachys.html.property uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.html.property, while a change to tachys.html.property can't break tachys.renderer.mock_dom.
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.
10→19 tachys.html.property uses tachys.html.attributepart of a loop✕
Connections
3 pairs of types, where a type in tachys.html.property uses a type in tachys.html.attribute.
tachys.html.property uses tachys.html.attribute, so a change to tachys.html.attribute can break tachys.html.property, while a change to tachys.html.property can't break tachys.html.attribute.
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.
reactive_graph.signal.read uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_graph.signal.read uses a module listed above it, which is the healthy direction.
reactive_graph.signal.read uses reactive_graph.owner.stored_value, so a change to reactive_graph.owner.stored_value can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break reactive_graph.owner.stored_value.
Position
Below the diagonal: reactive_graph.signal.read uses a module listed above it, which is the healthy direction.
reactive_graph.signal.read uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.signal.read uses a module listed above it, which is the healthy direction.
11→12 reactive_graph.signal.read uses reactive_graph.signal.arc_readpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.read uses a type in reactive_graph.signal.arc_read.
reactive_graph.signal.read uses reactive_graph.signal.arc_read, so a change to reactive_graph.signal.arc_read can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break reactive_graph.signal.arc_read.
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.
11→16 reactive_graph.signal.read uses leptos_router.locationpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.read uses a type in leptos_router.location.
reactive_graph.signal.read uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break leptos_router.location.
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.
11→17 reactive_graph.signal.read uses reactive_graph.traitspart of a loop✕
Connections
5 pairs of types, where a type in reactive_graph.signal.read uses a type in reactive_graph.traits.
reactive_graph.signal.read uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break reactive_graph.traits.
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.
11→18 reactive_graph.signal.read uses tachys.renderer.mock_dompart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.read uses a type in tachys.renderer.mock_dom.
reactive_graph.signal.read uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break tachys.renderer.mock_dom.
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.
11→22 reactive_graph.signal.read uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.read uses a type in leptos_meta.title.
reactive_graph.signal.read uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.signal.read, while a change to reactive_graph.signal.read can't break leptos_meta.title.
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.
reactive_graph.signal.arc_read uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.signal.arc_read, while a change to reactive_graph.signal.arc_read can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.signal.arc_read uses a module listed above it, which is the healthy direction.
reactive_graph.signal.arc_read uses reactive_graph.signal.read, so a change to reactive_graph.signal.read can break reactive_graph.signal.arc_read, while a change to reactive_graph.signal.arc_read can't break reactive_graph.signal.read.
Position
Below the diagonal: reactive_graph.signal.arc_read uses a module listed above it, which is the healthy direction.
12→16 reactive_graph.signal.arc_read uses leptos_router.locationpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.arc_read uses a type in leptos_router.location.
reactive_graph.signal.arc_read uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.signal.arc_read, while a change to reactive_graph.signal.arc_read can't break leptos_router.location.
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.
12→17 reactive_graph.signal.arc_read uses reactive_graph.traitspart of a loop✕
Connections
4 pairs of types, where a type in reactive_graph.signal.arc_read uses a type in reactive_graph.traits.
reactive_graph.signal.arc_read uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.signal.arc_read, while a change to reactive_graph.signal.arc_read can't break reactive_graph.traits.
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.
12→18 reactive_graph.signal.arc_read uses tachys.renderer.mock_dompart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.arc_read uses a type in tachys.renderer.mock_dom.
reactive_graph.signal.arc_read uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.signal.arc_read, while a change to reactive_graph.signal.arc_read can't break tachys.renderer.mock_dom.
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.
12→22 reactive_graph.signal.arc_read uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.arc_read uses a type in leptos_meta.title.
reactive_graph.signal.arc_read uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.signal.arc_read, while a change to reactive_graph.signal.arc_read can't break leptos_meta.title.
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.
reactive_graph.signal.rw uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_graph.signal.rw uses a module listed above it, which is the healthy direction.
reactive_graph.signal.rw uses reactive_graph.owner.stored_value, so a change to reactive_graph.owner.stored_value can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break reactive_graph.owner.stored_value.
Position
Below the diagonal: reactive_graph.signal.rw uses a module listed above it, which is the healthy direction.
reactive_graph.signal.rw uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.signal.rw uses a module listed above it, which is the healthy direction.
reactive_graph.signal.rw uses reactive_graph.signal.read, so a change to reactive_graph.signal.read can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break reactive_graph.signal.read.
Position
Below the diagonal: reactive_graph.signal.rw uses a module listed above it, which is the healthy direction.
13→15 reactive_graph.signal.rw uses reactive_graph.signal.arc_rwpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.rw uses a type in reactive_graph.signal.arc_rw.
reactive_graph.signal.rw uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break reactive_graph.signal.arc_rw.
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→16 reactive_graph.signal.rw uses leptos_router.locationpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.rw uses a type in leptos_router.location.
reactive_graph.signal.rw uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break leptos_router.location.
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→17 reactive_graph.signal.rw uses reactive_graph.traitspart of a loop✕
Connections
7 pairs of types, where a type in reactive_graph.signal.rw uses a type in reactive_graph.traits.
reactive_graph.signal.rw uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break reactive_graph.traits.
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→18 reactive_graph.signal.rw uses tachys.renderer.mock_dompart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.rw uses a type in tachys.renderer.mock_dom.
reactive_graph.signal.rw uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break tachys.renderer.mock_dom.
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→22 reactive_graph.signal.rw uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.rw uses a type in leptos_meta.title.
reactive_graph.signal.rw uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.signal.rw, while a change to reactive_graph.signal.rw can't break leptos_meta.title.
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.
reactive_graph.computed.memo uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_graph.computed.memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.memo uses reactive_graph.owner.stored_value, so a change to reactive_graph.owner.stored_value can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break reactive_graph.owner.stored_value.
Position
Below the diagonal: reactive_graph.computed.memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.memo uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.computed.memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.memo uses reactive_graph.signal.arc_read, so a change to reactive_graph.signal.arc_read can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break reactive_graph.signal.arc_read.
Position
Below the diagonal: reactive_graph.computed.memo uses a module listed above it, which is the healthy direction.
14→16 reactive_graph.computed.memo uses leptos_router.locationpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.computed.memo uses a type in leptos_router.location.
reactive_graph.computed.memo uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break leptos_router.location.
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→17 reactive_graph.computed.memo uses reactive_graph.traitspart of a loop✕
Connections
4 pairs of types, where a type in reactive_graph.computed.memo uses a type in reactive_graph.traits.
reactive_graph.computed.memo uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break reactive_graph.traits.
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→18 reactive_graph.computed.memo uses tachys.renderer.mock_dompart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.computed.memo uses a type in tachys.renderer.mock_dom.
reactive_graph.computed.memo uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break tachys.renderer.mock_dom.
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→22 reactive_graph.computed.memo uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.computed.memo uses a type in leptos_meta.title.
reactive_graph.computed.memo uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break leptos_meta.title.
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→36 reactive_graph.computed.memo uses reactive_graph.computed.arc_memopart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.computed.memo uses a type in reactive_graph.computed.arc_memo.
reactive_graph.computed.memo uses reactive_graph.computed.arc_memo, so a change to reactive_graph.computed.arc_memo can break reactive_graph.computed.memo, while a change to reactive_graph.computed.memo can't break reactive_graph.computed.arc_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.
reactive_graph.signal.arc_rw uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.signal.arc_rw uses a module listed above it, which is the healthy direction.
reactive_graph.signal.arc_rw uses reactive_graph.signal.arc_read, so a change to reactive_graph.signal.arc_read can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break reactive_graph.signal.arc_read.
Position
Below the diagonal: reactive_graph.signal.arc_rw uses a module listed above it, which is the healthy direction.
reactive_graph.signal.arc_rw uses reactive_graph.signal.rw, so a change to reactive_graph.signal.rw can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break reactive_graph.signal.rw.
Position
Below the diagonal: reactive_graph.signal.arc_rw uses a module listed above it, which is the healthy direction.
15→16 reactive_graph.signal.arc_rw uses leptos_router.locationpart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.arc_rw uses a type in leptos_router.location.
reactive_graph.signal.arc_rw uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break leptos_router.location.
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→17 reactive_graph.signal.arc_rw uses reactive_graph.traitspart of a loop✕
Connections
6 pairs of types, where a type in reactive_graph.signal.arc_rw uses a type in reactive_graph.traits.
reactive_graph.signal.arc_rw uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break reactive_graph.traits.
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→18 reactive_graph.signal.arc_rw uses tachys.renderer.mock_dompart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.arc_rw uses a type in tachys.renderer.mock_dom.
reactive_graph.signal.arc_rw uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break tachys.renderer.mock_dom.
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→22 reactive_graph.signal.arc_rw uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in reactive_graph.signal.arc_rw uses a type in leptos_meta.title.
reactive_graph.signal.arc_rw uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.signal.arc_rw, while a change to reactive_graph.signal.arc_rw can't break leptos_meta.title.
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.
leptos_router.location uses reactive_graph.signal.read, so a change to reactive_graph.signal.read can break leptos_router.location, while a change to leptos_router.location can't break reactive_graph.signal.read.
Position
Below the diagonal: leptos_router.location uses a module listed above it, which is the healthy direction.
leptos_router.location uses reactive_graph.computed.memo, so a change to reactive_graph.computed.memo can break leptos_router.location, while a change to leptos_router.location can't break reactive_graph.computed.memo.
Position
Below the diagonal: leptos_router.location uses a module listed above it, which is the healthy direction.
leptos_router.location uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break leptos_router.location, while a change to leptos_router.location can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: leptos_router.location uses a module listed above it, which is the healthy direction.
reactive_graph.traits uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.traits, while a change to reactive_graph.traits can't break leptos_router.location.
Position
Below the diagonal: reactive_graph.traits uses a module listed above it, which is the healthy direction.
tachys.renderer.mock_dom uses tachys.view, so a change to tachys.view can break tachys.renderer.mock_dom, while a change to tachys.renderer.mock_dom can't break tachys.view.
Position
Below the diagonal: tachys.renderer.mock_dom uses a module listed above it, which is the healthy direction.
tachys.renderer.mock_dom uses reactive_graph.traits, so a change to reactive_graph.traits can break tachys.renderer.mock_dom, while a change to tachys.renderer.mock_dom can't break reactive_graph.traits.
Position
Below the diagonal: tachys.renderer.mock_dom uses a module listed above it, which is the healthy direction.
tachys.html.attribute uses tachys.view, so a change to tachys.view can break tachys.html.attribute, while a change to tachys.html.attribute can't break tachys.view.
Position
Below the diagonal: tachys.html.attribute uses a module listed above it, which is the healthy direction.
tachys.html.attribute uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.html.attribute, while a change to tachys.html.attribute can't break tachys.renderer.mock_dom.
Position
Below the diagonal: tachys.html.attribute uses a module listed above it, which is the healthy direction.
tachys.html.attribute.any_attribute uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.html.attribute.any_attribute, while a change to tachys.html.attribute.any_attribute can't break tachys.renderer.mock_dom.
Position
Below the diagonal: tachys.html.attribute.any_attribute uses a module listed above it, which is the healthy direction.
tachys.html.attribute.any_attribute uses tachys.html.attribute, so a change to tachys.html.attribute can break tachys.html.attribute.any_attribute, while a change to tachys.html.attribute.any_attribute can't break tachys.html.attribute.
Position
Below the diagonal: tachys.html.attribute.any_attribute uses a module listed above it, which is the healthy direction.
20→22 tachys.html.attribute.any_attribute uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in tachys.html.attribute.any_attribute uses a type in leptos_meta.title.
tachys.html.attribute.any_attribute uses leptos_meta.title, so a change to leptos_meta.title can break tachys.html.attribute.any_attribute, while a change to tachys.html.attribute.any_attribute can't break leptos_meta.title.
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.
1 pair of types, where a type in oco_ref uses a type in tachys.renderer.mock_dom.
The types involved
oco_ref.Oco → tachys.renderer.mock_dom.Element
Direction
oco_ref uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break oco_ref, while a change to oco_ref can't break tachys.renderer.mock_dom.
Position
Below the diagonal: oco_ref uses a module listed above it, which is the healthy direction.
oco_ref uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break oco_ref, while a change to oco_ref can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: oco_ref uses a module listed above it, which is the healthy direction.
21→22 oco_ref uses leptos_meta.titlepart of a loop✕
Connections
1 pair of types, where a type in oco_ref uses a type in leptos_meta.title.
The types involved
oco_ref.Oco → leptos_meta.title.Formatter
Direction
oco_ref uses leptos_meta.title, so a change to leptos_meta.title can break oco_ref, while a change to oco_ref can't break leptos_meta.title.
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.
leptos_meta.title uses tachys.view.add_attr, so a change to tachys.view.add_attr can break leptos_meta.title, while a change to leptos_meta.title can't break tachys.view.add_attr.
Position
Below the diagonal: leptos_meta.title uses a module listed above it, which is the healthy direction.
leptos_meta.title uses tachys.hydration, so a change to tachys.hydration can break leptos_meta.title, while a change to leptos_meta.title can't break tachys.hydration.
Position
Below the diagonal: leptos_meta.title uses a module listed above it, which is the healthy direction.
leptos_meta.title uses tachys.view, so a change to tachys.view can break leptos_meta.title, while a change to leptos_meta.title can't break tachys.view.
Position
Below the diagonal: leptos_meta.title uses a module listed above it, which is the healthy direction.
leptos_meta.title uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break leptos_meta.title, while a change to leptos_meta.title can't break tachys.renderer.mock_dom.
Position
Below the diagonal: leptos_meta.title uses a module listed above it, which is the healthy direction.
leptos_meta.title uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break leptos_meta.title, while a change to leptos_meta.title can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: leptos_meta.title uses a module listed above it, which is the healthy direction.
leptos_config uses leptos_meta.title, so a change to leptos_meta.title can break leptos_config, while a change to leptos_config can't break leptos_meta.title.
Position
Below the diagonal: leptos_config uses a module listed above it, which is the healthy direction.
leptos_server.resource uses tachys.view.add_attr, so a change to tachys.view.add_attr can break leptos_server.resource, while a change to leptos_server.resource can't break tachys.view.add_attr.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses tachys.hydration, so a change to tachys.hydration can break leptos_server.resource, while a change to leptos_server.resource can't break tachys.hydration.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses tachys.ssr, so a change to tachys.ssr can break leptos_server.resource, while a change to leptos_server.resource can't break tachys.ssr.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses tachys.view, so a change to tachys.view can break leptos_server.resource, while a change to leptos_server.resource can't break tachys.view.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses reactive_graph.signal.rw, so a change to reactive_graph.signal.rw can break leptos_server.resource, while a change to leptos_server.resource can't break reactive_graph.signal.rw.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break leptos_server.resource, while a change to leptos_server.resource can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses leptos_router.location, so a change to leptos_router.location can break leptos_server.resource, while a change to leptos_server.resource can't break leptos_router.location.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses reactive_graph.traits, so a change to reactive_graph.traits can break leptos_server.resource, while a change to leptos_server.resource can't break reactive_graph.traits.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break leptos_server.resource, while a change to leptos_server.resource can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
leptos_server.resource uses leptos_meta.title, so a change to leptos_meta.title can break leptos_server.resource, while a change to leptos_server.resource can't break leptos_meta.title.
Position
Below the diagonal: leptos_server.resource uses a module listed above it, which is the healthy direction.
reactive_graph.graph.subscriber uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.graph.subscriber, while a change to reactive_graph.graph.subscriber can't break leptos_meta.title.
Position
Below the diagonal: reactive_graph.graph.subscriber uses a module listed above it, which is the healthy direction.
25→32 reactive_graph.graph.subscriber uses reactive_graph.graph.sourcepart of a loop✕
Connections
2 pairs of types, where a type in reactive_graph.graph.subscriber uses a type in reactive_graph.graph.source.
reactive_graph.graph.subscriber uses reactive_graph.graph.source, so a change to reactive_graph.graph.source can break reactive_graph.graph.subscriber, while a change to reactive_graph.graph.subscriber can't break reactive_graph.graph.source.
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.
reactive_graph.owner uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.owner, while a change to reactive_graph.owner can't break leptos_meta.title.
Position
Below the diagonal: reactive_graph.owner uses a module listed above it, which is the healthy direction.
reactive_stores uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_stores, while a change to reactive_stores can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_stores uses a module listed above it, which is the healthy direction.
reactive_stores uses tachys.html.property, so a change to tachys.html.property can break reactive_stores, while a change to reactive_stores can't break tachys.html.property.
Position
Below the diagonal: reactive_stores uses a module listed above it, which is the healthy direction.
reactive_stores uses leptos_router.location, so a change to leptos_router.location can break reactive_stores, while a change to reactive_stores can't break leptos_router.location.
Position
Below the diagonal: reactive_stores uses a module listed above it, which is the healthy direction.
reactive_stores uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_stores, while a change to reactive_stores can't break reactive_graph.traits.
Position
Below the diagonal: reactive_stores uses a module listed above it, which is the healthy direction.
reactive_stores uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_stores, while a change to reactive_stores can't break tachys.renderer.mock_dom.
Position
Below the diagonal: reactive_stores uses a module listed above it, which is the healthy direction.
reactive_stores uses leptos_meta.title, so a change to leptos_meta.title can break reactive_stores, while a change to reactive_stores can't break leptos_meta.title.
Position
Below the diagonal: reactive_stores uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses tachys.view.add_attr, so a change to tachys.view.add_attr can break tachys.view.any_view, while a change to tachys.view.any_view can't break tachys.view.add_attr.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses tachys.hydration, so a change to tachys.hydration can break tachys.view.any_view, while a change to tachys.view.any_view can't break tachys.hydration.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses tachys.ssr, so a change to tachys.ssr can break tachys.view.any_view, while a change to tachys.view.any_view can't break tachys.ssr.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses tachys.view, so a change to tachys.view can break tachys.view.any_view, while a change to tachys.view.any_view can't break tachys.view.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.view.any_view, while a change to tachys.view.any_view can't break tachys.renderer.mock_dom.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break tachys.view.any_view, while a change to tachys.view.any_view can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
tachys.view.any_view uses leptos_meta.title, so a change to leptos_meta.title can break tachys.view.any_view, while a change to tachys.view.any_view can't break leptos_meta.title.
Position
Below the diagonal: tachys.view.any_view uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in throw_error uses a type in leptos_meta.title.
The types involved
throw_error.Error → leptos_meta.title.Formatter
throw_error.ErrorId → leptos_meta.title.Formatter
Direction
throw_error uses leptos_meta.title, so a change to leptos_meta.title can break throw_error, while a change to throw_error can't break leptos_meta.title.
Position
Below the diagonal: throw_error uses a module listed above it, which is the healthy direction.
leptos_actix uses reactive_graph.owner, so a change to reactive_graph.owner can break leptos_actix, while a change to leptos_actix can't break reactive_graph.owner.
Position
Below the diagonal: leptos_actix uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses leptos_router.matching, so a change to leptos_router.matching can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break leptos_router.matching.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses reactive_graph.channel, so a change to reactive_graph.channel can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break reactive_graph.channel.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.view.add_attr, so a change to tachys.view.add_attr can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.view.add_attr.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.hydration, so a change to tachys.hydration can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.hydration.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.ssr, so a change to tachys.ssr can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.ssr.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.view, so a change to tachys.view can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.view.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses leptos_router.location, so a change to leptos_router.location can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break leptos_router.location.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.renderer.mock_dom.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses oco_ref, so a change to oco_ref can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break oco_ref.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses leptos_meta.title, so a change to leptos_meta.title can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break leptos_meta.title.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses reactive_graph.owner, so a change to reactive_graph.owner can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break reactive_graph.owner.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
leptos_router.nested_router uses tachys.view.any_view, so a change to tachys.view.any_view can break leptos_router.nested_router, while a change to leptos_router.nested_router can't break tachys.view.any_view.
Position
Below the diagonal: leptos_router.nested_router uses a module listed above it, which is the healthy direction.
reactive_graph.graph.source uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.graph.source, while a change to reactive_graph.graph.source can't break leptos_router.location.
Position
Below the diagonal: reactive_graph.graph.source uses a module listed above it, which is the healthy direction.
reactive_graph.graph.source uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.graph.source, while a change to reactive_graph.graph.source can't break reactive_graph.traits.
Position
Below the diagonal: reactive_graph.graph.source uses a module listed above it, which is the healthy direction.
reactive_graph.graph.source uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.graph.source, while a change to reactive_graph.graph.source can't break leptos_meta.title.
Position
Below the diagonal: reactive_graph.graph.source uses a module listed above it, which is the healthy direction.
reactive_graph.graph.source uses reactive_graph.graph.subscriber, so a change to reactive_graph.graph.subscriber can break reactive_graph.graph.source, while a change to reactive_graph.graph.source can't break reactive_graph.graph.subscriber.
Position
Below the diagonal: reactive_graph.graph.source uses a module listed above it, which is the healthy direction.
reactive_stores.field uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_stores.field, while a change to reactive_stores.field can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
reactive_stores.field uses tachys.html.property, so a change to tachys.html.property can break reactive_stores.field, while a change to reactive_stores.field can't break tachys.html.property.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
reactive_stores.field uses leptos_router.location, so a change to leptos_router.location can break reactive_stores.field, while a change to reactive_stores.field can't break leptos_router.location.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
reactive_stores.field uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_stores.field, while a change to reactive_stores.field can't break reactive_graph.traits.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
reactive_stores.field uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_stores.field, while a change to reactive_stores.field can't break tachys.renderer.mock_dom.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
reactive_stores.field uses leptos_meta.title, so a change to leptos_meta.title can break reactive_stores.field, while a change to reactive_stores.field can't break leptos_meta.title.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
reactive_stores.field uses reactive_stores, so a change to reactive_stores can break reactive_stores.field, while a change to reactive_stores.field can't break reactive_stores.
Position
Below the diagonal: reactive_stores.field uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.view.add_attr, so a change to tachys.view.add_attr can break tachys.html.element, while a change to tachys.html.element can't break tachys.view.add_attr.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.hydration, so a change to tachys.hydration can break tachys.html.element, while a change to tachys.html.element can't break tachys.hydration.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.ssr, so a change to tachys.ssr can break tachys.html.element, while a change to tachys.html.element can't break tachys.ssr.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.view, so a change to tachys.view can break tachys.html.element, while a change to tachys.html.element can't break tachys.view.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses leptos_router.location, so a change to leptos_router.location can break tachys.html.element, while a change to tachys.html.element can't break leptos_router.location.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break tachys.html.element, while a change to tachys.html.element can't break tachys.renderer.mock_dom.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break tachys.html.element, while a change to tachys.html.element can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
tachys.html.element uses tachys.view.any_view, so a change to tachys.view.any_view can break tachys.html.element, while a change to tachys.html.element can't break tachys.view.any_view.
Position
Below the diagonal: tachys.html.element uses a module listed above it, which is the healthy direction.
leptos_axum uses reactive_graph.owner, so a change to reactive_graph.owner can break leptos_axum, while a change to leptos_axum can't break reactive_graph.owner.
Position
Below the diagonal: leptos_axum uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses reactive_graph.signal.arc_read, so a change to reactive_graph.signal.arc_read can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break reactive_graph.signal.arc_read.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses reactive_graph.computed.memo, so a change to reactive_graph.computed.memo can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break reactive_graph.computed.memo.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break leptos_router.location.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break reactive_graph.traits.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break tachys.renderer.mock_dom.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break leptos_meta.title.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses reactive_graph.graph.subscriber, so a change to reactive_graph.graph.subscriber can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break reactive_graph.graph.subscriber.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
reactive_graph.computed.arc_memo uses reactive_graph.graph.source, so a change to reactive_graph.graph.source can break reactive_graph.computed.arc_memo, while a change to reactive_graph.computed.arc_memo can't break reactive_graph.graph.source.
Position
Below the diagonal: reactive_graph.computed.arc_memo uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses tachys.view.add_attr, so a change to tachys.view.add_attr can break leptos.error_boundary, while a change to leptos.error_boundary can't break tachys.view.add_attr.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses tachys.hydration, so a change to tachys.hydration can break leptos.error_boundary, while a change to leptos.error_boundary can't break tachys.hydration.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses tachys.ssr, so a change to tachys.ssr can break leptos.error_boundary, while a change to leptos.error_boundary can't break tachys.ssr.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses tachys.view, so a change to tachys.view can break leptos.error_boundary, while a change to leptos.error_boundary can't break tachys.view.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break leptos.error_boundary, while a change to leptos.error_boundary can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break leptos.error_boundary, while a change to leptos.error_boundary can't break tachys.renderer.mock_dom.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses tachys.html.attribute.any_attribute, so a change to tachys.html.attribute.any_attribute can break leptos.error_boundary, while a change to leptos.error_boundary can't break tachys.html.attribute.any_attribute.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses throw_error, so a change to throw_error can break leptos.error_boundary, while a change to leptos.error_boundary can't break throw_error.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
leptos.error_boundary uses reactive_graph.computed.arc_memo, so a change to reactive_graph.computed.arc_memo can break leptos.error_boundary, while a change to leptos.error_boundary can't break reactive_graph.computed.arc_memo.
Position
Below the diagonal: leptos.error_boundary uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.owner.arena_item, so a change to reactive_graph.owner.arena_item can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.owner.arena_item.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.owner.stored_value, so a change to reactive_graph.owner.stored_value can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.owner.stored_value.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses tachys.html.property, so a change to tachys.html.property can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break tachys.html.property.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.signal.read, so a change to reactive_graph.signal.read can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.signal.read.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.signal.arc_read, so a change to reactive_graph.signal.arc_read can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.signal.arc_read.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.signal.rw, so a change to reactive_graph.signal.rw can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.signal.rw.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.computed.memo, so a change to reactive_graph.computed.memo can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.computed.memo.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses leptos_router.location, so a change to leptos_router.location can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break leptos_router.location.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.traits, so a change to reactive_graph.traits can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.traits.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses tachys.renderer.mock_dom, so a change to tachys.renderer.mock_dom can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break tachys.renderer.mock_dom.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses leptos_meta.title, so a change to leptos_meta.title can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break leptos_meta.title.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
reactive_graph.wrappers.read uses reactive_graph.computed.arc_memo, so a change to reactive_graph.computed.arc_memo can break reactive_graph.wrappers.read, while a change to reactive_graph.wrappers.read can't break reactive_graph.computed.arc_memo.
Position
Below the diagonal: reactive_graph.wrappers.read uses a module listed above it, which is the healthy direction.
leptos_router.components uses leptos.into_view, so a change to leptos.into_view can break leptos_router.components, while a change to leptos_router.components can't break leptos.into_view.
Position
Below the diagonal: leptos_router.components uses a module listed above it, which is the healthy direction.
leptos_router.components uses reactive_graph.signal.arc_rw, so a change to reactive_graph.signal.arc_rw can break leptos_router.components, while a change to leptos_router.components can't break reactive_graph.signal.arc_rw.
Position
Below the diagonal: leptos_router.components uses a module listed above it, which is the healthy direction.
leptos_router.components uses leptos_router.location, so a change to leptos_router.location can break leptos_router.components, while a change to leptos_router.components can't break leptos_router.location.
Position
Below the diagonal: leptos_router.components uses a module listed above it, which is the healthy direction.
leptos_router.components uses leptos_meta.title, so a change to leptos_meta.title can break leptos_router.components, while a change to leptos_router.components can't break leptos_meta.title.
Position
Below the diagonal: leptos_router.components uses a module listed above it, which is the healthy direction.
leptos_router.components uses reactive_graph.wrappers.read, so a change to reactive_graph.wrappers.read can break leptos_router.components, while a change to leptos_router.components can't break reactive_graph.wrappers.read.
Position
Below the diagonal: leptos_router.components uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 35% · Weak · gated by R1, R2, R3, X4 ·
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
40
High / Critical
A03:2025 — Software Supply Chain Failures
34
High / Critical
A02:2025 — Security Misconfiguration
2
High / Critical
A01:2025 — Broken Access Control
2
Medium
Roadmap
First, reduce cyclomatic complexity by breaking down branch-heavy functions and refactoring the highest-complexity bodies to improve maintainability. Next, split the oversized patch file into smaller, focused modules and migrate the remaining JavaScript files to TypeScript to enhance type safety. Finally, replace interpolated log messages with structured logging to ensure consistent and parseable observability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Bring the 34 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with patch.patch (cyclomatic 48), patch (cyclomatic 48), ServerFnArgs::parse (cyclomatic 46).
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
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 — 45
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 — 461
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 — 119
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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. 84 of 84 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 84 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, 592 of 625 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 — examples/counters/e2e/ (@playwright/test), examples/error_boundary/e2e/ (@playwright/test), examples/islands_router/e2e/ (@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 27 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, .ts) and this repository declares a Cargo test suite (repository root, 132 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.178 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — kratos Pulling mailcrab Pulling kratos Error Get "https://registry-1.docker.io/v2/": Forbidden mailcrab Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mailcrab Pulling kratos Pulling kratos Error Get "https://registry-1.docker.io/v2/": Forbidden mailcrab Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
X5 Nullable reference types — 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 and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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 Dockerfile (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.
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.
C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
34 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was patch.patch at 48. A further 37 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 EitherOf16::fmt at 16 — they are counted neither in the figure above nor in this dimension's score. 2 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: router/src/matching/choose_view.rs (EitherOf16::choose at 16), router/src/matching/nested/tuples.rs (EitherOf16::to_params at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 18 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 34 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with patch.patch (cyclomatic 48), patch (cyclomatic 48), ServerFnArgs::parse (cyclomatic 46). — 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 34 together lifts Cyclomatic Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 60 down to 60 or less in Cognitive Complexity — start with patch.patch (cognitive 129), patch (cognitive 128), ServerFnArgs::parse (cognitive 113). — 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 9 together lifts Cognitive Complexity from 5.7 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.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 21 FileTooLong finding(s) in God Classes — start with lib.rs (6), mod.rs (2), keyed.rs (2). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 8 MethodTooLong finding(s) in God Classes — start with lib.rs (2), nested_router.rs (2), component.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 FunctionTooLong finding(s) in God Classes — start with patch.js, component_builder.rs, lib.rs. — One of this dimension's main actionable groups (5 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.
152 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with error_boundary.rs (2), lib.rs (2), mod.rs (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 10 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with lib.rs (4), component.rs, resource.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with logging.rs (2), action.rs (2), lib.rs. — One of this dimension's main actionable groups (9 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 · Coupling9.0 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
50 production modules (Cargo+npm), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 33 of the 50 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: api-boundary · ×4
Unstable project leptos_axum
Unstable project leptos_server
Off the main sequence: shared-server-2
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Unstable project leptos_axum finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project leptos_server 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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with resource.rs, lib.rs. — One of this dimension's main actionable groups (2 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 Distribution9.5 / 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.
632 test methods: 340 unit, 270 integration, 0 BDD, 22 e2e. The JavaScript/TypeScript suite contributes 27 `it`/`test` case(s) across 20 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 605 `#[test]` function(s) across 132 file(s) declaring at least one; its unit/integration split is Cargo's own — 75 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 27 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 dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
5 outdated, 0 yanked direct Cargo dependencies. 89 of 146 direct crates were graded against crates.io (0 not published there, 57 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: actix-http · ×5
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 433 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.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: integrations/axum/src/config.rs (17×27=459); leptos_macro/src/component.rs (8×37=296); leptos/src/hydration/islands_routing.js (5×15=75) Repeated repair below the complexity floor: server_fn/src/lib.rs (4 of 4 changes were fixes); leptos/src/error_boundary.rs (3 of 4 changes were fixes); integrations/utils/src/lib.rs (3 of 4 changes were fixes)
Resolve the 5 Repeated repair finding(s) in Churn × Complexity Hotspots — start with lib.rs (3), error_boundary.rs, mod.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with config.rs, component.rs, islands_routing.js. — 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.4 / 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.
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is integrations/axum/src/config.rs. Counted over 282 of the 396 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.
85 deducted task-comment markers across 105208 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 79 TodoComment finding(s) in Explicit Debt — start with lib.rs (17), mod.rs (5), class.rs (5). — One of this dimension's main actionable groups (79 warning-level).
Resolve the 5 FixmeComment finding(s) in Explicit Debt — start with main.rs (2), mod.rs, lib.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with event.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 138 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).
40 finding(s): 0 critical, 39 high, 1 medium, 0 low. 36 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 6 file(s) — `projects/openapi-openai-api-swagger-ui/src/open_ai.rs` (line 114), `projects/ory-kratos/app/src/auth/kratos_html.rs` (line 114), `router/src/components.rs` (line 568, line 575), `router/src/nested_router.rs` (line 1099), `server_fn/src/lib.rs` (line 985, line 1150, line 1280), … (+1 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 4 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) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 36 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (36 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d32_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.
44 of 282 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is projects/ory-kratos/app/src/auth/settings.rs. Counted over 282 of the 396 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 44 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (6), main.rs (4), app.rs (3). — One of this dimension's main actionable groups (44 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge 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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with error_boundary.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 9 Change coupling finding(s) in Change Coupling — start with action.rs (2), actix.rs (2), ssr.rs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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 1 platform declaration(s) and 0 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.
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.
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?
C1 · Data Protection4.0 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
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.
Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.
Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.
Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
Implement data export/portability for a data subject (a machine-readable export of their personal data).
Track GDPR consent (lawful basis) alongside the personal data it authorises.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
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.
222 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 36 of 102 project(s) that lack one — worth up to 0.7 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified
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.
What to do
Run the test suite in CI via an explicit runner step (`cargo test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
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.
601/759 types (79%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.9 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 30/31 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `projects/tauri-from-scratch/src-tauri`.
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` — add that `package-ecosystem` entry 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.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — projects/openapi-openai-api-swagger-ui/src/app.rs:145, projects/sso_auth_axum/src/sign_in_sign_up.rs:114
`reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×14) — projects/ory-kratos/app/src/auth/extractors.rs:33, projects/ory-kratos/app/src/auth/kratos_error.rs:43, projects/ory-kratos/app/src/auth/login.rs:17, …
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether 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.
`add_todo` 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. — projects/session_auth_axum/src/todo.rs:76
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.
2 typed · 5 plain JS — the untyped files are leptos/src/hydration/hydration_script.js, leptos/src/hydration/island_script.js, leptos/src/hydration/islands_routing.js, leptos/src/hydration/reload_script.js, leptos_hot_reload/src/patch.js.
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.
projects/hexagonal-architecture/end2end/playwright.config.ts:13 · projects/openapi-openai-api-swagger-ui/end2end/playwright.config.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — projects/hexagonal-architecture/end2end/playwright.config.ts:13
leptos_hot_reload/src/patch.js:361 · leptos_hot_reload/src/patch.js:382 — 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. — leptos_hot_reload/src/patch.js:361
leptos_hot_reload/src/patch.js:331 · leptos_hot_reload/src/patch.js:410 — 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. — leptos_hot_reload/src/patch.js:331
leptos/src/hydration/islands_routing.js:328 · leptos/src/hydration/islands_routing.js:375 — 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. — leptos/src/hydration/islands_routing.js:328
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.
patch has cyclomatic complexity 48 and cognitive complexity 128; 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. — leptos_hot_reload/src/patch.js:2
buildActualChildren has cyclomatic complexity 28 and cognitive complexity 84; 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. — leptos_hot_reload/src/patch.js:282
clickToReq has cyclomatic complexity 18 and cognitive complexity 13; 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. — leptos/src/hydration/islands_routing.js:84
diffRange has cyclomatic complexity 15 and cognitive complexity 18; 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. — leptos/src/hydration/islands_routing.js:178
collectForItems 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. — leptos/src/hydration/islands_routing.js:264
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files2.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
leptos_hot_reload/src/patch.js has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — leptos_hot_reload/src/patch.js: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.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Strong✓ 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.
test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 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.
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.
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 commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. This repository serves HTTP itself (`axum::serve(` (projects/tauri-from-scratch/src-orig/src/main.rs:91)), 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.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — projects/nginx-mpmc/nginx.conf:19
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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.
This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`. — projects/session_auth_axum/src/todo.rs:88
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 unescaped3.5 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`html` 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. — leptos_hot_reload/src/patch.js:470
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 146 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`. — router/src/form.rs:146
`warn!` at line 204 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`. — router/src/form.rs:204
`error!` at line 222 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`. — router/src/form.rs:222
`warn!` at line 280 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`. — router/src/form.rs:280
`warn!` at line 387 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`. — router/src/static_routes.rs:387
`warn!` at line 418 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`. — router/src/static_routes.rs:418
`error!` at line 164 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`. — router/src/location/history.rs:164
`error!` at line 192 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`. (×2) — router/src/location/history.rs:192, projects/ory-kratos/app/src/auth/settings.rs:192
`warn!` at line 129 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`. — reactive_graph/src/lib.rs:129
`error!` at line 37 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`. — projects/ory-kratos/app/src/auth/logout.rs:37
`debug!` at line 68 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`. — projects/ory-kratos/app/src/auth/logout.rs:68
`error!` at line 74 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`. — projects/ory-kratos/app/src/auth/recovery.rs:74
`error!` at line 94 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`. — projects/ory-kratos/app/src/auth/settings.rs:94
`error!` at line 133 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`. — projects/ory-kratos/app/src/auth/settings.rs:133
`error!` at line 150 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`. — projects/ory-kratos/app/src/auth/settings.rs:150
`error!` at line 178 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`. — projects/ory-kratos/app/src/auth/settings.rs:178
`error!` at line 261 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`. — projects/ory-kratos/app/src/auth/settings.rs:261
`error!` at line 264 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`. — projects/ory-kratos/app/src/auth/settings.rs:264
`debug!` at line 45 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`. — projects/ory-kratos/app/src/auth/verification.rs:45
`warn!` at line 451 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`. — meta/src/lib.rs:451
`error!` at line 199 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`. — leptos_server/src/once_resource.rs:199
`error!` at line 365 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`. — leptos_server/src/resource.rs:365
`error!` at line 452 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`. — leptos_server/src/resource.rs:452
`error!` at line 462 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`. — leptos_server/src/resource.rs:462
`error!` at line 219 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`. — leptos_server/src/shared.rs:219
`error!` at line 228 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`. — leptos_server/src/shared.rs:228
`error!` at line 250 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`. — leptos_server/src/shared.rs:250
`error!` at line 506 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`. — integrations/axum/src/lib.rs:506
`error!` at line 820 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`. — integrations/axum/src/lib.rs:820
`warn!` at line 1896 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`. — integrations/axum/src/lib.rs:1896
`warn!` at line 1987 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`. — integrations/axum/src/lib.rs:1987
`warn!` at line 2888 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`. — integrations/axum/src/lib.rs:2888
`warn!` at line 2994 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`. — integrations/axum/src/lib.rs:2994
`warn!` at line 199 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`. — integrations/actix/src/lib.rs:199
`warn!` 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: `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`. — integrations/actix/src/lib.rs:298
`error!` at line 922 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`. — integrations/actix/src/lib.rs:922
`warn!` at line 1418 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`. — integrations/actix/src/lib.rs:1418
`warn!` at line 1534 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`. — integrations/actix/src/lib.rs:1534
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a struct, Diesel table, SeaORM entity or SQL migration table named for it — a SeaORM ActiveModelBehavior hook or database trigger that records each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
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 — compose up failed (exit 18 — an image could not be pulled) — kratos Pulling mailcrab Pulling kratos Error Get "https://registry-1.docker.io/v2/": Forbidden mailcrab Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mailcrab Pulling kratos Pulling kratos Error Get "https://registry-1.docker.io/v2/": Forbidden mailcrab Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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 .rs, .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.
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 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — 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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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 — 2 test file(s) reach none of 5 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: error_boundary.rs ↔ error_boundary.rs leptos/src/error_boundary.rs:1— `leptos/src/error_boundary.rs` (context leptos) and `tachys/src/view/error_boundary.rs` (context tachys) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d9b590b8` fix: unique IDs and correct hydration for `<ErrorBoundary/>` (closes …; `ab67bea7` rename any_error; `2934c295` work on Axum integration and on error boundaries — run `git show` on any of them.
TodoComment tachys/src/view/iterators.rs:178— // TODO fast path for clearing — 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 tachys/src/view/iterators.rs:515— // TODO fast path for clearing — 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 tachys/src/view/keyed.rs:252— // 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 tachys/src/reactive_graph/owned.rs:107— // 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 tachys/src/html/style.rs:53— // 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 router/src/nested_router.rs:302— // 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 leptos/src/text_prop.rs:57— // 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 integrations/axum/src/lib.rs:901— // 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 integrations/actix/src/lib.rs:702— // 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 tachys/src/view/template.rs:41— // TODO try_build/try_rebuild() — 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 tachys/src/ssr/mod.rs:422— // TODO can probably make this more efficient — 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 tachys/src/renderer/dom.rs:392— // TODO reverse Shadow DOM retargetting — 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 tachys/src/renderer/sledgehammer.rs:431— // TODO reverse Shadow DOM retargetting — 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 tachys/src/renderer/dom.rs:393— // TODO simulate currentTarget — 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 tachys/src/renderer/sledgehammer.rs:432— // TODO simulate currentTarget — 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 tachys/src/renderer/mock_dom.rs:231— // 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 tachys/src/renderer/mod.rs:127— // TODO remove generic in 0.9 — 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 tachys/src/reactive_graph/class.rs:47— // TODO FROM_SERVER vs template — 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 tachys/src/reactive_graph/class.rs:147— // TODO FROM_SERVER vs template — 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 tachys/src/reactive_graph/class.rs:311— // TODO FROM_SERVER vs template — 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 tachys/src/reactive_graph/style.rs:136— // TODO FROM_SERVER vs template — 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 tachys/src/reactive_graph/class.rs:283— // TODO this needs a non-reactive form too to be restored — 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 tachys/src/reactive_graph/class.rs:321— // TODO multi-class optimizations 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.
TodoComment tachys/src/reactive_graph/suspense.rs:303— // TODO wrap this with a Suspense as needed — 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 tachys/src/reactive_graph/suspense.rs:354— // TODO in 0.8: this should include a nonce — 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.
FileTooLong: src/lib.rs integrations/axum/src/lib.rs— FileTooLong — 1516 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 44 free functions. The bar is 500 significant lines; this is 1016 over it, 3.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/wrappers.rs reactive_graph/src/wrappers.rs— FileTooLong — 1300 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 800 over it, 2.60× 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/lib.rs server_fn_macro/src/lib.rs— FileTooLong — 1027 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 527 over it, 2.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs integrations/actix/src/lib.rs— FileTooLong — 1016 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 516 over it, 2.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/component.rs leptos_macro/src/component.rs— FileTooLong — 982 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 482 over it, 1.96× 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/resource.rs leptos_server/src/resource.rs— FileTooLong — 799 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 299 over it, 1.60× 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/lib.rs server_fn/src/lib.rs— FileTooLong — 783 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 283 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/nested_router.rs router/src/nested_router.rs— FileTooLong — 773 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 273 over it, 1.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: reactive_graph/mod.rs tachys/src/reactive_graph/mod.rs— FileTooLong — 674 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 174 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/keyed.rs reactive_stores/src/keyed.rs— FileTooLong — 668 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 168 over it, 1.34× 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/lib.rs either_of/src/lib.rs— FileTooLong — 665 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 165 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: view/either.rs tachys/src/view/either.rs— FileTooLong — 649 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 149 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs reactive_stores_macro/src/lib.rs— FileTooLong — 634 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 134 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: src/once_resource.rs leptos_server/src/once_resource.rs— FileTooLong — 587 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 87 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: view/any_view.rs tachys/src/view/any_view.rs— FileTooLong — 584 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 84 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: view/keyed.rs tachys/src/view/keyed.rs— FileTooLong — 573 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 73 over it, 1.15× 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: element/mod.rs tachys/src/html/element/mod.rs— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 69% of them inside a single declaration: HtmlElement (10 blocks, 37-857). The bar is 500 significant lines; this is 68 over it, 1.14× 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/flat_router.rs router/src/flat_router.rs— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: FlatRoutesView (5 blocks, 35-823). The bar is 500 significant lines; this is 65 over it, 1.13× 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: view/iterators.rs tachys/src/view/iterators.rs— FileTooLong — 560 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 60 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: html/event.rs tachys/src/html/event.rs— FileTooLong — 558 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 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/config.rs integrations/axum/src/config.rs— FileTooLong — 501 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 1 over it, 1.00× 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.
Outbound HTTP without resilience projects/openapi-openai-api-swagger-ui/src/app.rs:145— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/extractors.rs:33— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/kratos_error.rs:43— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/login.rs:17— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/login.rs:98— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/logout.rs:16— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/recovery.rs:45— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/recovery.rs:104— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/registration.rs:34— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/registration.rs:116— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/settings.rs:44— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/settings.rs:168— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/verification.rs:29— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/app/src/auth/verification.rs:70— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/ory-kratos/server/src/extract_session.rs:30— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience projects/sso_auth_axum/src/sign_in_sign_up.rs:114— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (6 lines × 2) leptos/src/error_boundary.rs:224— leptos/src/error_boundary.rs:224-229 | leptos/src/error_boundary.rs:488-493 — 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) leptos_server/src/action.rs:63— leptos_server/src/action.rs:63-68 | leptos_server/src/action.rs:152-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) oco/src/lib.rs:671— oco/src/lib.rs:671-676 | oco/src/lib.rs:703-708 — 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) projects/nginx-mpmc/app-1/src/app.rs:74— projects/nginx-mpmc/app-1/src/app.rs:74-79 | projects/nginx-mpmc/app-2/src/app.rs:59-64 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/app.rs` and `projects/nginx-mpmc/app-2/src/app.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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) router/src/params.rs:32— router/src/params.rs:32-37 | router/src/params.rs:52-57 — 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) router/src/reactive.rs:229— router/src/reactive.rs:229-234 | router/src/reactive.rs:239-244 — 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) tachys/src/html/event.rs:240— tachys/src/html/event.rs:240-245 | tachys/src/html/event.rs:283-288 — 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) tachys/src/reactive_graph/mod.rs:502— tachys/src/reactive_graph/mod.rs:502-508 | tachys/src/reactive_graph/mod.rs:521-526 — 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) leptos/src/error_boundary.rs:266— leptos/src/error_boundary.rs:266-271 | leptos/src/suspense_component.rs:248-253 — 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) reactive_graph/src/signal/arc_rw.rs:268— reactive_graph/src/signal/arc_rw.rs:268-273 | reactive_graph/src/signal/arc_write.rs:137-142 — 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) reactive_graph/src/signal/rw.rs:371— reactive_graph/src/signal/rw.rs:371-376 | reactive_graph/src/signal/write.rs:179-184 — 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) either_of/src/lib.rs:202— either_of/src/lib.rs:202-468 | tachys/src/view/either.rs:70-75 — 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) leptos_macro/src/view/mod.rs:1486— leptos_macro/src/view/mod.rs:1486-1491 | leptos_macro/src/view/mod.rs:1492-1497 — 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.
leptos_macro::view::element_to_tokens (cognitive 79) leptos_macro/src/view/mod.rs:871— leptos_macro::view::element_to_tokens has cognitive complexity 79 (threshold 15). Drivers by points: if/else 27 (45 pts), match/switch 10 (21 pts), loops 3 (7 pts), boolean chains 6 (nesting depth added 33). Of this number, 77 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
leptos_macro::view::inert_element_to_tokens (cognitive 56) leptos_macro/src/view/mod.rs:382— leptos_macro::view::inert_element_to_tokens has cognitive complexity 56 (threshold 15). Drivers by points: if/else 10 (39 pts), loops 3 (10 pts), match/switch 2 (5 pts), boolean chains 2 (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. This shape REPEATS in the file: one other method here (leptos_macro::view::inert_svg_element_to_tokens) 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.
leptos_macro::view::inert_svg_element_to_tokens (cognitive 56) leptos_macro/src/view/mod.rs:485— leptos_macro::view::inert_svg_element_to_tokens has cognitive complexity 56 (threshold 15). Drivers by points: if/else 10 (39 pts), loops 3 (10 pts), match/switch 2 (5 pts), boolean chains 2 (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. This shape REPEATS in the file: one other method here (leptos_macro::view::inert_element_to_tokens) 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.
leptos_macro::view::attribute_absolute (cognitive 49) leptos_macro/src/view/mod.rs:1299— leptos_macro::view::attribute_absolute has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (32 pts), match/switch 3 (10 pts), boolean chains 7 (nesting depth added 20). 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.
leptos_macro::view::is_inert_element (cognitive 40) leptos_macro/src/view/mod.rs:189— leptos_macro::view::is_inert_element has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 5 (16 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
leptos_macro::view::component_builder::component_to_tokens (cognitive 38) leptos_macro/src/view/component_builder.rs:19— leptos_macro::view::component_builder::component_to_tokens has cognitive complexity 38 (threshold 15). Drivers by points: if/else 25 (30 pts), match/switch 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 8). 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.
leptos_macro::view::attribute_to_tokens (cognitive 30) leptos_macro/src/view/mod.rs:1193— leptos_macro::view::attribute_to_tokens has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 7 (11 pts), boolean chains 4 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
leptos_macro::view::attribute_value (cognitive 23) leptos_macro/src/view/mod.rs:1802— leptos_macro::view::attribute_value has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
leptos_macro::view::slot_helper::slot_to_tokens (cognitive 23) leptos_macro/src/view/slot_helper.rs:15— leptos_macro::view::slot_helper::slot_to_tokens has cognitive complexity 23 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
leptos_macro::view::event_type_and_handler (cognitive 22) leptos_macro/src/view/mod.rs:1466— leptos_macro::view::event_type_and_handler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), match/switch 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
leptos_macro::view::node_to_tokens (cognitive 20) leptos_macro/src/view/mod.rs:757— leptos_macro::view::node_to_tokens has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
leptos_macro::lazy::lazy_impl (cognitive 18) leptos_macro/src/lazy.rs:18— leptos_macro::lazy::lazy_impl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (5 lines × 2) integrations/actix/src/lib.rs:906— integrations/actix/src/lib.rs:906-910 | integrations/actix/src/lib.rs:935-939 — 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) leptos_macro/src/component.rs:70— leptos_macro/src/component.rs:70-74 | leptos_macro/src/slot.rs:35-39 — before extracting anything, compare `leptos_macro/src/component.rs` and `leptos_macro/src/slot.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) leptos_server/src/resource.rs:96— leptos_server/src/resource.rs:96-100 | leptos_server/src/resource.rs:895-899 — 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) projects/nginx-mpmc/app-1/src/app.rs:50— projects/nginx-mpmc/app-1/src/app.rs:50-54 | projects/nginx-mpmc/app-2/src/app.rs:45-49 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/app.rs` and `projects/nginx-mpmc/app-2/src/app.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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) reactive_graph/src/actions/action.rs:211— reactive_graph/src/actions/action.rs:211-215 | reactive_graph/src/actions/action.rs:399-403 — 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) tachys/src/renderer/dom.rs:522— tachys/src/renderer/dom.rs:522-526 | tachys/src/renderer/sledgehammer.rs:533-537 — 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) integrations/actix/src/lib.rs:128— integrations/actix/src/lib.rs:128-132 | integrations/axum/src/lib.rs:159-163 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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) integrations/actix/src/lib.rs:138— integrations/actix/src/lib.rs:138-142 | integrations/axum/src/lib.rs:165-169 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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) integrations/actix/src/lib.rs:148— integrations/actix/src/lib.rs:148-152 | integrations/axum/src/lib.rs:171-175 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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) reactive_graph/src/owner.rs:497— reactive_graph/src/owner.rs:497-501 | reactive_graph/src/owner.rs:520-524 — 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.
Change coupling: action.rs ↔ multi_action.rs reactive_graph/src/actions/action.rs:1— `reactive_graph/src/actions/action.rs` and `reactive_graph/src/actions/multi_action.rs` change together 90% of the time (9 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 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 9 shared commits counted here, the most recent 3 are `d29433b9` fix: more robust arena sandboxing (closes #2995) (#3026); `6166f6ed` fix: ensure that we retain the correct sandoxed arena when spawning F…; `a4ce7976` fix: improve type inference for the default threadsafe signal case — run `git show` on any of them.
Change coupling: ssr.rs ↔ mod.rs benchmarks/src/ssr.rs:1— `benchmarks/src/ssr.rs` and `benchmarks/src/todomvc/mod.rs` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `2e816b26` benchmarks: get `benchmarks` directory working with updated `tachys`; `a1a9d41a` updating SSR benchmarks to include tachys; `e0265252` fix: broken benchmarks (closes #1763) (#1771) — run `git show` on any of them.
Change coupling: hydrate.rs ↔ ssr.rs hydration_context/src/hydrate.rs:1— `hydration_context/src/hydrate.rs` and `hydration_context/src/ssr.rs` change together 69% of the time (11 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `a35175a9` fix: use nested serialization IDs to prevent mismatches that depend o…; `e113c79f` Revert "fix: preserve the ordering of read/write operations on atomic…; `2ea0381b` fix: preserve the ordering of read/write operations on atomic variables — run `git show` on any of them.
Change coupling: action.rs ↔ multi_action.rs leptos_server/src/action.rs:1— `leptos_server/src/action.rs` and `leptos_server/src/multi_action.rs` change together 68% of the time (13 of the 19 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 `309d3d16` fix(leptos_server): track caller location for ServerAction/ServerMult…; `be83b5f2` chore: remove unused imports; `200047a8` chore: remove unnecessary default generics — run `git show` on any of them.
Change coupling: memo.rs ↔ rw.rs reactive_graph/src/computed/memo.rs:1— `reactive_graph/src/computed/memo.rs` and `reactive_graph/src/signal/rw.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d29433b9` fix: more robust arena sandboxing (closes #2995) (#3026); `a4ce7976` fix: improve type inference for the default threadsafe signal case; `200047a8` chore: remove unnecessary default generics — run `git show` on any of them.
Change coupling: class.rs ↔ style.rs tachys/src/reactive_graph/class.rs:1— `tachys/src/reactive_graph/class.rs` and `tachys/src/reactive_graph/style.rs` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 `52a92999` fix: check for resource reads inside attribute values (see #4856) (#4…; `4833b4e2` fix: avoid double-polling synchronously-available Suspend (closes #31…; `f2582b6a` fix: properly scope Suspend rebuilds within ownership tree (closes #3… — run `git show` on any of them.
Change coupling: actix.rs ↔ axum.rs server_fn/src/request/actix.rs:1— `server_fn/src/request/actix.rs` and `server_fn/src/request/axum.rs` change together 50% of the time (11 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 11 shared commits counted here, the most recent 3 are `9ff36984` fix(server_fn): stop forwarding websocket output once the client is gone; `7eb5061e` fix: respect Axum/Actix built-in body size limits (#4813); `53ca15a0` fix(server_fn): apply back-pressure in websocket forwarding loop (#4725) — run `git show` on any of them.
Change coupling: browser.rs ↔ reqwest.rs server_fn/src/request/browser.rs:1— `server_fn/src/request/browser.rs` and `server_fn/src/request/reqwest.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 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 5 shared commits counted here, the most recent 3 are `a519859a` Revert "use `&[u8]` instead of `Bytes` for requests"; `e179db1d` use `&[u8]` instead of `Bytes` for requests; `88fee243` support setting server URL on either platform — run `git show` on any of them.
Change coupling: actix.rs ↔ generic.rs server_fn/src/request/actix.rs:1— `server_fn/src/request/actix.rs` and `server_fn/src/request/generic.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 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 5 shared commits counted here, the most recent 3 are `9ff36984` fix(server_fn): stop forwarding websocket output once the client is gone; `30c445a4` fix: send/receive websocket data; `ba7bfd8b` feat: allow using different error types for req/resp with WebSockets,… — run `git show` on any of them.
Duplicated block (7 lines × 2) integrations/actix/src/lib.rs:1268— integrations/actix/src/lib.rs:1268-1274 | integrations/axum/src/lib.rs:1578-1584 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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) reactive_graph/src/computed/async_derived/future_impls.rs:142— reactive_graph/src/computed/async_derived/future_impls.rs:142-148 | reactive_graph/src/computed/async_derived/future_impls.rs:209-215 — 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) leptos/src/logging.rs:64— leptos/src/logging.rs:64-70 | leptos_dom/src/logging.rs:85-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) leptos/src/logging.rs:75— leptos/src/logging.rs:75-81 | leptos_dom/src/logging.rs:96-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) leptos_server/src/action.rs:95— leptos_server/src/action.rs:95-101 | leptos_server/src/multi_action.rs:55-61 — 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) projects/session_auth_axum/src/auth.rs:120— projects/session_auth_axum/src/auth.rs:120-126 | projects/sso_auth_axum/src/auth.rs:101-107 — before extracting anything, compare `projects/session_auth_axum/src/auth.rs` and `projects/sso_auth_axum/src/auth.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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) reactive_graph/src/computed/arc_memo.rs:177— reactive_graph/src/computed/arc_memo.rs:177-183 | reactive_graph/src/signal/arc_trigger.rs:41-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) reactive_stores/src/keyed.rs:243— reactive_stores/src/keyed.rs:243-249 | reactive_stores/src/subfield.rs:107-118 — before extracting anything, compare `reactive_stores/src/keyed.rs` and `reactive_stores/src/subfield.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) reactive_graph/src/actions/action.rs:769— reactive_graph/src/actions/action.rs:769-775 | reactive_graph/src/actions/multi_action.rs:130-136 — 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.
leptos_macro::view::element_to_tokens (cyclomatic 43) leptos_macro/src/view/mod.rs:871— leptos_macro::view::element_to_tokens has cyclomatic complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
leptos_macro::view::attribute_absolute (cyclomatic 25) leptos_macro/src/view/mod.rs:1299— leptos_macro::view::attribute_absolute has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
leptos_macro::view::attribute_to_tokens (cyclomatic 23) leptos_macro/src/view/mod.rs:1193— leptos_macro::view::attribute_to_tokens has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
leptos_macro::view::component_builder::component_to_tokens (cyclomatic 21) leptos_macro/src/view/component_builder.rs:19— leptos_macro::view::component_builder::component_to_tokens has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
leptos_macro::view::node_to_tokens (cyclomatic 18) leptos_macro/src/view/mod.rs:757— leptos_macro::view::node_to_tokens 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.
leptos_macro::view::inert_element_to_tokens (cyclomatic 17) leptos_macro/src/view/mod.rs:382— leptos_macro::view::inert_element_to_tokens has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (leptos_macro::view::inert_svg_element_to_tokens) 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.
leptos_macro::view::inert_svg_element_to_tokens (cyclomatic 17) leptos_macro/src/view/mod.rs:485— leptos_macro::view::inert_svg_element_to_tokens has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (leptos_macro::view::inert_element_to_tokens) 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.
leptos_macro::view::is_inert_element (cyclomatic 16) leptos_macro/src/view/mod.rs:189— leptos_macro::view::is_inert_element 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.
MethodTooLong: Model.expand leptos_macro/src/component.rs:165— MethodTooLong — expand runs 321 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 221 over it, 3.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RouterConfiguration.apply integrations/axum/src/config.rs:769— MethodTooLong — apply runs 195 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 95 over it, 1.95× 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 server_fn_macro/src/lib.rs:1067— MethodTooLong — parse runs 185 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 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Match.rebuild_nested_route router/src/nested_router.rs:814— MethodTooLong — rebuild_nested_route 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: PatchModel.expand reactive_stores_macro/src/lib.rs:704— MethodTooLong — expand runs 151 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 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StreamBuilder.poll_next tachys/src/ssr/mod.rs:356— MethodTooLong — poll_next 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.
MethodTooLong: Match.build_nested_route router/src/nested_router.rs:649— MethodTooLong — build_nested_route runs 112 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 12 over it, 1.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.
MethodTooLong: SuspenseBoundary.to_html_async_with_buf leptos/src/suspense_component.rs:327— MethodTooLong — to_html_async_with_buf runs 111 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 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (10 lines × 2) projects/openapi-openai-api-swagger-ui/src/open_ai.rs:52— projects/openapi-openai-api-swagger-ui/src/open_ai.rs:52-61 | projects/openapi-openai-api-swagger-ui/src/open_ai.rs:176-185 — 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) reactive_graph/src/effect/render_effect.rs:220— reactive_graph/src/effect/render_effect.rs:220-231 | reactive_graph/src/effect/render_effect.rs:292-301 — 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) router/src/components.rs:242— router/src/components.rs:242-251 | router/src/components.rs:298-308 — 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) router/src/nested_router.rs:678— router/src/nested_router.rs:678-687 | router/src/nested_router.rs:905-914 — 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) server_fn/src/lib.rs:1174— server_fn/src/lib.rs:1174-1183 | server_fn/src/lib.rs:1304-1313 — 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) server_fn_macro/src/lib.rs:949— server_fn_macro/src/lib.rs:949-958 | server_fn_macro/src/lib.rs:966-975 — 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) tachys/src/html/event.rs:228— tachys/src/html/event.rs:228-237 | tachys/src/html/event.rs:271-280 — 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) integrations/actix/src/lib.rs:1340— integrations/actix/src/lib.rs:1340-1349 | integrations/axum/src/lib.rs:1806-1815 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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) leptos_server/src/once_resource.rs:106— leptos_server/src/once_resource.rs:106-113 | leptos_server/src/resource.rs:309-316 — 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) projects/session_auth_axum/src/main.rs:54— projects/session_auth_axum/src/main.rs:54-61 | projects/sso_auth_axum/src/main.rs:136-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) server_fn/src/request/browser.rs:147— server_fn/src/request/browser.rs:147-154 | server_fn/src/request/browser.rs:218-225 — 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) leptos/src/logging.rs:53— leptos/src/logging.rs:53-60 | leptos_dom/src/logging.rs:74-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) leptos_macro/src/component.rs:989— leptos_macro/src/component.rs:989-996 | server_fn_macro/src/lib.rs:1625-1632 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) reactive_graph/src/computed/arc_memo.rs:270— reactive_graph/src/computed/arc_memo.rs:270-277 | reactive_graph/src/computed/async_derived/arc_async_derived.rs:782-789 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) leptos_dom/src/helpers.rs:104— leptos_dom/src/helpers.rs:104-111 | tachys/src/dom.rs:53-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) tachys/src/renderer/dom.rs:612— tachys/src/renderer/dom.rs:612-619 | tachys/src/renderer/mock_dom.rs:352-359 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×6
Duplicated block (17 lines × 2) leptos_macro/src/params.rs:7— leptos_macro/src/params.rs:7-23 | leptos_macro/src/params.rs:39-55 — 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) projects/session_auth_axum/src/auth.rs:82— projects/session_auth_axum/src/auth.rs:82-98 | projects/sso_auth_axum/src/auth.rs:67-83 — before extracting anything, compare `projects/session_auth_axum/src/auth.rs` and `projects/sso_auth_axum/src/auth.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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 (17 lines × 2) reactive_graph/src/effect/render_effect.rs:63— reactive_graph/src/effect/render_effect.rs:63-79 | reactive_graph/src/effect/render_effect.rs:94-110 — 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) reactive_stores_macro/src/lib.rs:488— reactive_stores_macro/src/lib.rs:488-504 | reactive_stores_macro/src/lib.rs:567-583 — 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) server_fn_macro/src/lib.rs:722— server_fn_macro/src/lib.rs:722-738 | server_fn_macro/src/lib.rs:749-765 — 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) projects/session_auth_axum/src/todo.rs:311— projects/session_auth_axum/src/todo.rs:311-327 | projects/session_auth_axum/src/todo.rs:344-360 — 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) reactive_graph/src/effect/render_effect.rs:147— reactive_graph/src/effect/render_effect.rs:147-159 | reactive_graph/src/effect/render_effect.rs:254-266 — 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) router/src/form.rs:382— router/src/form.rs:382-394 | router/src/form.rs:413-425 — 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) router/src/form.rs:397— router/src/form.rs:397-409 | router/src/form.rs:428-440 — 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) tachys/src/view/keyed.rs:809— tachys/src/view/keyed.rs:809-821 | tachys/src/view/keyed.rs:829-841 — 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) projects/sso_auth_axum/src/lib.rs:62— projects/sso_auth_axum/src/lib.rs:62-74 | projects/sso_auth_axum/src/sign_in_sign_up.rs:147-160 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) any_spawner/src/lib.rs:549— any_spawner/src/lib.rs:549-561 | any_spawner/src/lib.rs:583-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.
Duplicated block (12 lines × 2) leptos_server/src/resource.rs:244— leptos_server/src/resource.rs:244-255 | leptos_server/src/resource.rs:980-991 — 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) reactive_graph/src/effect/render_effect.rs:236— reactive_graph/src/effect/render_effect.rs:236-247 | reactive_graph/src/effect/render_effect.rs:306-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) server_fn/src/lib.rs:1159— server_fn/src/lib.rs:1159-1170 | server_fn/src/lib.rs:1289-1300 — 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) tachys/src/renderer/dom.rs:433— tachys/src/renderer/dom.rs:433-444 | tachys/src/renderer/sledgehammer.rs:472-483 — 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) tachys/src/view/keyed.rs:731— tachys/src/view/keyed.rs:731-742 | tachys/src/view/keyed.rs:756-767 — 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) leptos_macro/src/component.rs:1263— leptos_macro/src/component.rs:1263-1274 | leptos_macro/src/slot.rs:274-285 — before extracting anything, compare `leptos_macro/src/component.rs` and `leptos_macro/src/slot.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) integrations/actix/src/lib.rs:800— integrations/actix/src/lib.rs:800-810 | integrations/axum/src/lib.rs:1264-1274 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) leptos_macro/src/view/component_builder.rs:260— leptos_macro/src/view/component_builder.rs:260-270 | leptos_macro/src/view/slot_helper.rs:164-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) reactive_graph/src/actions/action.rs:266— reactive_graph/src/actions/action.rs:266-276 | reactive_graph/src/actions/action.rs:321-331 — 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) reactive_stores/src/keyed.rs:690— reactive_stores/src/keyed.rs:690-700 | reactive_stores/src/keyed.rs:708-718 — 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) tachys/src/html/mod.rs:208— tachys/src/html/mod.rs:208-218 | tachys/src/svg/mod.rs:298-308 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) integrations/actix/src/lib.rs:1351— integrations/actix/src/lib.rs:1351-1361 | integrations/axum/src/lib.rs:1818-1828 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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.
Repeated repair: server_fn/src/lib.rs server_fn/src/lib.rs:1343— server_fn/src/lib.rs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is server_fn::actix::get_server_fn_service at line 1343), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(server_fn): finish websocket input cleanly and stop the client pump on drop”; “fix(server_fn): stop forwarding websocket output once the client is gone”; “fix(server_fn): run the redirect hook for error responses too”; “fix(server_fn): return None from actix get_server_fn_service on extension methods”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- server_fn/src/lib.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.
Repeated repair: leptos/src/error_boundary.rs leptos/src/error_boundary.rs:385— leptos/src/error_boundary.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ErrorBoundaryView::to_html_async_with_buf at line 385), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: allow Suspense inside ErrorBoundary (closes #4908)”; “fix: dispose boundary child views synchronously (#4960)”; “fix: use nested serialization IDs to prevent mismatches that depend on the timing of Suspense on the server (closes #4897) (#4900)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- leptos/src/error_boundary.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.
Repeated repair: integrations/utils/src/lib.rs integrations/utils/src/lib.rs:364— integrations/utils/src/lib.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is leptos_integration_utils::is_path_traversal at line 364), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(integrations): build split preload links under the response's owner (#4918)”; “fix(static): pair cache-hit body and headers by file identity”; “fix: don't panic in the wasm-split prefetch machinery when its lock is unavailable (#4830)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- integrations/utils/src/lib.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.
Repeated repair: reactive_graph/src/computed/async_derived/mod.rs reactive_graph/src/computed/async_derived/mod.rs:115— reactive_graph/src/computed/async_derived/mod.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is LocalResourceNotifier::notify at line 115), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[autofix.ci] apply automated fixes”; “[autofix.ci] apply automated fixes”; “fix(reactive_graph): ignore dropped local-resource listener (#4856)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- reactive_graph/src/computed/async_derived/mod.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.
Repeated repair: leptos/src/lib.rs leptos/src/lib.rs:407— leptos/src/lib.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is leptos::prefetch_lazy_fn_on_server at line 407), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[autofix.ci] apply automated fixes”; “[autofix.ci] apply automated fixes”; “fix: don't panic in the wasm-split prefetch machinery when its lock is unavailable (#4830)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- leptos/src/lib.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.
FixmeComment tachys/src/reactive_graph/mod.rs:46— // FIXME this seems wrong — 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 projects/sso_auth_axum/src/main.rs:72— // .with_security_mode(SecurityMode::PerSession); // FIXME did this disappear? — 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 leptos_macro/src/lib.rs:6— // FIXME? every use of quote! {} is warning here -- false positive? — 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 integrations/axum/tests/service_mode/src/main.rs:62— // FIXME When `RustEmbed` does support this, or this is supported through `leptos_macro`. — 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 examples/websocket/src/websocket.rs:32— // FIXME :-) server fn fields should pass mut through to destructure — 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.
FunctionTooLong: patch.patch leptos_hot_reload/src/patch.js:2— FunctionTooLong — patch runs 356 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 256 over it, 3.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: leptos_macro::view::component_builder::component_to_tokens leptos_macro/src/view/component_builder.rs:19— FunctionTooLong — leptos_macro::view::component_builder::component_to_tokens runs 187 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 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: reactive_stores_macro::variant_to_tokens reactive_stores_macro/src/lib.rs:446— FunctionTooLong — reactive_stores_macro::variant_to_tokens 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.
FunctionTooLong: leptos_macro::view::slot_helper::slot_to_tokens leptos_macro/src/view/slot_helper.rs:15— FunctionTooLong — leptos_macro::view::slot_helper::slot_to_tokens 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.
FunctionTooLong: leptos::hydration::HydrationScripts leptos/src/hydration/mod.rs:67— FunctionTooLong — leptos::hydration::HydrationScripts runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (9 lines × 2) leptos/src/suspense_component.rs:119— leptos/src/suspense_component.rs:119-127 | leptos/src/transition.rs:100-108 — 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) reactive_graph/src/owner.rs:444— reactive_graph/src/owner.rs:444-452 | reactive_graph/src/owner.rs:470-478 — 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) server_fn/src/client.rs:142— server_fn/src/client.rs:142-150 | server_fn/src/client.rs:289-297 — 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) server_fn/src/lib.rs:1220— server_fn/src/lib.rs:1220-1228 | server_fn/src/lib.rs:1366-1374 — 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) integrations/actix/src/lib.rs:1105— integrations/actix/src/lib.rs:1105-1113 | integrations/axum/src/lib.rs:1398-1406 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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.
Hotspot: integrations/axum/src/config.rs integrations/axum/src/config.rs:769— integrations/axum/src/config.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in RouterConfiguration::apply at line 769. 1 of those changes was a fix/bug commit, and the other 16 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 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- integrations/axum/src/config.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: leptos_macro/src/component.rs leptos_macro/src/component.rs:165— leptos_macro/src/component.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in Model::expand at line 165. 4 of those changes were fix/bug commits, and the other 4 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 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- leptos_macro/src/component.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: leptos/src/hydration/islands_routing.js leptos/src/hydration/islands_routing.js:178— leptos/src/hydration/islands_routing.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in islands_routing.diffRange at line 178. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- leptos/src/hydration/islands_routing.js`: 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: leptos/src/hydration/mod.rs leptos/src/hydration/mod.rs:67— leptos/src/hydration/mod.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in leptos::hydration::HydrationScripts at line 67. 1 of those changes was a fix/bug commit, and the other 2 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 16:31:15 -04:00' --until='2026-10-25 16:31:15 -04:00' --full-history --no-merges -- leptos/src/hydration/mod.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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
Duplicated block (19 lines × 2) leptos/src/suspense_component.rs:201— leptos/src/suspense_component.rs:201-219 | leptos/src/suspense_component.rs:536-554 — 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 (19 lines × 2) projects/session_auth_axum/src/auth.rs:50— projects/session_auth_axum/src/auth.rs:50-68 | projects/sso_auth_axum/src/auth.rs:41-59 — before extracting anything, compare `projects/session_auth_axum/src/auth.rs` and `projects/sso_auth_axum/src/auth.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) reactive_stores_macro/src/lib.rs:544— reactive_stores_macro/src/lib.rs:544-562 | reactive_stores_macro/src/lib.rs:628-646 — 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 (19 lines × 2) tachys/src/view/any_view.rs:498— tachys/src/view/any_view.rs:498-516 | tachys/src/view/any_view.rs:550-568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Off the main sequence: api-boundary — api-boundary: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: leptos_config — leptos_config: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: server_fn_macro — server_fn_macro: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: hydration_context — hydration_context: abstractness 0.10, instability 0.14, distance 0.76 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
tachys::view::keyed::apply_diff (cognitive 25) tachys/src/view/keyed.rs:669— tachys::view::keyed::apply_diff has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 5 (6 pts), match/switch 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.
tachys::view::keyed::diff (cognitive 19) tachys/src/view/keyed.rs:512— tachys::view::keyed::diff has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tachys::view::keyed::unpack_moves (cognitive 17) tachys/src/view/keyed.rs:781— tachys::view::keyed::unpack_moves has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: ServerFnCall server_fn_macro/src/lib.rs:19— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Dom tachys/src/renderer/dom.rs:22— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Owner reactive_graph/src/owner.rs:59— TooManyMethods — 31 methods, declared across 2 files: src/owner.rs (24), owner/context.rs (7). The bar is 30 methods; this is 1 over it, 1.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. This type is on a published API surface — a cargo-semver-checks gate in CI (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) projects/meilisearch-searchbar/src/fallback.rs:15— projects/meilisearch-searchbar/src/fallback.rs:15-29 | projects/nginx-mpmc/app-1/src/fileserv.rs:13-24 | projects/nginx-mpmc/app-2/src/fileserv.rs:13-27 | projects/openapi-openai-api-swagger-ui/src/fileserv.rs:13-23 | projects/ory-kratos/server/src/fileserv.rs:17-28 | projects/sitemap_axum/src/fileserv.rs:16-27 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) projects/meilisearch-searchbar/src/fallback.rs:31— projects/meilisearch-searchbar/src/fallback.rs:31-45 | projects/nginx-mpmc/app-1/src/fileserv.rs:29-43 | projects/nginx-mpmc/app-2/src/fileserv.rs:32-46 | projects/openapi-openai-api-swagger-ui/src/fileserv.rs:28-42 | projects/sitemap_axum/src/fileserv.rs:32-46 | projects/tauri-from-scratch/src-orig/src/fallback.rs:30-42 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) projects/nginx-mpmc/app-1/src/error_template.rs:25— projects/nginx-mpmc/app-1/src/error_template.rs:25-72 | projects/nginx-mpmc/app-2/src/error_template.rs:25-72 | projects/openapi-openai-api-swagger-ui/src/error_template.rs:25-72 | projects/ory-kratos/app/src/error_template.rs:28-83 | projects/session_auth_axum/src/error_template.rs:12-57 | projects/sitemap_axum/src/error_template.rs:25-72 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (18 lines × 2) const_str_slice_concat/src/lib.rs:29— const_str_slice_concat/src/lib.rs:29-46 | const_str_slice_concat/src/lib.rs:58-75 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) integrations/actix/src/lib.rs:1290— integrations/actix/src/lib.rs:1290-1307 | integrations/axum/src/lib.rs:1599-1616 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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) reactive_stores_macro/src/lib.rs:140— reactive_stores_macro/src/lib.rs:140-157 | reactive_stores_macro/src/lib.rs:663-680 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) leptos_macro/src/view/component_builder.rs:203— leptos_macro/src/view/component_builder.rs:203-217 | leptos_macro/src/view/slot_helper.rs:102-116 — 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 (15 lines × 2) meta/src/title.rs:102— meta/src/title.rs:102-116 | meta/src/title.rs:117-131 — 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) leptos_macro/src/component.rs:1388— leptos_macro/src/component.rs:1388-1402 | leptos_macro/src/slot.rs:354-368 — before extracting anything, compare `leptos_macro/src/component.rs` and `leptos_macro/src/slot.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) reactive_graph/src/effect/render_effect.rs:236— reactive_graph/src/effect/render_effect.rs:236-243 | reactive_graph/src/effect/render_effect.rs:306-313 | reactive_graph/src/effect/render_effect.rs:377-384 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) router/src/flat_router.rs:145— router/src/flat_router.rs:145-152 | router/src/flat_router.rs:700-707 | router/src/flat_router.rs:796-803 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) reactive_graph/src/signal/arc_read.rs:65— reactive_graph/src/signal/arc_read.rs:65-72 | reactive_graph/src/signal/arc_rw.rs:105-112 | reactive_graph/src/signal/arc_write.rs:65-72 — 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.
leptos_router::form::Form::inner (cyclomatic 29) router/src/form.rs:88— leptos_router::form::Form::inner has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
leptos_router::location::handle_anchor_click (cyclomatic 16) router/src/location/mod.rs:294— leptos_router::location::handle_anchor_click 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.
patch.patch::buildActualChildren (cognitive 88) leptos_hot_reload/src/patch.js:282— patch.patch::buildActualChildren has cognitive complexity 88 (threshold 15). Drivers by points: if/else 26 (68 pts), loops 5 (18 pts), boolean chains 2 (nesting depth added 55). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (patch.patch, patch.patch::fromReplacementNode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
patch.patch::fromReplacementNode (cognitive 18) leptos_hot_reload/src/patch.js:227— patch.patch::fromReplacementNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (6 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (patch.patch, patch.patch::buildActualChildren) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
leptos_router::form::Form::inner (cognitive 65) router/src/form.rs:88— leptos_router::form::Form::inner has cognitive complexity 65 (threshold 15). Drivers by points: if/else 25 (50 pts), match/switch 4 (12 pts), boolean chains 3 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
leptos_router::location::handle_anchor_click (cognitive 21) router/src/location/mod.rs:294— leptos_router::location::handle_anchor_click has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 7, 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.
LNode::diff_children (cognitive 37) leptos_hot_reload/src/diff.rs:230— LNode::diff_children has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 5 (11 pts), boolean chains 6 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LNode::parse_node (cognitive 28) leptos_hot_reload/src/node.rs:62— LNode::parse_node has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (11 pts), match/switch 2 (4 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.
openapi_openai_api_swagger_ui::open_ai::make_openapi_call_via_gpt (cognitive 20) projects/openapi-openai-api-swagger-ui/src/open_ai.rs:30— openapi_openai_api_swagger_ui::open_ai::make_openapi_call_via_gpt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (16 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.
openapi_openai_api_swagger_ui::open_ai::parse_schema_into_openapi_property (cognitive 20) projects/openapi-openai-api-swagger-ui/src/open_ai.rs:111— openapi_openai_api_swagger_ui::open_ai::parse_schema_into_openapi_property has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 3 (5 pts), loops 1 (3 pts) (nesting depth added 12). 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.
Either::to_html_with_buf (cognitive 19) tachys/src/view/either.rs:311— Either::to_html_with_buf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 4, 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. This shape REPEATS in the file: one other method here (Either::to_html_async_with_buf) 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.
Either::to_html_async_with_buf (cognitive 19) tachys/src/view/either.rs:346— Either::to_html_async_with_buf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 4, 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. This shape REPEATS in the file: one other method here (Either::to_html_with_buf) 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.
TypedBuilderOpts::expand (cognitive 18) leptos_macro/src/component.rs:1093— TypedBuilderOpts::expand has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TypedBuilderOpts::expand (cognitive 17) leptos_macro/src/slot.rs:177— TypedBuilderOpts::expand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
reactive_stores_macro::field_to_tokens (cognitive 18) reactive_stores_macro/src/lib.rs:364— reactive_stores_macro::field_to_tokens has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
reactive_stores_macro::variant_to_tokens (cognitive 16) reactive_stores_macro/src/lib.rs:446— reactive_stores_macro::variant_to_tokens has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassTooLong: ServerFnCall server_fn_macro/src/lib.rs:19— ClassTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 35 methods, 3 blocks, lines 19-876. The bar is 400 significant lines; this is 117 over it, 1.29× 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: FlatRoutesView router/src/flat_router.rs:35— ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 5 blocks, lines 35-823. The bar is 400 significant lines; this is 34 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) projects/nginx-mpmc/app-1/src/app.rs:7— projects/nginx-mpmc/app-1/src/app.rs:7-37 | projects/nginx-mpmc/app-2/src/app.rs:7-37 | projects/openapi-openai-api-swagger-ui/src/app.rs:7-37 | projects/ory-kratos/app/src/lib.rs:20-49 | projects/sitemap_axum/src/app.rs:7-37 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) reactive_stores/src/iter.rs:138— reactive_stores/src/iter.rs:138-153 | reactive_stores/src/keyed.rs:256-271 | reactive_stores/src/keyed.rs:778-793 | REDACTED:135-146 | reactive_stores/src/subfield.rs:126-141 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (25 lines × 2) integrations/actix/src/lib.rs:269— integrations/actix/src/lib.rs:269-293 | integrations/axum/src/lib.rs:286-310 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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 (25 lines × 2) tachys/src/html/element/mod.rs:561— tachys/src/html/element/mod.rs:561-585 | tachys/src/html/element/mod.rs:632-656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) reactive_graph/src/effect/effect.rs:357— reactive_graph/src/effect/effect.rs:357-377 | reactive_graph/src/effect/effect.rs:495-515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) router/src/nested_router.rs:471— router/src/nested_router.rs:471-491 | router/src/nested_router.rs:527-547 — 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) leptos_macro/src/memo.rs:19— leptos_macro/src/memo.rs:19-34 | leptos_macro/src/slice.rs:19-34 — 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 (16 lines × 2) projects/hexagonal-architecture/src/app.rs:12— projects/hexagonal-architecture/src/app.rs:12-27 | projects/tauri-from-scratch/src-orig/src/app.rs:6-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 (11–12 lines × 2) router/src/reactive.rs:325— router/src/reactive.rs:325-335 | router/src/reactive.rs:348-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) tachys/src/view/either.rs:324— tachys/src/view/either.rs:324-334 | tachys/src/view/either.rs:365-376 — 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) projects/openapi-openai-api-swagger-ui/src/fileserv.rs:14— projects/openapi-openai-api-swagger-ui/src/fileserv.rs:14-19 | projects/ory-kratos/server/src/fileserv.rs:18-24 | projects/sitemap_axum/src/fileserv.rs:17-23 — before extracting anything, compare `projects/openapi-openai-api-swagger-ui/src/fileserv.rs` and `projects/sitemap_axum/src/fileserv.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 × 3) server_fn/src/request/browser.rs:149— server_fn/src/request/browser.rs:149-154 | server_fn/src/request/browser.rs:186-191 | server_fn/src/request/browser.rs:220-225 — 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) oco/src/lib.rs:643— oco/src/lib.rs:643-647 | oco/src/lib.rs:671-675 | oco/src/lib.rs:703-707 — 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) projects/meilisearch-searchbar/src/fallback.rs:18— projects/meilisearch-searchbar/src/fallback.rs:18-24 | projects/nginx-mpmc/app-1/src/fileserv.rs:16-20 | projects/nginx-mpmc/app-2/src/fileserv.rs:18-23 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/fileserv.rs` and `projects/nginx-mpmc/app-2/src/fileserv.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 × 7) reactive_graph/src/computed/async_derived/async_derived.rs:161— reactive_graph/src/computed/async_derived/async_derived.rs:161-167 | reactive_graph/src/computed/async_derived/async_derived.rs:196-202 | reactive_graph/src/computed/memo.rs:176-182 | reactive_graph/src/computed/memo.rs:222-228 | reactive_graph/src/signal/rw.rs:140-146 | reactive_stores/src/lib.rs:678-684 | reactive_stores/src/lib.rs:702-708 — there are 7 copies across 4 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 7 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 7) reactive_graph/src/signal/mapped.rs:353— reactive_graph/src/signal/mapped.rs:353-359 | reactive_graph/src/signal/read.rs:169-175 | reactive_graph/src/signal/read.rs:183-189 | reactive_graph/src/signal/rw.rs:391-397 | reactive_graph/src/signal/rw.rs:415-421 | reactive_graph/src/signal/write.rs:119-125 | reactive_graph/src/signal/write.rs:133-139 — there are 7 copies across 4 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 7 sites; resolving a subset leaves the remainder to drift apart.
Low cohesion: Resource (LCOM4 8) leptos_server/src/resource.rs:878— Resource's methods fall into 8 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 8 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: Request (LCOM4 6) integrations/actix/src/lib.rs:89— Request'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.
patch.patch (cyclomatic 48) leptos_hot_reload/src/patch.js:2— patch.patch has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (patch.patch::buildActualChildren) 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.
ServerFnArgs::parse (cyclomatic 46) server_fn_macro/src/lib.rs:1067— ServerFnArgs::parse 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.
Model::expand (cyclomatic 37) leptos_macro/src/component.rs:165— Model::expand has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EitherOf16Future::poll (cyclomatic 32) either_of/src/lib.rs:453— EitherOf16Future::poll has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
patch.patch::buildActualChildren (cyclomatic 31) leptos_hot_reload/src/patch.js:282— patch.patch::buildActualChildren 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. This shape REPEATS in the file: one other method here (patch.patch) 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.
EitherOf15Future::poll (cyclomatic 30) either_of/src/lib.rs:453— EitherOf15Future::poll has cyclomatic complexity 30 (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.
EitherOf14Future::poll (cyclomatic 28) either_of/src/lib.rs:453— EitherOf14Future::poll has cyclomatic complexity 28 (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.
RouterConfiguration::apply (cyclomatic 27) integrations/axum/src/config.rs:769— RouterConfiguration::apply 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.
EitherOf13Future::poll (cyclomatic 26) either_of/src/lib.rs:453— EitherOf13Future::poll 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.
StreamBuilder::poll_next (cyclomatic 25) tachys/src/ssr/mod.rs:356— StreamBuilder::poll_next has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EitherOf12Future::poll (cyclomatic 24) either_of/src/lib.rs:453— EitherOf12Future::poll 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.
EitherOf11Future::poll (cyclomatic 22) either_of/src/lib.rs:453— EitherOf11Future::poll 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.
EitherOf10Future::poll (cyclomatic 20) either_of/src/lib.rs:453— EitherOf10Future::poll has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
LNode::diff_children (cyclomatic 20) leptos_hot_reload/src/diff.rs:230— LNode::diff_children 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.
leptos::hydration::HydrationScripts (cyclomatic 19) leptos/src/hydration/mod.rs:67— leptos::hydration::HydrationScripts 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.
islands_routing.clickToReq (cyclomatic 19) leptos/src/hydration/islands_routing.js:84— islands_routing.clickToReq has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EitherOf9Future::poll (cyclomatic 18) either_of/src/lib.rs:453— EitherOf9Future::poll 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.
StaticSegment::test (cyclomatic 17) router/src/matching/horizontal/static_segment.rs:65— StaticSegment::test 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.
EitherOf8Future::poll (cyclomatic 16) either_of/src/lib.rs:453— EitherOf8Future::poll has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
StaticPath::into_paths (cyclomatic 16) router/src/static_routes.rs:215— StaticPath::into_paths 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.
ActixRequest::try_into_websocket (cyclomatic 16) server_fn/src/request/actix.rs:119— ActixRequest::try_into_websocket 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 tachys/src/html/event.rs:780— // Hack for correct casing — 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.
patch.patch (cognitive 129) leptos_hot_reload/src/patch.js:2— patch.patch has cognitive complexity 129 (threshold 15). Drivers by points: if/else 71 (159 pts), loops 16 (55 pts), boolean chains 15, ternaries 3 (12 pts), error handling 1 (nesting depth added 136). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (patch.patch::fromReplacementNode, patch.patch::buildActualChildren) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ServerFnArgs::parse (cognitive 113) server_fn_macro/src/lib.rs:1067— ServerFnArgs::parse has cognitive complexity 113 (threshold 15). Drivers by points: if/else 40 (107 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 70). 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.
StreamBuilder::poll_next (cognitive 100) tachys/src/ssr/mod.rs:356— StreamBuilder::poll_next has cognitive complexity 100 (threshold 15). Drivers by points: if/else 18 (49 pts), loops 7 (38 pts), match/switch 4 (13 pts) (nesting depth added 71). 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.
Model::expand (cognitive 76) leptos_macro/src/component.rs:165— Model::expand has cognitive complexity 76 (threshold 15). Drivers by points: if/else 46 (64 pts), boolean chains 10, match/switch 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StaticPath::into_paths (cognitive 53) router/src/static_routes.rs:215— StaticPath::into_paths has cognitive complexity 53 (threshold 15). Drivers by points: if/else 9 (31 pts), loops 5 (19 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
leptos::hydration::HydrationScripts (cognitive 41) leptos/src/hydration/mod.rs:67— leptos::hydration::HydrationScripts has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (33 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 20). 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.
Request::try_into_websocket (cognitive 32) server_fn/src/request/axum.rs:80— Request::try_into_websocket has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (25 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
leptos_axum::handle_static_route (cognitive 32) integrations/axum/src/lib.rs:1866— leptos_axum::handle_static_route has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 4 (11 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ActixRequest::try_into_websocket (cognitive 32) server_fn/src/request/actix.rs:119— ActixRequest::try_into_websocket has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (25 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RouterConfiguration::apply (cognitive 26) integrations/axum/src/config.rs:769— RouterConfiguration::apply has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 5 (7 pts), boolean chains 2 (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.
StaticSegment::test (cognitive 25) router/src/matching/horizontal/static_segment.rs:65— StaticSegment::test has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 4, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NestedRoutesView::rebuild (cognitive 25) router/src/nested_router.rs:159— NestedRoutesView::rebuild has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (5 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.
Dom::add_event_listener_delegated (cognitive 24) tachys/src/renderer/dom.rs:365— Dom::add_event_listener_delegated has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 1 (2 pts), boolean chains 1 (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.
Sledgehammer::add_event_listener_delegated (cognitive 24) tachys/src/renderer/sledgehammer.rs:404— Sledgehammer::add_event_listener_delegated has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 1 (2 pts), boolean chains 1 (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.
SuspenseBoundary::to_html_async_with_buf (cognitive 23) leptos/src/suspense_component.rs:327— SuspenseBoundary::to_html_async_with_buf has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 4 (7 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Match::rebuild_nested_route (cognitive 23) router/src/nested_router.rs:814— Match::rebuild_nested_route has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 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.
App::leptos_routes_with_context (cognitive 22) integrations/actix/src/lib.rs:1612— App::leptos_routes_with_context has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (7 pts), match/switch 1 (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.
FlatRoutesView::rebuild (cognitive 22) router/src/flat_router.rs:197— FlatRoutesView::rebuild has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArcOnceResource::new_with_options (cognitive 20) leptos_server/src/once_resource.rs:101— ArcOnceResource::new_with_options has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 2 (7 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.
PatchModel::expand (cognitive 20) reactive_stores_macro/src/lib.rs:704— PatchModel::expand has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 4 (7 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.
AnyView::to_html_async_with_buf (cognitive 20) tachys/src/view/any_view.rs:518— AnyView::to_html_async_with_buf has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::hydrateIslands::traverse (cognitive 20) leptos/src/hydration/island_script.js:12— (anonymous)::hydrateIslands::traverse has cognitive complexity 20 (threshold 15). Drivers by points: loops 3 (11 pts), if/else 5 (8 pts), boolean chains 1 (nesting depth added 11). 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.
AsyncDataStream::poll_next (cognitive 19) hydration_context/src/ssr.rs:396— AsyncDataStream::poll_next has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 5 (7 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EitherOf16Future::poll (cognitive 18) either_of/src/lib.rs:453— EitherOf16Future::poll has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 17 (18 pts) (nesting depth added 1). 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.
islands_routing.diffRange (cognitive 18) leptos/src/hydration/islands_routing.js:178— islands_routing.diffRange has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EitherOf15Future::poll (cognitive 17) either_of/src/lib.rs:453— EitherOf15Future::poll has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 16 (17 pts) (nesting depth added 1). 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.
islands_routing.navigateToPage (cognitive 17) leptos/src/hydration/islands_routing.js:33— islands_routing.navigateToPage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 1 (2 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EitherOf14Future::poll (cognitive 16) either_of/src/lib.rs:453— EitherOf14Future::poll has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 15 (16 pts) (nesting depth added 1). 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.
islands_routing.collectForItems (cognitive 16) leptos/src/hydration/islands_routing.js:264— islands_routing.collectForItems has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (35 shared lines) reactive_graph/src/effect/render_effect.rs:145— reactive_graph/src/effect/render_effect.rs:145-247 | reactive_graph/src/effect/render_effect.rs:252-317 — These two members are variants of one another: 35 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) leptos/src/error_boundary.rs:220— leptos/src/error_boundary.rs:220-264 | leptos/src/error_boundary.rs:483-539 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) leptos_dom/src/helpers.rs:229— leptos_dom/src/helpers.rs:229-249 | leptos_dom/src/helpers.rs:278-298 | leptos_dom/src/helpers.rs:343-373 | leptos_dom/src/helpers.rs:482-512 — 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 (55 lines × 2) leptos_macro/src/view/mod.rs:421— leptos_macro/src/view/mod.rs:421-475 | leptos_macro/src/view/mod.rs:530-584 — 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 (50 lines × 2) leptos_macro/src/component.rs:1100— leptos_macro/src/component.rs:1100-1149 | leptos_macro/src/slot.rs:178-227 — before extracting anything, compare `leptos_macro/src/component.rs` and `leptos_macro/src/slot.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (43 lines × 2) router/src/flat_router.rs:570— router/src/flat_router.rs:570-612 | router/src/nested_router.rs:318-360 — 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 (37–39 lines × 3) router/src/flat_router.rs:89— router/src/flat_router.rs:89-125 | router/src/flat_router.rs:642-680 | router/src/flat_router.rs:737-775 — 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 (34–36 lines × 2) leptos_macro/src/view/mod.rs:387— leptos_macro/src/view/mod.rs:387-420 | leptos_macro/src/view/mod.rs:490-525 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (35 lines × 4) projects/nginx-mpmc/app-1/src/error_template.rs:26— projects/nginx-mpmc/app-1/src/error_template.rs:26-60 | projects/nginx-mpmc/app-2/src/error_template.rs:26-60 | projects/openapi-openai-api-swagger-ui/src/error_template.rs:26-60 | projects/sitemap_axum/src/error_template.rs:26-60 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/error_template.rs` and `projects/nginx-mpmc/app-2/src/error_template.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 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 (30–33 lines × 2) tachys/src/reactive_graph/suspense.rs:195— tachys/src/reactive_graph/suspense.rs:195-224 | tachys/src/reactive_graph/suspense.rs:409-441 — 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 (29–31 lines × 2) router/src/flat_router.rs:127— router/src/flat_router.rs:127-155 | router/src/flat_router.rs:682-712 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30 lines × 2) tachys/src/html/element/mod.rs:522— tachys/src/html/element/mod.rs:522-551 | tachys/src/html/element/mod.rs:593-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 (28–29 lines × 2) integrations/actix/src/lib.rs:1230— integrations/actix/src/lib.rs:1230-1257 | integrations/axum/src/lib.rs:1537-1565 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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 (27 lines × 2) integrations/actix/src/lib.rs:1369— integrations/actix/src/lib.rs:1369-1395 | integrations/axum/src/lib.rs:1837-1863 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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 (26–27 lines × 2) leptos/src/mount.rs:63— leptos/src/mount.rs:63-88 | leptos/src/mount.rs:115-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) leptos_macro/src/component.rs:1350— leptos_macro/src/component.rs:1350-1375 | leptos_macro/src/slot.rs:315-340 — before extracting anything, compare `leptos_macro/src/component.rs` and `leptos_macro/src/slot.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22–25 lines × 2) tachys/src/view/keyed.rs:362— tachys/src/view/keyed.rs:362-386 | tachys/src/view/keyed.rs:407-428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) router/src/form.rs:188— router/src/form.rs:188-210 | router/src/form.rs:264-286 — 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) leptos/src/form.rs:246— leptos/src/form.rs:246-267 | router/src/location/history.rs:296-317 — 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 (21–22 lines × 2) reactive_graph/src/callback.rs:107— reactive_graph/src/callback.rs:107-128 | reactive_graph/src/callback.rs:187-207 — 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 (20–21 lines × 2) tachys/src/hydration.rs:51— tachys/src/hydration.rs:51-71 | tachys/src/hydration.rs:79-98 — 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 (19–20 lines × 2) integrations/actix/src/lib.rs:1154— integrations/actix/src/lib.rs:1154-1172 | integrations/axum/src/lib.rs:1456-1475 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 3) projects/nginx-mpmc/app-1/src/app.rs:19— projects/nginx-mpmc/app-1/src/app.rs:19-37 | projects/openapi-openai-api-swagger-ui/src/app.rs:19-37 | projects/sitemap_axum/src/app.rs:19-37 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/app.rs` and `projects/openapi-openai-api-swagger-ui/src/app.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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–19 lines × 2) integrations/actix/src/lib.rs:250— integrations/actix/src/lib.rs:250-267 | integrations/axum/src/lib.rs:267-285 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–19 lines × 2) router/src/static_routes.rs:248— router/src/static_routes.rs:248-266 | router/src/static_routes.rs:277-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 (16–17 lines × 2) integrations/actix/src/lib.rs:1174— integrations/actix/src/lib.rs:1174-1190 | integrations/axum/src/lib.rs:1477-1492 — before extracting anything, compare `integrations/actix/src/lib.rs` and `integrations/axum/src/lib.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 218 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 (16 lines × 5) projects/nginx-mpmc/app-1/src/error_template.rs:26— projects/nginx-mpmc/app-1/src/error_template.rs:26-41 | projects/nginx-mpmc/app-2/src/error_template.rs:26-41 | projects/openapi-openai-api-swagger-ui/src/error_template.rs:26-41 | projects/ory-kratos/app/src/error_template.rs:34-49 | projects/sitemap_axum/src/error_template.rs:26-41 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/error_template.rs` and `projects/nginx-mpmc/app-2/src/error_template.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 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 (16 lines × 3) router/src/nested_router.rs:94— router/src/nested_router.rs:94-109 | router/src/nested_router.rs:462-477 | router/src/nested_router.rs:518-533 — 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 (15 lines × 6) projects/nginx-mpmc/app-1/src/error_template.rs:56— projects/nginx-mpmc/app-1/src/error_template.rs:56-70 | projects/nginx-mpmc/app-2/src/error_template.rs:56-70 | projects/openapi-openai-api-swagger-ui/src/error_template.rs:56-70 | projects/ory-kratos/app/src/error_template.rs:66-80 | projects/session_auth_axum/src/error_template.rs:41-55 | projects/sitemap_axum/src/error_template.rs:56-70 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/error_template.rs` and `projects/nginx-mpmc/app-2/src/error_template.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 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 (14–15 lines × 2) tachys/src/reactive_graph/suspense.rs:178— tachys/src/reactive_graph/suspense.rs:178-191 | tachys/src/reactive_graph/suspense.rs:393-407 — 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–14 lines × 5) reactive_stores/src/iter.rs:140— reactive_stores/src/iter.rs:140-153 | reactive_stores/src/keyed.rs:258-271 | reactive_stores/src/keyed.rs:780-793 | REDACTED:137-146 | reactive_stores/src/subfield.rs:128-141 — before extracting anything, compare `reactive_stores/src/keyed.rs` and `reactive_stores/src/subfield.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) reactive_graph/src/actions/action.rs:296— reactive_graph/src/actions/action.rs:296-309 | reactive_graph/src/actions/action.rs:351-363 — 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) tachys/src/renderer/dom.rs:167— tachys/src/renderer/dom.rs:167-180 | tachys/src/renderer/dom.rs:191-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 3) tachys/src/hydration.rs:158— tachys/src/hydration.rs:158-170 | tachys/src/hydration.rs:190-202 | tachys/src/hydration.rs:222-234 — 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–13 lines × 2) leptos_dom/src/helpers.rs:346— leptos_dom/src/helpers.rs:346-358 | leptos_dom/src/helpers.rs:485-496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–12 lines × 5) projects/nginx-mpmc/app-1/src/fileserv.rs:32— projects/nginx-mpmc/app-1/src/fileserv.rs:32-43 | projects/nginx-mpmc/app-2/src/fileserv.rs:35-46 | projects/openapi-openai-api-swagger-ui/src/fileserv.rs:31-42 | projects/sitemap_axum/src/fileserv.rs:35-46 | projects/tauri-from-scratch/src-orig/src/fallback.rs:33-42 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/fileserv.rs` and `projects/nginx-mpmc/app-2/src/fileserv.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) projects/nginx-mpmc/app-1/src/app.rs:19— projects/nginx-mpmc/app-1/src/app.rs:19-32 | projects/openapi-openai-api-swagger-ui/src/app.rs:19-32 | projects/ory-kratos/app/src/lib.rs:28-38 | projects/sitemap_axum/src/app.rs:19-32 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/app.rs` and `projects/openapi-openai-api-swagger-ui/src/app.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) server_fn/src/request/browser.rs:163— server_fn/src/request/browser.rs:163-173 | server_fn/src/request/browser.rs:200-210 | server_fn/src/request/browser.rs:279-289 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–10 lines × 6) projects/meilisearch-searchbar/src/fallback.rs:32— projects/meilisearch-searchbar/src/fallback.rs:32-41 | projects/nginx-mpmc/app-1/src/fileserv.rs:30-39 | projects/nginx-mpmc/app-2/src/fileserv.rs:33-42 | projects/openapi-openai-api-swagger-ui/src/fileserv.rs:29-38 | projects/sitemap_axum/src/fileserv.rs:33-42 | projects/tauri-from-scratch/src-orig/src/fallback.rs:31-38 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/fileserv.rs` and `projects/nginx-mpmc/app-2/src/fileserv.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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–10 lines × 4) projects/nginx-mpmc/app-1/src/fileserv.rs:16— projects/nginx-mpmc/app-1/src/fileserv.rs:16-24 | projects/nginx-mpmc/app-2/src/fileserv.rs:18-27 | projects/openapi-openai-api-swagger-ui/src/fileserv.rs:15-23 | projects/sitemap_axum/src/fileserv.rs:18-27 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/fileserv.rs` and `projects/nginx-mpmc/app-2/src/fileserv.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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–10 lines × 2) leptos/src/for_loop.rs:140— leptos/src/for_loop.rs:140-147 | leptos/src/for_loop.rs:233-242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) projects/nginx-mpmc/app-1/src/main.rs:32— projects/nginx-mpmc/app-1/src/main.rs:32-41 | projects/nginx-mpmc/app-2/src/main.rs:25-33 — 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 × 4) leptos_dom/src/helpers.rs:230— leptos_dom/src/helpers.rs:230-238 | leptos_dom/src/helpers.rs:279-287 | leptos_dom/src/helpers.rs:350-358 | leptos_dom/src/helpers.rs:488-496 — 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 (7–9 lines × 2) reactive_stores/src/store_field.rs:77— reactive_stores/src/store_field.rs:77-85 | reactive_stores/src/store_field.rs:108-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 2) reactive_graph/src/signal_fn.rs:41— reactive_graph/src/signal_fn.rs:41-48 | reactive_graph/src/signal_fn.rs:85-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 (7 lines × 3) projects/nginx-mpmc/app-1/src/main.rs:35— projects/nginx-mpmc/app-1/src/main.rs:35-42 | projects/nginx-mpmc/app-2/src/main.rs:28-34 | projects/openapi-openai-api-swagger-ui/src/main.rs:28-35 — 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 (10 lines × 40) leptos_server/src/action.rs:120— leptos_server/src/action.rs:120-129 | leptos_server/src/action.rs:223-232 | leptos_server/src/local_resource.rs:158-167 | leptos_server/src/local_resource.rs:399-408 | leptos_server/src/multi_action.rs:80-89 | leptos_server/src/multi_action.rs:179-188 | leptos_server/src/resource.rs:136-145 | leptos_server/src/resource.rs:906-915 | reactive_graph/src/actions/action.rs:555-564 | reactive_graph/src/actions/action.rs:1104-1113 | reactive_graph/src/actions/multi_action.rs:64-73 | reactive_graph/src/computed/arc_memo.rs:191-200 | reactive_graph/src/computed/async_derived/arc_async_derived.rs:212-221 | reactive_graph/src/computed/async_derived/async_derived.rs:306-315 | reactive_graph/src/computed/memo.rs:278-287 | reactive_graph/src/effect/immediate.rs:418-427 | reactive_graph/src/owner/arc_stored_value.rs:72-81 | reactive_graph/src/owner/stored_value.rs:66-75 | reactive_graph/src/signal/arc_read.rs:112-121 | reactive_graph/src/signal/arc_rw.rs:214-223 | reactive_graph/src/signal/arc_trigger.rs:90-99 | reactive_graph/src/signal/arc_write.rs:100-109 | reactive_graph/src/signal/mapped.rs:120-129 | reactive_graph/src/signal/mapped.rs:279-288 | reactive_graph/src/signal/read.rs:107-116 | reactive_graph/src/signal/rw.rs:298-307 | reactive_graph/src/signal/trigger.rs:85-94 | reactive_graph/src/signal/write.rs:102-111 | reactive_graph/src/wrappers.rs:347-356 | reactive_graph/src/wrappers.rs:509-518 | reactive_stores/src/arc_field.rs:296-305 | reactive_stores/src/deref.rs:104-113 | reactive_stores/src/field.rs:227-236 | reactive_stores/src/iter.rs:160-169 | reactive_stores/src/keyed.rs:429-438 | reactive_stores/src/keyed.rs:800-809 | reactive_stores/src/lib.rs:594-603 | reactive_stores/src/lib.rs:750-759 | REDACTED:150-159 | reactive_stores/src/subfield.rs:148-157 — before extracting anything, compare `reactive_stores/src/keyed.rs` and `reactive_stores/src/subfield.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) reactive_graph/src/computed/arc_memo.rs:301— reactive_graph/src/computed/arc_memo.rs:301-306 | reactive_graph/src/computed/async_derived/arc_async_derived.rs:793-798 | reactive_graph/src/effect/render_effect.rs:394-399 | tachys/src/reactive_graph/suspense.rs:109-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (5 lines × 6) reactive_stores/src/deref.rs:129— reactive_stores/src/deref.rs:129-133 | reactive_stores/src/keyed.rs:460-464 | reactive_stores/src/keyed.rs:833-837 | reactive_stores/src/lib.rs:651-655 | REDACTED:177-181 | reactive_stores/src/subfield.rs:175-179 — before extracting anything, compare `reactive_stores/src/keyed.rs` and `reactive_stores/src/subfield.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 18) either_of/src/lib.rs:119— either_of/src/lib.rs:119-468 | either_of/src/lib.rs:132-468 | either_of/src/lib.rs:138-468 | either_of/src/lib.rs:147-468 | either_of/src/lib.rs:156-468 | either_of/src/lib.rs:181-468 | either_of/src/lib.rs:272-468 | either_of/src/lib.rs:282-468 | either_of/src/lib.rs:332-468 | either_of/src/lib.rs:342-468 | either_of/src/lib.rs:407-468 | either_of/src/lib.rs:418-468 | tachys/src/view/either.rs:59-64 | tachys/src/view/either.rs:187-192 | tachys/src/view/either.rs:257-262 | tachys/src/view/either.rs:271-276 | tachys/src/view/either.rs:287-292 | tachys/src/view/either.rs:304-309 — there are 18 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 18 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (14 lines × 5) projects/nginx-mpmc/app-1/src/app.rs:9— projects/nginx-mpmc/app-1/src/app.rs:9-29 | projects/nginx-mpmc/app-2/src/app.rs:9-29 | projects/openapi-openai-api-swagger-ui/src/app.rs:9-29 | projects/ory-kratos/app/src/lib.rs:22-35 | projects/sitemap_axum/src/app.rs:9-29 — before extracting anything, compare `projects/nginx-mpmc/app-1/src/app.rs` and `projects/nginx-mpmc/app-2/src/app.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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.
Sync-over-async blocking projects/session_auth_axum/src/todo.rs:76— `add_todo` 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 (36 lines × 2 locations) projects/hexagonal-architecture/end2end/playwright.config.ts:13— projects/hexagonal-architecture/end2end/playwright.config.ts:13 · projects/openapi-openai-api-swagger-ui/end2end/playwright.config.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (19 lines × 2 locations) leptos_hot_reload/src/patch.js:361— leptos_hot_reload/src/patch.js:361 · leptos_hot_reload/src/patch.js:382 — 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 (15 lines × 2 locations) leptos_hot_reload/src/patch.js:331— leptos_hot_reload/src/patch.js:331 · leptos_hot_reload/src/patch.js:410 — 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 locations) leptos/src/hydration/islands_routing.js:328— leptos/src/hydration/islands_routing.js:328 · leptos/src/hydration/islands_routing.js:375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Complex function patch (cyclomatic 48, cognitive 128) leptos_hot_reload/src/patch.js:2— patch has cyclomatic complexity 48 and cognitive complexity 128; 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 buildActualChildren (cyclomatic 28, cognitive 84) leptos_hot_reload/src/patch.js:282— buildActualChildren has cyclomatic complexity 28 and cognitive complexity 84; 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 clickToReq (cyclomatic 18, cognitive 13) leptos/src/hydration/islands_routing.js:84— clickToReq has cyclomatic complexity 18 and cognitive complexity 13; 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 diffRange (cyclomatic 15, cognitive 18) leptos/src/hydration/islands_routing.js:178— diffRange has cyclomatic complexity 15 and cognitive complexity 18; 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 collectForItems (cyclomatic 11, cognitive 16) leptos/src/hydration/islands_routing.js:264— collectForItems 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· leptos_hot_reload/src/patch.js · ×1
leptos_hot_reload/src/patch.js: 458 lines of code leptos_hot_reload/src/patch.js:1— leptos_hot_reload/src/patch.js has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Blocking `thread::sleep` inside an `async` body projects/session_auth_axum/src/todo.rs:88— This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped leptos_hot_reload/src/patch.js:470— `html` 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.
Orphaned file projects/ory-kratos/app/src/auth/settings.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 projects/ory-kratos/app/src/auth/registration.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 projects/openapi-openai-api-swagger-ui/src/open_ai.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 projects/ory-kratos/app/src/auth/recovery.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 projects/ory-kratos/app/src/auth/login.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 projects/sso_auth_axum/src/sign_in_sign_up.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 projects/ory-kratos/app/src/database_calls.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 reactive_graph/src/trait_options.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 projects/ory-kratos/app/src/auth/verification.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 projects/sitemap_axum/src/sitemap.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 projects/ory-kratos/app/src/auth/kratos_html.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 projects/hexagonal-architecture/src/lib.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 projects/sso_auth_axum/src/lib.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 projects/openapi-openai-api-swagger-ui/src/app.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file projects/login_with_token_csr_only/client/src/lib.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 projects/hexagonal-architecture/src/trait_impl.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 reactive_stores/src/len.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 projects/login_with_token_csr_only/server/src/application.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 projects/meilisearch-searchbar/src/lib.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 reactive_graph/src/owner/arc_stored_value.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 projects/ory-kratos/app/src/lib.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 projects/bevy3d_ui/src/demos/bevydemo1/scene.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 projects/login_with_token_csr_only/server/src/main.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 projects/ory-kratos/app/src/posts/post.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 projects/ory-kratos/app/src/auth/logout.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging router/src/form.rs:146— `error!` at line 146 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 router/src/form.rs:204— `warn!` at line 204 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 router/src/form.rs:222— `error!` at line 222 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 router/src/form.rs:280— `warn!` at line 280 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 router/src/static_routes.rs:387— `warn!` at line 387 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 router/src/static_routes.rs:418— `warn!` at line 418 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 router/src/location/history.rs:164— `error!` at line 164 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 router/src/location/history.rs:192— `error!` at line 192 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 reactive_graph/src/lib.rs:129— `warn!` at line 129 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 projects/ory-kratos/app/src/auth/logout.rs:37— `error!` at line 37 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 projects/ory-kratos/app/src/auth/logout.rs:68— `debug!` at line 68 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 projects/ory-kratos/app/src/auth/recovery.rs:74— `error!` at line 74 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 projects/ory-kratos/app/src/auth/settings.rs:94— `error!` at line 94 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 projects/ory-kratos/app/src/auth/settings.rs:133— `error!` at line 133 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 projects/ory-kratos/app/src/auth/settings.rs:150— `error!` at line 150 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 projects/ory-kratos/app/src/auth/settings.rs:178— `error!` at line 178 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 projects/ory-kratos/app/src/auth/settings.rs:192— `error!` at line 192 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 projects/ory-kratos/app/src/auth/settings.rs:261— `error!` at line 261 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 projects/ory-kratos/app/src/auth/settings.rs:264— `error!` at line 264 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 projects/ory-kratos/app/src/auth/verification.rs:45— `debug!` at line 45 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 meta/src/lib.rs:451— `warn!` at line 451 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 leptos_server/src/once_resource.rs:199— `error!` at line 199 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 leptos_server/src/resource.rs:365— `error!` at line 365 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 leptos_server/src/resource.rs:452— `error!` at line 452 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 leptos_server/src/resource.rs:462— `error!` at line 462 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`.
Duplicated predicate leptos_macro/src/component.rs:1142— `!default.is_empty() || !setter.is_empty()` appears character-identically in 2 files — leptos_macro/src/component.rs, leptos_macro/src/slot.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.
Duplicated predicate integrations/actix/src/lib.rs:1006— `!raw.is_empty() && !raw.starts_with('/')` appears character-identically in 2 files — integrations/actix/src/lib.rs, integrations/axum/src/lib.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.
Duplicated predicate leptos_macro/src/component.rs:1136— `!strip_option.is_empty() || !into.is_empty()` appears character-identically in 2 files — leptos_macro/src/component.rs, leptos_macro/src/slot.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.
Duplicated predicate leptos_macro/src/component.rs:1350— `(prop_opts.optional || prop_opts.strip_option) && is_option(ty)` appears character-identically in 2 files — leptos_macro/src/component.rs, leptos_macro/src/slot.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.
Duplicated predicate integrations/actix/src/lib.rs:864— `cfg!(feature = "islands-router") && req.headers().get("Islands-Router").is_some()` appears character-identically in 2 files — integrations/actix/src/lib.rs, integrations/axum/src/lib.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.
Duplicated predicate tachys/src/view/primitives.rs:87— `flags.hydrate && matches!(position, Position::NextChildAfterText)` appears character-identically in 3 files — tachys/src/view/primitives.rs, tachys/src/view/static_types.rs, tachys/src/view/strings.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.
Duplicated predicate leptos_macro/src/component.rs:1064— `opts.optional || opts.optional_no_strip || opts.attrs` appears character-identically in 2 files — leptos_macro/src/component.rs, leptos_macro/src/slot.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.
Duplicated predicate leptos_macro/src/component.rs:1066— `opts.strip_option || opts.optional && is_option(ty)` appears character-identically in 2 files — leptos_macro/src/component.rs, leptos_macro/src/slot.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.
Duplicated predicate leptos_macro/src/component.rs:991— `path.is_ident("allow") || path.is_ident("warn") || path.is_ident("expect") || path.is_ident("deny") || path.is_ident("forbid")` appears character-identically in 2 files — leptos_macro/src/component.rs, server_fn_macro/src/lib.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.
Duplicated predicate router/src/matching/mod.rs:80— `remaining.is_empty() || remaining == "/"` appears character-identically in 2 files — router/src/matching/mod.rs, router/src/matching/nested/mod.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 8 significant file(s) lose their only recent owner: reactive_graph/src/signal_fn.rs, hydration_context/src/lib.rs, tachys/src/renderer/mod.rs, router/src/lib.rs, reactive_graph/src/lib.rs, reactive_graph/src/into_reactive_value.rs, reactive_graph/src/serde.rs, tachys/src/view/fragment.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 6 significant file(s) lose their only recent owner: oco/src/lib.rs, leptos_macro/src/view/tests.rs, router/src/location/server.rs, const_str_slice_concat/src/lib.rs, server_fn/src/codec/multipart.rs, leptos_macro/src/stable_hash.rs. Pair on, review, or document these before any departure.
Silent fallback default on Err projects/ory-kratos/app/src/database_calls.rs:212— `from_db_call` turns every `Err` into `Ok(Self::default())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err server_fn_macro/src/lib.rs:1561— `parse` turns every `Err` into `true` — 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.
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.
C5 · Data-Subject Rights· Partial data-subject-rights support · ×1
Partial data-subject-rights support — Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 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 (16 single-owned of 282 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; 282 of the 396 production source files in this repository met that bar). They are anonymized user #3 (2 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: integrations/axum/src/config.rs, integrations/axum/src/service.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 — 2 of 48 project(s) overshoot their size bounds, lowering Project Cohesion to 9.2/10. The most over is `tachys` (22569 LoC, 163 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· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 44 of 282 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 282 of the 396 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: projects/ory-kratos/app/src/auth/settings.rs, projects/ory-kratos/app/src/auth/registration.rs, projects/openapi-openai-api-swagger-ui/src/open_ai.rs, projects/ory-kratos/app/src/auth/recovery.rs, projects/ory-kratos/app/src/auth/login.rs, projects/sso_auth_axum/src/sign_in_sign_up.rs, projects/ory-kratos/app/src/database_calls.rs, reactive_graph/src/trait_options.rs (and 36 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 601/759 types (79%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 30/31 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `projects/tauri-from-scratch/src-tauri`.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
No security response headers detected projects/nginx-mpmc/nginx.conf:19— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
Outdated: actix-http — `actix-http` is locked at 3.18.13 but 3.20.0 is the current stable release on crates.io, and it already satisfies the `"3.12"` requirement declared in integrations/actix/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p actix-http` and commit the updated REDACTED.
Outdated: actix-web — `actix-web` is locked at 4.16.0 but 4.18.1 is the current stable release on crates.io, and it already satisfies the `"4.12"` requirement declared in server_fn/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p actix-web` and commit the updated REDACTED.
Outdated: const_format — `const_format` is locked at 0.2.36 but 0.2.37 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in server_fn/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p const_format` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.3 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.39"` requirement declared in examples/axum_js_ssr/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.28.0 but 1.29.0 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in benchmarks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
Off the main sequence: shared-server-2 — shared-server-2: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
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.
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 01a17662-95c5-74c5-a74d-3f07ec736031 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 45 · Warnings: 461 · Recommendations: 113 · Info: 6 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 04:05 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.