blitz — Watchdog Audit

Executive summary

Preview (pre-1.0). This repo hasn't declared a stable release, so it's judged against a relaxed, pre-production bar.

The system holds a strong overall standing at 74%, indicating a healthy asset that is largely stable but carries specific operational risks. With nearly 51,000 lines of production code and a modest rebuild cost of roughly €95,000, the platform represents significant value. The architecture is exceptionally robust, and the domain logic is mature, suggesting that the core business capabilities are well-protected and easy to maintain. However, the operational readiness lags behind the code quality, creating a gap between how well the system is built and how safely it is run.

The primary risk lies in observability gaps. While the code itself is clean, the lack of structured logging in several runnable modules means that when issues arise in production, diagnosing the root cause will be slow and difficult. This directly threatens delivery speed and increases the cost of fixing defects, as engineers will spend more time investigating than resolving. Without full visibility, the team cannot reliably predict system behavior under load or during failures, leaving the business exposed to extended outages or delayed incident response.

A secondary concern involves dependency and release governance. The current setup lacks automated dependency updates and clear release protections. This creates a security exposure and reliability risk, as outdated libraries may contain unpatched vulnerabilities, and the release process lacks visible safeguards to prevent bad builds from reaching users. While the architecture prevents ripple effects from code changes, the operational processes do not provide the same level of control, potentially leading to security incidents or unstable releases that erode customer trust.

On the positive side, the high scores in architecture and event sourcing indicate a well-designed system that is resilient to change. The low boilerplate content suggests that the codebase is focused on real business logic rather than administrative overhead. To maximize leverage, the team should first extend structured logging to all runnable modules. This single action will provide the visibility needed to manage the existing risks effectively, turning a partially measured picture into a fully controlled operational environment.

Code Health 81% Strong Architecture 96% ★ Exemplary Maturity 75% Strong Readiness 68% Strong Security 74% Adequate · gated by D36 Event Sourcing 100% ★ Exemplary Performance 100% ★ Exemplary

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Readiness 68% · 46% weightSecurity 74% · 25% weightMaturity 75% · 14% weightCode Health 81% · 8% weightArchitecture 96% · 4% weightEvent Sourcing 100% · 2% weightPerformance 100% · 1% weight

Raise Readiness 68 → 70 (the Healthy floor) ⇒ headline 74 → ~75.

Code composition — where the lines go

Tests 100%

New since the last scan (36+)

36 finding(s) are new versus the previous scan (2026-09-14) — surfaced by this scheduled scan itself, no pull request required.

D1 · BaseDocument::dispatch_child_layout (cyclomatic 32) packages/blitz-dom/src/layout/mod.rs
D1 · geometry.validateAndFixupMatrixInit (cyclomatic 26) packages/blitz-vibey-script/src/geometry.js
D1 · Node::write_outer_html_in_style (cyclomatic 24) packages/blitz-dom/src/node/serialize.rs
D1 · BaseDocument::propagate_damage_flags (cyclomatic 16) packages/blitz-dom/src/layout/damage.rs
D1 · BaseDocument::build_paint_tree_impl (cyclomatic 16) packages/blitz-dom/src/layout/paint_tree.rs
D2 · BaseDocument::dispatch_child_layout (cognitive 53) packages/blitz-dom/src/layout/mod.rs
D2 · Node::write_outer_html_in_style (cognitive 46) packages/blitz-dom/src/node/serialize.rs
D2 · BaseDocument::build_paint_tree_impl (cognitive 30) packages/blitz-dom/src/layout/paint_tree.rs
D2 · geometry.validateAndFixupMatrixInit (cognitive 30) packages/blitz-vibey-script/src/geometry.js
D2 · BaseDocument::resolve_transforms (cognitive 20) packages/blitz-dom/src/resolve.rs
D3 · MethodTooLong: BaseDocument.dispatch_child_layout packages/blitz-dom/src/layout/mod.rs
D3 · FunctionTooLong: blitz_paint::text::flush_line_decorations packages/blitz-paint/src/text.rs
D4 · Duplicated block (14–15 lines × 2) packages/blitz-dom/src/layout/construct.rs
D4 · Duplicated block (13 lines × 2) packages/blitz-paint/src/render.rs
D4 · Duplicated block (12 lines × 2) packages/blitz-dom/src/node/node.rs
D4 · Duplicated block (10–11 lines × 2) packages/blitz-dom/src/node/element.rs
D4 · Duplicated block (8 lines × 2) packages/blitz-dom/src/font_metrics.rs
D5 · Off the main sequence: browser-persistence
D5 · Off the main sequence: debug_timer
D5 · Off the main sequence: stylo_taffy
D5 · Off the main sequence: accesskit_xplat
D5 · Off the main sequence: blitz-traits
D5 · Off the main sequence: blitz-html
D5 · Off the main sequence: blitz-dom
D6 · Low cohesion: BlitzShellProvider (LCOM4 4) packages/blitz-shell/src/lib.rs
D17 · TodoComment packages/blitz-dom/src/stylo_to_parley.rs
D17 · TodoComment packages/blitz-dom/src/stylo_to_parley.rs
D22 · Ambiguous return type for mutator methods. `get_node_mut` returns `Node` (likely a value or wrapper) rather than a mutable reference `&mut Node` or a guard type, making it unclear if the mutation is immediate or deferred. This contrasts with `Document.inner_mut()` which returns a `DocGuardMut`.
D22 · Redundant getter methods. `get_viewport()` and `viewport()` perform the same operation (reading the viewport). Additionally, `viewport_mut()` returns a specific `ViewportMut` type, while other getters return the value directly, creating an inconsistent pattern for mutable access.
D22 · Confusing naming and return types for root access. `root_node` and `root_element` likely refer to the same underlying node (the `<html>` or document root), but one is 'try' (implying it might fail) and the other doesn't. Furthermore, `root_node_mut` returns `Node` instead of a mutable guard/reference, inconsistent with the `inner_mut` pattern.
D22 · Inconsistent scroll API design. `scroll_to` and `scroll_by` take a `NodeId` and `ScrollBehavior`, while `scroll_node_by` takes a callback `dispatch_event` and no behavior enum. `scroll_viewport_by` lacks behavior. The presence of `_has_changed` variants suggests a need for atomic check-and-set operations that are not consistently applied to all scroll methods.
D22 · Redundant 'raw' methods. `query_selector_raw` and `query_selector_all_raw` accept a pre-parsed `SelectorList`, while the non-raw versions accept a string. This duplicates the parsing logic externally. If the raw versions are for performance, they should be clearly documented as such, but the naming convention is inconsistent with standard library patterns (which often use `parse` separately).
D22 · Duplicate functionality across types. `BaseDocument` and `DocumentMutator` both expose `set_style_property` and `remove_style_property`. Since `DocumentMutator` is obtained via `BaseDocument.mutate()`, it is unclear if calling these on `BaseDocument` directly is valid or if it bypasses the mutation tracking system.
D29 · REDACTED
D29 · REDACTED
D30 · REDACTED

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €32,000–€160,000

Cost to rebuild	€32,000–€160,000 (0.3–1.0 person-years (528–1,674 h), ~1–2 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	1.1× (at 74% quality) — the last 20% of quality is most of the work
Size & shape	Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~0.7 person-years of build effort (about ~€95,000 to rebuild). Its weakest lens is Readiness at 68% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 1.1× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.

+4.9 pts · Medium effort · Observability

Enable Dependabot/Renovate or a dependency-review gate.

+4.9 pts · Medium effort · Security & performance tooling

The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download it.

+4.9 pts · Medium effort · Deployment & Rollback

Diagnosis — what's actually going on

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

156 modules, 306 dependencies. 2 dependency cycles across 20 modules, marked above the diagonal.

Showing the 40 most-connected modules; 116 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 blitz_paint.kurbo_css	2 blitz_traits.net	3 blitz_traits.node_id	4 blitz_traits.shell	5 blitz_dom.config	6 blitz_dom.node.scrollbar	7 blitz_dom.tree	8 blitz_shell.event	9 blitz_traits.events	10 blitz_traits.navigation	11 blitz_dom.layout.paint_tree	12 blitz_dom.node.text	14 blitz_dom.node.element	15 blitz_dom.node.node	16 blitz_dom.layout.construct	17 blitz_dom.mutator	18 blitz_dom.util	19 blitz_dom.scrolling	21 blitz_dom.events.pointer	22 blitz_dom.document	23 blitz_test_harness.inspect	24 blitz_vibey_script.state	26 accesskit_xplat	27 blitz_paint.kurbo_css.css_box	30 blitz_vibey_script.runtime	32 blitz_shell.accessibility	33 blitz_vibey_script.document	36 blitz_shell.window	37 wpt.test_runners	38 blitz_shell.application	39 wpt
1 blitz_paint.kurbo_css
2 blitz_traits.net
3 blitz_traits.node_id
4 blitz_traits.shell
5 blitz_dom.config		1		1
6 blitz_dom.node.scrollbar			1
7 blitz_dom.tree			2											1			1
8 blitz_shell.event		1
9 blitz_traits.events			2														2
10 blitz_traits.navigation		2
11 blitz_dom.layout.paint_tree			3				3							1			2				1
12 blitz_dom.node.text			1						2
13 browser.document_loader		3			1
14 blitz_dom.node.element			1									2					1
15 blitz_dom.node.node			1			2	1		3		1		3				1
16 blitz_dom.layout.construct			5				1					1		2						2
17 blitz_dom.mutator			1	1									1	1						2
18 blitz_dom.util														1
19 blitz_dom.scrolling			1														1
20 blitz_html.html_sink			2		1											2
21 blitz_dom.events.pointer			2			1			3									1		1
22 blitz_dom.document		2	1	1	2	1	1		3			1	2	2	1	2	2	6	1		1
23 blitz_test_harness.inspect														1						1
24 blitz_vibey_script.state																				1
25 dioxus_native_dom.events		1	2						6				1	1				1		1
26 accesskit_xplat																					1
27 blitz_paint.kurbo_css.css_box	4																2				1
28 blitz_test_harness.harness			1	1	1				3											2	1
29 blitz_vibey_script.dom.element			1														1	2		1		1
30 blitz_vibey_script.runtime			1						2											1		3
31 blitz_paint.render	1		1			1						1	3	2			1			1	3			2
32 blitz_shell.accessibility								2												1			3
33 blitz_vibey_script.document					1				2											4					1
34 dioxus_native_dom.dioxus_document			1		1				3					1						4			1
35 blitz_dom.events.driver			1						9								1						1			1
36 blitz_shell.window								1	4														1			1
37 wpt.test_runners													1	1						1							1				2
38 blitz_shell.application								2															1					2
39 wpt				1																									1
40 rdme.readme_application								1		1													1					2		1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 81% · Strong ·

The Good

D3 · Rust God Classes 7.2 D4 · Rust Code Duplication 9.6 D17 · Rust Explicit Debt 9.5 X29 · Repo Per-element action decided by a fixed element 10.0

The Bad

D1 · Rust Cyclomatic Complexity 6.0 D2 · Rust Cognitive Complexity 5.5

At a glance — Architecture · 96% · Exemplary ·

The Good

D5 · Rust Coupling 7.1 D6 · Rust Cohesion (LCOM4) 9.8 D26 · Rust Project Cohesion 8.9 D35 · Rust Change Coupling 9.7 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

The Ugly

D22 · Rust Internal API Consistency 4.0

At a glance — Maturity · 75% · Strong ·

The Good

D15 · Rust Churn × Complexity Hotspots 8.7 D19 · Rust Documentation Quality 9.0 D21 · Rust Naming Consistency 10.0 D34 · Rust Knowledge Freshness 9.9 M1 · Repo Documentation (README) 7.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M2 · Repo Architecture documentation 5.0

The Ugly

D20 · Rust ADR Quality 0.0

At a glance — Readiness · 68% · Strong ·

The Good

D9 · Rust Test Distribution 10.0 D12 · Rust Dependency Hygiene 9.8 D13 · Rust REDACTED Scanning 10.0 D14 · Rust License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 6.8 P6 · Repo Release Hygiene 10.0

The Bad

P4 · Repo Deployment & Rollback 5.0

The Ugly

P3 · Repo Security & performance tooling 4.0

At a glance — Security · 74% · Adequate · gated by D36 ·

The Good

D28 · Rust Secrets (history) 8.0 D30 · Rust Dependency Vulnerabilities 9.2 D43 · Rust Malicious Dependencies 10.0 D44 · Rust Platform End-of-Life 10.0

The Ugly

D29 · Rust Static Analysis (SAST) 4.8 D36 · Rust Supply-chain Provenance & Signing 2.5

At a glance — Event Sourcing · 100% · Exemplary ·

The Good

ES1 · Repo Fold determinism 10.0 ES2 · Repo Immutable events 10.0

At a glance — Performance · 100% · Exemplary ·

The Good

PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A03:2021 — Injection	47	High / Critical
A06:2021 — Vulnerable & Outdated Components	4	Medium
A02:2021 — Cryptographic Failures	2	High / Critical

Roadmap

First, extend structured logging across all runnable modules to ensure full production diagnosability, and enable automated dependency review tools to strengthen security and performance. Next, verify that deployment protection rules are properly configured to allow for safe rollbacks and controlled releases. Finally, address the missing architectural decision record and add a quick-start section to the root README to improve onboarding for new contributors.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.	+4.9 pts	Medium	Observability
Enable Dependabot/Renovate or a dependency-review gate.	+4.9 pts	Medium	Security & performance tooling
The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download it.	+4.9 pts	Medium	Deployment & Rollback
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+2.1 pts	Low	ADR Quality
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.	+2.1 pts	Medium	Documentation (README)
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).	+2.1 pts	Medium	Architecture documentation
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).	+0.6 pts	Low	Static Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED.	+0.5 pts	Low	Secrets (history)

File quality

Per-file score 0–10 — a quality signature. Of 88 files carrying findings, judged against the Preview bar: 1% slop · 40% mixed · 59% near-clean.

File	Score	Band	Worst signal
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
packages/blitz-dom/src/node/text.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/layout/inline.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-shell/src/window.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/events/mod.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/node/node.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/layout/mod.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/events/pointer.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/mutator.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-paint/src/render/border.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/layout/construct.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/form.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-dom/src/document.rs	6.0	Mixed	Explicit Debt: TodoComment
apps/browser/src/toolbar.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-paint/src/render.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/blitz-paint/src/render/background.rs	6.0	Mixed	Explicit Debt: TodoComment
packages/dioxus-native-dom/src/mutation_writer.rs	6.0	Mixed	Explicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 49

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 — 401

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 — 15

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 39

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 39 of 44 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 44 dimensions across the health lenses

D1D2D3D4D5D6D9D12D13D14D15D17D19D20D21D22D26D28D29D30D34D35D36D43D44AX10AX3AX4AX8AX9ES1ES2M1M2M3M4P1P10P2P3P4P6PF3X29

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, 435 of 465 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0f321-6145-7b94-804a-1aafd2fc7117.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 84 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
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 (47 contributor(s) across 1976 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 46 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.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and no container it models, or knows cannot hold a captive, was found in this repository's source, 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.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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, or an npm dev script. None was found, 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. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust and Go), and its Kotlin source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (5): D19, D21, D22, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

47 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TextInputData::apply_apple_standard_keybinding at 100. A further 16 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_shell::convert_events::winit_key_to_kbt_key at 311 — they are counted neither in the figure above nor in this dimension's score. 7 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-shell/src/convert_events.rs (blitz_shell::convert_events::winit_key_to_kbt_key at 311), 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-paint/src/kurbo_css/css_box.rs (CssBox::partial_corner_arc at 22), and 2 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.

blitz_dom::accessibility::role_from_element_data (cyclomatic 64) · ×14packages/blitz-dom/src/accessibility.rs:165

BaseDocument::resolved_style_value (cyclomatic 60) · ×9packages/blitz-dom/src/resolved_style.rs:341

blitz_paint::gradient::resolve_color_stops (cyclomatic 24) · ×3packages/blitz-paint/src/gradient.rs:331

TextInputData::apply_apple_standard_keybinding (cyclomatic 100) · ×2packages/blitz-dom/src/node/text.rs:365

Node::hit_inner (cyclomatic 34) · ×2packages/blitz-dom/src/node/node.rs:1295

+ 14 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 14 blitz_dom finding(s) in Cyclomatic Complexity — start with pointer.rs (3), construct.rs (2), table.rs (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 9 BaseDocument finding(s) in Cyclomatic Complexity — start with document.rs (2), resolved_style.rs, inline.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 3 blitz_paint finding(s) in Cyclomatic Complexity — start with gradient.rs (2), background.rs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity5.5 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.5 / 10 · rule-coverage 100% · ceiling Prevented

60 method(s) exceeded the cognitive complexity threshold of 15; the worst was BaseDocument::compute_inline_layout_inner at 129.

blitz_dom::events::pointer::handle_pointermove (cognitive 77) · ×18packages/blitz-dom/src/events/pointer.rs:206

BaseDocument::compute_inline_layout_inner (cognitive 129) · ×12packages/blitz-dom/src/layout/inline.rs:182

blitz_paint::gradient::resolve_color_stops (cognitive 56) · ×6packages/blitz-paint/src/gradient.rs:331

ElementCx::draw_border (cognitive 32) · ×4packages/blitz-paint/src/render/border.rs:149

DocumentMutator::set_attribute (cognitive 35) · ×3packages/blitz-dom/src/mutator.rs:268

+ 16 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 18 blitz_dom finding(s) in Cognitive Complexity — start with pointer.rs (4), construct.rs (4), table.rs (3). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 12 BaseDocument finding(s) in Cognitive Complexity — start with traversal.rs (2), document.rs (2), resolve.rs (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 6 blitz_paint finding(s) in Cognitive Complexity — start with text.rs (3), gradient.rs (2), background.rs. — One of this dimension's main actionable groups (6 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God 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.

Maturity: Documented → Verified → Prevented · effective 7.2 / 10 · rule-coverage 100% · ceiling Prevented

59 god class(es) detected.

FileTooLong: src/runtime.rs · ×19packages/blitz-vibey-script/src/runtime.rs

FunctionTooLong: blitz_shell::convert_events::winit_key_to_kbt_key · ×15packages/blitz-shell/src/convert_events.rs:404

MethodTooLong: BaseDocument.compute_inline_layout_inner · ×12packages/blitz-dom/src/layout/inline.rs:182

ClassTooLong: BaseDocument · ×6packages/blitz-dom/src/document.rs:193

TooManyMethods: BaseDocument · ×5packages/blitz-dom/src/document.rs:193

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 19 FileTooLong finding(s) in God Classes — start with element.rs (2), runtime.rs, document.rs. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 15 FunctionTooLong finding(s) in God Classes — start with pointer.rs (3), convert_events.rs (2), construct.rs (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 12 MethodTooLong finding(s) in God Classes — start with text.rs (2), inline.rs, mod.rs. — One of this dimension's main actionable groups (12 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication9.6 / 10Stronggated by 45 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Verified

45 duplicated block group(s) detected.

Duplicated block (8 lines × 2) · ×6packages/blitz-dom/src/cssom.rs:559

Duplicated block (6 lines × 2) · ×6packages/blitz-vibey-script/src/dom/element.rs:252

Duplicated block (9 lines × 2) · ×4packages/blitz-dom/src/layout/construct.rs:977

Duplicated block (5 lines × 2) · ×4packages/blitz-vibey-script/src/runtime.rs:2154

Duplicated block (17 lines × 2) · ×2packages/blitz-paint/src/render/background.rs:819

+ 17 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with cssom.rs (2), pointer.rs, font_metrics.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with element.rs (2), document.rs (2), runtime.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with construct.rs, element.rs, document.rs. — One of this dimension's main actionable groups (4 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D5 · Coupling7.1 / 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.

Maturity: Documented → Verified → Prevented · effective 7.1 / 10 · rule-coverage 100% · ceiling Prevented

19 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 16 of the 19 (the rest declare no modelled class or interface, export only macros, 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).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

1 of 69 classes have LCOM4 above 3.

Low cohesion: BlitzShellProvider (LCOM4 4)packages/blitz-shell/src/lib.rs:87

What to do

Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

405 test methods: 119 unit, 286 integration, 0 BDD, 0 e2e. The Rust suite contributes 405 `#[test]` function(s) across 84 file(s) declaring at least one; its unit/integration split is Cargo's own — 61 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.

Inverted test pyramid

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D12 · Dependency Hygiene9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

5 outdated, 0 yanked direct Cargo dependencies. 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 · ×5

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 933 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 7 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots8.7 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/blitz-dom/src/layout/inline.rs (31×56=1736); packages/blitz-dom/src/node/node.rs (41×34=1394); packages/blitz-dom/src/document.rs (49×24=1176)

Hotspot: packages/blitz-dom/src/layout/inline.rs · ×23packages/blitz-dom/src/layout/inline.rs:182

What to do

Resolve the 23 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), inline.rs, node.rs. — One of this dimension's main actionable groups (23 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt9.5 / 10Stronggated by 145 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Prevented

145 deducted task-comment markers across 50948 LoC (0.3/KLoC) → score 9.5. 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.

TodoComment · ×135apps/browser/src/toolbar.rs:55

FixmeComment · ×8packages/blitz-dom/src/stylo.rs:1214

HackComment · ×2apps/browser/src/main.rs:147

What to do

Resolve the 135 TodoComment finding(s) in Explicit Debt — start with text.rs (8), convert.rs (7), stylo.rs (6). — One of this dimension's main actionable groups (135 warning-level).
Resolve the 8 FixmeComment finding(s) in Explicit Debt — start with mutation_writer.rs (2), stylo.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 main.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

The repository's root README gives a strong overview (Blitz is a modular HTML/CSS rendering engine in beta, docs.rs link, status page, and the native/dropdown examples), installation/usage instructions for running the Browser UI and Markdown viewer, goals section, and links to the architecture doc. The architecture/doc files are well-structured flowcharts plus prose covering AnyRender renderers (vello_cpu, vello, vello_hybrid, skia, wgpu), the Dioxus Native component hierarchy, styling conventions, and Parley WPT test integration with prerequisites, local-pointing, version compatibility gotchas, and output interpretation. The READMEs for example directories are focused on their own tiers (preact TodoMVC, seven_guis benchmark) rather than the repository's overview.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyWeak◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Verified

6 API inconsistencies across a 400-member sample of 151 exposed types.

Ambiguous return type for mutator methods. `get_node_mut` returns `Node` (likely a value or wrapper) rather than a mutable reference `&mut Node` or a guard type, making it unclear if the mutation is immediate or deferred. This contrasts with `Document.inner_mut()` which returns a `DocGuardMut`.

Redundant getter methods. `get_viewport()` and `viewport()` perform the same operation (reading the viewport). Additionally, `viewport_mut()` returns a specific `ViewportMut` type, while other getters return the value directly, creating an inconsistent pattern for mutable access.

Confusing naming and return types for root access. `root_node` and `root_element` likely refer to the same underlying node (the `<html>` or document root), but one is 'try' (implying it might fail) and the other doesn't. Furthermore, `root_node_mut` returns `Node` instead of a mutable guard/reference, inconsistent with the `inner_mut` pattern.

Inconsistent scroll API design. `scroll_to` and `scroll_by` take a `NodeId` and `ScrollBehavior`, while `scroll_node_by` takes a callback `dispatch_event` and no behavior enum. `scroll_viewport_by` lacks behavior. The presence of `_has_changed` variants suggests a need for atomic check-and-set operations that are not consistently applied to all scroll methods.

Redundant 'raw' methods. `query_selector_raw` and `query_selector_all_raw` accept a pre-parsed `SelectorList`, while the non-raw versions accept a string. This duplicates the parsing logic externally. If the raw versions are for performance, they should be clearly documented as such, but the naming convention is inconsistent with standard library patterns (which often use `parse` separately).

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 1 Ambiguous return type for mutator methods. `get_node_mut` returns `Node`… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Redundant getter methods. `get_viewport()` and `viewport()` perform the… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Confusing naming and return types for root access. `root_node` and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D26 · Project Cohesion8.9 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Documented

1 of 19 build units (Cargo) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D28 · Secrets (history)8.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)4.8 / 10Weak✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 4.8 / 10 · rule-coverage 100% · ceiling Documented

47 finding(s): 0 critical, 46 high, 1 medium, 0 low. 42 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) — `examples/assets/graphite.html` (lines 2–2104), `examples/assets/graphite_software_overview.html` (lines 2–1645), `packages/blitz-shell/src/window.rs` (line 445, lines 446–447, lines 447–448) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

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 42 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 (42 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities9.2 / 10Stronggated by 4 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

4 finding(s): 0 critical, 0 high, 4 medium, 0 low.

REDACTED

What to do

Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness9.9 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

2 of 120 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 120 of the 163 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling9.7 / 10Adequategated by 2 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: html_document.rs↔dioxus_document.rs 66%; html_document.rs↔window.rs 50%; ime.rs↔construct.rs 50%

Boundary-crossing change coupling: html_document.rs ↔ dioxus_document.rs · ×2packages/blitz-html/src/html_document.rs

Change coupling: ime.rs ↔ construct.rspackages/blitz-dom/src/events/ime.rs

What to do

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).
Resolve the 1 Change coupling finding(s) in Change Coupling — start with ime.rs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

Do you agree with this assessment?

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

M1 · Documentation (README)7.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 21 of 25 project(s) that lack one — worth up to 1.7 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P2 · Observability6.8 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

Only 13/14 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/bump`.

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.

Do you agree with this assessment?

P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

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.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download it.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — 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?

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?

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.

Lens	Score	Rating	Impact
Code Health	81%	Strong	Solid.
Architecture	96%	Exemplary	Solid.
Maturity	75%	Strong	Solid.
Readiness	68%	Strong	Largest drag on the score — prioritise here.
Security	74%	Adequate — gated by D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event Sourcing	100%	Exemplary	Strongest area.
Performance	100%	Exemplary	Solid.

Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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.
AC7 A11y enforcement — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~14585 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.
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. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 31 value object(s); 2 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 — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Kotlin has 41 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — 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
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — 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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score.
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.

Critical — 49 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 17 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D35 · Change Coupling · Boundary-crossing change coupling · ×2

Boundary-crossing change coupling: html_document.rs ↔ dioxus_document.rs packages/blitz-html/src/html_document.rs — `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 (21 of the 32 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 21 shared commits counted here, the most recent 3 are `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`); `dbf070f2` Introduce DocumentConfig struct (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 — `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 50% of the time (16 of the 32 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 16 shared commits counted here, the most recent 3 are `8440724b` Make Document trait RefCell compatible + make DioxusDocument use RefCell; `40c31dd9` Refactor Document trait; `77bd553f` Switch Document trait from AsRef to Deref — run `git show` on any of them.

D28 · Secrets (history) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

Serious — 401 finding(s)

D17 · Explicit Debt · TodoComment · ×135

TodoComment apps/browser/src/toolbar.rs:55 — // TODO: sync state of incremental rendering when changing tabs — 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:58 — // Setup viewport. 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:136 — // Determine output path, and open a file at that path. 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 wpt/runner/src/test_runners/ref_test.rs:326 — // 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 packages/blitz-dom/src/stylo_to_parley.rs:359 — // TODO: `center` (align the aligned subtree's centre with the line box's centre) is not — 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/blitz-dom/src/stylo_to_parley.rs:369 — // TODO: `normal` resolves against the first available font's metrics, which — 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/blitz-dom/src/stylo_to_kurbo.rs:45 — // TODO: support 3D transforms — 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/blitz-dom/src/stylo_to_kurbo.rs:68 — // TODO: support 3D transforms. Outside a 3d rendering context the spec — 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/blitz-dom/src/stylo_to_kurbo.rs:81 — // TODO: support the "offset" property — 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/blitz-dom/src/stylo.rs:357 — // TODO: implement shadow DOM — 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/blitz-dom/src/stylo.rs:834 — // TODO: case-insensitive matching for HTML-ns attrs — 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/blitz-dom/src/stylo.rs:1254 — // todo!() — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blitz-dom/src/stylo.rs:1258 — // todo!() — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blitz-dom/src/stylo.rs:1266 — // todo!() — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blitz-dom/src/stylo.rs:1297 — /// todo: actually implement this — 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/blitz-dom/src/scrolling.rs:213 — // TODO: propagate the remaining scroll to the outer document — 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/blitz-dom/src/scrolling.rs:574 — // TODO: dispatch `scroll` events for programmatic scrolls. — 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/blitz-dom/src/scrolling.rs:768 — // TODO: dispatch `scroll` events for programmatic scrolls. — 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/blitz-dom/src/resolve.rs:430 — /// TODO: update taffy to use an associated type instead of slab key — 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/blitz-dom/src/resolve.rs:431 — /// TODO: update taffy to support traited styles so we don't even need to rely on taffy for storage — 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/blitz-dom/src/net.rs:444 — // TODO: support local fonts in @font-face — 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/blitz-dom/src/mutator.rs:204 — // TODO: otherwise this is basically element.textContent which is a bit different - need to parse as html — 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/blitz-dom/src/mutator.rs:280 — // TODO: make this fine grained / conditional based on ElementSelectorFlags — 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/blitz-dom/src/mutator.rs:577 — // TODO: make this fine grained / conditional based on ElementSelectorFlags — 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.
+ 110 more in this group — see findings.md.

D15 · Churn × Complexity Hotspots · Hotspot · ×23

Hotspot: packages/blitz-dom/src/layout/inline.rs packages/blitz-dom/src/layout/inline.rs:182 — packages/blitz-dom/src/layout/inline.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in BaseDocument::compute_inline_layout_inner at line 182. 9 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/blitz-dom/src/layout/inline.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:1295 — 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 34 in Node::hit_inner at line 1295. 9 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/document.rs packages/blitz-dom/src/document.rs:2707 — packages/blitz-dom/src/document.rs changed 49 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in BaseDocument::get_text_selection_ranges at line 2707. 9 of those changes were fix/bug commits, and the other 40 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/blitz-dom/src/document.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:416 — packages/blitz-dom/src/layout/construct.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in blitz_dom::layout::construct::collect_layout_children_with_wrap at line 416. 2 of those changes were fix/bug commits, and the other 31 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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-dom/src/layout/mod.rs packages/blitz-dom/src/layout/mod.rs:103 — packages/blitz-dom/src/layout/mod.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in BaseDocument::dispatch_child_layout at line 103. 6 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/mutator.rs packages/blitz-dom/src/mutator.rs:268 — packages/blitz-dom/src/mutator.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in DocumentMutator::set_attribute at line 268. 5 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/layout/damage.rs packages/blitz-dom/src/layout/damage.rs:269 — packages/blitz-dom/src/layout/damage.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in blitz_dom::layout::damage::compute_layout_damage at line 269. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/resolved_style.rs packages/blitz-dom/src/resolved_style.rs:341 — packages/blitz-dom/src/resolved_style.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in BaseDocument::resolved_style_value at line 341. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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-paint/src/render.rs packages/blitz-paint/src/render.rs:287 — packages/blitz-paint/src/render.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in BlitzDomPainter::render_element at line 287. 3 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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: wpt/runner/src/main.rs wpt/runner/src/main.rs:457 — wpt/runner/src/main.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in wpt::main at line 457. 1 of those changes was a fix/bug commit, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/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 41 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/stylo.rs packages/blitz-dom/src/stylo.rs:63 — packages/blitz-dom/src/stylo.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in BaseDocument::resolve_stylist at line 63. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/blitz-dom/src/stylo.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:172 — wpt/runner/src/test_runners/mod.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in wpt::test_runners::process_test_file at line 172. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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: packages/stylo_taffy/src/convert.rs packages/stylo_taffy/src/convert.rs:412 — packages/stylo_taffy/src/convert.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in stylo_taffy::convert::content_alignment at line 412. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/stylo_taffy/src/convert.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:206 — packages/blitz-dom/src/events/pointer.rs changed 10 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 206. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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: packages/blitz-shell/src/window.rs packages/blitz-shell/src/window.rs:585 — packages/blitz-shell/src/window.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in View::handle_winit_event at line 585. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/net.rs packages/blitz-dom/src/net.rs:405 — packages/blitz-dom/src/net.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in blitz_dom::net::fetch_font_face_rules at line 405. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/blitz-dom/src/net.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:161 — packages/blitz-dom/src/layout/table.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in blitz_dom::layout::table::build_table_context at line 161. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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-dom/src/events/driver.rs packages/blitz-dom/src/events/driver.rs:148 — packages/blitz-dom/src/events/driver.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in EventDriver::handle_ui_event at line 148. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/dioxus-native-dom/src/mutation_writer.rs packages/dioxus-native-dom/src/mutation_writer.rs:207 — packages/dioxus-native-dom/src/mutation_writer.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in MutationWriter::set_attribute 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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/dioxus-native-dom/src/dioxus_document.rs packages/dioxus-native-dom/src/dioxus_document.rs:268 — packages/dioxus-native-dom/src/dioxus_document.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DioxusEventHandler::handle_event at line 268. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/dioxus-native-dom/src/dioxus_document.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 17 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +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.
Hotspot: packages/blitz-dom/src/stylo_to_kurbo.rs packages/blitz-dom/src/stylo_to_kurbo.rs:25 — packages/blitz-dom/src/stylo_to_kurbo.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in blitz_dom::stylo_to_kurbo::resolve_2d_transform at line 25. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 14:43:35 +00:00' --until='2026-09-30 14:43:35 +00:00' --full-history --no-merges -- packages/blitz-dom/src/stylo_to_kurbo.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.

D3 · God Classes · FileTooLong · ×19

FileTooLong: src/runtime.rs packages/blitz-vibey-script/src/runtime.rs — FileTooLong — 1663 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 1163 over it, 3.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/document.rs packages/blitz-dom/src/document.rs — FileTooLong — 1629 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: BaseDocument (5 blocks, 164-2841). The bar is 500 significant lines; this is 1129 over it, 3.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: dom/element.rs packages/blitz-vibey-script/src/dom/element.rs — FileTooLong — 1028 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 100 free functions. The bar is 500 significant lines; this is 528 over it, 2.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: node/node.rs packages/blitz-dom/src/node/node.rs — FileTooLong — 967 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: Node (7 blocks, 84-1734). The bar is 500 significant lines; this is 467 over it, 1.93× 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/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: src/stylo.rs packages/blitz-dom/src/stylo.rs — FileTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 69% of them inside a single declaration: BlitzNode (7 blocks, 238-1293). The bar is 500 significant lines; this is 368 over it, 1.74× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/render.rs packages/blitz-paint/src/render.rs — FileTooLong — 816 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 316 over it, 1.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: layout/construct.rs packages/blitz-dom/src/layout/construct.rs — FileTooLong — 801 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 301 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/mutator.rs packages/blitz-dom/src/mutator.rs — FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: DocumentMutator (4 blocks, 46-1278). The bar is 500 significant lines; this is 291 over it, 1.58× 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/inline.rs packages/blitz-dom/src/layout/inline.rs — FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: BaseDocument (69-1035). The bar is 500 significant lines; this is 181 over it, 1.36× 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 — 668 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 46 free functions. The bar is 500 significant lines; this is 168 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/cssom.rs packages/blitz-dom/src/cssom.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), about 72% of them inside a single declaration: BaseDocument (284-946). The bar is 500 significant lines; this is 164 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/convert_events.rs packages/blitz-shell/src/convert_events.rs — FileTooLong — 661 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 161 over it, 1.32× 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: render/background.rs packages/blitz-paint/src/render/background.rs — FileTooLong — 600 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 100 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/main.rs wpt/runner/src/main.rs — FileTooLong — 598 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 98 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: node/element.rs packages/blitz-dom/src/node/element.rs — FileTooLong — 596 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 96 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/window.rs packages/blitz-shell/src/window.rs — FileTooLong — 545 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-863). The bar is 500 significant lines; this is 45 over it, 1.09× 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: events/pointer.rs packages/blitz-dom/src/events/pointer.rs — FileTooLong — 527 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 27 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/events.rs packages/blitz-traits/src/events.rs — FileTooLong — 512 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 12 over it, 1.02× 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.

D2 · Cognitive Complexity · blitz_dom · ×18

blitz_dom::events::pointer::handle_pointermove (cognitive 77) packages/blitz-dom/src/events/pointer.rs:206 — 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:614 — 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 53) packages/blitz-dom/src/layout/replaced.rs:52 — blitz_dom::layout::replaced::compute_replaced_layout has cognitive complexity 53 (threshold 15). Drivers by points: if/else 37 (42 pts), match/switch 5 (9 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
blitz_dom::events::keyboard::handle_key_or_input_event (cognitive 50) packages/blitz-dom/src/events/keyboard.rs:16 — blitz_dom::events::keyboard::handle_key_or_input_event has cognitive complexity 50 (threshold 15). Drivers by points: if/else 16 (47 pts), match/switch 1 (3 pts) (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
blitz_dom::form::construct_entry_list (cognitive 43) packages/blitz-dom/src/form.rs:184 — 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 39) packages/blitz-dom/src/layout/table.rs:161 — blitz_dom::layout::table::build_table_context has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 7 (11 pts), match/switch 4 (5 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::table::collect_table_cells (cognitive 39) packages/blitz-dom/src/layout/table.rs:437 — blitz_dom::layout::table::collect_table_cells has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (24 pts), match/switch 4 (9 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::layout::construct::collect_layout_children_with_wrap (cognitive 37) packages/blitz-dom/src/layout/construct.rs:416 — blitz_dom::layout::construct::collect_layout_children_with_wrap has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (30 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blitz_dom::events::pointer::handle_pointerdown (cognitive 36) packages/blitz-dom/src/events/pointer.rs:383 — 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::construct::build_inline_layout_into::build_inline_layout_recursive (cognitive 34) packages/blitz-dom/src/layout/construct.rs:1110 — blitz_dom::layout::construct::build_inline_layout_into::build_inline_layout_recursive has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (7 pts), match/switch 3 (5 pts) (nesting depth added 19). 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_dom::layout::damage::compute_layout_damage (cognitive 25) packages/blitz-dom/src/layout/damage.rs:269 — blitz_dom::layout::damage::compute_layout_damage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 10 (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 24) packages/blitz-dom/src/layout/construct.rs:315 — blitz_dom::layout::construct::classify_flow_children has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 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:677 — 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 18) packages/blitz-dom/src/layout/table.rs:371 — blitz_dom::layout::table::collect_columns has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 3 (5 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.
blitz_dom::stylo::sync_pseudo_element_styles (cognitive 18) packages/blitz-dom/src/stylo.rs:1402 — blitz_dom::stylo::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::pointer::touch_action_pan_axes (cognitive 17) packages/blitz-dom/src/events/pointer.rs:167 — 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.
blitz_dom::events::handle_dom_event (cognitive 17) packages/blitz-dom/src/events/mod.rs:96 — 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.

D3 · God Classes · FunctionTooLong · ×15

FunctionTooLong: blitz_shell::convert_events::winit_key_to_kbt_key packages/blitz-shell/src/convert_events.rs:404 — FunctionTooLong — blitz_shell::convert_events::winit_key_to_kbt_key runs 315 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 215 over it, 3.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.
FunctionTooLong: browser::toolbar::Toolbar apps/browser/src/toolbar.rs:28 — FunctionTooLong — browser::toolbar::Toolbar runs 293 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 193 over it, 2.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::replaced::compute_replaced_layout packages/blitz-dom/src/layout/replaced.rs:52 — FunctionTooLong — blitz_dom::layout::replaced::compute_replaced_layout runs 243 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 143 over it, 2.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_shell::convert_events::winit_physical_key_to_kbt_code packages/blitz-shell/src/convert_events.rs:178 — FunctionTooLong — blitz_shell::convert_events::winit_physical_key_to_kbt_code runs 221 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 121 over it, 2.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::construct::build_inline_layout_into packages/blitz-dom/src/layout/construct.rs:1035 — FunctionTooLong — blitz_dom::layout::construct::build_inline_layout_into runs 161 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 61 over it, 1.61× 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:20 — FunctionTooLong — blitz_vibey_script::dom::element::init_element_proto runs 161 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 61 over it, 1.61× 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:416 — FunctionTooLong — blitz_dom::layout::construct::collect_layout_children_with_wrap runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::events::pointer::handle_click packages/blitz-dom/src/events/pointer.rs:614 — 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_dom::layout::table::collect_table_cells packages/blitz-dom/src/layout/table.rs:437 — FunctionTooLong — blitz_dom::layout::table::collect_table_cells runs 138 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 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blitz_dom::layout::table::build_table_context packages/blitz-dom/src/layout/table.rs:161 — FunctionTooLong — blitz_dom::layout::table::build_table_context runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: stylo_taffy::convert::to_taffy_style packages/stylo_taffy/src/convert.rs:819 — FunctionTooLong — stylo_taffy::convert::to_taffy_style runs 119 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 19 over it, 1.19× 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:96 — 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:206 — 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:383 — 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_paint::text::flush_line_decorations packages/blitz-paint/src/text.rs:389 — FunctionTooLong — blitz_paint::text::flush_line_decorations 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.

D1 · Cyclomatic Complexity · blitz_dom · ×14

blitz_dom::accessibility::role_from_element_data (cyclomatic 64) packages/blitz-dom/src/accessibility.rs:165 — blitz_dom::accessibility::role_from_element_data has cyclomatic complexity 64 (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:96 — 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 41) packages/blitz-dom/src/layout/replaced.rs:52 — blitz_dom::layout::replaced::compute_replaced_layout has cyclomatic complexity 41 (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:206 — 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:614 — 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::construct::collect_layout_children_with_wrap (cyclomatic 26) packages/blitz-dom/src/layout/construct.rs:416 — blitz_dom::layout::construct::collect_layout_children_with_wrap has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blitz_dom::layout::table::build_table_context (cyclomatic 25) packages/blitz-dom/src/layout/table.rs:161 — blitz_dom::layout::table::build_table_context 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::table::collect_table_cells (cyclomatic 25) packages/blitz-dom/src/layout/table.rs:437 — blitz_dom::layout::table::collect_table_cells 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::form::construct_entry_list (cyclomatic 25) packages/blitz-dom/src/form.rs:184 — 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 23) packages/blitz-dom/src/layout/damage.rs:269 — blitz_dom::layout::damage::compute_layout_damage 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.
blitz_dom::events::pointer::handle_pointerdown (cyclomatic 20) packages/blitz-dom/src/events/pointer.rs:383 — 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::layout::construct::build_inline_layout_into::build_inline_layout_recursive (cyclomatic 19) packages/blitz-dom/src/layout/construct.rs:1110 — blitz_dom::layout::construct::build_inline_layout_into::build_inline_layout_recursive 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.
blitz_dom::net::fetch_font_face_rules (cyclomatic 19) packages/blitz-dom/src/net.rs:405 — blitz_dom::net::fetch_font_face_rules has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
blitz_dom::events::keyboard::handle_key_or_input_event (cyclomatic 17) packages/blitz-dom/src/events/keyboard.rs:16 — blitz_dom::events::keyboard::handle_key_or_input_event has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · BaseDocument · ×12

BaseDocument::compute_inline_layout_inner (cognitive 129) packages/blitz-dom/src/layout/inline.rs:182 — BaseDocument::compute_inline_layout_inner has cognitive complexity 129 (threshold 15). Drivers by points: if/else 41 (97 pts), match/switch 7 (13 pts), boolean chains 10, loops 6 (9 pts) (nesting depth added 65). 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::resolved_style_value (cognitive 95) packages/blitz-dom/src/resolved_style.rs:341 — BaseDocument::resolved_style_value has cognitive complexity 95 (threshold 15). Drivers by points: if/else 32 (66 pts), match/switch 11 (20 pts), boolean chains 9 (nesting depth added 43). To reduce it, split the body into named stages: move each independent 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::dispatch_child_layout (cognitive 53) packages/blitz-dom/src/layout/mod.rs:103 — BaseDocument::dispatch_child_layout has cognitive complexity 53 (threshold 15). Drivers by points: if/else 11 (30 pts), match/switch 8 (22 pts), boolean chains 1 (nesting depth added 33). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BaseDocument::collect_inline_roots_in_range (cognitive 51) packages/blitz-dom/src/traversal.rs:379 — 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::get_text_selection_ranges (cognitive 35) packages/blitz-dom/src/document.rs:2707 — 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::resolve_stylist (cognitive 32) packages/blitz-dom/src/stylo.rs:63 — BaseDocument::resolve_stylist has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 7 (11 pts), boolean chains 4 (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.
BaseDocument::build_paint_tree_impl (cognitive 30) packages/blitz-dom/src/layout/paint_tree.rs:222 — BaseDocument::build_paint_tree_impl has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (7 pts), match/switch 2 (5 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::inline_fragment_rects (cognitive 29) packages/blitz-dom/src/document.rs:2345 — BaseDocument::inline_fragment_rects has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 3 (7 pts), loops 3 (4 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.
BaseDocument::resolve_transforms (cognitive 20) packages/blitz-dom/src/resolve.rs:170 — BaseDocument::resolve_transforms has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseDocument::collect_layout_children_inline_roots (cognitive 20) packages/blitz-dom/src/traversal.rs:549 — 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::propagate_damage_flags (cognitive 19) packages/blitz-dom/src/layout/damage.rs:54 — BaseDocument::propagate_damage_flags has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, 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_layout_children::resolve_layout_children_recursive (cognitive 19) packages/blitz-dom/src/resolve.rs:252 — 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.

D3 · God Classes · MethodTooLong · ×12

MethodTooLong: BaseDocument.compute_inline_layout_inner packages/blitz-dom/src/layout/inline.rs:182 — MethodTooLong — compute_inline_layout_inner runs 547 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 447 over it, 5.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInputData.apply_apple_standard_keybinding packages/blitz-dom/src/node/text.rs:365 — 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: BaseDocument.dispatch_child_layout packages/blitz-dom/src/layout/mod.rs:103 — MethodTooLong — dispatch_child_layout runs 201 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 101 over it, 2.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.
MethodTooLong: BaseDocument.resolved_style_value packages/blitz-dom/src/resolved_style.rs:341 — MethodTooLong — resolved_style_value runs 200 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 100 over it, 2.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BlitzDomPainter.render_element packages/blitz-paint/src/render.rs:287 — MethodTooLong — render_element runs 199 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: View.handle_winit_event packages/blitz-shell/src/window.rs:585 — MethodTooLong — handle_winit_event runs 180 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BaseDocument.new packages/blitz-dom/src/document.rs:365 — MethodTooLong — new runs 135 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 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInputData.apply_keypress_event packages/blitz-dom/src/node/text.rs:195 — MethodTooLong — apply_keypress_event runs 123 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Node.hit_inner packages/blitz-dom/src/node/node.rs:1295 — MethodTooLong — hit_inner runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ElementCx.draw_border packages/blitz-paint/src/render/border.rs:149 — 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.new packages/blitz-vibey-script/src/runtime.rs:1276 — MethodTooLong — new 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.
MethodTooLong: BaseDocument.debug_log_node packages/blitz-dom/src/debug.rs:17 — 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.

D1 · Cyclomatic Complexity · BaseDocument · ×9

BaseDocument::resolved_style_value (cyclomatic 60) packages/blitz-dom/src/resolved_style.rs:341 — BaseDocument::resolved_style_value has cyclomatic complexity 60 (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::compute_inline_layout_inner (cyclomatic 56) packages/blitz-dom/src/layout/inline.rs:182 — BaseDocument::compute_inline_layout_inner has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaseDocument::dispatch_child_layout (cyclomatic 32) packages/blitz-dom/src/layout/mod.rs:103 — BaseDocument::dispatch_child_layout 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.
BaseDocument::get_text_selection_ranges (cyclomatic 24) packages/blitz-dom/src/document.rs:2707 — 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::resolve_stylist (cyclomatic 19) packages/blitz-dom/src/stylo.rs:63 — BaseDocument::resolve_stylist 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::collect_inline_roots_in_range (cyclomatic 19) packages/blitz-dom/src/traversal.rs:379 — 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::inline_fragment_rects (cyclomatic 16) packages/blitz-dom/src/document.rs:2345 — BaseDocument::inline_fragment_rects 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.
BaseDocument::propagate_damage_flags (cyclomatic 16) packages/blitz-dom/src/layout/damage.rs:54 — BaseDocument::propagate_damage_flags 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.
BaseDocument::build_paint_tree_impl (cyclomatic 16) packages/blitz-dom/src/layout/paint_tree.rs:222 — BaseDocument::build_paint_tree_impl 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.

D17 · Explicit Debt · FixmeComment · ×8

FixmeComment packages/blitz-dom/src/stylo.rs:1214 — // 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/resolve.rs:15 — // 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/events/pointer.rs:101 — // 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.
FixmeComment packages/blitz-dom/src/node/text.rs:70 — // 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/node/node.rs:1720 — // 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-paint/src/render/background.rs:545 — // FIXME: https://wpt.live/css/css-backgrounds/background-size/background-size-near-zero-gradient.html
FixmeComment packages/dioxus-native-dom/src/mutation_writer.rs:285 — // 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:402 — // 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.

D5 · Coupling · Off the main sequence · ×7

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: stylo_taffy — stylo_taffy: 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 12 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.06, instability 0.23, distance 0.71 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.

D2 · Cognitive Complexity · blitz_paint · ×6

blitz_paint::gradient::resolve_color_stops (cognitive 56) packages/blitz-paint/src/gradient.rs:331 — 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 48) packages/blitz-paint/src/text.rs:556 — blitz_paint::text::stroke_text has cognitive complexity 48 (threshold 15). Drivers by points: if/else 7 (28 pts), loops 5 (15 pts), match/switch 1 (5 pts) (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_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::render::background::compute_layer_size (cognitive 23) packages/blitz-paint/src/render/background.rs:638 — 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::draw_decoration_line (cognitive 20) packages/blitz-paint/src/text.rs:283 — blitz_paint::text::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.
blitz_paint::text::flush_line_decorations (cognitive 20) packages/blitz-paint/src/text.rs:389 — blitz_paint::text::flush_line_decorations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D3 · God Classes · ClassTooLong · ×6

ClassTooLong: BaseDocument packages/blitz-dom/src/document.rs:193 — ClassTooLong — 1487 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 264 methods, 5 blocks, lines 164-2841. The bar is 400 significant lines; this is 1087 over it, 3.72× 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:84 — ClassTooLong — 845 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 124 methods, 7 blocks, lines 84-1734. The bar is 400 significant lines; this is 445 over it, 2.11× 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:46 — ClassTooLong — 728 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 57 methods, 4 blocks, lines 46-1278. The bar is 400 significant lines; this is 328 over it, 1.82× 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 — 497 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-863. The bar is 400 significant lines; this is 97 over it, 1.24× 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:57 — ClassTooLong — 450 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 57-797. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ScriptRuntime packages/blitz-vibey-script/src/runtime.rs:1269 — ClassTooLong — 411 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 2 blocks, lines 1269-1920. The bar is 400 significant lines; this is 11 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 · Duplicated block (8 lines × 2) · ×6

Duplicated block (8 lines × 2) packages/blitz-dom/src/cssom.rs:559 — packages/blitz-dom/src/cssom.rs:559-566 | packages/blitz-dom/src/cssom.rs:770-777 — 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/blitz-dom/src/cssom.rs:768 — packages/blitz-dom/src/cssom.rs:768-775 | packages/blitz-dom/src/cssom.rs:822-829 — 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/blitz-dom/src/events/pointer.rs:348 — packages/blitz-dom/src/events/pointer.rs:348-356 | packages/blitz-dom/src/events/pointer.rs:467-474 — 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/blitz-dom/src/font_metrics.rs:113 — packages/blitz-dom/src/font_metrics.rs:113-120 | packages/blitz-dom/src/font_metrics.rs:138-145 — 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/blitz-dom/src/layout/inline.rs:633 — packages/blitz-dom/src/layout/inline.rs:633-640 | packages/blitz-dom/src/layout/inline.rs:690-697 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:252 — packages/blitz-vibey-script/src/dom/document.rs:252-259 | packages/blitz-vibey-script/src/dom/element.rs:1404-1411 — before extracting anything, compare `packages/blitz-vibey-script/src/dom/document.rs` and `packages/blitz-vibey-script/src/dom/element.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×6

Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/dom/element.rs:252 — packages/blitz-vibey-script/src/dom/element.rs:252-257 | packages/blitz-vibey-script/src/dom/element.rs:264-269 — 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/blitz-vibey-script/src/dom/element.rs:618 — packages/blitz-vibey-script/src/dom/element.rs:618-623 | packages/blitz-vibey-script/src/dom/element.rs:636-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.
Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:270 — packages/blitz-vibey-script/src/dom/document.rs:270-275 | packages/blitz-vibey-script/src/dom/element.rs:1422-1427 — before extracting anything, compare `packages/blitz-vibey-script/src/dom/document.rs` and `packages/blitz-vibey-script/src/dom/element.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) packages/blitz-vibey-script/src/runtime.rs:2063 — packages/blitz-vibey-script/src/runtime.rs:2063-2068 | packages/blitz-vibey-script/src/runtime.rs:2074-2079 — 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:937 — packages/stylo_taffy/src/convert.rs:937-942 | packages/stylo_taffy/src/convert.rs:945-950 — 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/blitz-vibey-script/src/document.rs:300 — packages/blitz-vibey-script/src/document.rs:300-306 | packages/blitz-vibey-script/src/runtime.rs:1526-1531 — 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.

D3 · God Classes · TooManyMethods · ×5

TooManyMethods: BaseDocument packages/blitz-dom/src/document.rs:193 — TooManyMethods — 264 methods, declared across 18 files: src/document.rs (136), src/scrolling.rs (23), src/cssom.rs (20), src/traversal.rs (19), +14 more file(s). The bar is 30 methods; this is 234 over it, 8.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: Node packages/blitz-dom/src/node/node.rs:84 — TooManyMethods — 124 methods, declared across 4 files: node/node.rs (107), node/scrollbar.rs (7), node/serialize.rs (6), src/query_selector.rs (4). The bar is 30 methods; this is 94 over it, 4.13× 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:46 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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:692 — TooManyMethods — 39 methods, declared across 7 files: render/background.rs (12), src/render.rs (10), render/border.rs (6), render/clip_path.rs (4), +3 more file(s). The bar is 30 methods; this is 9 over it, 1.30× 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:45 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D2 · Cognitive Complexity · ElementCx · ×4

ElementCx::draw_border (cognitive 32) packages/blitz-paint/src/render/border.rs:149 — 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:446 — 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:725 — 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_text_input_text (cognitive 16) packages/blitz-paint/src/render.rs:887 — 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.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×4

Duplicated block (9 lines × 2) packages/blitz-dom/src/layout/construct.rs:977 — packages/blitz-dom/src/layout/construct.rs:977-985 | packages/blitz-dom/src/layout/construct.rs:1126-1134 — 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-vibey-script/src/dom/element.rs:764 — packages/blitz-vibey-script/src/dom/element.rs:764-772 | packages/blitz-vibey-script/src/dom/element.rs:780-788 — 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-vibey-script/src/dom/document.rs:277 — packages/blitz-vibey-script/src/dom/document.rs:277-285 | packages/blitz-vibey-script/src/dom/element.rs:1428-1436 — before extracting anything, compare `packages/blitz-vibey-script/src/dom/document.rs` and `packages/blitz-vibey-script/src/dom/element.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) packages/blitz/src/lib.rs:88 — packages/blitz/src/lib.rs:88-96 | packages/dioxus-native/src/lib.rs:156-164 — 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.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4

Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/runtime.rs:2154 — packages/blitz-vibey-script/src/runtime.rs:2154-2158 | packages/blitz-vibey-script/src/runtime.rs:2172-2176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:194 — packages/blitz-vibey-script/src/dom/document.rs:194-198 | packages/blitz-vibey-script/src/dom/document.rs:205-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.
Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/dom/element.rs:585 — packages/blitz-vibey-script/src/dom/element.rs:585-589 | packages/blitz-vibey-script/src/dom/hyperlink.rs:55-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/blitz-vibey-script/src/dom/node.rs:600 — packages/blitz-vibey-script/src/dom/node.rs:600-604 | packages/blitz-vibey-script/src/dom/node.rs:655-659 — 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.

D1 · Cyclomatic Complexity · blitz_paint · ×3

blitz_paint::gradient::resolve_color_stops (cyclomatic 24) packages/blitz-paint/src/gradient.rs:331 — 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:638 — 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::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.

D2 · Cognitive Complexity · DocumentMutator · ×3

DocumentMutator::set_attribute (cognitive 35) packages/blitz-dom/src/mutator.rs:268 — DocumentMutator::set_attribute has cognitive complexity 35 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 5 (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.
DocumentMutator::clear_attribute (cognitive 24) packages/blitz-dom/src/mutator.rs:396 — DocumentMutator::clear_attribute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocumentMutator::add_children_to_parent (cognitive 18) packages/blitz-dom/src/mutator.rs:657 — DocumentMutator::add_children_to_parent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D1 · Cyclomatic Complexity · TextInputData · ×2

TextInputData::apply_apple_standard_keybinding (cyclomatic 100) packages/blitz-dom/src/node/text.rs:365 — 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 42) packages/blitz-dom/src/node/text.rs:195 — TextInputData::apply_keypress_event has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Node · ×2

Node::hit_inner (cyclomatic 34) packages/blitz-dom/src/node/node.rs:1295 — Node::hit_inner has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Node::write_outer_html_in_style (cyclomatic 24) packages/blitz-dom/src/node/serialize.rs:116 — 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.

D1 · Cyclomatic Complexity · DocumentMutator · ×2

DocumentMutator::set_attribute (cyclomatic 28) packages/blitz-dom/src/mutator.rs:268 — DocumentMutator::set_attribute 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.
DocumentMutator::clear_attribute (cyclomatic 22) packages/blitz-dom/src/mutator.rs:396 — DocumentMutator::clear_attribute has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ElementCx · ×2

ElementCx::draw_border (cyclomatic 27) packages/blitz-paint/src/render/border.rs:149 — 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:725 — 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.

D1 · Cyclomatic Complexity · blitz_vibey_script · ×2

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.

D17 · Explicit Debt · HackComment · ×2

HackComment apps/browser/src/main.rs:147 — // 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.
HackComment packages/blitz-dom/src/layout/mod.rs:386 — // 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.

D2 · Cognitive Complexity · Node · ×2

Node::hit_inner (cognitive 58) packages/blitz-dom/src/node/node.rs:1295 — Node::hit_inner has cognitive complexity 58 (threshold 15). Drivers by points: if/else 21 (42 pts), boolean chains 8, loops 3 (7 pts), match/switch 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Node::write_outer_html_in_style (cognitive 46) packages/blitz-dom/src/node/serialize.rs:116 — 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.

D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×2

REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2

Duplicated block (17 lines × 2) packages/blitz-paint/src/render/background.rs:819 — packages/blitz-paint/src/render/background.rs:819-835 | packages/blitz-paint/src/render/background.rs:872-888 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) packages/stylo_taffy/src/wrapper.rs:441 — packages/stylo_taffy/src/wrapper.rs:441-457 | packages/stylo_taffy/src/wrapper.rs:462-478 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2

Duplicated block (16 lines × 2) packages/blitz-dom/src/events/driver.rs:347 — packages/blitz-dom/src/events/driver.rs:347-362 | 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:364 — packages/blitz-traits/src/events.rs:364-379 | packages/blitz-traits/src/events.rs:410-425 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2

Duplicated block (14 lines × 2) packages/blitz-dom/src/mutator.rs:578 — packages/blitz-dom/src/mutator.rs:578-591 | packages/blitz-dom/src/mutator.rs:683-696 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) packages/blitz-dom/src/mutator.rs:679 — packages/blitz-dom/src/mutator.rs:679-692 | packages/blitz-dom/src/mutator.rs:698-711 — 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.

D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×2

Duplicated block (10–11 lines × 2) packages/blitz-dom/src/mutator.rs:269 — packages/blitz-dom/src/mutator.rs:269-278 | packages/blitz-dom/src/mutator.rs:397-407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) packages/blitz-dom/src/node/element.rs:312 — packages/blitz-dom/src/node/element.rs:312-322 | packages/blitz-dom/src/node/element.rs:419-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.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2

Duplicated block (11 lines × 2) packages/blitz-traits/src/events.rs:382 — packages/blitz-traits/src/events.rs:382-392 | packages/blitz-traits/src/events.rs:428-438 — 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.rs:1806 — packages/blitz-vibey-script/src/runtime.rs:1806-1816 | packages/blitz-vibey-script/src/runtime.rs:1874-1884 — 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.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2

Duplicated block (10 lines × 2) packages/blitz-paint/src/render/background.rs:476 — packages/blitz-paint/src/render/background.rs:476-485 | packages/blitz-paint/src/render/background.rs:568-577 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) 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.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2

Duplicated block (7 lines × 2) packages/blitz-vibey-script/src/dom/document.rs:373 — packages/blitz-vibey-script/src/dom/document.rs:373-379 | packages/blitz-vibey-script/src/dom/element.rs:1360-1366 — before extracting anything, compare `packages/blitz-vibey-script/src/dom/document.rs` and `packages/blitz-vibey-script/src/dom/element.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) apps/browser/src/toolbar.rs:213 — apps/browser/src/toolbar.rs:213-219 | apps/browser/src/toolbar.rs:235-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D1 · Cyclomatic Complexity · View · ×1

View::handle_winit_event (cyclomatic 56) packages/blitz-shell/src/window.rs:585 — 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.

D1 · Cyclomatic Complexity · wpt · ×1

wpt::main (cyclomatic 32) wpt/runner/src/main.rs:457 — wpt::main has cyclomatic complexity 32 (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.

D1 · Cyclomatic Complexity · EventDriver · ×1

EventDriver::handle_ui_event (cyclomatic 27) packages/blitz-dom/src/events/driver.rs:148 — EventDriver::handle_ui_event has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ScriptRuntime · ×1

ScriptRuntime::dispatch_event_inner (cyclomatic 27) packages/blitz-vibey-script/src/runtime.rs:1703 — 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.

D1 · Cyclomatic Complexity · geometry.validateAndFixupMatrixInit (cyclomatic 26) · ×1

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 literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · (anonymous) · ×1

(anonymous)::validateAndFixupMatrixInit (cyclomatic 24) packages/blitz-vibey-script/src/geometry.js:647 — (anonymous)::validateAndFixupMatrixInit 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.

D1 · Cyclomatic Complexity · browser · ×1

browser::toolbar::Toolbar (cyclomatic 21) apps/browser/src/toolbar.rs:28 — browser::toolbar::Toolbar 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.

D1 · Cyclomatic Complexity · BlitzDomPainter · ×1

BlitzDomPainter::render_element (cyclomatic 21) packages/blitz-paint/src/render.rs:287 — BlitzDomPainter::render_element 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.

D1 · Cyclomatic Complexity · TestResult · ×1

TestResult::print_to (cyclomatic 21) wpt/runner/src/main.rs:359 — 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.

D1 · Cyclomatic Complexity · MutationWriter · ×1

MutationWriter::set_attribute (cyclomatic 20) packages/dioxus-native-dom/src/mutation_writer.rs:207 — MutationWriter::set_attribute 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.

D1 · Cyclomatic Complexity · BlitzApplication · ×1

BlitzApplication::handle_blitz_shell_event (cyclomatic 17) packages/blitz-shell/src/application.rs:41 — BlitzApplication::handle_blitz_shell_event has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · TextInputData · ×1

TextInputData::apply_keypress_event (cognitive 66) packages/blitz-dom/src/node/text.rs:195 — TextInputData::apply_keypress_event has cognitive complexity 66 (threshold 15). Drivers by points: if/else 37 (60 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ScriptRuntime · ×1

ScriptRuntime::dispatch_event_inner (cognitive 56) packages/blitz-vibey-script/src/runtime.rs:1703 — 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.

D2 · Cognitive Complexity · View · ×1

View::handle_winit_event (cognitive 48) packages/blitz-shell/src/window.rs:585 — 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.

D2 · Cognitive Complexity · wpt · ×1

wpt::main (cognitive 35) wpt/runner/src/main.rs:457 — wpt::main has cognitive complexity 35 (threshold 15). Drivers by points: if/else 22 (24 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.

D2 · Cognitive Complexity · (anonymous) · ×1

(anonymous)::validateAndFixupMatrixInit (cognitive 32) packages/blitz-vibey-script/src/geometry.js:647 — (anonymous)::validateAndFixupMatrixInit has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 7, boolean chains 5, ternaries 2 (4 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.

D2 · Cognitive Complexity · geometry.validateAndFixupMatrixInit (cognitive 30) · ×1

geometry.validateAndFixupMatrixInit (cognitive 30) packages/blitz-vibey-script/src/geometry.js:647 — geometry.validateAndFixupMatrixInit has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 7, boolean chains 6, ternaries 1 (nesting depth added 7). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BlitzDomPainter · ×1

BlitzDomPainter::render_element (cognitive 24) packages/blitz-paint/src/render.rs:287 — BlitzDomPainter::render_element has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 8 (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.

D2 · Cognitive Complexity · browser · ×1

browser::toolbar::Toolbar (cognitive 23) apps/browser/src/toolbar.rs:28 — browser::toolbar::Toolbar has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (17 pts), match/switch 6 (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.

D2 · Cognitive Complexity · blitz_vibey_script · ×1

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.

D2 · Cognitive Complexity · MutationWriter · ×1

MutationWriter::set_attribute (cognitive 20) packages/dioxus-native-dom/src/mutation_writer.rs:207 — MutationWriter::set_attribute 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.

D2 · Cognitive Complexity · TestResult · ×1

TestResult::print_to (cognitive 20) wpt/runner/src/main.rs:359 — 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.

D2 · Cognitive Complexity · wpt_diff_to_pr.render (cognitive 18) · ×1

wpt_diff_to_pr.render (cognitive 18) .github/scripts/wpt_diff_to_pr.py:116 — wpt_diff_to_pr.render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 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.

D2 · Cognitive Complexity · EventDriver · ×1

EventDriver::handle_pointer_move (cognitive 17) packages/blitz-dom/src/events/driver.rs:47 — EventDriver::handle_pointer_move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 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.

D2 · Cognitive Complexity · DioxusNativeApplication · ×1

DioxusNativeApplication::handle_dioxus_native_event (cognitive 17) packages/dioxus-native/src/dioxus_application.rs:58 — DioxusNativeApplication::handle_dioxus_native_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 2 (7 pts), match/switch 2 (3 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · BlitzApplication · ×1

BlitzApplication::handle_blitz_shell_event (cognitive 16) packages/blitz-shell/src/application.rs:41 — BlitzApplication::handle_blitz_shell_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (4 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D22 · Internal API Consistency · Ambiguous return type for mutator methods. `get_node_mut` returns `Node` (likely a value or wrapper) rather than a mutable reference `&mut Node` or a guard type, making it unclear if the mutation is immediate or deferred. This contrasts with `Document.inner_mut()` which returns a `DocGuardMut`. · ×1

Ambiguous return type for mutator methods. `get_node_mut` returns `Node` (likely a value or wrapper) rather than a mutable reference `&mut Node` or a guard type, making it unclear if the mutation is immediate or deferred. This contrasts with `Document.inner_mut()` which returns a `DocGuardMut`. — Return a mutable reference `&mut Node` or a specific mutable guard type to clearly indicate ownership and mutation semantics. (signatures: BaseDocument.get_node(node_id: NodeId): Node | BaseDocument.get_node_mut(node_id: NodeId): Node)

D22 · Internal API Consistency · Redundant getter methods. `get_viewport()` and `viewport()` perform the same operation (reading the viewport). Additionally, `viewport_mut()` returns a specific `ViewportMut` type, while other getters return the value directly, creating an inconsistent pattern for mutable access. · ×1

Redundant getter methods. `get_viewport()` and `viewport()` perform the same operation (reading the viewport). Additionally, `viewport_mut()` returns a specific `ViewportMut` type, while other getters return the value directly, creating an inconsistent pattern for mutable access. — Remove `get_viewport()` in favor of `viewport()`. Standardize mutable access to either return a mutable reference or a consistent guard type across all properties. (signatures: BaseDocument.get_viewport(): Viewport | BaseDocument.viewport(): Viewport | BaseDocument.viewport_mut(): ViewportMut)

D22 · Internal API Consistency · Confusing naming and return types for root access. `root_node` and `root_element` likely refer to the same underlying node (the `<html>` or document root), but one is 'try' (implying it might fail) and the other doesn't. Furthermore, `root_node_mut` returns `Node` instead of a mutable guard/reference, inconsistent with the `inner_mut` pattern. · ×1

Confusing naming and return types for root access. `root_node` and `root_element` likely refer to the same underlying node (the `<html>` or document root), but one is 'try' (implying it might fail) and the other doesn't. Furthermore, `root_node_mut` returns `Node` instead of a mutable guard/reference, inconsistent with the `inner_mut` pattern. — Clarify the distinction between 'node' and 'element' if they are different. If they are the same, unify the names. Ensure `root_node_mut` returns a mutable guard or reference consistent with `inner_mut`. (signatures: BaseDocument.root_node(): Node | BaseDocument.root_node_mut(): Node | BaseDocument.try_root_element(): Node | BaseDocument.root_element(): Node)

D22 · Internal API Consistency · Inconsistent scroll API design. `scroll_to` and `scroll_by` take a `NodeId` and `ScrollBehavior`, while `scroll_node_by` takes a callback `dispatch_event` and no behavior enum. `scroll_viewport_by` lacks behavior. The presence of `_has_changed` variants suggests a need for atomic check-and-set operations that are not consistently applied to all scroll methods. · ×1

Inconsistent scroll API design. `scroll_to` and `scroll_by` take a `NodeId` and `ScrollBehavior`, while `scroll_node_by` takes a callback `dispatch_event` and no behavior enum. `scroll_viewport_by` lacks behavior. The presence of `_has_changed` variants suggests a need for atomic check-and-set operations that are not consistently applied to all scroll methods. — Unify scroll methods to accept a consistent `ScrollBehavior` enum. Either expose the event dispatching callback in all methods or handle it internally. Remove `_has_changed` variants if the operation is expected to always succeed or fail deterministically, or apply them consistently to all scroll actions. (signatures: BaseDocument.scroll_to(node_id: NodeId, x: f64, y: f64, behavior: ScrollBehavior) | BaseDocument.scroll_by(node_id: NodeId, x: f64, y: f64, behavior: ScrollBehavior) | BaseDocument.scroll_node_by(node_id: NodeId, x: f64, y: f64, dispatch_event: F) | BaseDocument.scroll_viewport_by(x: f64, y: f64) | BaseDocument.scroll_viewport_by_has_changed(x: f64, y: f64): bool)

D22 · Internal API Consistency · Redundant 'raw' methods. `query_selector_raw` and `query_selector_all_raw` accept a pre-parsed `SelectorList`, while the non-raw versions accept a string. This duplicates the parsing logic externally. If the raw versions are for performance, they should be clearly documented as such, but the naming convention is inconsistent with standard library patterns (which often use `parse` separately). · ×1

Redundant 'raw' methods. `query_selector_raw` and `query_selector_all_raw` accept a pre-parsed `SelectorList`, while the non-raw versions accept a string. This duplicates the parsing logic externally. If the raw versions are for performance, they should be clearly documented as such, but the naming convention is inconsistent with standard library patterns (which often use `parse` separately). — Remove the `_raw` suffix methods if the parsing overhead is negligible, or rename them to `query_selector_with_list` to be more explicit. Alternatively, provide a separate `SelectorList` type that can be passed to the main methods. (signatures: BaseDocument.query_selector(selector: str): Result | BaseDocument.query_selector_raw(selector_list: SelectorList): NodeId | BaseDocument.query_selector_all(selector: str): Result | BaseDocument.query_selector_all_raw(selector_list: SelectorList): SmallVec)

D22 · Internal API Consistency · Duplicate functionality across types. `BaseDocument` and `DocumentMutator` both expose `set_style_property` and `remove_style_property`. Since `DocumentMutator` is obtained via `BaseDocument.mutate()`, it is unclear if calling these on `BaseDocument` directly is valid or if it bypasses the mutation tracking system. · ×1

Duplicate functionality across types. `BaseDocument` and `DocumentMutator` both expose `set_style_property` and `remove_style_property`. Since `DocumentMutator` is obtained via `BaseDocument.mutate()`, it is unclear if calling these on `BaseDocument` directly is valid or if it bypasses the mutation tracking system. — Remove these methods from `BaseDocument` and enforce that style changes must go through `DocumentMutator` to ensure consistency with the mutation tracking system. (signatures: BaseDocument.set_style_property(node_id: NodeId, name: str, value: str) | BaseDocument.remove_style_property(node_id: NodeId, name: str) | DocumentMutator.set_style_property(node_id: NodeId, name: str, value: str) | DocumentMutator.remove_style_property(node_id: NodeId, name: str))

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D3 · God Classes · TooManyFields · ×1

TooManyFields: BaseDocument packages/blitz-dom/src/document.rs:193 — TooManyFields — 58 stored fields beside 264 methods. The bar is 30 stored fields; this is 28 over it, 1.93× 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.

D3 · God Classes · TooManyFunctions · ×1

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.

D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×1

REDACTED

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

D35 · Change Coupling · Change coupling · ×1

Change coupling: ime.rs ↔ construct.rs packages/blitz-dom/src/events/ime.rs — `packages/blitz-dom/src/events/ime.rs` and `packages/blitz-dom/src/layout/construct.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `8cf13b96` chore: move from print to tracing (#356); `cc86d6fa` Implement skrifa-based FontMetricsProvider (#204); `1247c804` Fix lints (2025-04-24) — run `git show` on any of them.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1

Duplicated block (16–17 lines × 2) packages/blitz-dom/src/node/element.rs:681 — packages/blitz-dom/src/node/element.rs:681-697 | packages/blitz-dom/src/node/element.rs:748-763 — 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.

D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1

Duplicated block (14–15 lines × 2) packages/blitz-dom/src/layout/construct.rs:1179 — packages/blitz-dom/src/layout/construct.rs:1179-1192 | packages/blitz-dom/src/layout/construct.rs:1246-1260 — 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.

D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1

Duplicated block (11–13 lines × 2) packages/blitz-paint/src/render/background.rs:251 — packages/blitz-paint/src/render/background.rs:251-263 | packages/blitz-paint/src/render/background.rs:275-285 — 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.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1

Duplicated block (13 lines × 2) packages/blitz-paint/src/render.rs:1011 — packages/blitz-paint/src/render.rs:1011-1023 | packages/blitz-paint/src/render.rs:1051-1063 — 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.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1

Duplicated block (12 lines × 2) packages/blitz-dom/src/node/node.rs:1389 — packages/blitz-dom/src/node/node.rs:1389-1400 | packages/blitz-dom/src/node/node.rs:1436-1447 — 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.

D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1

Duplicated block (11–12 lines × 2) packages/blitz-paint/src/render.rs:1098 — packages/blitz-paint/src/render.rs:1098-1109 | packages/blitz-paint/src/render.rs:1142-1152 — 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.

D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1

Duplicated block (9–10 lines × 2) packages/blitz-html/src/html_sink.rs:226 — packages/blitz-html/src/html_sink.rs:226-234 | packages/blitz-html/src/html_sink.rs:248-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.

D4 · Code Duplication · Duplicated block (5–7 lines × 2) · ×1

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.

D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1

Duplicated block (6 lines × 4) packages/blitz-vibey-script/src/dom/element.rs:307 — packages/blitz-vibey-script/src/dom/element.rs:307-312 | packages/blitz-vibey-script/src/dom/element.rs:1363-1368 | packages/blitz-vibey-script/src/dom/element.rs:1408-1413 | packages/blitz-vibey-script/src/dom/element.rs:1433-1438 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1

Duplicated block (6 lines × 3) packages/blitz-dom/src/cssom.rs:559 — packages/blitz-dom/src/cssom.rs:559-564 | packages/blitz-dom/src/cssom.rs:770-775 | packages/blitz-dom/src/cssom.rs:824-829 — 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.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1

Duplicated block (5 lines × 3) packages/blitz-vibey-script/src/dom/element.rs:1153 — packages/blitz-vibey-script/src/dom/element.rs:1153-1157 | packages/blitz-vibey-script/src/dom/element.rs:1164-1168 | packages/blitz-vibey-script/src/dom/element.rs:1175-1181 — 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.

D6 · Cohesion (LCOM4) · Low cohesion · ×1

Low cohesion: BlitzShellProvider (LCOM4 4) packages/blitz-shell/src/lib.rs:87 — BlitzShellProvider's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

Minor — 10 finding(s)

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 1 of 19 project(s) overshoot their size bounds, lowering Project Cohesion to 8.9/10. The most over is `packages/blitz-dom` (23497 LoC, 121 public types across 4 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.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 2 of 120 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 and example/demo trees and test files identified by path convention, largest first; 120 of the 163 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, packages/blitz-dom/src/selection.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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D9 · Test Distribution · Inverted test pyramid · ×1

Inverted test pyramid — Only 29 % of tests are unit tests (119 unit vs 286 integration, 0 BDD); a broader unit base gives faster, more localised feedback.

M2 · Architecture documentation · No ADRs · ×1

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.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 13/14 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/bump`.

Minor — 5 finding(s)

D12 · Dependency Hygiene · Outdated · ×5

Outdated: accesskit — `accesskit` is locked at 0.25.0 but 0.25.1 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_macos — `accesskit_macos` is locked at 0.27.0 but 0.27.1 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_windows — `accesskit_windows` is locked at 0.35.0 but 0.35.1 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: bitflags — `bitflags` is locked at 2.13.1 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.6.0"` requirement declared in wpt/runner/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: cfg-if — `cfg-if` is locked at 1.0.4 but 1.0.5 is the current stable release on crates.io, and it already satisfies the `"1.0.4"` requirement declared in packages/dioxus-native/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cfg-if` 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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-99cd0f59ce53425ba12c099fecb69c8b/history.json --exit-code 0 --source .	2	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-99cd0f59ce53425ba12c099fecb69c8b/tree.json --exit-code 0 --source .	2	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	47	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	4	artifacts/raw/osv-scanner.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	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.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	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.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	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.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	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.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	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.	0	—
D43 · Malicious Dependencies	osv-scanner	—	osv-scanner --format json --recursive .	0	artifacts/raw/osv-scanner.json

Run 01a0f321-6145-7b94-804a-1aafd2fc7117 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

DioxusLabs/blitz

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 81% · Strong ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 75% · Strong ·

At a glance — Readiness · 68% · Strong ·

At a glance — Security · 74% · Adequate · gated by D36 ·

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts