Public report of DioxusLabs/blitz, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 21:19 UTC · Survey ID cd_3d16db99cc4941a7bd929b14a12ddf7a
DioxusLabs/blitz
Measured 14 November 2026, 21:12 UTC, at code version beaa796
CAI scoreAt riskNo change 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 medium codebase: 66,080 lines of product code in 20 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Code Health, 40
Findings by how serious they are
43 critical535 serious78 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 21:12 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
52of 52 dimensions measured by tools.
619of 656 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
52dimensions across 7 lenses, read from 66,080 lines of product code in 20 projects.
DioxusLabs/blitz is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 58 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Code Health, at 40, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 7 points. Recording design decisions comes next, worth about 2 points. Raising Code Health to 67 would lift the score to about 71.
Thirty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and two sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, limiting each secret to its own step and making the hidden dependencies explicit would close these risks. Updating the vulnerable packages would fix the package with a known security hole.
The product code is 66,080 lines, about €92,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 40 to 67, the lowest score rated Strong, the score would rise from 58 to about 71.
Code composition: what the lines of code are
Product code 76%Tests 24%
New since the last survey: 140 findings
These 140 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FunctionTooLong: blitz_dom::stylo::presentational_hints::compute_presentational_hints packages/blitz-dom/src/stylo/presentational_hints.rs
God Classes · FunctionTooLong: blitz_vibey_cdp_server::session::dom::dispatch packages/blitz-vibey-cdp-server/src/session/dom.rs
God Classes · TooManyMethods: CodeEditor packages/parley_code_editor/src/editor.rs
God Classes · FunctionTooLong: blitz_vibey_cdp_server::session::css::dispatch packages/blitz-vibey-cdp-server/src/session/css.rs
God Classes · ClassTooLong: CodeEditor packages/parley_code_editor/src/editor.rs
God Classes · FunctionTooLong: blitz_paint::text_decorations::flush_line_decorations packages/blitz-paint/src/text_decorations.rs
God Classes · FileTooLong: src/editor.rs packages/parley_code_editor/src/editor.rs
God Classes · ClassTooLong: BlitzDomPainter packages/blitz-paint/src/render.rs
God Classes · MethodTooLong: BaseDocument.build_paint_tree_impl packages/blitz-dom/src/layout/paint_tree.rs
God Classes · FunctionTooLong: blitz_vibey_cdp_server::transport::handle_connection packages/blitz-vibey-cdp-server/src/transport.rs
God Classes · ClassTooLong: BlitzNode packages/blitz-dom/src/stylo/dom.rs
God Classes · FileTooLong: node/text.rs packages/blitz-dom/src/node/text.rs
Code Duplication · Edited copy of a member (45 corresponding lines) packages/blitz-traits/src/events.rs
Code Duplication · Edited copy of a member (53 corresponding lines) packages/blitz-paint/src/render.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-dom/src/cssom.rs
Code Duplication · Edited copy of a member (18 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs
Code Duplication · Edited copy of a member (26 corresponding lines) packages/blitz-dom/src/mutator.rs
Code Duplication · Edited copy of a member (19 corresponding lines) packages/blitz-net/src/lib.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/dom/node.rs
Code Duplication · Edited copy of a member (18 corresponding lines) packages/stylo_taffy/src/convert.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-paint/src/render/background.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/runtime/events.rs
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) packages/blitz-vibey-script/src/dom/element/selectors.rs
Code Duplication · Edited copy of a member (19 corresponding lines) packages/blitz-html/src/html_sink.rs
Code Duplication · Edited copy of a member (22 corresponding lines) packages/blitz-dom/src/document.rs
Code Duplication · Edited copy of a member (16 corresponding lines) packages/blitz-vibey-script/src/runtime/window.rs
Code Duplication · Edited copy of a member (15 corresponding lines) packages/blitz-vibey-script/src/dom/element/form_controls.rs
Code Duplication · Edited copy of a member (18 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs
Code Duplication · Edited copy of a member (18 corresponding lines) packages/stylo_taffy/src/wrapper.rs
Code Duplication · Edited copy of a member (17 corresponding lines) packages/blitz-paint/src/sizing.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs
Code Duplication · Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs
Code Duplication · Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/runtime/timers.rs
Code Duplication · Edited copy of a member (12 corresponding lines) packages/blitz-dom/src/layout/construct.rs
Code Duplication · Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/dom/element/selectors.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/document.rs
Code Duplication · Edited copy of a member (17 corresponding lines) packages/blitz-vibey-script/src/dom/mod.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/dom/mod.rs
Code Duplication · Edited copy of a member (14 corresponding lines) packages/blitz-dom/src/mutator.rs
Code Duplication · Edited copy of a member (12 corresponding lines) packages/stylo_taffy/src/convert.rs
Code Duplication · Edited copy of a member (12 corresponding lines) packages/blitz-dom/src/mutator.rs
Code Duplication · Edited copy of a member (11 corresponding lines) packages/blitz-vibey-script/src/dom/element/form_controls.rs
Code Duplication · Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs
Code Duplication · Edited copy of a member (16 corresponding lines) packages/blitz-vibey-script/src/dom/element/scrolling.rs
Code Duplication · Edited copy of a member (9 corresponding lines) packages/blitz-paint/src/render/border.rs
Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) packages/blitz-vibey-script/src/dom/element.rs
Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/element/scrolling.rs
Code Duplication · Edited copy of a member (8 corresponding lines) packages/blitz-dom/src/node/svg.rs
Code Duplication · Edited copy of a member (7 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs
Code Duplication · Edited copy of a member (15 corresponding lines) packages/blitz-shell/src/convert_events.rs
Code Duplication · Edited copy of a member (7 corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs
Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/element.rs
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs
Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs
Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) packages/blitz-vibey-script/src/dom/element/geometry.rs
Code Duplication · Edited copy of a member (7 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs
Code Duplication · Edited copy of a member (13 corresponding lines) packages/blitz-dom/src/scrolling.rs
Code Duplication · Edited copy of a member (7 corresponding lines) apps/browser/src/nav.rs
Code Duplication · Edited copy of a member (10 corresponding lines) packages/accesskit_xplat/src/platform_impl/macos.rs
Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) packages/blitz-vibey-script/src/dom/node.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/node.rs
Code Duplication · Edited copy of a member (6 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs
Code Duplication · Edited copy of a member (10 corresponding lines) packages/stylo_taffy/src/convert.rs
Code Duplication · Edited copy of a member (8 corresponding lines) packages/blitz-vibey-cdp-server/src/lib.rs
Code Duplication · Edited copy of a member (5 corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs
Code Duplication · Edited copy of a member (5 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs
Code Duplication · Edited copy of a member (6 corresponding lines) packages/blitz-vibey-cdp-server/src/css.rs
Code Duplication · Edited copy of a member (5 corresponding lines) packages/blitz-vibey-cdp-server/src/style_sheets.rs
Code Duplication · Edited copy of a member (4 corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs
Code Duplication · Edited copy of a member (5 corresponding lines) packages/blitz-dom/src/document.rs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 46 findings
These 46 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
€30,000 to €150,000, for 507 to 1,608 hours of work, about 0.6 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.8 at a score of 58. 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
Medium: 66,080 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 7 points · Medium effort · Type Safety
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 2 points · Low effort · ADR Quality
3
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
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €92,000 to build again, about 0.6 person-years of work. Its weakest lens is Code Health, at 40 (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
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. Of all the actions in this report, it raises the score most for the work it takes: about 7 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
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 79,994 lines over the last 90 days, which is about 324,420 lines a year. At that pace, the extra work comes to an estimated 16.2 to 108.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
207 modules, with 354 dependencies between them. 4 loops run through 15 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 167 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.
blitz_dom.config uses blitz_traits.net, so a change to blitz_traits.net can break blitz_dom.config, while a change to blitz_dom.config can't break blitz_traits.net.
Position
Below the diagonal: blitz_dom.config uses a module listed above it, which is the healthy direction.
blitz_dom.config uses blitz_traits.shell, so a change to blitz_traits.shell can break blitz_dom.config, while a change to blitz_dom.config can't break blitz_traits.shell.
Position
Below the diagonal: blitz_dom.config uses a module listed above it, which is the healthy direction.
blitz_dom.node.scrollbar uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.node.scrollbar, while a change to blitz_dom.node.scrollbar can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.node.scrollbar uses a module listed above it, which is the healthy direction.
blitz_dom.tree uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.tree, while a change to blitz_dom.tree can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.tree uses a module listed above it, which is the healthy direction.
7→16 blitz_dom.tree uses blitz_dom.node.nodepart of a loop✕
Connections
1 pair of types, where a type in blitz_dom.tree uses a type in blitz_dom.node.node.
blitz_dom.tree uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_dom.tree, while a change to blitz_dom.tree can't break blitz_dom.node.node.
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→18 blitz_dom.tree uses blitz_dom.utilpart of a loop✕
Connections
1 pair of types, where a type in blitz_dom.tree uses a type in blitz_dom.util.
The types involved
blitz_dom.tree.NodeTree → blitz_dom.util.Point
Direction
blitz_dom.tree uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.tree, while a change to blitz_dom.tree can't break blitz_dom.util.
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.
blitz_traits.devtools uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_traits.devtools, while a change to blitz_traits.devtools can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_traits.devtools uses a module listed above it, which is the healthy direction.
blitz_traits.events uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_traits.events, while a change to blitz_traits.events can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_traits.events uses a module listed above it, which is the healthy direction.
blitz_traits.navigation uses blitz_traits.net, so a change to blitz_traits.net can break blitz_traits.navigation, while a change to blitz_traits.navigation can't break blitz_traits.net.
Position
Below the diagonal: blitz_traits.navigation uses a module listed above it, which is the healthy direction.
blitz_dom.layout.paint_tree uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.layout.paint_tree, while a change to blitz_dom.layout.paint_tree can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.layout.paint_tree uses a module listed above it, which is the healthy direction.
blitz_dom.layout.paint_tree uses blitz_dom.tree, so a change to blitz_dom.tree can break blitz_dom.layout.paint_tree, while a change to blitz_dom.layout.paint_tree can't break blitz_dom.tree.
Position
Below the diagonal: blitz_dom.layout.paint_tree uses a module listed above it, which is the healthy direction.
12→16 blitz_dom.layout.paint_tree uses blitz_dom.node.nodepart of a loop✕
Connections
1 pair of types, where a type in blitz_dom.layout.paint_tree uses a type in blitz_dom.node.node.
blitz_dom.layout.paint_tree uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_dom.layout.paint_tree, while a change to blitz_dom.layout.paint_tree can't break blitz_dom.node.node.
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 blitz_dom.layout.paint_tree uses blitz_dom.utilpart of a loop✕
Connections
2 pairs of types, where a type in blitz_dom.layout.paint_tree uses a type in blitz_dom.util.
blitz_dom.layout.paint_tree uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.layout.paint_tree, while a change to blitz_dom.layout.paint_tree can't break blitz_dom.util.
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.
blitz_dom.node.text uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.node.text, while a change to blitz_dom.node.text can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.node.text uses a module listed above it, which is the healthy direction.
blitz_dom.node.text uses blitz_traits.events, so a change to blitz_traits.events can break blitz_dom.node.text, while a change to blitz_dom.node.text can't break blitz_traits.events.
Position
Below the diagonal: blitz_dom.node.text uses a module listed above it, which is the healthy direction.
13→18 blitz_dom.node.text uses blitz_dom.utilpart of a loop✕
Connections
2 pairs of types, where a type in blitz_dom.node.text uses a type in blitz_dom.util.
blitz_dom.node.text uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.node.text, while a change to blitz_dom.node.text can't break blitz_dom.util.
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.
browser.document_loader uses blitz_traits.net, so a change to blitz_traits.net can break browser.document_loader, while a change to browser.document_loader can't break blitz_traits.net.
Position
Below the diagonal: browser.document_loader uses a module listed above it, which is the healthy direction.
browser.document_loader uses blitz_dom.config, so a change to blitz_dom.config can break browser.document_loader, while a change to browser.document_loader can't break blitz_dom.config.
Position
Below the diagonal: browser.document_loader uses a module listed above it, which is the healthy direction.
blitz_dom.node.element uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.node.element, while a change to blitz_dom.node.element can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.node.element uses a module listed above it, which is the healthy direction.
blitz_dom.node.element uses blitz_dom.node.text, so a change to blitz_dom.node.text can break blitz_dom.node.element, while a change to blitz_dom.node.element can't break blitz_dom.node.text.
Position
Below the diagonal: blitz_dom.node.element uses a module listed above it, which is the healthy direction.
15→18 blitz_dom.node.element uses blitz_dom.utilpart of a loop✕
Connections
2 pairs of types, where a type in blitz_dom.node.element uses a type in blitz_dom.util.
blitz_dom.node.element uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.node.element, while a change to blitz_dom.node.element can't break blitz_dom.util.
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.
blitz_dom.node.node uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.node.node uses a module listed above it, which is the healthy direction.
blitz_dom.node.node uses blitz_dom.node.scrollbar, so a change to blitz_dom.node.scrollbar can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_dom.node.scrollbar.
Position
Below the diagonal: blitz_dom.node.node uses a module listed above it, which is the healthy direction.
blitz_dom.node.node uses blitz_dom.tree, so a change to blitz_dom.tree can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_dom.tree.
Position
Below the diagonal: blitz_dom.node.node uses a module listed above it, which is the healthy direction.
blitz_dom.node.node uses blitz_traits.events, so a change to blitz_traits.events can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_traits.events.
Position
Below the diagonal: blitz_dom.node.node uses a module listed above it, which is the healthy direction.
blitz_dom.node.node uses blitz_dom.layout.paint_tree, so a change to blitz_dom.layout.paint_tree can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_dom.layout.paint_tree.
Position
Below the diagonal: blitz_dom.node.node uses a module listed above it, which is the healthy direction.
blitz_dom.node.node uses blitz_dom.node.element, so a change to blitz_dom.node.element can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_dom.node.element.
Position
Below the diagonal: blitz_dom.node.node uses a module listed above it, which is the healthy direction.
16→18 blitz_dom.node.node uses blitz_dom.utilpart of a loop✕
Connections
1 pair of types, where a type in blitz_dom.node.node uses a type in blitz_dom.util.
The types involved
blitz_dom.node.node.Node → blitz_dom.util.Point
Direction
blitz_dom.node.node uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.node.node, while a change to blitz_dom.node.node can't break blitz_dom.util.
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.
blitz_dom.mutator uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.mutator, while a change to blitz_dom.mutator can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.mutator uses a module listed above it, which is the healthy direction.
blitz_dom.mutator uses blitz_traits.shell, so a change to blitz_traits.shell can break blitz_dom.mutator, while a change to blitz_dom.mutator can't break blitz_traits.shell.
Position
Below the diagonal: blitz_dom.mutator uses a module listed above it, which is the healthy direction.
blitz_dom.mutator uses blitz_traits.devtools, so a change to blitz_traits.devtools can break blitz_dom.mutator, while a change to blitz_dom.mutator can't break blitz_traits.devtools.
Position
Below the diagonal: blitz_dom.mutator uses a module listed above it, which is the healthy direction.
blitz_dom.mutator uses blitz_dom.node.element, so a change to blitz_dom.node.element can break blitz_dom.mutator, while a change to blitz_dom.mutator can't break blitz_dom.node.element.
Position
Below the diagonal: blitz_dom.mutator uses a module listed above it, which is the healthy direction.
blitz_dom.mutator uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_dom.mutator, while a change to blitz_dom.mutator can't break blitz_dom.node.node.
Position
Below the diagonal: blitz_dom.mutator uses a module listed above it, which is the healthy direction.
17→24 blitz_dom.mutator uses blitz_dom.documentpart of a loop✕
Connections
2 pairs of types, where a type in blitz_dom.mutator uses a type in blitz_dom.document.
blitz_dom.mutator uses blitz_dom.document, so a change to blitz_dom.document can break blitz_dom.mutator, while a change to blitz_dom.mutator can't break blitz_dom.document.
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.
blitz_dom.util uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_dom.util, while a change to blitz_dom.util can't break blitz_dom.node.node.
Position
Below the diagonal: blitz_dom.util uses a module listed above it, which is the healthy direction.
blitz_dom.events.driver uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.events.driver, while a change to blitz_dom.events.driver can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.events.driver uses a module listed above it, which is the healthy direction.
blitz_dom.events.driver uses blitz_traits.events, so a change to blitz_traits.events can break blitz_dom.events.driver, while a change to blitz_dom.events.driver can't break blitz_traits.events.
Position
Below the diagonal: blitz_dom.events.driver uses a module listed above it, which is the healthy direction.
blitz_dom.events.driver uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.events.driver, while a change to blitz_dom.events.driver can't break blitz_dom.util.
Position
Below the diagonal: blitz_dom.events.driver uses a module listed above it, which is the healthy direction.
blitz_dom.net uses blitz_traits.net, so a change to blitz_traits.net can break blitz_dom.net, while a change to blitz_dom.net can't break blitz_traits.net.
Position
Below the diagonal: blitz_dom.net uses a module listed above it, which is the healthy direction.
blitz_dom.net uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.net, while a change to blitz_dom.net can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.net uses a module listed above it, which is the healthy direction.
blitz_dom.scrolling uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.scrolling, while a change to blitz_dom.scrolling can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.scrolling uses a module listed above it, which is the healthy direction.
blitz_dom.scrolling uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.scrolling, while a change to blitz_dom.scrolling can't break blitz_dom.util.
Position
Below the diagonal: blitz_dom.scrolling uses a module listed above it, which is the healthy direction.
blitz_html.html_sink uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_html.html_sink, while a change to blitz_html.html_sink can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_html.html_sink uses a module listed above it, which is the healthy direction.
blitz_html.html_sink uses blitz_dom.config, so a change to blitz_dom.config can break blitz_html.html_sink, while a change to blitz_html.html_sink can't break blitz_dom.config.
Position
Below the diagonal: blitz_html.html_sink uses a module listed above it, which is the healthy direction.
blitz_html.html_sink uses blitz_dom.mutator, so a change to blitz_dom.mutator can break blitz_html.html_sink, while a change to blitz_html.html_sink can't break blitz_dom.mutator.
Position
Below the diagonal: blitz_html.html_sink uses a module listed above it, which is the healthy direction.
blitz_dom.events.pointer uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.events.pointer, while a change to blitz_dom.events.pointer can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.events.pointer uses a module listed above it, which is the healthy direction.
blitz_dom.events.pointer uses blitz_dom.node.scrollbar, so a change to blitz_dom.node.scrollbar can break blitz_dom.events.pointer, while a change to blitz_dom.events.pointer can't break blitz_dom.node.scrollbar.
Position
Below the diagonal: blitz_dom.events.pointer uses a module listed above it, which is the healthy direction.
blitz_dom.events.pointer uses blitz_traits.events, so a change to blitz_traits.events can break blitz_dom.events.pointer, while a change to blitz_dom.events.pointer can't break blitz_traits.events.
Position
Below the diagonal: blitz_dom.events.pointer uses a module listed above it, which is the healthy direction.
blitz_dom.events.pointer uses blitz_dom.scrolling, so a change to blitz_dom.scrolling can break blitz_dom.events.pointer, while a change to blitz_dom.events.pointer can't break blitz_dom.scrolling.
Position
Below the diagonal: blitz_dom.events.pointer uses a module listed above it, which is the healthy direction.
23→24 blitz_dom.events.pointer uses blitz_dom.documentpart of a loop✕
Connections
1 pair of types, where a type in blitz_dom.events.pointer uses a type in blitz_dom.document.
blitz_dom.events.pointer uses blitz_dom.document, so a change to blitz_dom.document can break blitz_dom.events.pointer, while a change to blitz_dom.events.pointer can't break blitz_dom.document.
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.
blitz_dom.document uses blitz_traits.net, so a change to blitz_traits.net can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_traits.net.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_traits.shell, so a change to blitz_traits.shell can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_traits.shell.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.config, so a change to blitz_dom.config can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.config.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.node.scrollbar, so a change to blitz_dom.node.scrollbar can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.node.scrollbar.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.tree, so a change to blitz_dom.tree can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.tree.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_traits.devtools, so a change to blitz_traits.devtools can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_traits.devtools.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_traits.events, so a change to blitz_traits.events can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_traits.events.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.node.text, so a change to blitz_dom.node.text can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.node.text.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.node.element, so a change to blitz_dom.node.element can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.node.element.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.node.node.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.mutator, so a change to blitz_dom.mutator can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.mutator.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.util.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.net, so a change to blitz_dom.net can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.net.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.scrolling, so a change to blitz_dom.scrolling can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.scrolling.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.document uses blitz_dom.events.pointer, so a change to blitz_dom.events.pointer can break blitz_dom.document, while a change to blitz_dom.document can't break blitz_dom.events.pointer.
Position
Below the diagonal: blitz_dom.document uses a module listed above it, which is the healthy direction.
blitz_dom.layout uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_dom.layout, while a change to blitz_dom.layout can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_dom.layout uses a module listed above it, which is the healthy direction.
blitz_dom.layout uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_dom.layout, while a change to blitz_dom.layout can't break blitz_dom.node.node.
Position
Below the diagonal: blitz_dom.layout uses a module listed above it, which is the healthy direction.
blitz_dom.layout uses blitz_dom.util, so a change to blitz_dom.util can break blitz_dom.layout, while a change to blitz_dom.layout can't break blitz_dom.util.
Position
Below the diagonal: blitz_dom.layout uses a module listed above it, which is the healthy direction.
blitz_dom.layout uses blitz_dom.document, so a change to blitz_dom.document can break blitz_dom.layout, while a change to blitz_dom.layout can't break blitz_dom.document.
Position
Below the diagonal: blitz_dom.layout uses a module listed above it, which is the healthy direction.
blitz_paint.text uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_paint.text, while a change to blitz_paint.text can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_paint.text uses a module listed above it, which is the healthy direction.
blitz_paint.text uses blitz_dom.document, so a change to blitz_dom.document can break blitz_paint.text, while a change to blitz_paint.text can't break blitz_dom.document.
Position
Below the diagonal: blitz_paint.text uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server.style_sheets uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_vibey_cdp_server.style_sheets, while a change to blitz_vibey_cdp_server.style_sheets can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_vibey_cdp_server.style_sheets uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server.style_sheets uses blitz_dom.net, so a change to blitz_dom.net can break blitz_vibey_cdp_server.style_sheets, while a change to blitz_vibey_cdp_server.style_sheets can't break blitz_dom.net.
Position
Below the diagonal: blitz_vibey_cdp_server.style_sheets uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server.style_sheets uses blitz_dom.document, so a change to blitz_dom.document can break blitz_vibey_cdp_server.style_sheets, while a change to blitz_vibey_cdp_server.style_sheets can't break blitz_dom.document.
Position
Below the diagonal: blitz_vibey_cdp_server.style_sheets uses a module listed above it, which is the healthy direction.
27→35 blitz_vibey_cdp_server.style_sheets uses blitz_vibey_cdp_serverpart of a loop✕
Connections
1 pair of types, where a type in blitz_vibey_cdp_server.style_sheets uses a type in blitz_vibey_cdp_server.
blitz_vibey_cdp_server.style_sheets uses blitz_vibey_cdp_server, so a change to blitz_vibey_cdp_server can break blitz_vibey_cdp_server.style_sheets, while a change to blitz_vibey_cdp_server.style_sheets can't break blitz_vibey_cdp_server.
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.
blitz_vibey_script.state uses blitz_dom.document, so a change to blitz_dom.document can break blitz_vibey_script.state, while a change to blitz_vibey_script.state can't break blitz_dom.document.
Position
Below the diagonal: blitz_vibey_script.state uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_traits.net, so a change to blitz_traits.net can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_traits.net.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_traits.node_id, so a change to blitz_traits.node_id can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_traits.node_id.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_traits.events, so a change to blitz_traits.events can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_traits.events.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_dom.node.element, so a change to blitz_dom.node.element can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_dom.node.element.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_dom.node.node, so a change to blitz_dom.node.node can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_dom.node.node.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_dom.scrolling, so a change to blitz_dom.scrolling can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_dom.scrolling.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.events uses blitz_dom.document, so a change to blitz_dom.document can break dioxus_native_dom.events, while a change to dioxus_native_dom.events can't break blitz_dom.document.
Position
Below the diagonal: dioxus_native_dom.events uses a module listed above it, which is the healthy direction.
dioxus_native_dom.mutation_writer uses blitz_traits.node_id, so a change to blitz_traits.node_id can break dioxus_native_dom.mutation_writer, while a change to dioxus_native_dom.mutation_writer can't break blitz_traits.node_id.
Position
Below the diagonal: dioxus_native_dom.mutation_writer uses a module listed above it, which is the healthy direction.
dioxus_native_dom.mutation_writer uses blitz_dom.mutator, so a change to blitz_dom.mutator can break dioxus_native_dom.mutation_writer, while a change to dioxus_native_dom.mutation_writer can't break blitz_dom.mutator.
Position
Below the diagonal: dioxus_native_dom.mutation_writer uses a module listed above it, which is the healthy direction.
dioxus_native_dom.mutation_writer uses blitz_dom.document, so a change to blitz_dom.document can break dioxus_native_dom.mutation_writer, while a change to dioxus_native_dom.mutation_writer can't break blitz_dom.document.
Position
Below the diagonal: dioxus_native_dom.mutation_writer uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_dom.node.scrollbar, so a change to blitz_dom.node.scrollbar can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_dom.node.scrollbar.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_traits.devtools, so a change to blitz_traits.devtools can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_traits.devtools.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_dom.node.text, so a change to blitz_dom.node.text can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_dom.node.text.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_dom.node.element, so a change to blitz_dom.node.element can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_dom.node.element.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_dom.node.node, so a change to blitz_dom.node.node can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_dom.node.node.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_dom.util, so a change to blitz_dom.util can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_dom.util.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_dom.document, so a change to blitz_dom.document can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_dom.document.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_paint.render uses blitz_paint.text, so a change to blitz_paint.text can break blitz_paint.render, while a change to blitz_paint.render can't break blitz_paint.text.
Position
Below the diagonal: blitz_paint.render uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server.session uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_vibey_cdp_server.session, while a change to blitz_vibey_cdp_server.session can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_vibey_cdp_server.session uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server.session uses blitz_dom.document, so a change to blitz_dom.document can break blitz_vibey_cdp_server.session, while a change to blitz_vibey_cdp_server.session can't break blitz_dom.document.
Position
Below the diagonal: blitz_vibey_cdp_server.session uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server.session uses blitz_vibey_cdp_server.style_sheets, so a change to blitz_vibey_cdp_server.style_sheets can break blitz_vibey_cdp_server.session, while a change to blitz_vibey_cdp_server.session can't break blitz_vibey_cdp_server.style_sheets.
Position
Below the diagonal: blitz_vibey_cdp_server.session uses a module listed above it, which is the healthy direction.
32→35 blitz_vibey_cdp_server.session uses blitz_vibey_cdp_serverpart of a loop✕
Connections
5 pairs of types, where a type in blitz_vibey_cdp_server.session uses a type in blitz_vibey_cdp_server.
blitz_vibey_cdp_server.session uses blitz_vibey_cdp_server, so a change to blitz_vibey_cdp_server can break blitz_vibey_cdp_server.session, while a change to blitz_vibey_cdp_server.session can't break blitz_vibey_cdp_server.
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.
blitz_vibey_script.runtime uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_vibey_script.runtime, while a change to blitz_vibey_script.runtime can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_vibey_script.runtime uses a module listed above it, which is the healthy direction.
blitz_vibey_script.runtime uses blitz_traits.events, so a change to blitz_traits.events can break blitz_vibey_script.runtime, while a change to blitz_vibey_script.runtime can't break blitz_traits.events.
Position
Below the diagonal: blitz_vibey_script.runtime uses a module listed above it, which is the healthy direction.
blitz_vibey_script.runtime uses blitz_dom.document, so a change to blitz_dom.document can break blitz_vibey_script.runtime, while a change to blitz_vibey_script.runtime can't break blitz_dom.document.
Position
Below the diagonal: blitz_vibey_script.runtime uses a module listed above it, which is the healthy direction.
blitz_vibey_script.runtime uses blitz_vibey_script.state, so a change to blitz_vibey_script.state can break blitz_vibey_script.runtime, while a change to blitz_vibey_script.runtime can't break blitz_vibey_script.state.
Position
Below the diagonal: blitz_vibey_script.runtime uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses blitz_traits.node_id, so a change to blitz_traits.node_id can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break blitz_traits.node_id.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses blitz_dom.config, so a change to blitz_dom.config can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break blitz_dom.config.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses blitz_traits.events, so a change to blitz_traits.events can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break blitz_traits.events.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses blitz_dom.node.node, so a change to blitz_dom.node.node can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break blitz_dom.node.node.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses blitz_dom.events.driver, so a change to blitz_dom.events.driver can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break blitz_dom.events.driver.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses blitz_dom.document, so a change to blitz_dom.document can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break blitz_dom.document.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
dioxus_native_dom.dioxus_document uses dioxus_native_dom.mutation_writer, so a change to dioxus_native_dom.mutation_writer can break dioxus_native_dom.dioxus_document, while a change to dioxus_native_dom.dioxus_document can't break dioxus_native_dom.mutation_writer.
Position
Below the diagonal: dioxus_native_dom.dioxus_document uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server uses blitz_traits.node_id, so a change to blitz_traits.node_id can break blitz_vibey_cdp_server, while a change to blitz_vibey_cdp_server can't break blitz_traits.node_id.
Position
Below the diagonal: blitz_vibey_cdp_server uses a module listed above it, which is the healthy direction.
blitz_vibey_cdp_server uses blitz_vibey_cdp_server.session, so a change to blitz_vibey_cdp_server.session can break blitz_vibey_cdp_server, while a change to blitz_vibey_cdp_server can't break blitz_vibey_cdp_server.session.
Position
Below the diagonal: blitz_vibey_cdp_server uses a module listed above it, which is the healthy direction.
blitz_shell.event uses blitz_traits.net, so a change to blitz_traits.net can break blitz_shell.event, while a change to blitz_shell.event can't break blitz_traits.net.
Position
Below the diagonal: blitz_shell.event uses a module listed above it, which is the healthy direction.
blitz_shell.event uses blitz_vibey_cdp_server, so a change to blitz_vibey_cdp_server can break blitz_shell.event, while a change to blitz_shell.event can't break blitz_vibey_cdp_server.
Position
Below the diagonal: blitz_shell.event uses a module listed above it, which is the healthy direction.
blitz_shell.window uses accesskit_xplat, so a change to accesskit_xplat can break blitz_shell.window, while a change to blitz_shell.window can't break accesskit_xplat.
Position
Below the diagonal: blitz_shell.window uses a module listed above it, which is the healthy direction.
blitz_shell.window uses blitz_traits.events, so a change to blitz_traits.events can break blitz_shell.window, while a change to blitz_shell.window can't break blitz_traits.events.
Position
Below the diagonal: blitz_shell.window uses a module listed above it, which is the healthy direction.
blitz_shell.window uses blitz_shell.event, so a change to blitz_shell.event can break blitz_shell.window, while a change to blitz_shell.window can't break blitz_shell.event.
Position
Below the diagonal: blitz_shell.window uses a module listed above it, which is the healthy direction.
blitz_shell.application uses accesskit_xplat, so a change to accesskit_xplat can break blitz_shell.application, while a change to blitz_shell.application can't break accesskit_xplat.
Position
Below the diagonal: blitz_shell.application uses a module listed above it, which is the healthy direction.
blitz_shell.application uses blitz_dom.document, so a change to blitz_dom.document can break blitz_shell.application, while a change to blitz_shell.application can't break blitz_dom.document.
Position
Below the diagonal: blitz_shell.application uses a module listed above it, which is the healthy direction.
blitz_shell.application uses blitz_shell.event, so a change to blitz_shell.event can break blitz_shell.application, while a change to blitz_shell.application can't break blitz_shell.event.
Position
Below the diagonal: blitz_shell.application uses a module listed above it, which is the healthy direction.
blitz_shell.application uses blitz_shell.window, so a change to blitz_shell.window can break blitz_shell.application, while a change to blitz_shell.application can't break blitz_shell.window.
Position
Below the diagonal: blitz_shell.application uses a module listed above it, which is the healthy direction.
dioxus_native.dioxus_application uses accesskit_xplat, so a change to accesskit_xplat can break dioxus_native.dioxus_application, while a change to dioxus_native.dioxus_application can't break accesskit_xplat.
Position
Below the diagonal: dioxus_native.dioxus_application uses a module listed above it, which is the healthy direction.
dioxus_native.dioxus_application uses blitz_shell.event, so a change to blitz_shell.event can break dioxus_native.dioxus_application, while a change to dioxus_native.dioxus_application can't break blitz_shell.event.
Position
Below the diagonal: dioxus_native.dioxus_application uses a module listed above it, which is the healthy direction.
dioxus_native.dioxus_application uses blitz_shell.window, so a change to blitz_shell.window can break dioxus_native.dioxus_application, while a change to dioxus_native.dioxus_application can't break blitz_shell.window.
Position
Below the diagonal: dioxus_native.dioxus_application uses a module listed above it, which is the healthy direction.
dioxus_native.dioxus_application uses blitz_shell.application, so a change to blitz_shell.application can break dioxus_native.dioxus_application, while a change to dioxus_native.dioxus_application can't break blitz_shell.application.
Position
Below the diagonal: dioxus_native.dioxus_application uses a module listed above it, which is the healthy direction.
rdme.readme_application uses accesskit_xplat, so a change to accesskit_xplat can break rdme.readme_application, while a change to rdme.readme_application can't break accesskit_xplat.
Position
Below the diagonal: rdme.readme_application uses a module listed above it, which is the healthy direction.
rdme.readme_application uses blitz_traits.navigation, so a change to blitz_traits.navigation can break rdme.readme_application, while a change to rdme.readme_application can't break blitz_traits.navigation.
Position
Below the diagonal: rdme.readme_application uses a module listed above it, which is the healthy direction.
rdme.readme_application uses blitz_shell.event, so a change to blitz_shell.event can break rdme.readme_application, while a change to rdme.readme_application can't break blitz_shell.event.
Position
Below the diagonal: rdme.readme_application uses a module listed above it, which is the healthy direction.
rdme.readme_application uses blitz_shell.window, so a change to blitz_shell.window can break rdme.readme_application, while a change to rdme.readme_application can't break blitz_shell.window.
Position
Below the diagonal: rdme.readme_application uses a module listed above it, which is the healthy direction.
rdme.readme_application uses blitz_shell.application, so a change to blitz_shell.application can break rdme.readme_application, while a change to rdme.readme_application can't break blitz_shell.application.
Position
Below the diagonal: rdme.readme_application uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 40% · Weak · gated by R1, 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
47
High / Critical
A03:2025 — Software Supply Chain Failures
19
High / Critical
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Interpolated log message defeats structured logging.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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.
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 — 43
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 — 535
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 — 78
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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 52 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, 619 of 656 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 133 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.006 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.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (59 contributor(s) across 2265 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 58 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 3 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
65 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TextInputData::apply_apple_standard_keybinding at 100. A further 20 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 blitz_dom::accessibility::role_from_name at 59 — they are counted neither in the figure above nor in this dimension's score. 10 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: packages/blitz-dom/src/stylo/dom.rs (BlitzNode::match_non_ts_pseudo_class at 39), packages/blitz-dom/src/stylo_to_cursor_icon.rs (blitz_dom::stylo_to_cursor_icon::stylo_to_cursor_icon at 36), packages/blitz-traits/src/events.rs (DomEventKind::from_str at 34), packages/blitz-dom/src/cssom.rs (blitz_dom::cssom::css_rule_interface at 24), packages/blitz-dom/src/layout/text_transform.rs (blitz_dom::layout::text_transform::full_width at 23), and 5 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with TextInputData::apply_apple_standard_keybinding (cyclomatic 100), blitz_dom::stylo::presentational_hints::compute_presentational_hints (cyclomatic 85), LayoutPassState::compute_inline_layout_inner (cyclomatic 78). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 27 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with LayoutPassState::compute_inline_layout_inner (cognitive 165), blitz_dom::stylo::presentational_hints::compute_presentational_hints (cognitive 146). — 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 2 together lifts Cognitive Complexity from 5.2 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.2 / 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 21 FileTooLong finding(s) in God Classes — start with document.rs, node.rs, mutator.rs. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 16 FunctionTooLong finding(s) in God Classes — start with pointer.rs (3), table.rs (2), toolbar.rs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 14 MethodTooLong finding(s) in God Classes — start with text.rs (2), layout.rs, mod.rs. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
58 duplicated block group(s) detected. 3.7 % of the production lines (2,412 of 66,080) are in a reported copy. A further 59 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (14 corresponding lines) · ×7packages/blitz-dom/src/cssom.rs:122
+ 52 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with cssom.rs, node.rs, background.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with document.rs (3), attributes.rs, timers.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with document.rs, timers.rs, selectors.rs. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.2 / 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.
20 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 18 of the 20 (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: browser-persistence · ×7
What to do
Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
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.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
22 outdated, 0 yanked direct Cargo dependencies. 110 of 115 direct crates were graded against crates.io (0 not published there, 5 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: accesskit · ×22
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 965 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 14 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 24 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), layout.rs, node.rs. — One of this dimension's main actionable groups (24 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
127 deducted task-comment markers across 66080 LoC (0.2/KLoC) → score 9.6. 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 117 TodoComment finding(s) in Explicit Debt — start with text.rs (8), convert.rs (6), events.rs (6). — One of this dimension's main actionable groups (117 warning-level).
Resolve the 8 FixmeComment finding(s) in Explicit Debt — start with mutation_writer.rs (2), background.rs, resolve.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with mod.rs, main.rs. — One of this dimension's main actionable groups (2 warning-level).
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. 5 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: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
Resolve the 1 redundant comment finding(s) in Comment Value — start with stylesheets.js. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
47 finding(s): 0 critical, 40 high, 7 medium, 0 low. 37 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 3 file(s) — `REDACTED` (lines 2–2104), `REDACTED` (lines 2–1645), `packages/blitz-shell/src/window.rs` (line 460, lines 461–462, lines 462–463) — 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 2 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 37 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 (37 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
4 of 171 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is apps/browser/persistence/src/lib.rs. Counted over 171 of the 220 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with html_document.rs (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
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.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ 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.
0 typed · 11 plain JS — the untyped files are packages/blitz-vibey-script/src/geometry.js, packages/blitz-vibey-script/src/runtime/bootstrap/css.js, packages/blitz-vibey-script/src/runtime/bootstrap/dom_exception.js, packages/blitz-vibey-script/src/runtime/bootstrap/fetch.js, packages/blitz-vibey-script/src/runtime/bootstrap/fonts.js, packages/blitz-vibey-script/src/runtime/bootstrap/interfaces.js (+5 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Do you agree with this assessment?
R10 · Code Duplication4.4 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
packages/blitz-vibey-script/src/geometry.js:81 · packages/blitz-vibey-script/src/geometry.js:204 — the two spans are one implementation copied and then locally edited — 604 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blitz-vibey-script/src/geometry.js:81
packages/blitz-vibey-script/src/geometry.js:788 · packages/blitz-vibey-script/src/geometry.js:960 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — packages/blitz-vibey-script/src/geometry.js:788
packages/blitz-vibey-script/src/geometry.js:845 · packages/blitz-vibey-script/src/geometry.js:864 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blitz-vibey-script/src/geometry.js:845
packages/blitz-vibey-script/src/geometry.js:385 · packages/blitz-vibey-script/src/runtime/bootstrap/style.js:100 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/blitz-vibey-script/src/geometry.js:385
packages/blitz-vibey-script/src/geometry.js:237 · packages/blitz-vibey-script/src/geometry.js:245 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blitz-vibey-script/src/geometry.js:237
packages/blitz-vibey-script/src/geometry.js:368 · packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js:35 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/blitz-vibey-script/src/geometry.js:368
packages/blitz-vibey-script/src/geometry.js:1031 · packages/blitz-vibey-script/src/geometry.js:1046 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blitz-vibey-script/src/geometry.js:1031
packages/blitz-vibey-script/src/geometry.js:717 · packages/blitz-vibey-script/src/geometry.js:723 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blitz-vibey-script/src/geometry.js:717
packages/blitz-vibey-script/src/geometry.js:834 · packages/blitz-vibey-script/src/geometry.js:1020 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blitz-vibey-script/src/geometry.js:834
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.
validateAndFixupMatrixInit has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blitz-vibey-script/src/geometry.js:647
escape has cyclomatic complexity 24 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blitz-vibey-script/src/runtime/bootstrap/css.js:5
constructor has cyclomatic complexity 16 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blitz-vibey-script/src/runtime/bootstrap/url_search_params.js:30
(anonymous) has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blitz-vibey-script/src/runtime/bootstrap/fetch.js:73
replaceGeometry has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blitz-vibey-script/src/geometry.js:1188
Do you agree with this assessment?
R3 · Large Files2.7 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/blitz-vibey-script/src/geometry.js has 1273 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/blitz-vibey-script/src/geometry.js:1
packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js has 531 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
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 · 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 · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` 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?
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.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`trace!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/dioxus-native/src/assets.rs:48
`warn!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/dioxus-native/src/assets.rs:53
`warn!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/dioxus-native/src/assets.rs:60
`error!` at line 15 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/dioxus-native/src/link_handler.rs:15
`error!` at line 266 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-script/src/document.rs:266
`error!` at line 21 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-script/src/runtime/events.rs:21
`warn!` at line 61 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/frontend.rs:61
`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`. — packages/blitz-vibey-cdp-server/src/lib.rs:129
`debug!` at line 214 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/lib.rs:214
`trace!` at line 215 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/lib.rs:215
`trace!` at line 404 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/lib.rs:404
`info!` at line 32 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/transport.rs:32
`warn!` at line 43 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/transport.rs:43
`debug!` 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: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/transport.rs:178
`warn!` at line 224 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/transport.rs:224
`warn!` 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: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/transport.rs:228
`debug!` at line 197 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-vibey-cdp-server/src/session/mod.rs:197
`error!` at line 85 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-shell/src/application.rs:85
`error!` at line 75 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-shell/src/convert_events.rs:75
`error!` at line 91 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-shell/src/convert_events.rs:91
`error!` at line 109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-shell/src/convert_events.rs:109
`error!` at line 137 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-shell/src/convert_events.rs:137
`error!` at line 867 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-shell/src/window.rs:867
`error!` at line 141 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-net/src/lib.rs:141
`error!` at line 184 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-html/src/html_sink.rs:184
`info!` at line 24 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/debug.rs:24
`info!` at line 25 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/debug.rs:25
`info!` at line 1432 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/document.rs:1432
`info!` at line 1759 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/document.rs:1759
`warn!` at line 155 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/form.rs:155
`info!` at line 1439 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/mutator.rs:1439
`info!` at line 1451 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/mutator.rs:1451
`info!` at line 1458 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/mutator.rs:1458
`warn!` at line 1508 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/mutator.rs:1508
`warn!` at line 491 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/net.rs:491
`info!` at line 597 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/layout/damage.rs:597
`info!` at line 606 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/layout/damage.rs:606
`info!` at line 612 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/layout/damage.rs:612
`warn!` at line 754 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/events/pointer.rs:754
`info!` at line 759 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — packages/blitz-dom/src/events/pointer.rs:759
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
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 — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 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 (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (9 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; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~21336 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; 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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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"]`.
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.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 — Rust suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 43 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
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 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (11 production file(s)) has no JavaScript/TypeScript test, but it is 4.12% of this repository's production source and the other 95.88% carries 21,336 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
S1 Web-Security Posture — No web surface: 210 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — X12 reached only 4% of this repository's production lines — rust (66,021 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 4% of this repository's production lines — rust (66,021 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Kotlin and Rust were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour; 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 4% of this repository's production lines — rust (66,021 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: html_document.rs ↔ dioxus_document.rs packages/blitz-html/src/html_document.rs:1— `packages/blitz-html/src/html_document.rs` (context blitz-html) and `packages/dioxus-native-dom/src/dioxus_document.rs` (context dioxus-native-dom) sit in DIFFERENT parts of the tree yet change together 66% of the time (23 of the 35 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 23 shared commits counted here, the most recent 3 are `7b28f0f1` Share parsed UA stylesheets (and their cascade data) across documents…; `8440724b` Make Document trait RefCell compatible + make DioxusDocument use RefCell; `40c31dd9` Refactor Document trait (at that commit the file was still `packages/mini-dxn/src/dioxus_document.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: html_document.rs ↔ window.rs packages/blitz-html/src/html_document.rs:1— `packages/blitz-html/src/html_document.rs` (context blitz-html) and `packages/blitz-shell/src/window.rs` (context blitz-shell) sit in DIFFERENT parts of the tree yet change together 51% of the time (18 of the 35 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 18 shared commits counted here, the most recent 3 are `8440724b` Make Document trait RefCell compatible + make DioxusDocument use RefCell; `40c31dd9` Refactor Document trait; `c03ac9cc` Refactor event handling (#221) — run `git show` on any of them.
TodoComment wpt/runner/src/net_provider.rs:71— // TODO: Should we resolve path differently if it does not begin with '/' — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment wpt/runner/src/test_runners/mod.rs:281— // TODO: handle tests with multiple calls to checkLayout. — 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 wpt/runner/src/test_runners/ref_test.rs:316— // Set pixels-per-meter. TODO: make configurable. — 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 examples/screenshot.rs:152— // Set pixels-per-meter. TODO: make configurable. — 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 tests/stylo_usage.rs:2— //! TODO: clean up and upstream to stylo repo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/stylo_usage.rs:112— // // // Todo: pull this in from wgpu — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/convert.rs:238— // TODO: Support display:contents in Taffy — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/convert.rs:239— // TODO: Support table layout in Taffy — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/convert.rs:253— // TODO: Support flow and table layout — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/convert.rs:413— // TODO: Support Overflow::Auto in Taffy — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/convert.rs:812— // TODO: Implement subgrid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/convert.rs:828— // TODO: Implement subgrid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/wrapper.rs:792— // TODO: Implement subgrid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/wrapper.rs:812— // TODO: Implement subgrid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/wrapper.rs:856— // TODO: Implement subgrid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/stylo_taffy/src/wrapper.rs:867— // TODO: Implement subgrid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/dioxus_document.rs:105— // TODO: Support arbitrary "index.html" templates — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/dioxus_document.rs:333— // TODO: Implement IME handling — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/events.rs:302— // TODO: queue focus events somehow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/events.rs:306— // TODO: queue blur events somehow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/events.rs:333— // todo: actually implement validation 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 packages/dioxus-native-dom/src/events.rs:470— // TODO: implement these fields with real values — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/events.rs:551— // TODO: expose real touch radius once blitz tracks it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/events.rs:556— // TODO: expose real touch rotation once blitz tracks it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/dioxus-native-dom/src/mutation_writer.rs:498— // TODO: accumulate style attributes into a single style element. — 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.
Hotspot: packages/blitz-dom/src/layout/inline/layout.rs packages/blitz-dom/src/layout/inline/layout.rs:338— packages/blitz-dom/src/layout/inline/layout.rs changed 49 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in LayoutPassState::compute_inline_layout_inner at line 338. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/inline/layout.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/node/node.rs packages/blitz-dom/src/node/node.rs:1469— packages/blitz-dom/src/node/node.rs changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in Node::hit_inner at line 1469. 3 of those changes were fix/bug commits, and the other 38 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/node/node.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/mutator.rs packages/blitz-dom/src/mutator.rs:323— packages/blitz-dom/src/mutator.rs changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in DocumentMutator::set_attribute at line 323. 2 of those changes were fix/bug commits, and the other 36 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/mutator.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/resolved_style.rs packages/blitz-dom/src/resolved_style.rs:344— packages/blitz-dom/src/resolved_style.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in BaseDocument::resolved_style_value at line 344. 1 of those changes was a fix/bug commit, and the other 14 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/resolved_style.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/layout/mod.rs packages/blitz-dom/src/layout/mod.rs:220— packages/blitz-dom/src/layout/mod.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in LayoutPassState::dispatch_child_layout at line 220. 3 of those changes were fix/bug commits, and the other 22 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/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.
Hotspot: packages/blitz-dom/src/layout/construct.rs packages/blitz-dom/src/layout/construct.rs:404— packages/blitz-dom/src/layout/construct.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in blitz_dom::layout::construct::collect_layout_children_with_wrap at line 404. 2 of those changes were fix/bug commits, and the other 25 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/construct.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-paint/src/render.rs packages/blitz-paint/src/render.rs:435— packages/blitz-paint/src/render.rs changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in BlitzDomPainter::render_element at line 435. 3 of those changes were fix/bug commits, and the other 25 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-paint/src/render.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/accessibility.rs packages/blitz-dom/src/accessibility.rs:341— packages/blitz-dom/src/accessibility.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in blitz_dom::accessibility::role_from_element_data at line 341. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/accessibility.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/layout/damage.rs packages/blitz-dom/src/layout/damage.rs:363— packages/blitz-dom/src/layout/damage.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in blitz_dom::layout::damage::compute_layout_damage at line 363. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/damage.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/layout/replaced.rs packages/blitz-dom/src/layout/replaced.rs:52— packages/blitz-dom/src/layout/replaced.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in blitz_dom::layout::replaced::compute_replaced_layout at line 52. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/replaced.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/layout/table.rs packages/blitz-dom/src/layout/table.rs:515— packages/blitz-dom/src/layout/table.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in blitz_dom::layout::table::collect_table_cells at line 515. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/table.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-shell/src/window.rs packages/blitz-shell/src/window.rs:600— packages/blitz-shell/src/window.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in View::handle_winit_event at line 600. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-shell/src/window.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/node/text.rs packages/blitz-dom/src/node/text.rs:235— packages/blitz-dom/src/node/text.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in TextInputData::apply_keypress_event at line 235. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/node/text.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: wpt/runner/src/main.rs wpt/runner/src/main.rs:348— wpt/runner/src/main.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in wpt::main at line 348. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- wpt/runner/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/stylo_to_parley.rs packages/blitz-dom/src/stylo_to_parley.rs:441— packages/blitz-dom/src/stylo_to_parley.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in blitz_dom::stylo_to_parley::style at line 441. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/stylo_to_parley.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/events/pointer.rs packages/blitz-dom/src/events/pointer.rs:207— packages/blitz-dom/src/events/pointer.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in blitz_dom::events::pointer::handle_pointermove at line 207. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/events/pointer.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: wpt/runner/src/test_runners/mod.rs wpt/runner/src/test_runners/mod.rs:173— wpt/runner/src/test_runners/mod.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in wpt::test_runners::process_test_file at line 173. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- wpt/runner/src/test_runners/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.
Hotspot: apps/browser/src/toolbar.rs apps/browser/src/toolbar.rs:36— apps/browser/src/toolbar.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in browser::toolbar::Toolbar at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- apps/browser/src/toolbar.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/dioxus-native-dom/src/mutation_writer.rs packages/dioxus-native-dom/src/mutation_writer.rs:404— packages/dioxus-native-dom/src/mutation_writer.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in BlitzBackend::set_attribute_impl at line 404. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/dioxus-native-dom/src/mutation_writer.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/layout/paint_tree.rs packages/blitz-dom/src/layout/paint_tree.rs:222— packages/blitz-dom/src/layout/paint_tree.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in BaseDocument::build_paint_tree_impl at line 222. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/paint_tree.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/events/driver.rs packages/blitz-dom/src/events/driver.rs:168— packages/blitz-dom/src/events/driver.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in EventDriver::handle_ui_event at line 168. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/events/driver.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-shell/src/application.rs packages/blitz-shell/src/application.rs:73— packages/blitz-shell/src/application.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in BlitzApplication::handle_blitz_shell_event at line 73. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-shell/src/application.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-vibey-cdp-server/src/session/css.rs packages/blitz-vibey-cdp-server/src/session/css.rs:14— packages/blitz-vibey-cdp-server/src/session/css.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in blitz_vibey_cdp_server::session::css::dispatch at line 14. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-vibey-cdp-server/src/session/css.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/blitz-dom/src/events/keyboard.rs packages/blitz-dom/src/events/keyboard.rs:16— packages/blitz-dom/src/events/keyboard.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in blitz_dom::events::keyboard::handle_key_or_input_event at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:33:33 +00:00' --until='2026-11-14 19:33:33 +00:00' --full-history --no-merges -- packages/blitz-dom/src/events/keyboard.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.
FileTooLong: src/document.rs packages/blitz-dom/src/document.rs— FileTooLong — 1652 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: BaseDocument (6 blocks, 164-2910). The bar is 500 significant lines; this is 1152 over it, 3.30× 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: node/node.rs packages/blitz-dom/src/node/node.rs— FileTooLong — 1232 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: Node (7 blocks, 92-2168). The bar is 500 significant lines; this is 732 over it, 2.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/mutator.rs packages/blitz-dom/src/mutator.rs— FileTooLong — 991 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: DocumentMutator (4 blocks, 64-1582). The bar is 500 significant lines; this is 491 over it, 1.98× 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/render.rs packages/blitz-paint/src/render.rs— FileTooLong — 988 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 488 over it, 1.98× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/geometry.js packages/blitz-vibey-script/src/geometry.js— FileTooLong — 940 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 440 over it, 1.88× 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: inline/layout.rs packages/blitz-dom/src/layout/inline/layout.rs— FileTooLong — 919 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: LayoutPassState (147-1385). The bar is 500 significant lines; this is 419 over it, 1.84× 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/convert.rs packages/stylo_taffy/src/convert.rs— FileTooLong — 751 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 54 free functions. The bar is 500 significant lines; this is 251 over it, 1.50× 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/cssom.rs packages/blitz-dom/src/cssom.rs— FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: BaseDocument (284-971). The bar is 500 significant lines; this is 175 over it, 1.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: render/background.rs packages/blitz-paint/src/render/background.rs— FileTooLong — 664 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 164 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: layout/construct.rs packages/blitz-dom/src/layout/construct.rs— FileTooLong — 643 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 143 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: node/element.rs packages/blitz-dom/src/node/element.rs— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: ElementData (5 blocks, 51-876). The bar is 500 significant lines; this is 132 over it, 1.26× 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/wrapper.rs packages/stylo_taffy/src/wrapper.rs— FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 84% of them inside a single declaration: TaffyStyloStyle (13 blocks, 42-983). The bar is 500 significant lines; this is 120 over it, 1.24× 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: layout/mod.rs packages/blitz-dom/src/layout/mod.rs— FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: LayoutPassState (14 blocks, 85-871). The bar is 500 significant lines; this is 119 over it, 1.24× 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/editor.rs packages/parley_code_editor/src/editor.rs— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: CodeEditor (2 blocks, 123-902). The bar is 500 significant lines; this is 115 over it, 1.23× 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/window.rs packages/blitz-shell/src/window.rs— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: View (4 blocks, 67-894). The bar is 500 significant lines; this is 64 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: layout/table.rs packages/blitz-dom/src/layout/table.rs— FileTooLong — 546 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 46 over it, 1.09× 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: events/pointer.rs packages/blitz-dom/src/events/pointer.rs— FileTooLong — 528 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 28 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/resolved_style.rs packages/blitz-dom/src/resolved_style.rs— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: BaseDocument (162-726). The bar is 500 significant lines; this is 16 over it, 1.03× 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/main.rs wpt/runner/src/main.rs— FileTooLong — 516 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 16 over it, 1.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/events.rs packages/blitz-traits/src/events.rs— FileTooLong — 514 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 14 over it, 1.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: node/text.rs packages/blitz-dom/src/node/text.rs— FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: TextInputData (3 blocks, 92-840). The bar is 500 significant lines; this is 4 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
blitz_dom::stylo::presentational_hints::compute_presentational_hints (cognitive 146) packages/blitz-dom/src/stylo/presentational_hints.rs:84— blitz_dom::stylo::presentational_hints::compute_presentational_hints has cognitive complexity 146 (threshold 15). Drivers by points: if/else 50 (103 pts), boolean chains 21, match/switch 6 (15 pts), loops 3 (7 pts) (nesting depth added 66). Of this number, 135 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
blitz_dom::events::pointer::handle_pointermove (cognitive 77) packages/blitz-dom/src/events/pointer.rs:207— blitz_dom::events::pointer::handle_pointermove has cognitive complexity 77 (threshold 15). Drivers by points: if/else 25 (66 pts), match/switch 3 (6 pts), boolean chains 5 (nesting depth added 44). 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.
blitz_dom::events::pointer::handle_click (cognitive 63) packages/blitz-dom/src/events/pointer.rs:615— blitz_dom::events::pointer::handle_click has cognitive complexity 63 (threshold 15). Drivers by points: if/else 22 (54 pts), match/switch 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::replaced::compute_replaced_layout (cognitive 56) packages/blitz-dom/src/layout/replaced.rs:52— blitz_dom::layout::replaced::compute_replaced_layout has cognitive complexity 56 (threshold 15). Drivers by points: if/else 37 (43 pts), match/switch 6 (10 pts), boolean chains 3 (nesting depth added 10). 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.
blitz_dom::layout::table::collect_table_cells (cognitive 49) packages/blitz-dom/src/layout/table.rs:515— blitz_dom::layout::table::collect_table_cells has cognitive complexity 49 (threshold 15). Drivers by points: if/else 16 (30 pts), match/switch 4 (9 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::events::keyboard::handle_key_or_input_event (cognitive 47) packages/blitz-dom/src/events/keyboard.rs:16— blitz_dom::events::keyboard::handle_key_or_input_event has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (44 pts), match/switch 1 (3 pts) (nesting depth added 31). 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.
blitz_dom::form::construct_entry_list (cognitive 43) packages/blitz-dom/src/form.rs:186— blitz_dom::form::construct_entry_list has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 8, loops 2 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::table::build_table_context (cognitive 43) packages/blitz-dom/src/layout/table.rs:203— blitz_dom::layout::table::build_table_context has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (24 pts), loops 7 (11 pts), match/switch 5 (6 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::construct::collect_layout_children_with_wrap (cognitive 40) packages/blitz-dom/src/layout/construct.rs:404— blitz_dom::layout::construct::collect_layout_children_with_wrap has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (32 pts), match/switch 3 (5 pts), boolean chains 3 (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.
blitz_dom::events::pointer::handle_pointerdown (cognitive 36) packages/blitz-dom/src/events/pointer.rs:384— blitz_dom::events::pointer::handle_pointerdown has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (26 pts), match/switch 4 (8 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::damage::compute_layout_damage (cognitive 26) packages/blitz-dom/src/layout/damage.rs:363— blitz_dom::layout::damage::compute_layout_damage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 12 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
blitz_dom::layout::construct::classify_flow_children (cognitive 25) packages/blitz-dom/src/layout/construct.rs:313— blitz_dom::layout::construct::classify_flow_children has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::construct::flush_pseudo_elements (cognitive 23) packages/blitz-dom/src/layout/construct.rs:678— blitz_dom::layout::construct::flush_pseudo_elements has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::util::walk_tree (cognitive 21) packages/blitz-dom/src/util.rs:91— blitz_dom::util::walk_tree has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::table::collect_columns (cognitive 20) packages/blitz-dom/src/layout/table.rs:441— blitz_dom::layout::table::collect_columns has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), match/switch 3 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::stylo::traversal::sync_pseudo_element_styles (cognitive 18) packages/blitz-dom/src/stylo/traversal.rs:345— blitz_dom::stylo::traversal::sync_pseudo_element_styles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::events::handle_dom_event (cognitive 17) packages/blitz-dom/src/events/mod.rs:102— blitz_dom::events::handle_dom_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::events::pointer::touch_action_pan_axes (cognitive 17) packages/blitz-dom/src/events/pointer.rs:168— blitz_dom::events::pointer::touch_action_pan_axes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 5, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FunctionTooLong: browser::toolbar::Toolbar apps/browser/src/toolbar.rs:36— FunctionTooLong — browser::toolbar::Toolbar runs 320 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 220 over it, 3.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_vibey_script::dom::element::init_element_proto packages/blitz-vibey-script/src/dom/element.rs:19— FunctionTooLong — blitz_vibey_script::dom::element::init_element_proto runs 313 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 213 over it, 3.13× 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: blitz_dom::stylo::presentational_hints::compute_presentational_hints packages/blitz-dom/src/stylo/presentational_hints.rs:84— FunctionTooLong — blitz_dom::stylo::presentational_hints::compute_presentational_hints runs 289 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 189 over it, 2.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::replaced::compute_replaced_layout packages/blitz-dom/src/layout/replaced.rs:52— FunctionTooLong — blitz_dom::layout::replaced::compute_replaced_layout runs 253 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 153 over it, 2.53× 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: blitz_vibey_cdp_server::session::dom::dispatch packages/blitz-vibey-cdp-server/src/session/dom.rs:14— FunctionTooLong — blitz_vibey_cdp_server::session::dom::dispatch runs 237 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 137 over it, 2.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_vibey_cdp_server::session::css::dispatch packages/blitz-vibey-cdp-server/src/session/css.rs:14— FunctionTooLong — blitz_vibey_cdp_server::session::css::dispatch runs 203 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 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::table::collect_table_cells packages/blitz-dom/src/layout/table.rs:515— FunctionTooLong — blitz_dom::layout::table::collect_table_cells runs 165 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 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::construct::collect_layout_children_with_wrap packages/blitz-dom/src/layout/construct.rs:404— FunctionTooLong — blitz_dom::layout::construct::collect_layout_children_with_wrap runs 158 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 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::table::build_table_context packages/blitz-dom/src/layout/table.rs:203— FunctionTooLong — blitz_dom::layout::table::build_table_context runs 155 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 55 over it, 1.55× 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: blitz_dom::events::pointer::handle_click packages/blitz-dom/src/events/pointer.rs:615— FunctionTooLong — blitz_dom::events::pointer::handle_click runs 139 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 39 over it, 1.39× 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: blitz_paint::text_decorations::flush_line_decorations packages/blitz-paint/src/text_decorations.rs:398— FunctionTooLong — blitz_paint::text_decorations::flush_line_decorations runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: stylo_taffy::convert::to_taffy_style packages/stylo_taffy/src/convert.rs:958— FunctionTooLong — stylo_taffy::convert::to_taffy_style runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::events::handle_dom_event packages/blitz-dom/src/events/mod.rs:102— FunctionTooLong — blitz_dom::events::handle_dom_event 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.
FunctionTooLong: blitz_dom::events::pointer::handle_pointermove packages/blitz-dom/src/events/pointer.rs:207— FunctionTooLong — blitz_dom::events::pointer::handle_pointermove runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::events::pointer::handle_pointerdown packages/blitz-dom/src/events/pointer.rs:384— FunctionTooLong — blitz_dom::events::pointer::handle_pointerdown runs 109 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 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_vibey_cdp_server::transport::handle_connection packages/blitz-vibey-cdp-server/src/transport.rs:52— FunctionTooLong — blitz_vibey_cdp_server::transport::handle_connection runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
BaseDocument::resolved_style_value (cognitive 108) packages/blitz-dom/src/resolved_style.rs:344— BaseDocument::resolved_style_value has cognitive complexity 108 (threshold 15). Drivers by points: if/else 38 (76 pts), match/switch 13 (23 pts), boolean chains 9 (nesting depth added 48). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::collect_inline_roots_in_range (cognitive 51) packages/blitz-dom/src/traversal.rs:377— BaseDocument::collect_inline_roots_in_range has cognitive complexity 51 (threshold 15). Drivers by points: if/else 15 (45 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 30). 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.
BaseDocument::build_paint_tree_impl (cognitive 50) packages/blitz-dom/src/layout/paint_tree.rs:222— BaseDocument::build_paint_tree_impl has cognitive complexity 50 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 4 (12 pts), boolean chains 6, match/switch 2 (5 pts) (nesting depth added 25). 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.
BaseDocument::resolve_stylist (cognitive 38) packages/blitz-dom/src/stylo/traversal.rs:40— BaseDocument::resolve_stylist has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 8 (12 pts), boolean chains 4 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::get_text_selection_ranges (cognitive 35) packages/blitz-dom/src/document.rs:2753— BaseDocument::get_text_selection_ranges has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 5, match/switch 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::build_accessibility_tree (cognitive 31) packages/blitz-dom/src/accessibility.rs:9— BaseDocument::build_accessibility_tree has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 4 (6 pts), boolean chains 3 (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.
BaseDocument::snapshot_node_impl (cognitive 21) packages/blitz-dom/src/document.rs:1492— BaseDocument::snapshot_node_impl has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::propagate_damage_flags (cognitive 21) packages/blitz-dom/src/layout/damage.rs:58— BaseDocument::propagate_damage_flags has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaseDocument::resolve_transforms (cognitive 21) packages/blitz-dom/src/resolve.rs:169— BaseDocument::resolve_transforms has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::refresh_anonymous_block_styles (cognitive 20) packages/blitz-dom/src/layout/damage.rs:200— BaseDocument::refresh_anonymous_block_styles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::collect_layout_children_inline_roots (cognitive 20) packages/blitz-dom/src/traversal.rs:547— BaseDocument::collect_layout_children_inline_roots has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::resolve_layout_children::resolve_layout_children_recursive (cognitive 19) packages/blitz-dom/src/resolve.rs:256— BaseDocument::resolve_layout_children::resolve_layout_children_recursive has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (7 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.
BaseDocument::build_accessibility_node (cognitive 17) packages/blitz-dom/src/accessibility.rs:108— BaseDocument::build_accessibility_node has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
BaseDocument::clear_interaction_state_for_removed_node (cognitive 17) packages/blitz-dom/src/document.rs:942— BaseDocument::clear_interaction_state_for_removed_node has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaseDocument::scroll_state (cognitive 17) packages/blitz-dom/src/scrolling.rs:438— BaseDocument::scroll_state has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 5 (8 pts) (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
blitz_dom::stylo::presentational_hints::compute_presentational_hints (cyclomatic 85) packages/blitz-dom/src/stylo/presentational_hints.rs:84— blitz_dom::stylo::presentational_hints::compute_presentational_hints has cyclomatic complexity 85 (threshold 15). Of this number, 73 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::accessibility::role_from_element_data (cyclomatic 65) packages/blitz-dom/src/accessibility.rs:341— blitz_dom::accessibility::role_from_element_data has cyclomatic complexity 65 (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.
blitz_dom::events::handle_dom_event (cyclomatic 45) packages/blitz-dom/src/events/mod.rs:102— blitz_dom::events::handle_dom_event has cyclomatic complexity 45 (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.
blitz_dom::layout::replaced::compute_replaced_layout (cyclomatic 43) packages/blitz-dom/src/layout/replaced.rs:52— blitz_dom::layout::replaced::compute_replaced_layout has cyclomatic complexity 43 (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.
blitz_dom::events::pointer::handle_pointermove (cyclomatic 32) packages/blitz-dom/src/events/pointer.rs:207— blitz_dom::events::pointer::handle_pointermove has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::events::pointer::handle_click (cyclomatic 32) packages/blitz-dom/src/events/pointer.rs:615— blitz_dom::events::pointer::handle_click has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::layout::table::collect_table_cells (cyclomatic 31) packages/blitz-dom/src/layout/table.rs:515— blitz_dom::layout::table::collect_table_cells 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.
blitz_dom::layout::construct::collect_layout_children_with_wrap (cyclomatic 28) packages/blitz-dom/src/layout/construct.rs:404— blitz_dom::layout::construct::collect_layout_children_with_wrap has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::layout::table::build_table_context (cyclomatic 28) packages/blitz-dom/src/layout/table.rs:203— blitz_dom::layout::table::build_table_context has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::form::construct_entry_list (cyclomatic 25) packages/blitz-dom/src/form.rs:186— blitz_dom::form::construct_entry_list 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.
blitz_dom::layout::damage::compute_layout_damage (cyclomatic 24) packages/blitz-dom/src/layout/damage.rs:363— blitz_dom::layout::damage::compute_layout_damage has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
blitz_dom::events::pointer::handle_pointerdown (cyclomatic 20) packages/blitz-dom/src/events/pointer.rs:384— blitz_dom::events::pointer::handle_pointerdown 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.
blitz_dom::events::keyboard::handle_key_or_input_event (cyclomatic 16) packages/blitz-dom/src/events/keyboard.rs:16— blitz_dom::events::keyboard::handle_key_or_input_event has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::stylo_to_parley::style (cyclomatic 16) packages/blitz-dom/src/stylo_to_parley.rs:441— blitz_dom::stylo_to_parley::style 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.
MethodTooLong: LayoutPassState.compute_inline_layout_inner packages/blitz-dom/src/layout/inline/layout.rs:338— MethodTooLong — compute_inline_layout_inner runs 685 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 585 over it, 6.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: LayoutPassState.dispatch_child_layout packages/blitz-dom/src/layout/mod.rs:220— MethodTooLong — dispatch_child_layout runs 251 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 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BaseDocument.resolved_style_value packages/blitz-dom/src/resolved_style.rs:344— MethodTooLong — resolved_style_value runs 246 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 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInputData.apply_apple_standard_keybinding packages/blitz-dom/src/node/text.rs:407— MethodTooLong — apply_apple_standard_keybinding runs 230 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 130 over it, 2.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BlitzDomPainter.render_element packages/blitz-paint/src/render.rs:435— MethodTooLong — render_element runs 198 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 98 over it, 1.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: View.handle_winit_event packages/blitz-shell/src/window.rs:600— MethodTooLong — handle_winit_event runs 192 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 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Node.hit_inner packages/blitz-dom/src/node/node.rs:1469— MethodTooLong — hit_inner runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BaseDocument.new packages/blitz-dom/src/document.rs:395— MethodTooLong — new runs 129 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 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInputData.apply_keypress_event packages/blitz-dom/src/node/text.rs:235— MethodTooLong — apply_keypress_event runs 124 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 24 over it, 1.24× 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: BaseDocument.build_paint_tree_impl packages/blitz-dom/src/layout/paint_tree.rs:222— MethodTooLong — build_paint_tree_impl runs 115 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 15 over it, 1.15× 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: ElementCx.draw_border packages/blitz-paint/src/render/border.rs:150— MethodTooLong — draw_border 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.
MethodTooLong: ScriptRuntime.dispatch_event_inner packages/blitz-vibey-script/src/runtime/events.rs:212— MethodTooLong — dispatch_event_inner runs 105 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 5 over it, 1.05× 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: BaseDocument.debug_log_node packages/blitz-dom/src/debug.rs:19— MethodTooLong — debug_log_node runs 104 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 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventDriver.handle_ui_event packages/blitz-dom/src/events/driver.rs:168— MethodTooLong — handle_ui_event runs 101 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 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: BaseDocument packages/blitz-dom/src/document.rs:193— ClassTooLong — 1494 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 272 methods, 6 blocks, lines 164-2910. The bar is 400 significant lines; this is 1094 over it, 3.74× 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: Node packages/blitz-dom/src/node/node.rs:92— ClassTooLong — 1099 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 144 methods, 7 blocks, lines 92-2168. The bar is 400 significant lines; this is 699 over it, 2.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DocumentMutator packages/blitz-dom/src/mutator.rs:64— ClassTooLong — 917 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 60 methods, 4 blocks, lines 64-1582. The bar is 400 significant lines; this is 517 over it, 2.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: CodeEditor packages/parley_code_editor/src/editor.rs:123— ClassTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 61 methods, 2 blocks, lines 123-902. The bar is 400 significant lines; this is 141 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TaffyStyloStyle packages/stylo_taffy/src/wrapper.rs:42— ClassTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 13 blocks, lines 42-983. The bar is 400 significant lines; this is 118 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: View packages/blitz-shell/src/window.rs:67— ClassTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 4 blocks, lines 67-894. The bar is 400 significant lines; this is 116 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: LayoutPassState packages/blitz-dom/src/layout/mod.rs:85— ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 14 blocks, lines 85-871. The bar is 400 significant lines; this is 103 over it, 1.26× 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: BlitzDomPainter packages/blitz-paint/src/render.rs:116— ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 2 blocks, lines 116-814. The bar is 400 significant lines; this is 65 over it, 1.16× 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: TextInputData packages/blitz-dom/src/node/text.rs:92— ClassTooLong — 454 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 3 blocks, lines 92-840. The bar is 400 significant lines; this is 54 over it, 1.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BlitzNode packages/blitz-dom/src/stylo/dom.rs:43— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods, 9 blocks, lines 45-801. The bar is 400 significant lines; this is 21 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
BaseDocument::resolved_style_value (cyclomatic 72) packages/blitz-dom/src/resolved_style.rs:344— BaseDocument::resolved_style_value has cyclomatic complexity 72 (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.
BaseDocument::get_text_selection_ranges (cyclomatic 24) packages/blitz-dom/src/document.rs:2753— BaseDocument::get_text_selection_ranges has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaseDocument::build_paint_tree_impl (cyclomatic 23) packages/blitz-dom/src/layout/paint_tree.rs:222— BaseDocument::build_paint_tree_impl has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaseDocument::resolve_stylist (cyclomatic 23) packages/blitz-dom/src/stylo/traversal.rs:40— BaseDocument::resolve_stylist has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaseDocument::build_accessibility_tree (cyclomatic 19) packages/blitz-dom/src/accessibility.rs:9— BaseDocument::build_accessibility_tree has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: blitz_dom::accessibility::role_from_name (cyclomatic 59) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
BaseDocument::collect_inline_roots_in_range (cyclomatic 19) packages/blitz-dom/src/traversal.rs:377— BaseDocument::collect_inline_roots_in_range 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.
BaseDocument::propagate_damage_flags (cyclomatic 18) packages/blitz-dom/src/layout/damage.rs:58— BaseDocument::propagate_damage_flags has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaseDocument::build_accessibility_node (cyclomatic 16) packages/blitz-dom/src/accessibility.rs:108— BaseDocument::build_accessibility_node has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: blitz_dom::accessibility::role_from_name (cyclomatic 59) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
FixmeComment packages/dioxus-native-dom/src/mutation_writer.rs:481— // FIXME: support all attribute types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/dioxus-native-dom/src/mutation_writer.rs:509— // FIXME: more principled handling of special case attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/blitz-dom/src/resolve.rs:13— // FIXME: static thread_local FontCtx isn't necessarily correct in multi-document context. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/blitz-dom/src/stylo/dom.rs:722— // FIXME: Implement container queries. For now this effectively disables them without panicking. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/blitz-dom/src/node/node.rs:2154— // FIXME: update to reflect changes to fields — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/blitz-dom/src/node/text.rs:109— // FIXME: Implement Clone for PlainEditor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/blitz-dom/src/events/pointer.rs:102— // FIXME: use truncate_front once stable — 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.
blitz_paint::gradient::resolve_color_stops (cognitive 56) packages/blitz-paint/src/gradient.rs:325— blitz_paint::gradient::resolve_color_stops has cognitive complexity 56 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 4 (14 pts), match/switch 3 (8 pts), boolean chains 3 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_paint::text::stroke_text (cognitive 39) packages/blitz-paint/src/text.rs:94— blitz_paint::text::stroke_text has cognitive complexity 39 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 6 (14 pts), match/switch 1 (4 pts) (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.
blitz_paint::text_decorations::flush_line_decorations (cognitive 32) packages/blitz-paint/src/text_decorations.rs:398— blitz_paint::text_decorations::flush_line_decorations has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 3 (5 pts), boolean chains 4, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_paint::gradient::radial_gradient (cognitive 27) packages/blitz-paint/src/gradient.rs:161— blitz_paint::gradient::radial_gradient has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 5 (11 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_paint::text_decorations::draw_line_text_shadows (cognitive 24) packages/blitz-paint/src/text_decorations.rs:604— blitz_paint::text_decorations::draw_line_text_shadows has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_paint::render::background::compute_layer_size (cognitive 23) packages/blitz-paint/src/render/background.rs:725— blitz_paint::render::background::compute_layer_size has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 10 (23 pts) (nesting depth added 13). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
blitz_paint::text_decorations::draw_decoration_line (cognitive 20) packages/blitz-paint/src/text_decorations.rs:287— blitz_paint::text_decorations::draw_decoration_line has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (8 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×7
Edited copy of a member (14 corresponding lines) packages/blitz-dom/src/cssom.rs:122— packages/blitz-dom/src/cssom.rs:122-137 | packages/blitz-vibey-cdp-server/src/style_sheets.rs:462-475 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/dom/node.rs:84— packages/blitz-vibey-script/src/dom/node.rs:84-97 | packages/blitz-vibey-script/src/dom/node.rs:99-115 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) packages/blitz-paint/src/render/background.rs:94— packages/blitz-paint/src/render/background.rs:94-107 | packages/blitz-paint/src/render/background.rs:113-127 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/runtime/events.rs:450— packages/blitz-vibey-script/src/runtime/events.rs:450-475 | packages/blitz-vibey-script/src/runtime/events.rs:481-494 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs:339— packages/blitz-vibey-script/src/dom/document.rs:339-355 | packages/blitz-vibey-script/src/dom/document.rs:382-395 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) packages/blitz-vibey-script/src/dom/mod.rs:429— packages/blitz-vibey-script/src/dom/mod.rs:429-446 | packages/blitz-vibey-script/src/dom/mod.rs:465-478 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) packages/blitz-dom/src/mutator.rs:1079— packages/blitz-dom/src/mutator.rs:1079-1092 | packages/blitz-dom/src/mutator.rs:1115-1129 — These two members are one piece of code written twice and then edited apart: 14 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.
Duplicated block (6 lines × 2) packages/blitz-dom/src/document.rs:1780— packages/blitz-dom/src/document.rs:1780-1785 | packages/blitz-dom/src/document.rs:1967-1972 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/document.rs:1780` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:284— packages/blitz-vibey-script/src/dom/document.rs:284-289 | packages/blitz-vibey-script/src/dom/element/selectors.rs:117-122 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/document.rs:284` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/dom/element/attributes.rs:308— packages/blitz-vibey-script/src/dom/element/attributes.rs:308-313 | packages/blitz-vibey-script/src/dom/element/attributes.rs:326-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/element/attributes.rs:308` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/runtime/timers.rs:73— packages/blitz-vibey-script/src/runtime/timers.rs:73-78 | packages/blitz-vibey-script/src/runtime/timers.rs:88-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) packages/stylo_taffy/src/convert.rs:1077— packages/stylo_taffy/src/convert.rs:1077-1082 | packages/stylo_taffy/src/convert.rs:1085-1090 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/document.rs:300— packages/blitz-vibey-script/src/document.rs:300-306 | packages/blitz-vibey-script/src/runtime/events.rs:109-114 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/document.rs:300` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) packages/blitz-dom/src/stylo/presentational_hints.rs:98— packages/blitz-dom/src/stylo/presentational_hints.rs:98-103 | packages/blitz-dom/src/stylo/presentational_hints.rs:105-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Off the main sequence: browser-persistence — browser-persistence: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: debug_timer — debug_timer: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: accesskit_xplat — accesskit_xplat: abstractness 0.13, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: blitz-traits — blitz-traits: abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: blitz-html — blitz-html: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: blitz-dom — blitz-dom: abstractness 0.05, instability 0.21, distance 0.74 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
Off the main sequence: stylo_taffy — stylo_taffy: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
TooManyMethods: BaseDocument packages/blitz-dom/src/document.rs:193— TooManyMethods — 272 methods, declared across 17 files: src/document.rs (144), src/scrolling.rs (23), src/cssom.rs (22), src/traversal.rs (19), +13 more file(s). The bar is 30 methods; this is 242 over it, 9.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Node packages/blitz-dom/src/node/node.rs:92— TooManyMethods — 144 methods, declared across 5 files: node/node.rs (124), node/scrollbar.rs (7), node/serialize.rs (6), src/query_selector.rs (4), +1 more file(s). The bar is 30 methods; this is 114 over it, 4.80× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CodeEditor packages/parley_code_editor/src/editor.rs:123— TooManyMethods — 61 methods, declared across 3 files: src/editor.rs (53), editor/multi_selection.rs (7), src/paint.rs (1). The bar is 30 methods; this is 31 over it, 2.03× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DocumentMutator packages/blitz-dom/src/mutator.rs:64— TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ElementCx packages/blitz-paint/src/render.rs:851— TooManyMethods — 44 methods, declared across 7 files: render/background.rs (14), src/render.rs (11), render/border.rs (6), render/mask.rs (5), +3 more file(s). The bar is 30 methods; this is 14 over it, 1.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ElementData packages/blitz-dom/src/node/element.rs:51— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×6
Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs:367— packages/blitz-vibey-script/src/dom/document.rs:367-376 | packages/blitz-vibey-script/src/dom/element/selectors.rs:23-34 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/runtime/timers.rs:72— packages/blitz-vibey-script/src/runtime/timers.rs:72-81 | packages/blitz-vibey-script/src/runtime/timers.rs:87-96 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/dom/element/selectors.rs:61— packages/blitz-vibey-script/src/dom/element/selectors.rs:61-70 | packages/blitz-vibey-script/src/dom/element/selectors.rs:76-86 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs:138— packages/blitz-vibey-script/src/dom/stylesheet.rs:138-147 | packages/blitz-vibey-script/src/dom/stylesheet.rs:186-195 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) packages/accesskit_xplat/src/platform_impl/macos.rs:19— packages/accesskit_xplat/src/platform_impl/macos.rs:19-28 | packages/accesskit_xplat/src/platform_impl/windows.rs:19-28 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) packages/stylo_taffy/src/convert.rs:821— packages/stylo_taffy/src/convert.rs:821-831 | packages/stylo_taffy/src/wrapper.rs:850-859 — These two members are one piece of code written twice and then edited apart: 10 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.
Duplicated block (8 lines × 2) packages/blitz-dom/src/cssom.rs:584— packages/blitz-dom/src/cssom.rs:584-591 | packages/blitz-dom/src/cssom.rs:795-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/cssom.rs:584` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) packages/blitz-dom/src/cssom.rs:793— packages/blitz-dom/src/cssom.rs:793-800 | packages/blitz-dom/src/cssom.rs:847-854 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/cssom.rs:793` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) packages/blitz-dom/src/events/driver.rs:193— packages/blitz-dom/src/events/driver.rs:193-200 | packages/blitz-dom/src/events/driver.rs:202-209 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) packages/blitz-dom/src/events/pointer.rs:349— packages/blitz-dom/src/events/pointer.rs:349-357 | packages/blitz-dom/src/events/pointer.rs:468-475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/events/pointer.rs:349` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) packages/blitz-dom/src/font_metrics.rs:115— packages/blitz-dom/src/font_metrics.rs:115-122 | packages/blitz-dom/src/font_metrics.rs:140-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/stylo_taffy/src/convert.rs:600— packages/stylo_taffy/src/convert.rs:600-607 | packages/stylo_taffy/src/convert.rs:634-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/stylo_taffy/src/convert.rs:600` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) packages/blitz-shell/src/window.rs:755— packages/blitz-shell/src/window.rs:755-761 | packages/blitz-shell/src/window.rs:837-843 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-shell/src/window.rs:755` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) packages/blitz-vibey-cdp-server/src/session/css.rs:87— packages/blitz-vibey-cdp-server/src/session/css.rs:87-93 | packages/blitz-vibey-cdp-server/src/session/css.rs:143-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:267— packages/blitz-vibey-script/src/dom/document.rs:267-273 | packages/blitz-vibey-script/src/dom/element/selectors.rs:100-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/document.rs:267` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:387— packages/blitz-vibey-script/src/dom/document.rs:387-393 | packages/blitz-vibey-script/src/dom/element/selectors.rs:47-53 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/document.rs:387` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) packages/blitz-vibey-script/src/runtime/window.rs:172— packages/blitz-vibey-script/src/runtime/window.rs:172-178 | packages/blitz-vibey-script/src/runtime/window.rs:194-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) apps/browser/src/toolbar.rs:221— apps/browser/src/toolbar.rs:221-227 | apps/browser/src/toolbar.rs:243-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/browser/src/toolbar.rs:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
ElementCx::draw_border (cognitive 32) packages/blitz-paint/src/render/border.rs:150— ElementCx::draw_border has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6, loops 3 (4 pts), match/switch 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElementCx::draw_dotted_border_edge (cognitive 19) packages/blitz-paint/src/render/border.rs:447— ElementCx::draw_dotted_border_edge has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (5 pts), match/switch 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElementCx::draw_scrollbars (cognitive 19) packages/blitz-paint/src/render.rs:884— ElementCx::draw_scrollbars has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 4 (7 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElementCx::draw_table_borders (cognitive 16) packages/blitz-paint/src/render/border.rs:513— ElementCx::draw_table_borders has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ElementCx::draw_text_input_text (cognitive 16) packages/blitz-paint/src/render.rs:1055— ElementCx::draw_text_input_text has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 1 (4 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×5
CodeEditor::key_action (cyclomatic 56) packages/parley_code_editor/src/editor.rs:570— CodeEditor::key_action has cyclomatic complexity 56 (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.
CodeEditor::paint (cyclomatic 22) packages/parley_code_editor/src/paint.rs:15— CodeEditor::paint has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CodeEditor::move_region (cyclomatic 21) packages/parley_code_editor/src/editor.rs:684— CodeEditor::move_region has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CodeEditor::handle_input (cyclomatic 16) packages/parley_code_editor/src/editor.rs:249— CodeEditor::handle_input 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.
blitz_paint::gradient::resolve_color_stops (cyclomatic 24) packages/blitz-paint/src/gradient.rs:325— blitz_paint::gradient::resolve_color_stops has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_paint::render::background::compute_layer_size (cyclomatic 20) packages/blitz-paint/src/render/background.rs:725— blitz_paint::render::background::compute_layer_size 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.
blitz_paint::text_decorations::flush_line_decorations (cyclomatic 20) packages/blitz-paint/src/text_decorations.rs:398— blitz_paint::text_decorations::flush_line_decorations 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.
blitz_paint::gradient::radial_gradient (cyclomatic 16) packages/blitz-paint/src/gradient.rs:161— blitz_paint::gradient::radial_gradient 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.
LayoutPassState::compute_inline_layout_inner (cognitive 165) packages/blitz-dom/src/layout/inline/layout.rs:338— LayoutPassState::compute_inline_layout_inner has cognitive complexity 165 (threshold 15). Drivers by points: if/else 56 (118 pts), boolean chains 18, match/switch 9 (16 pts), loops 7 (13 pts) (nesting depth added 75). 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.
LayoutPassState::dispatch_child_layout (cognitive 68) packages/blitz-dom/src/layout/mod.rs:220— LayoutPassState::dispatch_child_layout has cognitive complexity 68 (threshold 15). Drivers by points: if/else 15 (40 pts), match/switch 8 (22 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 42). 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.
LayoutPassState::inline_span_cb_flags (cognitive 18) packages/blitz-dom/src/layout/inline/layout.rs:307— LayoutPassState::inline_span_cb_flags has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutPassState::compute_orthogonal_child_layout (cognitive 16) packages/blitz-dom/src/layout/writing_mode.rs:129— LayoutPassState::compute_orthogonal_child_layout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, 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.
Node::hit_inner (cognitive 80) packages/blitz-dom/src/node/node.rs:1469— Node::hit_inner has cognitive complexity 80 (threshold 15). Drivers by points: if/else 31 (57 pts), boolean chains 15, loops 3 (7 pts), match/switch 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Node::write_outer_html_in_style (cognitive 46) packages/blitz-dom/src/node/serialize.rs:117— Node::write_outer_html_in_style has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 5 (15 pts), boolean chains 3, match/switch 1 (nesting depth added 24). 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.
Node::cssom_scroll_size (cognitive 20) packages/blitz-dom/src/node/node.rs:2015— Node::cssom_scroll_size has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Node::inline_fragment_boxes (cognitive 18) packages/blitz-dom/src/node/node.rs:1841— Node::inline_fragment_boxes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 3 (5 pts), loops 2 (nesting depth added 8). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocumentMutator::set_attribute (cognitive 35) packages/blitz-dom/src/mutator.rs:323— DocumentMutator::set_attribute has cognitive complexity 35 (threshold 15). Drivers by points: if/else 24 (29 pts), boolean chains 6 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocumentMutator::add_children_to_parent (cognitive 27) packages/blitz-dom/src/mutator.rs:863— DocumentMutator::add_children_to_parent has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 4 (6 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocumentMutator::clear_attribute (cognitive 26) packages/blitz-dom/src/mutator.rs:459— DocumentMutator::clear_attribute has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocumentMutator::restyle_for_child_list_change (cognitive 21) packages/blitz-dom/src/mutator.rs:756— DocumentMutator::restyle_for_child_list_change has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_vibey_cdp_server::session::dom::dispatch (cognitive 33) packages/blitz-vibey-cdp-server/src/session/dom.rs:14— blitz_vibey_cdp_server::session::dom::dispatch has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 4 (7 pts), loops 2 (4 pts), boolean chains 1 (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.
blitz_vibey_cdp_server::session::css::dispatch (cognitive 31) packages/blitz-vibey-cdp-server/src/session/css.rs:14— blitz_vibey_cdp_server::session::css::dispatch has cognitive complexity 31 (threshold 15). Drivers by points: loops 7 (16 pts), if/else 4 (10 pts), match/switch 2 (4 pts), boolean chains 1 (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.
blitz_vibey_cdp_server::session::dom::parse_attributes_text (cognitive 26) packages/blitz-vibey-cdp-server/src/session/dom.rs:326— blitz_vibey_cdp_server::session::dom::parse_attributes_text has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (18 pts), if/else 2 (4 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 15). 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.
blitz_vibey_cdp_server::transport::handle_connection (cognitive 18) packages/blitz-vibey-cdp-server/src/transport.rs:52— blitz_vibey_cdp_server::transport::handle_connection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (6 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×4
Edited copy of a member (18 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs:258— packages/blitz-vibey-script/src/dom/document.rs:258-275 | packages/blitz-vibey-script/src/dom/document.rs:281-301 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) packages/stylo_taffy/src/convert.rs:130— packages/stylo_taffy/src/convert.rs:130-147 | packages/stylo_taffy/src/convert.rs:150-167 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs:197— packages/blitz-vibey-script/src/dom/stylesheet.rs:197-215 | packages/blitz-vibey-script/src/dom/stylesheet.rs:217-234 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) packages/stylo_taffy/src/wrapper.rs:778— packages/stylo_taffy/src/wrapper.rs:778-795 | packages/stylo_taffy/src/wrapper.rs:798-815 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs:246— packages/blitz-vibey-script/src/dom/document.rs:246-252 | packages/blitz-vibey-script/src/dom/style.rs:116-125 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs:49— packages/blitz-vibey-script/src/dom/element/attributes.rs:49-55 | packages/blitz-vibey-script/src/dom/hyperlink.rs:98-104 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs:106— packages/blitz-vibey-script/src/dom/stylesheet.rs:106-112 | packages/blitz-vibey-script/src/dom/stylesheet.rs:120-126 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) apps/browser/src/nav.rs:34— apps/browser/src/nav.rs:34-40 | packages/dioxus-native/src/link_handler.rs:9-17 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×4
Edited copy of a member (5 corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs:247— packages/blitz-vibey-script/src/dom/element/attributes.rs:247-251 | packages/blitz-vibey-script/src/dom/element/form_controls.rs:45-51 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs:114— packages/blitz-vibey-script/src/dom/stylesheet.rs:114-118 | packages/blitz-vibey-script/src/runtime/window.rs:147-151 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) packages/blitz-vibey-cdp-server/src/style_sheets.rs:397— packages/blitz-vibey-cdp-server/src/style_sheets.rs:397-401 | packages/blitz-vibey-script/src/dom/node.rs:413-417 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) packages/blitz-dom/src/document.rs:2124— packages/blitz-dom/src/document.rs:2124-2128 | packages/blitz-dom/src/mutator.rs:214-219 — These two members are one piece of code written twice and then edited apart: 5 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.
Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:208— packages/blitz-vibey-script/src/dom/document.rs:208-212 | packages/blitz-vibey-script/src/dom/document.rs:219-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/document.rs:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/dom/element/attributes.rs:275— packages/blitz-vibey-script/src/dom/element/attributes.rs:275-279 | packages/blitz-vibey-script/src/dom/hyperlink.rs:55-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) packages/blitz-dom/src/document.rs:2372— packages/blitz-dom/src/document.rs:2372-2376 | packages/blitz-dom/src/layout/writing_mode.rs:545-549 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/document.rs:2372` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `node_id` to `NodeId` in one and `crate::NodeId` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/blitz-dom/src/layout/writing_mode.rs:550` calls `layout_data`, `is_vertical` and `packages/blitz-dom/src/document.rs:2377` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/dom/node.rs:608— packages/blitz-vibey-script/src/dom/node.rs:608-612 | packages/blitz-vibey-script/src/dom/node.rs:663-667 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/node.rs:608` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
DocumentMutator::set_attribute (cyclomatic 31) packages/blitz-dom/src/mutator.rs:323— DocumentMutator::set_attribute has cyclomatic complexity 31 (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.
DocumentMutator::clear_attribute (cyclomatic 25) packages/blitz-dom/src/mutator.rs:459— DocumentMutator::clear_attribute has cyclomatic complexity 25 (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.
DocumentMutator::add_children_to_parent (cyclomatic 19) packages/blitz-dom/src/mutator.rs:863— DocumentMutator::add_children_to_parent 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.
CodeEditor::paint (cognitive 40) packages/parley_code_editor/src/paint.rs:15— CodeEditor::paint has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 7 (16 pts), boolean chains 6, match/switch 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeEditor::move_region (cognitive 18) packages/parley_code_editor/src/editor.rs:684— CodeEditor::move_region has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 4 (7 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
CodeEditor::key_action (cognitive 17) packages/parley_code_editor/src/editor.rs:570— CodeEditor::key_action has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, match/switch 3 (5 pts), if/else 4 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) packages/blitz-dom/src/layout/construct.rs:181— packages/blitz-dom/src/layout/construct.rs:181-192 | packages/blitz-dom/src/layout/construct.rs:273-284 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) packages/stylo_taffy/src/convert.rs:914— packages/stylo_taffy/src/convert.rs:914-925 | packages/stylo_taffy/src/convert.rs:931-943 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) packages/blitz-dom/src/mutator.rs:1041— packages/blitz-dom/src/mutator.rs:1041-1052 | packages/blitz-vibey-script/src/dom/element.rs:497-511 — These two members are one piece of code written twice and then edited apart: 12 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.
Duplicated block (16 lines × 2) packages/blitz-dom/src/events/driver.rs:395— packages/blitz-dom/src/events/driver.rs:395-410 | packages/blitz-vibey-script/src/dom/event.rs:244-259 — 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 (16 lines × 2) packages/blitz-traits/src/events.rs:367— packages/blitz-traits/src/events.rs:367-382 | packages/blitz-traits/src/events.rs:413-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 (16 lines × 2) packages/stylo_taffy/src/wrapper.rs:780— packages/stylo_taffy/src/wrapper.rs:780-795 | packages/stylo_taffy/src/wrapper.rs:800-815 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/stylo_taffy/src/wrapper.rs:780` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) packages/blitz-dom/src/node/node.rs:1597— packages/blitz-dom/src/node/node.rs:1597-1608 | packages/blitz-dom/src/node/node.rs:1643-1654 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/node/node.rs:1597` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) packages/blitz-paint/src/text.rs:317— packages/blitz-paint/src/text.rs:317-328 | packages/parley_code_editor/src/paint.rs:182-193 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-paint/src/text.rs:317` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) packages/blitz-paint/src/render.rs:1289— packages/blitz-paint/src/render.rs:1289-1300 | packages/blitz-paint/src/render.rs:1366-1377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-paint/src/render.rs:1289` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) packages/blitz-traits/src/events.rs:385— packages/blitz-traits/src/events.rs:385-395 | packages/blitz-traits/src/events.rs:431-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 (11 lines × 2) packages/blitz-vibey-script/src/runtime/events.rs:329— packages/blitz-vibey-script/src/runtime/events.rs:329-339 | packages/blitz-vibey-script/src/runtime/events.rs:398-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) packages/blitz-vibey-cdp-server/src/style_sheets.rs:297— packages/blitz-vibey-cdp-server/src/style_sheets.rs:297-307 | packages/blitz-vibey-cdp-server/src/style_sheets.rs:372-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-cdp-server/src/style_sheets.rs:297` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) packages/blitz-dom/src/mutator.rs:324— packages/blitz-dom/src/mutator.rs:324-333 | packages/blitz-dom/src/mutator.rs:460-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/mutator.rs:324` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) packages/blitz-paint/src/render/background.rs:563— packages/blitz-paint/src/render/background.rs:563-572 | packages/blitz-paint/src/render/background.rs:655-664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-paint/src/render/background.rs:563` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) apps/browser/src/url_suggestions.rs:275— apps/browser/src/url_suggestions.rs:275-284 | apps/browser/src/url_suggestions.rs:287-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/browser/src/url_suggestions.rs:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:237— packages/blitz-vibey-script/src/geometry.js:237 · packages/blitz-vibey-script/src/geometry.js:245 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:368— packages/blitz-vibey-script/src/geometry.js:368 · packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js:35 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (8 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:1031— packages/blitz-vibey-script/src/geometry.js:1031 · packages/blitz-vibey-script/src/geometry.js:1046 — 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.
TextInputData::apply_apple_standard_keybinding (cyclomatic 100) packages/blitz-dom/src/node/text.rs:407— TextInputData::apply_apple_standard_keybinding has cyclomatic complexity 100 (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.
TextInputData::apply_keypress_event (cyclomatic 41) packages/blitz-dom/src/node/text.rs:235— TextInputData::apply_keypress_event has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LayoutPassState::compute_inline_layout_inner (cyclomatic 78) packages/blitz-dom/src/layout/inline/layout.rs:338— LayoutPassState::compute_inline_layout_inner has cyclomatic complexity 78 (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.
LayoutPassState::dispatch_child_layout (cyclomatic 37) packages/blitz-dom/src/layout/mod.rs:220— LayoutPassState::dispatch_child_layout 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.
Node::hit_inner (cyclomatic 47) packages/blitz-dom/src/node/node.rs:1469— Node::hit_inner has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Node::write_outer_html_in_style (cyclomatic 24) packages/blitz-dom/src/node/serialize.rs:117— Node::write_outer_html_in_style has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_vibey_cdp_server::session::dom::dispatch (cyclomatic 30) packages/blitz-vibey-cdp-server/src/session/dom.rs:14— blitz_vibey_cdp_server::session::dom::dispatch has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
blitz_vibey_cdp_server::session::css::dispatch (cyclomatic 24) packages/blitz-vibey-cdp-server/src/session/css.rs:14— blitz_vibey_cdp_server::session::css::dispatch has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ElementCx::draw_border (cyclomatic 27) packages/blitz-paint/src/render/border.rs:150— ElementCx::draw_border has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElementCx::draw_scrollbars (cyclomatic 16) packages/blitz-paint/src/render.rs:884— ElementCx::draw_scrollbars 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.
OffsetMapper::visit (cyclomatic 22) packages/blitz-vibey-script/src/dom/selection.rs:274— OffsetMapper::visit has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OffsetMapper::advance (cyclomatic 18) packages/blitz-vibey-script/src/dom/selection.rs:358— OffsetMapper::advance has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
blitz_vibey_script::dom::hyperlink::component_setter (cyclomatic 18) packages/blitz-vibey-script/src/dom/hyperlink.rs:148— blitz_vibey_script::dom::hyperlink::component_setter 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.
blitz_vibey_script::dom::hyperlink::component_getter (cyclomatic 17) packages/blitz-vibey-script/src/dom/hyperlink.rs:106— blitz_vibey_script::dom::hyperlink::component_getter has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
HackComment packages/blitz-dom/src/layout/mod.rs:570— // HACK: Cap scrollable overflow at node size to prevent scrolling — 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.
HackComment apps/browser/src/main.rs:153— // HACK: Winit doesn't support "safe area" on Android yet. — 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.
wpt::main (cognitive 32) wpt/runner/src/main.rs:348— wpt::main has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (21 pts), loops 3 (5 pts), boolean chains 4, match/switch 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
wpt::manifest::load_tests (cognitive 28) wpt/runner/src/manifest.rs:89— wpt::manifest::load_tests has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 4 (11 pts), match/switch 1 (4 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.
OffsetMapper::visit (cognitive 31) packages/blitz-vibey-script/src/dom/selection.rs:274— OffsetMapper::visit has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OffsetMapper::advance (cognitive 22) packages/blitz-vibey-script/src/dom/selection.rs:358— OffsetMapper::advance has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 3, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TooManyFunctions: blitz_vibey_script::dom::node packages/blitz-vibey-script/src/dom/node.rs:17— TooManyFunctions — 39 free functions. The bar is 30 free functions; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFunctions: blitz_vibey_script::dom::element::attributes packages/blitz-vibey-script/src/dom/element/attributes.rs:11— TooManyFunctions — 31 free functions. The bar is 30 free functions; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) packages/blitz-net/src/lib.rs:236— packages/blitz-net/src/lib.rs:236-256 | packages/blitz-net/src/lib.rs:258-276 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) packages/blitz-html/src/html_sink.rs:221— packages/blitz-html/src/html_sink.rs:221-239 | packages/blitz-html/src/html_sink.rs:243-262 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) packages/blitz-vibey-script/src/runtime/window.rs:171— packages/blitz-vibey-script/src/runtime/window.rs:171-187 | packages/blitz-vibey-script/src/runtime/window.rs:193-208 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) packages/blitz-vibey-script/src/dom/element/scrolling.rs:37— packages/blitz-vibey-script/src/dom/element/scrolling.rs:37-52 | packages/blitz-vibey-script/src/dom/element/scrolling.rs:212-228 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) packages/blitz-vibey-script/src/dom/element/form_controls.rs:225— packages/blitz-vibey-script/src/dom/element/form_controls.rs:225-239 | packages/blitz-vibey-script/src/dom/element/form_controls.rs:245-259 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) packages/blitz-shell/src/convert_events.rs:63— packages/blitz-shell/src/convert_events.rs:63-79 | packages/blitz-shell/src/convert_events.rs:81-95 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) packages/blitz-paint/src/sizing.rs:26— packages/blitz-paint/src/sizing.rs:26-42 | packages/blitz-paint/src/sizing.rs:47-63 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) packages/blitz-vibey-script/src/dom/mod.rs:222— packages/blitz-vibey-script/src/dom/mod.rs:222-238 | packages/blitz-vibey-script/src/runtime/bootstrap.rs:200-221 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/document.rs:182— packages/blitz-vibey-script/src/dom/document.rs:182-192 | packages/blitz-vibey-script/src/dom/document.rs:207-216 | packages/blitz-vibey-script/src/dom/document.rs:218-227 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/node.rs:147— packages/blitz-vibey-script/src/dom/node.rs:147-156 | packages/blitz-vibey-script/src/dom/node.rs:158-167 | packages/blitz-vibey-script/src/dom/node.rs:536-545 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) packages/blitz-dom/src/node/svg.rs:173— packages/blitz-dom/src/node/svg.rs:173-180 | packages/blitz-dom/src/node/svg.rs:184-191 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) packages/blitz-vibey-cdp-server/src/lib.rs:437— packages/blitz-vibey-cdp-server/src/lib.rs:437-444 | packages/blitz-vibey-cdp-server/src/session/mod.rs:423-432 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) packages/blitz-vibey-script/src/dom/document.rs:122— packages/blitz-vibey-script/src/dom/document.rs:122-127 | packages/blitz-vibey-script/src/dom/node.rs:203-208 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) packages/blitz-vibey-cdp-server/src/css.rs:455— packages/blitz-vibey-cdp-server/src/css.rs:455-460 | packages/blitz-vibey-script/src/dom/style.rs:89-96 — These two members are one piece of code written twice and then edited apart: 6 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.
Duplicated block (13 lines × 2) packages/blitz-paint/src/render.rs:1194— packages/blitz-paint/src/render.rs:1194-1206 | packages/blitz-paint/src/render.rs:1239-1251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-paint/src/render.rs:1194` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) packages/stylo_taffy/src/wrapper.rs:565— packages/stylo_taffy/src/wrapper.rs:565-577 | packages/stylo_taffy/src/wrapper.rs:896-908 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) packages/blitz-vibey-script/src/dom/element/form_controls.rs:226— packages/blitz-vibey-script/src/dom/element/form_controls.rs:226-234 | packages/blitz-vibey-script/src/dom/element/form_controls.rs:246-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) packages/blitz/src/lib.rs:88— packages/blitz/src/lib.rs:88-96 | packages/dioxus-native/src/lib.rs:159-167 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `cfg` to `Config` in one and `Vec<Box<dyn Any>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7–8 lines × 2) packages/blitz-html/src/html_sink.rs:228— packages/blitz-html/src/html_sink.rs:228-234 | packages/blitz-html/src/html_sink.rs:250-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-html/src/html_sink.rs:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) packages/blitz-vibey-script/src/document.rs:297— packages/blitz-vibey-script/src/document.rs:297-303 | packages/blitz-vibey-script/src/runtime/window.rs:22-29 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/document.rs:297` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 3) packages/blitz-dom/src/cssom.rs:584— packages/blitz-dom/src/cssom.rs:584-589 | packages/blitz-dom/src/cssom.rs:795-800 | packages/blitz-dom/src/cssom.rs:849-854 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/cssom.rs:584` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) packages/blitz-vibey-script/src/dom/element.rs:392— packages/blitz-vibey-script/src/dom/element.rs:392-397 | packages/blitz-vibey-script/src/dom/element.rs:404-409 | packages/blitz-vibey-script/src/dom/element.rs:416-421 — 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 (14 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:788— packages/blitz-vibey-script/src/geometry.js:788 · packages/blitz-vibey-script/src/geometry.js:960 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (14 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:845— packages/blitz-vibey-script/src/geometry.js:845 · packages/blitz-vibey-script/src/geometry.js:864 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (6 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:717— packages/blitz-vibey-script/src/geometry.js:717 · packages/blitz-vibey-script/src/geometry.js:723 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (6 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:834— packages/blitz-vibey-script/src/geometry.js:834 · packages/blitz-vibey-script/src/geometry.js:1020 — 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.
View::handle_winit_event (cyclomatic 56) packages/blitz-shell/src/window.rs:600— View::handle_winit_event has cyclomatic complexity 56 (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.
EventDriver::handle_ui_event (cyclomatic 34) packages/blitz-dom/src/events/driver.rs:168— EventDriver::handle_ui_event has cyclomatic complexity 34 (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.
browser::toolbar::Toolbar (cyclomatic 31) apps/browser/src/toolbar.rs:36— browser::toolbar::Toolbar has cyclomatic complexity 31 (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.
wpt::main (cyclomatic 30) wpt/runner/src/main.rs:348— wpt::main has cyclomatic complexity 30 (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.
Session::emit_mutations (cyclomatic 28) packages/blitz-vibey-cdp-server/src/session/mutations.rs:20— Session::emit_mutations has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScriptRuntime::dispatch_event_inner (cyclomatic 27) packages/blitz-vibey-script/src/runtime/events.rs:212— ScriptRuntime::dispatch_event_inner has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
geometry.validateAndFixupMatrixInit (cyclomatic 26) packages/blitz-vibey-script/src/geometry.js:647— geometry.validateAndFixupMatrixInit has cyclomatic complexity 26 (threshold 15). Of this number, 24 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.
style.__blitz_wrap_style (cyclomatic 25) packages/blitz-vibey-script/src/runtime/bootstrap/style.js:49— style.__blitz_wrap_style 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.
BlitzApplication::handle_blitz_shell_event (cyclomatic 24) packages/blitz-shell/src/application.rs:73— BlitzApplication::handle_blitz_shell_event has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
escape (cyclomatic 24) packages/blitz-vibey-script/src/runtime/bootstrap/css.js:5— escape has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BlitzDomPainter::render_element (cyclomatic 23) packages/blitz-paint/src/render.rs:435— BlitzDomPainter::render_element 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.
TestResult::print_to (cyclomatic 21) wpt/runner/src/main.rs:250— TestResult::print_to 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.
BlitzBackend::set_attribute_impl (cyclomatic 20) packages/dioxus-native-dom/src/mutation_writer.rs:404— BlitzBackend::set_attribute_impl has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
InnerTextCollector::visit (cyclomatic 16) packages/blitz-vibey-script/src/inner_text.rs:129— InnerTextCollector::visit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
URLSearchParams.constructor (cyclomatic 16) packages/blitz-vibey-script/src/runtime/bootstrap/url_search_params.js:30— URLSearchParams.constructor 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.
TextInputData::apply_keypress_event (cognitive 63) packages/blitz-dom/src/node/text.rs:235— TextInputData::apply_keypress_event has cognitive complexity 63 (threshold 15). Drivers by points: if/else 36 (57 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScriptRuntime::dispatch_event_inner (cognitive 56) packages/blitz-vibey-script/src/runtime/events.rs:212— ScriptRuntime::dispatch_event_inner has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (44 pts), loops 3 (6 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 30). 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.
Session::emit_mutations (cognitive 49) packages/blitz-vibey-cdp-server/src/session/mutations.rs:20— Session::emit_mutations has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (30 pts), match/switch 3 (8 pts), loops 4 (6 pts), boolean chains 5 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
View::handle_winit_event (cognitive 48) packages/blitz-shell/src/window.rs:600— View::handle_winit_event has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 8 (19 pts), boolean chains 4 (nesting depth added 24). 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.
URLSearchParams.constructor (cognitive 35) packages/blitz-vibey-script/src/runtime/bootstrap/url_search_params.js:30— URLSearchParams.constructor has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (6 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validateAndFixupMatrixInit (cognitive 34) packages/blitz-vibey-script/src/geometry.js:647— validateAndFixupMatrixInit has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7, loops 7, ternaries 2 (4 pts) (nesting depth added 9). Of this number, 32 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.
browser::toolbar::Toolbar (cognitive 32) apps/browser/src/toolbar.rs:36— browser::toolbar::Toolbar has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (20 pts), match/switch 8 (9 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
style.__blitz_wrap_style (cognitive 32) packages/blitz-vibey-script/src/runtime/bootstrap/style.js:49— style.__blitz_wrap_style has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 6, ternaries 3 (6 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlitzDomPainter::render_element (cognitive 27) packages/blitz-paint/src/render.rs:435— BlitzDomPainter::render_element has cognitive complexity 27 (threshold 15). Drivers by points: if/else 20 (21 pts), boolean chains 6 (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.
wpt_area_changes.compare (cognitive 24) .github/scripts/wpt_area_changes.py:42— wpt_area_changes.compare has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (8 pts), boolean chains 4 (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.
BlitzApplication::handle_blitz_shell_event (cognitive 21) packages/blitz-shell/src/application.rs:73— BlitzApplication::handle_blitz_shell_event has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
wpt_diff_to_pr.render (cognitive 21) .github/scripts/wpt_diff_to_pr.py:192— wpt_diff_to_pr.render has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InnerTextCollector::visit_inline_layout (cognitive 20) packages/blitz-vibey-script/src/inner_text.rs:187— InnerTextCollector::visit_inline_layout has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 3 (7 pts), boolean chains 2 (nesting depth added 10). 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.
blitz_vibey_script::document::timer_thread_main (cognitive 20) packages/blitz-vibey-script/src/document.rs:369— blitz_vibey_script::document::timer_thread_main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (11 pts), match/switch 3 (8 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlitzBackend::set_attribute_impl (cognitive 20) packages/dioxus-native-dom/src/mutation_writer.rs:404— BlitzBackend::set_attribute_impl has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 9). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TestResult::print_to (cognitive 20) wpt/runner/src/main.rs:250— TestResult::print_to has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 1, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CdpServer::handle_event (cognitive 19) packages/blitz-vibey-cdp-server/src/lib.rs:193— CdpServer::handle_event has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 3 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
escape (cognitive 19) packages/blitz-vibey-script/src/runtime/bootstrap/css.js:5— escape has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (6 pts), loops 1 (nesting depth added 1). 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.
DioxusNativeApplication::handle_dioxus_native_event (cognitive 17) packages/dioxus-native/src/dioxus_application.rs:116— DioxusNativeApplication::handle_dioxus_native_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 2 (7 pts), match/switch 2 (3 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EventDriver::dispatch_hover_change (cognitive 16) packages/blitz-dom/src/events/driver.rs:76— EventDriver::dispatch_hover_change has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScriptDocument::execute_scripts (cognitive 16) packages/blitz-vibey-script/src/document.rs:148— ScriptDocument::execute_scripts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: BaseDocument packages/blitz-dom/src/document.rs:193— TooManyFields — 61 stored fields beside 272 methods. The bar is 30 stored fields; this is 31 over it, 2.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) packages/blitz-traits/src/events.rs:361— packages/blitz-traits/src/events.rs:361-405 | packages/blitz-traits/src/events.rs:407-451 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) packages/blitz-paint/src/render.rs:1255— packages/blitz-paint/src/render.rs:1255-1315 | packages/blitz-paint/src/render.rs:1345-1397 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) packages/blitz-dom/src/mutator.rs:606— packages/blitz-dom/src/mutator.rs:606-631 | packages/blitz-dom/src/mutator.rs:643-670 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) packages/blitz-vibey-script/src/dom/element/selectors.rs:40— packages/blitz-vibey-script/src/dom/element/selectors.rs:40-55 | packages/blitz-vibey-script/src/dom/element/selectors.rs:92-108 | packages/blitz-vibey-script/src/dom/element/selectors.rs:114-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) packages/blitz-dom/src/document.rs:1216— packages/blitz-dom/src/document.rs:1216-1237 | packages/blitz-dom/src/net.rs:150-178 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) packages/blitz-vibey-script/src/dom/element/form_controls.rs:193— packages/blitz-vibey-script/src/dom/element/form_controls.rs:193-203 | packages/blitz-vibey-script/src/dom/element/form_controls.rs:209-219 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) packages/blitz-paint/src/render/border.rs:21— packages/blitz-paint/src/render/border.rs:21-29 | packages/blitz-paint/src/render/border.rs:34-43 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) packages/blitz-vibey-script/src/dom/stylesheet.rs:248— packages/blitz-vibey-script/src/dom/stylesheet.rs:248-260 | packages/blitz-vibey-script/src/dom/stylesheet.rs:262-274 | packages/blitz-vibey-script/src/dom/stylesheet.rs:289-300 | packages/blitz-vibey-script/src/dom/stylesheet.rs:302-315 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) packages/blitz-vibey-script/src/dom/element.rs:443— packages/blitz-vibey-script/src/dom/element.rs:443-452 | packages/blitz-vibey-script/src/dom/node.rs:136-145 | packages/blitz-vibey-script/src/dom/stylesheet.rs:96-104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/element/scrolling.rs:141— packages/blitz-vibey-script/src/dom/element/scrolling.rs:141-150 | packages/blitz-vibey-script/src/dom/element/scrolling.rs:156-165 | packages/blitz-vibey-script/src/dom/element/scrolling.rs:171-185 | packages/blitz-vibey-script/src/dom/element/scrolling.rs:191-204 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) packages/blitz-vibey-script/src/dom/element.rs:391— packages/blitz-vibey-script/src/dom/element.rs:391-401 | packages/blitz-vibey-script/src/dom/element.rs:403-413 | packages/blitz-vibey-script/src/dom/element.rs:415-425 | packages/blitz-vibey-script/src/dom/element/markup.rs:120-129 | packages/blitz-vibey-script/src/dom/node.rs:216-225 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs:257— packages/blitz-vibey-script/src/dom/element/attributes.rs:257-267 | packages/blitz-vibey-script/src/dom/element/form_controls.rs:56-66 | packages/blitz-vibey-script/src/dom/element/form_controls.rs:122-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs:63— packages/blitz-vibey-script/src/dom/element/attributes.rs:63-72 | packages/blitz-vibey-script/src/dom/element/attributes.rs:148-155 | packages/blitz-vibey-script/src/dom/element/attributes.rs:161-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) packages/blitz-vibey-script/src/dom/element/geometry.rs:20— packages/blitz-vibey-script/src/dom/element/geometry.rs:20-27 | packages/blitz-vibey-script/src/dom/element/geometry.rs:37-44 | packages/blitz-vibey-script/src/dom/element/markup.rs:12-22 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) packages/blitz-dom/src/scrolling.rs:371— packages/blitz-dom/src/scrolling.rs:371-385 | packages/blitz-dom/src/scrolling.rs:392-404 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 8+ corresponding lines) · ×1
Edited copies of one member (8 members, 8+ corresponding lines) packages/blitz-vibey-script/src/dom/node.rs:273— packages/blitz-vibey-script/src/dom/node.rs:273-280 | packages/blitz-vibey-script/src/dom/node.rs:344-354 | packages/blitz-vibey-script/src/dom/node.rs:474-481 | packages/blitz-vibey-script/src/dom/node.rs:487-494 | packages/blitz-vibey-script/src/dom/node.rs:500-507 | packages/blitz-vibey-script/src/dom/node.rs:509-516 | packages/blitz-vibey-script/src/dom/node.rs:518-525 | packages/blitz-vibey-script/src/dom/node.rs:527-534 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) packages/blitz-vibey-script/src/dom/element/attributes.rs:28— packages/blitz-vibey-script/src/dom/element/attributes.rs:28-31 | packages/blitz-vibey-script/src/dom/style.rs:98-102 — These two members are one piece of code written twice and then edited apart: 4 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.
Duplicated block (28 lines × 2) packages/blitz-dom/src/layout/inline/layout.rs:226— packages/blitz-dom/src/layout/inline/layout.rs:226-253 | packages/blitz-dom/src/layout/inline/layout.rs:407-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14–21 lines × 2) packages/blitz-dom/src/mutator.rs:368— packages/blitz-dom/src/mutator.rs:368-388 | packages/blitz-dom/src/mutator.rs:518-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/mutator.rs:368` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) packages/blitz-paint/src/render/background.rs:906— packages/blitz-paint/src/render/background.rs:906-922 | packages/blitz-paint/src/render/background.rs:959-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-paint/src/render/background.rs:906` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) packages/blitz-dom/src/node/element.rs:729— packages/blitz-dom/src/node/element.rs:729-744 | packages/blitz-dom/src/node/element.rs:796-810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/node/element.rs:729` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11–13 lines × 2) packages/blitz-dom/src/mutator.rs:620— packages/blitz-dom/src/mutator.rs:620-630 | packages/blitz-dom/src/mutator.rs:655-667 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/mutator.rs:620` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/blitz-dom/src/mutator.rs:654` calls `is_in_document` and `packages/blitz-dom/src/mutator.rs:619` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–12 lines × 2) packages/blitz-dom/src/node/element.rs:340— packages/blitz-dom/src/node/element.rs:340-351 | packages/blitz-dom/src/node/element.rs:455-465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/node/element.rs:340` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) packages/blitz-net/src/lib.rs:243— packages/blitz-net/src/lib.rs:243-252 | packages/blitz-net/src/lib.rs:264-275 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/blitz-net/src/lib.rs:242` calls `spawn` and `packages/blitz-net/src/lib.rs:263` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–12 lines × 2) packages/blitz-vibey-cdp-server/src/css.rs:542— packages/blitz-vibey-cdp-server/src/css.rs:542-553 | packages/blitz-vibey-cdp-server/src/dom.rs:125-131 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) apps/browser/src/toolbar.rs:229— apps/browser/src/toolbar.rs:229-238 | apps/browser/src/toolbar.rs:251-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/browser/src/toolbar.rs:229` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8–10 lines × 2) packages/blitz-dom/src/mutator.rs:618— packages/blitz-dom/src/mutator.rs:618-625 | packages/blitz-dom/src/mutator.rs:896-905 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-dom/src/mutator.rs:618` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 3) packages/blitz-vibey-cdp-server/src/style_sheets.rs:175— packages/blitz-vibey-cdp-server/src/style_sheets.rs:175-182 | packages/blitz-vibey-cdp-server/src/style_sheets.rs:254-261 | packages/blitz-vibey-cdp-server/src/style_sheets.rs:318-325 — 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–7 lines × 2) packages/blitz-vibey-script/src/dom/style.rs:155— packages/blitz-vibey-script/src/dom/style.rs:155-161 | packages/blitz-vibey-script/src/dom/style.rs:176-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 4) packages/blitz-vibey-script/src/dom/element.rs:447— packages/blitz-vibey-script/src/dom/element.rs:447-452 | packages/blitz-vibey-script/src/dom/element/selectors.rs:50-55 | packages/blitz-vibey-script/src/dom/element/selectors.rs:103-108 | packages/blitz-vibey-script/src/dom/element/selectors.rs:128-133 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/element.rs:447` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) packages/blitz-vibey-script/src/dom/element/scrolling.rs:143— packages/blitz-vibey-script/src/dom/element/scrolling.rs:143-147 | packages/blitz-vibey-script/src/dom/element/scrolling.rs:158-162 | packages/blitz-vibey-script/src/dom/element/scrolling.rs:173-179 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-script/src/dom/element/scrolling.rs:173` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 6) packages/blitz-vibey-cdp-server/src/session/dom.rs:110— packages/blitz-vibey-cdp-server/src/session/dom.rs:110-118 | packages/blitz-vibey-cdp-server/src/session/dom.rs:126-137 | packages/blitz-vibey-cdp-server/src/session/dom.rs:157-165 | packages/blitz-vibey-cdp-server/src/session/dom.rs:174-182 | packages/blitz-vibey-cdp-server/src/session/dom.rs:187-198 | packages/blitz-vibey-cdp-server/src/session/dom.rs:221-230 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/blitz-vibey-cdp-server/src/session/dom.rs:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Type Safety — 0 typed · 11 plain JS — the untyped files are packages/blitz-vibey-script/src/geometry.js, packages/blitz-vibey-script/src/runtime/bootstrap/css.js, packages/blitz-vibey-script/src/runtime/bootstrap/dom_exception.js, packages/blitz-vibey-script/src/runtime/bootstrap/fetch.js, packages/blitz-vibey-script/src/runtime/bootstrap/fonts.js, packages/blitz-vibey-script/src/runtime/bootstrap/interfaces.js (+5 more).
R10 · Code Duplication· Duplicated block with local edits (98 matched lines × 2 locations) · ×1
Duplicated block with local edits (98 matched lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:81— packages/blitz-vibey-script/src/geometry.js:81 · packages/blitz-vibey-script/src/geometry.js:204 — the two spans are one implementation copied and then locally edited — 604 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (11 lines × 2 locations) packages/blitz-vibey-script/src/geometry.js:385— packages/blitz-vibey-script/src/geometry.js:385 · packages/blitz-vibey-script/src/runtime/bootstrap/style.js:100 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function validateAndFixupMatrixInit (cyclomatic 24, cognitive 32) packages/blitz-vibey-script/src/geometry.js:647— validateAndFixupMatrixInit has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 escape (cyclomatic 24, cognitive 19) packages/blitz-vibey-script/src/runtime/bootstrap/css.js:5— escape has cyclomatic complexity 24 and cognitive complexity 19; 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 constructor (cyclomatic 16, cognitive 35) packages/blitz-vibey-script/src/runtime/bootstrap/url_search_params.js:30— constructor has cyclomatic complexity 16 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 11) packages/blitz-vibey-script/src/runtime/bootstrap/fetch.js:73— (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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 replaceGeometry (cyclomatic 11, cognitive 12) packages/blitz-vibey-script/src/geometry.js:1188— replaceGeometry has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/blitz-vibey-script/src/geometry.js · ×1
packages/blitz-vibey-script/src/geometry.js: 1273 lines of code packages/blitz-vibey-script/src/geometry.js:1— packages/blitz-vibey-script/src/geometry.js has 1273 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js · ×1
packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js: 531 lines of code packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js:1— packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js has 531 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Interpolated log message defeats structured logging packages/dioxus-native/src/assets.rs:48— `trace!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/dioxus-native/src/assets.rs:53— `warn!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/dioxus-native/src/assets.rs:60— `warn!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/dioxus-native/src/link_handler.rs:15— `error!` at line 15 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-script/src/document.rs:266— `error!` at line 266 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-script/src/runtime/events.rs:21— `error!` at line 21 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/frontend.rs:61— `warn!` at line 61 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/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 packages/blitz-vibey-cdp-server/src/lib.rs:214— `debug!` at line 214 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/lib.rs:215— `trace!` at line 215 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/lib.rs:404— `trace!` at line 404 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/transport.rs:32— `info!` at line 32 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/transport.rs:43— `warn!` at line 43 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/transport.rs:178— `debug!` 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: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/transport.rs:224— `warn!` at line 224 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/transport.rs:228— `warn!` 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: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-vibey-cdp-server/src/session/mod.rs:197— `debug!` at line 197 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-shell/src/application.rs:85— `error!` at line 85 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-shell/src/convert_events.rs:75— `error!` at line 75 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-shell/src/convert_events.rs:91— `error!` at line 91 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-shell/src/convert_events.rs:109— `error!` at line 109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-shell/src/convert_events.rs:137— `error!` at line 137 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-shell/src/window.rs:867— `error!` at line 867 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-net/src/lib.rs:141— `error!` at line 141 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging packages/blitz-html/src/html_sink.rs:184— `error!` at line 184 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Orphaned file apps/browser/persistence/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 apps/browser/src/browser_history.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/blitz-dom/src/selection.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 apps/browser/src/favicon.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.
Duplicated predicate packages/blitz-vibey-script/src/runtime/bootstrap/style.js:20— `typeof prop === "string" && /^\d+$/.test(prop)` appears character-identically in 2 files — packages/blitz-vibey-script/src/runtime/bootstrap/style.js, packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/blitz-dom/src/layout/inline/layout.rs:321— `display.outside() == DisplayOutside::Inline && display.inside() == DisplayInside::Flow` appears character-identically in 2 files — packages/blitz-dom/src/layout/inline/layout.rs, packages/blitz-dom/src/node/node.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 packages/blitz-dom/src/layout/inline/layout.rs:439— `overflow.x.is_scroll_container() || overflow.y.is_scroll_container()` appears character-identically in 4 files — packages/blitz-dom/src/layout/inline/layout.rs, packages/blitz-dom/src/layout/replaced.rs, packages/blitz-dom/src/layout/writing_mode.rs, packages/blitz-dom/src/node/node.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.
No ADRs found wpt/runner/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `wpt/runner/src/main.rs` makes this repository a deployable product (line 1).
redundant comment packages/blitz-vibey-script/src/runtime/bootstrap/stylesheets.js:128— "`CSSStyleDeclaration` for the declarations of a rule (`CSSStyleRule.style`, ...)" repeats the code it sits on: 4 of its 5 words (style, declaration, declarations, rule) are already in `class RuleStyleDeclaration`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 20 project(s) overshoot their size bounds, lowering Project Cohesion to 9.0/10. The most over is `packages/blitz-dom` (28848 LoC, 130 module-visible types across 6 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 — 4 of 171 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; 171 of the 220 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: apps/browser/persistence/src/lib.rs, apps/browser/src/browser_history.rs, packages/blitz-dom/src/selection.rs, apps/browser/src/favicon.rs. 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.
Silent fallback default on Err packages/blitz-dom/src/resolved_style.rs:210— `style_attr_get_property` turns every `Err` into `String::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Outdated: accesskit — `accesskit` is locked at 0.25.1 but 0.25.2 is the current stable release on crates.io, and it already satisfies the `"0.25"` requirement declared in packages/accesskit_xplat/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p accesskit` and commit the updated REDACTED.
Outdated: accesskit_android — `accesskit_android` is locked at 0.9.0 but 0.9.1 is the current stable release on crates.io, and it already satisfies the `"0.9.0"` requirement declared in packages/accesskit_xplat/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p accesskit_android` and commit the updated REDACTED.
Outdated: accesskit_macos — `accesskit_macos` is locked at 0.27.1 but 0.27.2 is the current stable release on crates.io, and it already satisfies the `"0.27.0"` requirement declared in packages/accesskit_xplat/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p accesskit_macos` and commit the updated REDACTED.
Outdated: accesskit_unix — `accesskit_unix` is locked at 0.24.0 but 0.24.1 is the current stable release on crates.io, and it already satisfies the `"0.24.0"` requirement declared in packages/accesskit_xplat/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p accesskit_unix` and commit the updated REDACTED.
Outdated: accesskit_windows — `accesskit_windows` is locked at 0.35.1 but 0.35.2 is the current stable release on crates.io, and it already satisfies the `"0.35.0"` requirement declared in packages/accesskit_xplat/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p accesskit_windows` and commit the updated REDACTED.
Outdated: icu_casemap — `icu_casemap` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in packages/blitz-dom/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_casemap` and commit the updated REDACTED.
Outdated: icu_locale_core — `icu_locale_core` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in packages/blitz-dom/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_locale_core` and commit the updated REDACTED.
Outdated: icu_properties — `icu_properties` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in packages/blitz-dom/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_properties` and commit the updated REDACTED.
Outdated: icu_segmenter — `icu_segmenter` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in packages/blitz-dom/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_segmenter` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.34 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in packages/blitz-vibey-script/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.2 is the current stable release on crates.io, and it already satisfies the `"8.0.0"` requirement declared in apps/readme/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: pulldown-cmark — `pulldown-cmark` is locked at 0.13.4 but 0.13.6 is the current stable release on crates.io, and it already satisfies the `"0.13"` requirement declared in apps/readme/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p pulldown-cmark` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in packages/blitz-vibey-cdp-server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.16.2 but 1.16.5 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in packages/blitz-dom/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: smol_str — `smol_str` is locked at 0.3.6 but 0.3.7 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in packages/blitz-test-harness/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smol_str` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.2 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.42"` requirement declared in apps/browser/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: wasm-bindgen — `wasm-bindgen` is locked at 0.2.129 but 0.2.130 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in examples/seven_guis/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen` and commit the updated REDACTED.
Outdated: wasm-bindgen-futures — `wasm-bindgen-futures` is locked at 0.4.79 but 0.4.80 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in packages/blitz-net/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen-futures` and commit the updated REDACTED.
Outdated: web-sys — `web-sys` is locked at 0.3.106 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.98"` requirement declared in examples/wasm_hello/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p web-sys` and commit the updated REDACTED.
Outdated: webbrowser — `webbrowser` is locked at 1.2.4 but 1.2.7 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in apps/browser/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p webbrowser` and commit the updated REDACTED.
Outdated: wgpu — `wgpu` is locked at 30.0.1 but 30.0.2 is the current stable release on crates.io, and it already satisfies the `"30"` requirement declared in examples/wgpu_texture/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wgpu` and commit the updated REDACTED.
Outdated: wuff — `wuff` is locked at 0.2.9 but 0.2.10 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in packages/blitz-dom/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wuff` and commit the updated REDACTED.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dbe7-68ad-7436-92d3-cf2de9d6c2ca · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 43 · Warnings: 535 · Recommendations: 56 · Info: 22 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 21:12 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.