Public report — imprint.canine.dev, published 5 Sep 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
552findings with an exact file:lineof 581 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
99/144dimensions across the health lenses25237 LoC · 15 projects — wide & deep
Executive summary
Template / example. This repo declares itself a template, kata, sample or demo — code to read or copy, not operate — so the ship-it and operate-it dimensions (CI/CD, observability, ADRs, architecture docs, deployment security) are N/A and what remains is judged accordingly.
Workable, but carrying real maintenance and quality risk in places that will slow change if left.
It's a medium codebase: about 25,237 lines of production code, roughly 39% of it boilerplate and declarations rather than real logic. Rebuilding it from scratch would take about ~2.0 person-years (~1–4 engineers, around ~€290,000) — a sense of the value tied up here and the cost of changing it.
Across the health lenses (Code Health 42%, Architecture 88%, Maturity 63%, Readiness 57%, Security 87%, Domain Modelling 65%, Event Sourcing 100%, Accessibility 59%, Performance 71%), the strongest area is Event Sourcing and the one that most needs attention is Code Health.
Worth flagging (advisory, not scored): coverage not measured — no coverage collector is wired up; bounded contexts not declared.
Start with: adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
How the score is built — each lens's share of the headlineWidth 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.
R7 · Dead file (~130 LoC) widgets/_src/cai-composition-bar.js
R7 · Dead file (~128 LoC) widgets/cai-composition-bar.js
R7 · Dead file (~112 LoC) widgets/_src/cai-score-card.js
R7 · Dead file (~108 LoC) widgets/_src/cai-link-cards.js
DM10 · One operation mutates 2 aggregates: DefineBlockFromNodeHandler.Handle src/Imprint.Authoring/Features/Blocks/DefineBlockFromNode/DefineBlockFromNodeHandler.cs
DM10 · One operation mutates 2 aggregates: UpdateBlockFromInstanceHandler.Handle src/Imprint.Authoring/Features/Blocks/UpdateBlockFromInstance/UpdateBlockFromInstanceHandler.cs
DM10 · One operation mutates 2 aggregates: CreateSiteFromTemplateHandler.Handle src/Imprint.Authoring/Features/Sites/CreateSiteFromTemplate/CreateSiteFromTemplateHandler.cs
DM10 · One operation mutates 2 aggregates: SeedLocaleHandler.Handle src/Imprint.Authoring/Features/Sites/SeedLocale/SeedLocaleHandler.cs
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.
~8501 LoC unreachable (46 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~2.0 person-years of build effort (about ~€290,000 to rebuild). Its weakest lens is Code Health at 42% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Very high (×1.8) — service/app, CQRS, domain model, event sourcing, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. 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.
1
Resolve the 1 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~2.0 person-years to rebuild), and its weakest lens is Code Health at 42%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Code Health first — highest risk-reduction per euro on an asset this size.
The top fix pays for itself · High · Economics
The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 20.1–120.6 engineer-days every year, paid as drag on the ~358,763 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–2 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 2–5% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 88,462 line(s) changed over a 90-day window ⇒ ~358,763/year · D1/D2/D4/D6 code quality: averaging 7.1/10 ⇒ a 2–5% drag on each change · top-ranked remediation: Low effort ⇒ about 1–3 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 2 months.
Root cause: an un-encapsulated domain · Medium · Root cause
16 findings across public setters, anemic types and primitive ids share one root cause — the domain layer doesn't protect its own invariants. Fixing the encapsulation pattern resolves them together, rather than chasing each finding.
→ Address encapsulation as one pattern (private setters + behaviour + strongly-typed ids), not 100 separate findings.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 7.1/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 2–5% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4/D6 code quality: averaging 7.1/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
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
116 modules, 303 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. 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.)
At a glance — Code Health · 42% · Weak · gated by R1, R2, R7
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
4
High / Critical
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
1 of the 47 unreached modules is an entry point — something executes or loads it by path at run time, so no import specifier addresses it and no public entry publishes it. An importing test cannot be written for it as it ships, and two different things are worth doing here — they are not the same thing. To EXERCISE it, a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make it addressable: lift the logic into a module a test can import and leave the entry point a thin shim over it, or put its body behind a main-guard (`import.meta.url === argv[1]`) and export it. Add tests that import the other 46 — directly or through their public entry.
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Test Quality: No assertions: ChangeNodeProps_unknown_node_is_rejected
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. 95 of 99 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 99 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 552 of 581 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
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 (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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.
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.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
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".
The LLM boundary
LLM-set scores this run (5): D19, D21, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
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.
54 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AuthoringApi.MapAuthoringApi at 212. A further 14 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 BlockMapper.Map at 28 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Imprint.Authoring/Domain/Sites/Site.cs (Site.When at 23), src/Imprint.Authoring/Domain/Pages/Page.cs (Page.When at 19), src/Imprint.Authoring/Domain/Assets/Asset.cs (Asset.When at 18), src/Imprint.Rendering/NodeTypeNames.cs (NodeTypeNames.Of at 18), src/Imprint.Publishing/SitePreview.cs (SitePreview.ContentTypeOf at 17), and 3 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.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 render (cyclomatic 19) finding(s) in Cyclomatic Complexity — start with cai-trend.js (2), cai-score-card.js (2). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 render (cyclomatic 48) finding(s) in Cyclomatic Complexity — start with cai-dimensions.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 render (cyclomatic 28) finding(s) in Cyclomatic Complexity — start with contact-form.js (2). — One of this dimension's main actionable groups (2 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.
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.
+ 65 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 render (cognitive 19) finding(s) in Cognitive Complexity — start with cai-survey-list.js (2), cai-trend.js. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 render (cognitive 16) finding(s) in Cognitive Complexity — start with cai-lens-gauges.js, cai-language-support.js, cai-language-board.js. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 render (cognitive 21) finding(s) in Cognitive Complexity — start with cai-trend.js, cai-score-card.js. — One of this dimension's main actionable groups (2 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 Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 6 TooManyMethods finding(s) in God Classes — start with SitePublisher.cs, ImprintAuthoringMcpTools.cs, Page.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 FileTooLong finding(s) in God Classes — start with AuthoringApi.cs, SitePublisher.cs, ImprintAuthoringMcpTools.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with AuthoringApi.cs, Verify.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
51 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.7 / 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.
1322 test methods: 1287 unit, 0 integration, 0 BDD, 35 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality6.5 / 10Adequate✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 308 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1322 tests.
No assertions: UploadDarkVariant_on_ready_degraded_base_is_accepted · ×308tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:79
What to do
Resolve the 308 No assertions finding(s) in Test Quality — start with SiteChromeTests.cs (26), PageAddNodeTests.cs (23), AssetDarkVariantTests.cs (22). — One of this dimension's main actionable groups (308 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: src/Imprint.Editor/Api/AuthoringApi.cs (25×212=5300); src/Imprint.Publishing/SitePublisher.cs (32×17=544); src/Imprint.Authoring/Domain/Sites/Site.cs (15×23=345) Repeated repair below the complexity floor: src/Imprint.Editor/Components/Pages/PostEditor.razor (5 of 9 changes were fixes); src/Imprint.Authoring/Syndication/SyndicatedPath.cs (3 of 4 changes were fixes); src/Imprint.Media/SvgSanitizer.cs (3 of 4 changes were fixes)
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.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
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.
Clear, complete, and well-structured documentation for an event-sourced domain-driven CMS. The README is a strong narrative describing the three architectural styles and the projection idea, with a detailed What-you-get list plus quickstart (data on first run). A dedicated publishing-and-delivery specification covers output layout, the HTML contract verified by tests, the machine layer (`llms.txt`), theme→CSS mapping, publish manifest, and *.br/*.gz precompressed siblings. The Site scorecard tool is documented as a reproducible quality measure that does not reward bad prose, with a rubric table and an independent 'Result — 2026-08-01' benchmark. A domain-model specification enumerates aggregates, events, node types, and invariants with conventions (C# `record` types under `Imprint.Authoring.Domain`, stable-name serialization) enforced by the analyzer. The deployment runbook maps the estate topology to each layer (Keycloak, blue/green editor, reverse-proxy vhosts). A dedicated Editor UX specification describes layout, selection model, drag and drop, inline text editing, keyboard mapping, panels, publish UX, and JS interop architecture. Conventions are a standalone file covering .NET 10, central package management, no reflection magic beyond sanctioned scans, scoped namespaces, XML docs on every public type in `Imprint.EventSourcing`, and naming rules for commands/events/projections/slices. Imprint's architecture document is exemplary: it states the three styles (DDD, event sourcing, vertical slices), explains the one-sentence projection model, and maps two planes with a clipped Events table. The companion Watchdog surveyor doc is also top-notch — it defines CAI determinism, multi-language coverage, and the neutral-measurer guarantee while laying out key facts like depth-gated CAI and model-aware lens detection. A third proposal document (theme-aware media variants plus widget request/approval) is present but clipped mid-table, so its outline sections are not flagged as missing.
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.
1 naming inconsistencies across 200 sampled symbols.
The parameter name 'Node Copy' contains a space, which is non-standard for C# identifiers and likely a typo or copy-paste artifact. It refers to the same concept as the type 'Node' or a copy of it.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment Value / 10Exemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
62 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
5 finding(s): 0 critical, 1 high, 4 medium, 0 low. 1 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 123 file(s) — `src/Imprint.Authoring/Domain/Pages/Page.cs` (line 510), `src/Imprint.Authoring/Domain/Sites/Site.cs` (line 198, line 199), `src/Imprint.Authoring/Features/Assets/DeleteAsset/DeleteAssetHandler.cs` (lines 7–9, line 10), `src/Imprint.Authoring/Features/Assets/ProcessAssetDarkVariant/ProcessAssetDarkVariantHandler.cs` (lines 6–7, line 8), `src/Imprint.Authoring/Features/Assets/ProcessUploadedAsset/AssetProcessingWorker.cs` (lines 17–20, line 21), … (+118 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 108 of those file(s) — `src/Imprint.Authoring/Features/Assets/DeleteAsset/DeleteAssetHandler.cs`, `src/Imprint.Authoring/Features/Assets/ProcessAssetDarkVariant/ProcessAssetDarkVariantHandler.cs`, `src/Imprint.Authoring/Features/Assets/ProcessUploadedAsset/AssetProcessingWorker.cs`, `src/Imprint.Authoring/Features/Assets/ProcessUploadedAsset/ProcessUploadedAssetHandler.cs`, `src/Imprint.Authoring/Features/Assets/RemoveAssetDarkVariant/RemoveAssetDarkVariantHandler.cs`, … (+103 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 8 of those file(s) — `src/Imprint.Authoring/Features/Sites/CreateSiteFromTemplate/SiteTemplates.cs`, `src/Imprint.Authoring/Projections/ContentUsage.cs`, `src/Imprint.Editor/Services/EditorContent.cs`, `src/Imprint.EventSourcing/Exceptions.cs`, `src/Imprint.Media/DiskMediaStore.cs`, … (+3 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.
High: github-actions-mutable-action-tag.github/workflows/deploy.yml:43detected by semgrep finding
Medium: raw-html-format · ×3widgets/_src/cai-evidence-flow.js:59detected by semgrep finding
What to do
Resolve the 1 High finding(s) in Static Analysis (SAST) — start with deploy.yml. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium finding(s) in Static Analysis (SAST) — start with cai-evidence-flow.js (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 102 of the 312 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Workflow token permissions not restricted finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance 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?
D39 · IL Efficiency9.8 / 10Exemplary✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
17 of 2252 first-party methods have an oversized IL body.
IL efficiency: 17 authored method(s) exceed the IL budgetsrc/Imprint.Editor/Api/AuthoringNodeJson.cs:386
✓ On the Gold path — maintain.
Detailed fixes: d39_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.2 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — VideoView.razor:9
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels7.5 / 10Strong✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×4) — InsertPicker.razor:20, NodeToolbar.razor:45, AdminWidgets.razor:86, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — Canvas.razor:21
The repo's own CSS styles .locale-row with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — LocaleManager.razor:20
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge.
What to do
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`PublisherStatus` is a singleton (one shared instance) but mutates instance state outside any lock (Last; e.g. `Last` at line 17). — PublisherStatus.cs:9
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM10 · One transaction, one aggregate9.6 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
`DefineBlockFromNodeHandler.Handle` saves `BlockDefinition`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — DefineBlockFromNodeHandler.cs:16
`UpdateBlockFromInstanceHandler.Handle` saves `BlockDefinition`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — UpdateBlockFromInstanceHandler.cs:9
`CreateSiteFromTemplateHandler.Handle` saves `Site`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — CreateSiteFromTemplateHandler.cs:15
`SeedLocaleHandler.Handle` saves `Site`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — SeedLocaleHandler.cs:22
What to do
Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`Asset.OriginalStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Asset.cs:29
`Asset.DerivedStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Asset.cs:34
`Asset.DarkOriginalStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Asset.cs:40
`Asset.DarkDerivedStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Asset.cs:46
`Asset.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Asset.cs:60
`BlockDefinition.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BlockDefinition.cs:29
`Page.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Page.cs:40
`Post.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Post.cs:68
`Site.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Site.cs:113
`WidgetSubmission.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — WidgetSubmission.cs:38
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`Asset` is an aggregate/entity with 20 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Asset.cs:12
`BlockDefinition` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlockDefinition.cs:11
`Page` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Page.cs:11
`Post` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Post.cs:25
`Site` is an aggregate/entity with 23 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Site.cs:13
`WidgetSubmission` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — WidgetSubmission.cs:15
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
`PublishPost.PublishPostHandler.Handle` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — PublishPostHandler.cs:14
What to do
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
Other · Event Sourcing — Whether Apply/When folds reconstruct state purely from the event (no DateTime.Now, Guid.NewGuid, Random or IO) so replay is reproducible.
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.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 15 of 15 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record 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).
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.
README advertises Docker containerisation, but no Dockerfile/compose file exists
What to do
Reconcile the README with reality: README advertises Docker containerisation, but no Dockerfile/compose file exists.
Only 6/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
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
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 15 use(s) across 25,492 production line(s) (~0.6/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock, and, where the code is a reusable library, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 47 plain JS — the untyped files are tools/mobile-sweep.js, widgets/_src/cai-band-scale.js, widgets/_src/cai-c4-heat.js, widgets/_src/cai-calculator.js, widgets/_src/cai-card-gallery.js, widgets/_src/cai-composition-bar.js (+41 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
widgets/_src/cai-calculator.js:133 · widgets/_src/cai-verifier.js:80 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — cai-calculator.js:133
widgets/_src/cai-band-scale.js:41 · widgets/_src/cai-composition-bar.js:71 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cai-band-scale.js:41
widgets/_src/cai-language-board.js:221 · widgets/_src/cai-survey-list.js:206 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — cai-language-board.js:221
widgets/_src/cai-survey-list.js:90 · widgets/_src/cai-trend.js:137 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cai-survey-list.js:90
widgets/_src/cai-calculator.js:98 · widgets/_src/cai-report-index.js:75 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cai-calculator.js:98
widgets/_src/cai-lens-gauges.js:49 · widgets/_src/cai-link-cards.js:78 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — cai-lens-gauges.js:49
widgets/_src/cai-report-index.js:75 · widgets/_src/cai-verifier.js:51 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cai-report-index.js:75
widgets/_src/cai-c4-heat.js:165 · widgets/_src/cai-findings.js:172 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — cai-c4-heat.js:165
widgets/_src/cai-language-board.js:197 · widgets/_src/cai-trend.js:238 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — cai-language-board.js:197
widgets/_src/cai-evidence-flow.js:44 · widgets/_src/cai-lens-gauges.js:42 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — cai-evidence-flow.js:44
widgets/_src/cai-report-index.js:172 · widgets/cai-report-index.js:145 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — cai-report-index.js:172
widgets/_src/cai-calculator.js:190 · widgets/cai-calculator.js:206 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — cai-calculator.js:190
widgets/_src/cai-dimensions.js:137 · widgets/_src/live.js:245 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — cai-dimensions.js:137
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×20) — cai-dimensions.js:192, cai-dimensions.js:173, scorecard.js:130, …
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 47 production file(s) reachable from 0 test file(s) via the import graph
What to do
1 of the 47 unreached modules is an entry point — something executes or loads it by path at run time, so no import specifier addresses it and no public entry publishes it. An importing test cannot be written for it as it ships, and two different things are worth doing here — they are not the same thing. To EXERCISE it, a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make it addressable: lift the logic into a module a test can import and leave the entry point a thin shim over it, or put its body behind a main-guard (`import.meta.url === argv[1]`) and export it. Add tests that import the other 46 — directly or through their public entry.
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 1 application, 1 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (widgets/_src/cai-band-scale.js, widgets/_src/cai-card-gallery.js, widgets/_src/cai-language-board.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — scorecard.js
no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×36) — cai-language-board.js, cai-dimensions.js, cai-language-board.js, …
no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (widgets/_src/cai-band-scale.js, widgets/_src/cai-c4-heat.js, widgets/_src/cai-card-gallery.js and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — live.js
no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 20 in-repo import(s) from 20 other file(s) do name it (widgets/_src/cai-band-scale.js, widgets/_src/cai-c4-heat.js, widgets/_src/cai-calculator.js and 17 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — tokens.js
7 further occurrence(s) are not listed individually; the score already reflects all 47.
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. Deterministic, provable per finding. Advisory.
`pending` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `ExecuteAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var pending = …;`), which releases it at the end of the scope on every path including a throw. — PublisherHostedService.cs:36
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 173/205 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×32) — EditorActor.cs:54, SiteAccess.cs:27, SiteAccess.cs:30, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.8 `!` suppressions per 1k syntax nodes — 109 suppression(s) across the 135067 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 3 observation(s) recorded · Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — 1 observation(s) recorded · Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Not included — 42 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.
AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
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 dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — no coverage collector is wired up
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution (Roslyn), which the neutral model does not carry
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 event handler(s); 76 CQRS handler(s)
ES2 Immutable events — no persisted event types detected — immutability check not applicable
ES3 PII in the event store — no persisted event types detected — PII-in-events check not applicable
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P7 Outbound HTTP resilience — no outbound HTTP usage detected
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X8 JS interop contract — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X9 Subsumed condition operand — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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.
Issue — 10 finding(s)
AC2 · Forms & labels· <input> without a programmatic label · ×3
<input> without a programmatic label src/Imprint.Editor/Components/Editor/InsertPicker.razor:20— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/Imprint.Editor/Components/Editor/NodeToolbar.razor:45— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/Imprint.Editor/Components/Pages/AdminWidgets.razor:86— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
WriteOnlyPrivateField tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:47— private DarkSvgSanitized DarkSvg — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField tools/ContentSeeder/CmsModel.cs:32— private JsonSerializerOptions Json — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label src/Imprint.Editor/Components/Pages/PostEditor.razor:146— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> src/Imprint.Editor/Components/Editor/Canvas.razor:21— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×1
Clickable element isn't keyboard-operable src/Imprint.Editor/Components/Panels/Pages/LocaleManager.razor:20— The repo's own CSS styles .locale-row with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AnalyzerSeverityNone .editorconfig:24— XUNIT1051 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why in a comment above the entry: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
High: github-actions-mutable-action-tag .github/workflows/deploy.yml:43— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
No assertions: UploadDarkVariant_on_ready_degraded_base_is_accepted tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:79— Test method exercises code but verifies nothing — add an assertion.
No assertions: UploadDarkVariant_before_the_base_is_processed_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:87— Test method exercises code but verifies nothing — add an assertion.
No assertions: UploadDarkVariant_on_a_video_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:94— Test method exercises code but verifies nothing — add an assertion.
No assertions: UploadDarkVariant_on_a_file_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:101— Test method exercises code but verifies nothing — add an assertion.
No assertions: UploadDarkVariant_with_a_mismatched_kind_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:108— Test method exercises code but verifies nothing — add an assertion.
No assertions: UploadDarkVariant_on_a_deleted_asset_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:130— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkImageVariants_with_no_variants_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:152— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkImageVariants_on_a_vector_dark_variant_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:159— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkImageVariants_without_a_pending_variant_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:166— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkImageVariants_when_dark_already_ready_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:173— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkSvg_with_negative_removed_nodes_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:195— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkSvg_on_an_image_dark_variant_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:202— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkSvg_without_a_pending_variant_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:209— Test method exercises code but verifies nothing — add an assertion.
No assertions: FailDarkVariant_without_reason_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:233— Test method exercises code but verifies nothing — add an assertion.
No assertions: FailDarkVariant_without_a_pending_variant_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:242— Test method exercises code but verifies nothing — add an assertion.
No assertions: FailDarkVariant_when_dark_already_ready_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:249— Test method exercises code but verifies nothing — add an assertion.
No assertions: RemoveDarkVariant_while_still_pending_is_accepted tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:272— Test method exercises code but verifies nothing — add an assertion.
No assertions: RemoveDarkVariant_when_none_exists_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:279— Test method exercises code but verifies nothing — add an assertion.
No assertions: RemoveDarkVariant_on_a_deleted_asset_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:286— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkImageVariants_on_a_deleted_asset_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:295— Test method exercises code but verifies nothing — add an assertion.
No assertions: CompleteDarkSvg_on_a_deleted_asset_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:302— Test method exercises code but verifies nothing — add an assertion.
No assertions: FailDarkVariant_on_a_deleted_asset_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetDarkVariantTests.cs:309— Test method exercises code but verifies nothing — add an assertion.
No assertions: SetAlt_over_500_characters_is_rejected tests/Imprint.Authoring.Tests/Domain/Assets/AssetEditingTests.cs:40— Test method exercises code but verifies nothing — add an assertion.
No assertions: SetAlt_at_500_characters_is_accepted tests/Imprint.Authoring.Tests/Domain/Assets/AssetEditingTests.cs:47— Test method exercises code but verifies nothing — add an assertion.
No assertions: Rename_to_unchanged_name_raises_nothing tests/Imprint.Authoring.Tests/Domain/Assets/AssetEditingTests.cs:67— Test method exercises code but verifies nothing — add an assertion.
Hotspot: src/Imprint.Editor/Api/AuthoringApi.cs src/Imprint.Editor/Api/AuthoringApi.cs:88— src/Imprint.Editor/Api/AuthoringApi.cs changed 25 times in last 90 days, max cyclomatic complexity 212 in AuthoringApi.MapAuthoringApi at line 88. 6 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Editor/Api/AuthoringApi.cs`: 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: src/Imprint.Publishing/SitePublisher.cs src/Imprint.Publishing/SitePublisher.cs:502— src/Imprint.Publishing/SitePublisher.cs changed 32 times in last 90 days, max cyclomatic complexity 17 in Pass.PlanPages at line 502. 10 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-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Publishing/SitePublisher.cs`: 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: src/Imprint.Authoring/Domain/Sites/Site.cs src/Imprint.Authoring/Domain/Sites/Site.cs:775— src/Imprint.Authoring/Domain/Sites/Site.cs changed 15 times in last 90 days, max cyclomatic complexity 23 in Site.When at line 775. 1 of those changes was a fix/bug commit, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Authoring/Domain/Sites/Site.cs`: 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: tools/ContentSeeder/BlockMapper.cs tools/ContentSeeder/BlockMapper.cs:37— tools/ContentSeeder/BlockMapper.cs changed 11 times in last 90 days, max cyclomatic complexity 28 in BlockMapper.Map at line 37. 1 of those changes was a fix/bug commit, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- tools/ContentSeeder/BlockMapper.cs`: 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: tools/ContentSeeder/Migrator.cs tools/ContentSeeder/Migrator.cs:56— tools/ContentSeeder/Migrator.cs changed 9 times in last 90 days, max cyclomatic complexity 24 in Migrator.MigrateSite at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- tools/ContentSeeder/Migrator.cs`: 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: widgets/cai-card-gallery.js widgets/cai-card-gallery.js:122— widgets/cai-card-gallery.js changed 8 times in last 90 days, max cyclomatic complexity 26 in z at line 122. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/cai-card-gallery.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/cai-score-card.js widgets/cai-score-card.js:117— widgets/cai-score-card.js changed 7 times in last 90 days, max cyclomatic complexity 26 in H at line 117. 3 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/cai-score-card.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Imprint.Editor/Api/AuthoringNodeJson.cs src/Imprint.Editor/Api/AuthoringNodeJson.cs:384— src/Imprint.Editor/Api/AuthoringNodeJson.cs changed 5 times in last 90 days, max cyclomatic complexity 34 in AuthoringNodeJson.ApplyProps at line 384. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Editor/Api/AuthoringNodeJson.cs`: 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: tools/ContentSeeder/Verify.cs tools/ContentSeeder/Verify.cs:19— tools/ContentSeeder/Verify.cs changed 5 times in last 90 days, max cyclomatic complexity 29 in Verify.Run at line 19. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- tools/ContentSeeder/Verify.cs`: 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: tools/ContentSeeder/Program.cs tools/ContentSeeder/Program.cs:345— tools/ContentSeeder/Program.cs changed 9 times in last 90 days, max cyclomatic complexity 16 in Args.Parse at line 345. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- tools/ContentSeeder/Program.cs`: 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: widgets/_src/cai-dimensions.js widgets/_src/cai-dimensions.js:192— widgets/_src/cai-dimensions.js changed 4 times in last 90 days, max cyclomatic complexity 35 in render at line 192. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/_src/cai-dimensions.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Imprint.Authoring/Domain/Pages/Page.cs src/Imprint.Authoring/Domain/Pages/Page.cs:462— src/Imprint.Authoring/Domain/Pages/Page.cs changed 7 times in last 90 days, max cyclomatic complexity 19 in Page.When at line 462. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Authoring/Domain/Pages/Page.cs`: 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: widgets/_src/live.js widgets/_src/live.js:64— widgets/_src/live.js changed 7 times in last 90 days, max cyclomatic complexity 18 in cardFromGallery at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/_src/live.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/cai-findings.js widgets/cai-findings.js:143— widgets/cai-findings.js changed 6 times in last 90 days, max cyclomatic complexity 20 in #r at line 143. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/cai-findings.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/cai-dimensions.js widgets/cai-dimensions.js:173— widgets/cai-dimensions.js changed 3 times in last 90 days, max cyclomatic complexity 35 in render at line 173. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/cai-dimensions.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Imprint.Editor/wwwroot/js/canvas-interop.js src/Imprint.Editor/wwwroot/js/canvas-interop.js:275— src/Imprint.Editor/wwwroot/js/canvas-interop.js changed 6 times in last 90 days, max cyclomatic complexity 16 in onKeyDown at line 275. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Editor/wwwroot/js/canvas-interop.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/_src/cai-score-card.js widgets/_src/cai-score-card.js:72— widgets/_src/cai-score-card.js changed 5 times in last 90 days, max cyclomatic complexity 19 in render at line 72. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/_src/cai-score-card.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/cai-language-support.js widgets/cai-language-support.js:158— widgets/cai-language-support.js changed 5 times in last 90 days, max cyclomatic complexity 16 in render at line 158. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/cai-language-support.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/_src/cai-findings.js widgets/_src/cai-findings.js:107— widgets/_src/cai-findings.js changed 4 times in last 90 days, max cyclomatic complexity 20 in #repoHtml at line 107. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/_src/cai-findings.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Imprint.Authoring/Domain/Assets/Asset.cs src/Imprint.Authoring/Domain/Assets/Asset.cs:328— src/Imprint.Authoring/Domain/Assets/Asset.cs changed 4 times in last 90 days, max cyclomatic complexity 18 in Asset.When at line 328. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Authoring/Domain/Assets/Asset.cs`: 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: widgets/_src/cai-survey-list.js widgets/_src/cai-survey-list.js:92— widgets/_src/cai-survey-list.js changed 4 times in last 90 days, max cyclomatic complexity 17 in render at line 92. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/_src/cai-survey-list.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widgets/cai-survey-list.js widgets/cai-survey-list.js:268— widgets/cai-survey-list.js changed 4 times in last 90 days, max cyclomatic complexity 17 in render 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-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/cai-survey-list.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs:105— src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs changed 4 times in last 90 days, max cyclomatic complexity 17 in CanonicalHtml.ParseInlineUntil at line 105. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs`: 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: widgets/_src/cai-language-support.js widgets/_src/cai-language-support.js:148— widgets/_src/cai-language-support.js changed 4 times in last 90 days, max cyclomatic complexity 16 in render 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-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- widgets/_src/cai-language-support.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Imprint.Rendering/NodeTypeNames.cs src/Imprint.Rendering/NodeTypeNames.cs:13— src/Imprint.Rendering/NodeTypeNames.cs changed 3 times in last 90 days, max cyclomatic complexity 18 in NodeTypeNames.Of at line 13. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Rendering/NodeTypeNames.cs`: 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.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:111— src/Imprint.Editor/Api/AuthoringApi.cs:111-115 | src/Imprint.Editor/Api/AuthoringApi.cs:180-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:323— src/Imprint.Editor/Api/AuthoringApi.cs:323-327 | src/Imprint.Editor/Api/AuthoringApi.cs:351-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:323` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Imprint.Editor/Api/AuthoringApi.cs:356` calls `IsNullOrWhiteSpace`, `BadRequest` and `src/Imprint.Editor/Api/AuthoringApi.cs:328` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:371— src/Imprint.Editor/Api/AuthoringApi.cs:371-375 | src/Imprint.Editor/Api/AuthoringApi.cs:390-394 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:371` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:389— src/Imprint.Editor/Api/AuthoringApi.cs:389-393 | src/Imprint.Editor/Api/AuthoringApi.cs:447-451 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:389` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:842— src/Imprint.Editor/Api/AuthoringApi.cs:842-846 | src/Imprint.Editor/Api/AuthoringApi.cs:910-914 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:842` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/Imprint.Editor/Components/Panels/Inspector/AssetPicker.razor:71— src/Imprint.Editor/Components/Panels/Inspector/AssetPicker.razor:71-75 | src/Imprint.Editor/Components/Posts/PostMediaShelf.razor:269-273 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Components/Panels/Inspector/AssetPicker.razor:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:1683— src/Imprint.Editor/Api/AuthoringApi.cs:1683-1687 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:1151-1155 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:1690— src/Imprint.Editor/Api/AuthoringApi.cs:1690-1694 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:1158-1162 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
TooManyMethods: Pass src/Imprint.Publishing/SitePublisher.cs— TooManyMethods — 932 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. The bar is 30 methods; this is 42 over it, 2.40× 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: ImprintAuthoringMcpTools src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs— TooManyMethods — 813 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Page src/Imprint.Authoring/Domain/Pages/Page.cs— TooManyMethods — 369 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BlockMapper tools/ContentSeeder/BlockMapper.cs— TooManyMethods — 588 significant lines (blank, comment-only and punctuation-only lines excluded), 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.
TooManyMethods: AuthoringApi src/Imprint.Editor/Api/AuthoringApi.cs— TooManyMethods — 904 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Site src/Imprint.Authoring/Domain/Sites/Site.cs— TooManyMethods — 362 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (6 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:609— src/Imprint.Editor/Api/AuthoringApi.cs:609-614 | src/Imprint.Editor/Api/AuthoringApi.cs:805-810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:609` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:712— src/Imprint.Editor/Api/AuthoringApi.cs:712-717 | src/Imprint.Editor/Api/AuthoringApi.cs:729-734 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:712` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:425— src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:425-430 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:442-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:425` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) tools/ContentSeeder/Migrator.cs:231— tools/ContentSeeder/Migrator.cs:231-236 | tools/ContentSeeder/Migrator.cs:259-264 — 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) src/Imprint.Authoring/Features/Pages/ChangeSlug/ChangeSlug.cs:9— src/Imprint.Authoring/Features/Pages/ChangeSlug/ChangeSlug.cs:9-14 | src/Imprint.Authoring/Features/Posts/ChangePostSlug/ChangePostSlug.cs:9-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:1378— src/Imprint.Editor/Api/AuthoringApi.cs:1378-1383 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:1202-1207 — 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.
Anemic entity: Asset src/Imprint.Authoring/Domain/Assets/Asset.cs:12— `Asset` is an aggregate/entity with 20 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: BlockDefinition src/Imprint.Authoring/Domain/Blocks/BlockDefinition.cs:11— `BlockDefinition` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Page src/Imprint.Authoring/Domain/Pages/Page.cs:11— `Page` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Post src/Imprint.Authoring/Domain/Posts/Post.cs:25— `Post` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Site src/Imprint.Authoring/Domain/Sites/Site.cs:13— `Site` is an aggregate/entity with 23 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: WidgetSubmission src/Imprint.Authoring/Domain/Widgets/WidgetSubmission.cs:15— `WidgetSubmission` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
render (cyclomatic 19) widgets/cai-trend.js:258— render has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to 5 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 19) widgets/cai-score-card.js:221— render has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 19) widgets/_src/cai-trend.js:139— render has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to 5 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 19) widgets/_src/cai-score-card.js:72— render has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
FileTooLong: Api/AuthoringApi.cs src/Imprint.Editor/Api/AuthoringApi.cs— FileTooLong — 999 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 499 over it, 2.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Imprint.Publishing/SitePublisher.cs src/Imprint.Publishing/SitePublisher.cs— FileTooLong — 986 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 486 over it, 1.97× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Mcp/ImprintAuthoringMcpTools.cs src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs— FileTooLong — 867 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 367 over it, 1.73× 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: ContentSeeder/BlockMapper.cs tools/ContentSeeder/BlockMapper.cs— FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 93 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.
DM10 · One transaction, one aggregate· One operation mutates 2 aggregates · ×4
One operation mutates 2 aggregates: DefineBlockFromNodeHandler.Handle src/Imprint.Authoring/Features/Blocks/DefineBlockFromNode/DefineBlockFromNodeHandler.cs:16— `DefineBlockFromNodeHandler.Handle` saves `BlockDefinition`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: UpdateBlockFromInstanceHandler.Handle src/Imprint.Authoring/Features/Blocks/UpdateBlockFromInstance/UpdateBlockFromInstanceHandler.cs:9— `UpdateBlockFromInstanceHandler.Handle` saves `BlockDefinition`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: CreateSiteFromTemplateHandler.Handle src/Imprint.Authoring/Features/Sites/CreateSiteFromTemplate/CreateSiteFromTemplateHandler.cs:15— `CreateSiteFromTemplateHandler.Handle` saves `Site`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: SeedLocaleHandler.Handle src/Imprint.Authoring/Features/Sites/SeedLocale/SeedLocaleHandler.cs:22— `SeedLocaleHandler.Handle` saves `Site`, `Page` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
Repeated repair: src/Imprint.Editor/Components/Pages/PostEditor.razor src/Imprint.Editor/Components/Pages/PostEditor.razor— src/Imprint.Editor/Components/Pages/PostEditor.razor changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10, UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(posts): opening a post is not editing it, and a reviewer may open theirs”; “fix(posts): a preview link that resolves, and panes you can resize”; “fix(posts): the preview could not be scrolled, because the scroller was inert”; “fix(posts): tags you can see, and an upload that is never unfiled”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Editor/Components/Pages/PostEditor.razor`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Imprint.Authoring/Syndication/SyndicatedPath.cs src/Imprint.Authoring/Syndication/SyndicatedPath.cs:33— src/Imprint.Authoring/Syndication/SyndicatedPath.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is SyndicatedPath.Sanitize at line 33), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(syndication): the rejection message states the depth actually enforced”; “fix(syndication): a nested namespace needs room to be a path”; “fix(syndication): a locale can only shadow the FIRST segment of a path”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Authoring/Syndication/SyndicatedPath.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Imprint.Media/SvgSanitizer.cs src/Imprint.Media/SvgSanitizer.cs:130— src/Imprint.Media/SvgSanitizer.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is SvgSanitizer.SanitizeElement at line 130), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(security): close SVG integration-point XSS + block-override XSS; harden undo/dup/staleness”; “fix(security): validate node content at every entry point + SVG case-insensitivity”; “fix(security): harden SVG sanitization, publish guard, media serving, color validation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-07..2026-09-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-07 08:50:05 +02:00' --until='2026-09-05 08:50:05 +02:00' --full-history --no-merges -- src/Imprint.Media/SvgSanitizer.cs`: 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.
render (cognitive 19) widgets/cai-trend.js:258— render has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 19) widgets/cai-survey-list.js:268— render has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 19) widgets/_src/cai-survey-list.js:92— render has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 16) widgets/cai-lens-gauges.js:235— render has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 16) widgets/cai-language-support.js:158— render has cognitive complexity 16 (threshold 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.
render (cognitive 16) widgets/cai-language-board.js:284— render has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Medium: raw-html-format widgets/_src/cai-evidence-flow.js:59— User data flows into the host portion of this manually-constructed HTML. This can introduce a Cross-Site-Scripting (XSS) vulnerability if this comes from user-provided input. Consider using a sanitization library such as DOMPurify to sanitize the HTML within.
Medium: raw-html-format widgets/_src/cai-evidence-flow.js:66— User data flows into the host portion of this manually-constructed HTML. This can introduce a Cross-Site-Scripting (XSS) vulnerability if this comes from user-provided input. Consider using a sanitization library such as DOMPurify to sanitize the HTML within.
Medium: raw-html-format widgets/cai-evidence-flow.js:144— User data flows into the host portion of this manually-constructed HTML. This can introduce a Cross-Site-Scripting (XSS) vulnerability if this comes from user-provided input. Consider using a sanitization library such as DOMPurify to sanitize the HTML within.
Duplicated block (11 lines × 2) src/Imprint.Authoring/Features/Pages/PublishAllStale/PublishAllStaleHandler.cs:29— src/Imprint.Authoring/Features/Pages/PublishAllStale/PublishAllStaleHandler.cs:29-44 | src/Imprint.Authoring/Features/Sites/SeedLocale/SeedLocaleHandler.cs:49-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Authoring/Features/Pages/PublishAllStale/PublishAllStaleHandler.cs:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) tools/ContentSeeder/BlockMapper.cs:492— tools/ContentSeeder/BlockMapper.cs:492-502 | tools/ContentSeeder/BlockMapper.cs:905-915 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:492` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) tools/ContentSeeder/BlockMapper.cs:872— tools/ContentSeeder/BlockMapper.cs:872-882 | tools/ContentSeeder/BlockMapper.cs:915-925 — 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) src/Imprint.Editor/Api/AuthoringApi.cs:403— src/Imprint.Editor/Api/AuthoringApi.cs:403-411 | src/Imprint.Editor/Api/AuthoringApi.cs:433-441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:403` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:543— src/Imprint.Editor/Api/AuthoringApi.cs:543-551 | src/Imprint.Editor/Api/AuthoringApi.cs:581-589 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:543` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Imprint.Editor/Components/Pages/SiteSettings.razor:841— src/Imprint.Editor/Components/Pages/SiteSettings.razor:841-849 | src/Imprint.Editor/Components/Pages/SiteSettings.razor:869-877 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Components/Pages/SiteSettings.razor:841` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Imprint.Editor/Components/Pages/SiteSettings.razor:839` calls `foreach` and `src/Imprint.Editor/Components/Pages/SiteSettings.razor:867` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:151— src/Imprint.Editor/Api/AuthoringApi.cs:151-158 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:127-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/Imprint.Editor/Api/AuthoringApi.cs:743— src/Imprint.Editor/Api/AuthoringApi.cs:743-750 | src/Imprint.Editor/Api/AuthoringApi.cs:774-781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:743` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472— src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472-479 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:508-515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) src/Imprint.Editor/Api/AuthoringApi.cs:111— src/Imprint.Editor/Api/AuthoringApi.cs:111-116 | src/Imprint.Editor/Api/AuthoringApi.cs:743-749 | src/Imprint.Editor/Api/AuthoringApi.cs:774-780 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) src/Imprint.Editor/Api/AuthoringApi.cs:535— src/Imprint.Editor/Api/AuthoringApi.cs:535-540 | src/Imprint.Editor/Api/AuthoringApi.cs:573-578 | src/Imprint.Editor/Api/AuthoringApi.cs:633-638 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:535` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 3) src/Imprint.Editor/Api/AuthoringApi.cs:534— src/Imprint.Editor/Api/AuthoringApi.cs:534-539 | src/Imprint.Editor/Api/AuthoringApi.cs:572-577 | src/Imprint.Editor/Api/AuthoringApi.cs:742-747 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:534` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Dead file (~221 LoC) widgets/_src/contact-form.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~221 LoC) widgets/cai-calculator.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~221 LoC) widgets/cai-score-card.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
render (cyclomatic 48) widgets/cai-dimensions.js:173— render has cyclomatic complexity 48 (threshold 15). Of this number, 35 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 48) widgets/_src/cai-dimensions.js:192— render has cyclomatic complexity 48 (threshold 15). Of this number, 35 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 28) widgets/contact-form.js:152— render has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 28) widgets/_src/contact-form.js:90— render has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
paint (cyclomatic 24) widgets/cai-survey-list.js:268— paint has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
paint (cyclomatic 24) widgets/_src/cai-survey-list.js:182— paint has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 18) widgets/cai-survey-list.js:268— render has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 18) widgets/_src/cai-survey-list.js:92— render has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 17) widgets/cai-language-board.js:284— render has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 17) widgets/_src/cai-language-board.js:136— render has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
paint (cyclomatic 17) widgets/cai-language-board.js:284— paint has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
paint (cyclomatic 17) widgets/_src/cai-language-board.js:201— paint has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 7 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 16) widgets/cai-language-support.js:158— render has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cyclomatic 16) widgets/_src/cai-language-support.js:148— render has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
render (cognitive 21) widgets/_src/cai-trend.js:139— render has cognitive complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 21) widgets/_src/cai-score-card.js:72— render has cognitive complexity 21 (threshold 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.
render (cognitive 20) widgets/_src/cai-language-support.js:148— render has cognitive complexity 20 (threshold 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.
render (cognitive 20) widgets/_src/cai-language-board.js:136— render has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: AuthoringApi.MapAuthoringApi src/Imprint.Editor/Api/AuthoringApi.cs:88— MethodTooLong — MapAuthoringApi runs 586 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 486 over it, 5.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Verify.Run tools/ContentSeeder/Verify.cs:19— MethodTooLong — Run runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472— src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472-499 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:508-535 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:560-592 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:601-611 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) tools/ContentSeeder/BlockMapper.cs:537— tools/ContentSeeder/BlockMapper.cs:537-631 | tools/ContentSeeder/BlockMapper.cs:641-674 | tools/ContentSeeder/BlockMapper.cs:683-716 | tools/ContentSeeder/BlockMapper.cs:791-848 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (14 lines × 3) tools/ContentSeeder/BlockMapper.cs:296— tools/ContentSeeder/BlockMapper.cs:296-309 | tools/ContentSeeder/BlockMapper.cs:440-453 | tools/ContentSeeder/BlockMapper.cs:483-496 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) tools/ContentSeeder/BlockMapper.cs:586— tools/ContentSeeder/BlockMapper.cs:586-599 | tools/ContentSeeder/BlockMapper.cs:654-667 | tools/ContentSeeder/BlockMapper.cs:828-841 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 2) src/Imprint.Authoring/Features/Sites/CreateSite/CreateSite.cs:10— src/Imprint.Authoring/Features/Sites/CreateSite/CreateSite.cs:10-23 | src/Imprint.Authoring/Features/Sites/CreateSiteFromTemplate/CreateSiteFromTemplate.cs:15-28 — `src/Imprint.Authoring/Features/Sites/CreateSite/CreateSite.cs` and `src/Imprint.Authoring/Features/Sites/CreateSiteFromTemplate/CreateSiteFromTemplate.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Authoring/Features/Sites/CreateSite/CreateSite.cs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) tools/ContentSeeder/BlockMapper.cs:1180— tools/ContentSeeder/BlockMapper.cs:1180-1193 | tools/ContentSeeder/Markdown.cs:268-281 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:1180` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:714— src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:714-726 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:744-756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/Imprint.Editor/Components/Pages/PostEditor.razor:462— src/Imprint.Editor/Components/Pages/PostEditor.razor:462-474 | src/Imprint.Editor/Components/Panels/AssetsPanel.razor:159-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Components/Pages/PostEditor.razor:462` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Imprint.Editor/Components/Pages/PostEditor.razor:476` calls `New` and `src/Imprint.Editor/Components/Panels/AssetsPanel.razor:173` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) src/Imprint.Editor/Api/AuthoringApi.cs:292— src/Imprint.Editor/Api/AuthoringApi.cs:292-297 | src/Imprint.Editor/Api/AuthoringApi.cs:403-407 | src/Imprint.Editor/Api/AuthoringApi.cs:433-437 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:292` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/Imprint.Editor/Api/AuthoringApi.cs:1093— src/Imprint.Editor/Api/AuthoringApi.cs:1093-1097 | src/Imprint.Editor/Api/AuthoringApi.cs:1103-1107 | src/Imprint.Editor/Api/AuthoringApi.cs:1113-1117 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:1093` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×2
Duplicated block with local edits (11 matched lines × 2 locations) widgets/_src/cai-band-scale.js:41— widgets/_src/cai-band-scale.js:41 · widgets/_src/cai-composition-bar.js:71 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (11 matched lines × 2 locations) widgets/_src/cai-survey-list.js:90— widgets/_src/cai-survey-list.js:90 · widgets/_src/cai-trend.js:137 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (10 matched lines × 2 locations) · ×2
Duplicated block with local edits (10 matched lines × 2 locations) widgets/_src/cai-calculator.js:98— widgets/_src/cai-calculator.js:98 · widgets/_src/cai-report-index.js:75 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (10 matched lines × 2 locations) widgets/_src/cai-report-index.js:75— widgets/_src/cai-report-index.js:75 · widgets/_src/cai-verifier.js:51 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (5 lines × 2 locations) widgets/_src/cai-calculator.js:190— widgets/_src/cai-calculator.js:190 · widgets/cai-calculator.js:206 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (5 lines × 2 locations) widgets/_src/cai-dimensions.js:137— widgets/_src/cai-dimensions.js:137 · widgets/_src/live.js:245 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function render (cyclomatic 17, cognitive 18) widgets/_src/cai-survey-list.js:92— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 17, cognitive 18) widgets/cai-survey-list.js:268— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Dead file (~158 LoC) widgets/cai-language-support.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~158 LoC) widgets/contact-form.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC1 · Text alternatives· <video> without a captions track · ×1
<video> without a captions track src/Imprint.Rendering/Views/VideoView.razor:9— Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge.
Stateful singleton: PublisherStatus src/Imprint.Publishing/PublisherStatus.cs:9— `PublisherStatus` is a singleton (one shared instance) but mutates instance state outside any lock (Last; e.g. `Last` at line 17).
AuthoringApi.MapAuthoringApi (cyclomatic 212) src/Imprint.Editor/Api/AuthoringApi.cs:88— AuthoringApi.MapAuthoringApi has cyclomatic complexity 212 (threshold 15). Most of this is not in the body itself: 3 of the 212 points are its own statements and the rest belongs to 54 function literals inside it that branch (lines 291, 322, 134, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AuthoringNodeJson.ApplyProps (cyclomatic 34) src/Imprint.Editor/Api/AuthoringNodeJson.cs:384— AuthoringNodeJson.ApplyProps has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
scorecard.check_page (cyclomatic 31) tools/site-scorecard/scorecard.py:239— scorecard.check_page has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Verify.Run (cyclomatic 29) tools/ContentSeeder/Verify.cs:19— Verify.Run has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scorecard.scoreCardBodyHtml (cyclomatic 28) widgets/_src/scorecard.js:130— scorecard.scoreCardBodyHtml has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cai-card-gallery.z (cyclomatic 28) widgets/cai-card-gallery.js:122— cai-card-gallery.z has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
cai-score-card.H (cyclomatic 28) widgets/cai-score-card.js:117— cai-score-card.H has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MarkdownToNodes.Inline (cyclomatic 26) src/Imprint.Authoring/Markdown/MarkdownToNodes.cs:395— MarkdownToNodes.Inline 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.
Migrator.MigrateSite (cyclomatic 24) tools/ContentSeeder/Migrator.cs:56— Migrator.MigrateSite 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.
scorecard.audit_site (cyclomatic 24) tools/site-scorecard/scorecard.py:393— scorecard.audit_site 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.
Markdown.ToNodes (cyclomatic 21) tools/ContentSeeder/Markdown.cs:23— Markdown.ToNodes has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
#r (cyclomatic 21) widgets/cai-findings.js:143— #r has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
#repoHtml (cyclomatic 21) widgets/_src/cai-findings.js:107— #repoHtml has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
serializeInline (cyclomatic 21) src/Imprint.Editor/wwwroot/js/rich-toolbar.js:26— serializeInline has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
rich-toolbar.serializeInline (cyclomatic 20) src/Imprint.Editor/wwwroot/js/rich-toolbar.js:26— rich-toolbar.serializeInline 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.
live.cardFromGallery (cyclomatic 19) widgets/_src/live.js:64— live.cardFromGallery has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
cai-card-gallery.U (cyclomatic 19) widgets/cai-card-gallery.js:223— cai-card-gallery.U has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
cai-score-card.z (cyclomatic 19) widgets/cai-score-card.js:218— cai-score-card.z has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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· R (cyclomatic 18) · ×1
R (cyclomatic 18) widgets/cai-score-card.js:218— R has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 8 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity· B (cyclomatic 18) · ×1
B (cyclomatic 18) widgets/cai-card-gallery.js:223— B has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 8 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
#n (cyclomatic 18) widgets/cai-calculator.js:206— #n has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
parseCard (cyclomatic 18) widgets/_src/scorecard.js:311— parseCard has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 8 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
#result (cyclomatic 18) widgets/_src/cai-calculator.js:182— #result has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CanonicalHtml.ParseInlineUntil (cyclomatic 17) src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs:105— CanonicalHtml.ParseInlineUntil 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.
BlockMapper.PricingTiers (cyclomatic 17) tools/ContentSeeder/BlockMapper.cs:536— BlockMapper.PricingTiers has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: BlockMapper.Map (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
init (cyclomatic 17) src/Imprint.Editor/wwwroot/js/post-split.js:33— init has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 8 function items inside it that branch (onKeyDown, onPointerDown, remember, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
restore-wiped-post-bodies.blanked (cyclomatic 16) tools/restore-wiped-post-bodies.py:42— restore-wiped-post-bodies.blanked 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.
canvas-interop.onKeyDown (cyclomatic 16) src/Imprint.Editor/wwwroot/js/canvas-interop.js:275— canvas-interop.onKeyDown has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
post-split.init (cyclomatic 16) src/Imprint.Editor/wwwroot/js/post-split.js:33— post-split.init has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 90, 77, 51). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AuthoringApi.MapAuthoringApi (cognitive 225) src/Imprint.Editor/Api/AuthoringApi.cs:88— AuthoringApi.MapAuthoringApi has cognitive complexity 225 (threshold 15). Most of this is not in the body itself: 2 of the 225 points are its own statements and the rest belongs to 54 function literals inside it that branch (lines 134, 291, 254, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
render (cognitive 68) widgets/_src/cai-dimensions.js:192— render has cognitive complexity 68 (threshold 15). Of this number, 48 points are the body's own statements and 20 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Verify.Run (cognitive 64) tools/ContentSeeder/Verify.cs:19— Verify.Run has cognitive complexity 64 (threshold 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.
render (cognitive 60) widgets/cai-dimensions.js:173— render has cognitive complexity 60 (threshold 15). Of this number, 43 points are the body's own statements and 17 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CanonicalHtml.ParseInlineUntil (cognitive 46) src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs:105— CanonicalHtml.ParseInlineUntil has cognitive complexity 46 (threshold 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.
scoreCardBodyHtml (cognitive 40) widgets/_src/scorecard.js:130— scoreCardBodyHtml has cognitive complexity 40 (threshold 15). Of this number, 38 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Migrator.MigrateSite (cognitive 39) tools/ContentSeeder/Migrator.cs:56— Migrator.MigrateSite has cognitive complexity 39 (threshold 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.
MarkdownToNodes.Inline (cognitive 38) src/Imprint.Authoring/Markdown/MarkdownToNodes.cs:395— MarkdownToNodes.Inline has cognitive complexity 38 (threshold 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.
H (cognitive 37) widgets/cai-score-card.js:117— H has cognitive complexity 37 (threshold 15). Of this number, 35 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
z (cognitive 37) widgets/cai-card-gallery.js:122— z has cognitive complexity 37 (threshold 15). Of this number, 35 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scorecard.scoreCardBodyHtml (cognitive 33) widgets/_src/scorecard.js:130— scorecard.scoreCardBodyHtml has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 9, ternaries 4 (8 pts), loops 2 (4 pts) (nesting depth added 10). Of this number, 31 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scorecard.audit_site (cognitive 32) tools/site-scorecard/scorecard.py:393— scorecard.audit_site has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 5, loops 2 (3 pts), ternaries 3 (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.
BlockMapper.PricingTiers (cognitive 30) tools/ContentSeeder/BlockMapper.cs:536— BlockMapper.PricingTiers has cognitive complexity 30 (threshold 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.
scorecard.check_page (cognitive 30) tools/site-scorecard/scorecard.py:239— scorecard.check_page has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, ternaries 14, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
(anonymous) (cognitive 30) tools/mobile-sweep.js:16— (anonymous) has cognitive complexity 30 (threshold 15). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 27, 22, 23). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
serializeInline (cognitive 30) src/Imprint.Editor/wwwroot/js/rich-toolbar.js:26— serializeInline has cognitive complexity 30 (threshold 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.
SiteSettings.razor › SaveNavigation (cognitive 28) src/Imprint.Editor/Components/Pages/SiteSettings.razor:819— SiteSettings.razor › SaveNavigation has cognitive complexity 28 (threshold 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.
Markdown.ToNodes (cognitive 28) tools/ContentSeeder/Markdown.cs:23— Markdown.ToNodes has cognitive complexity 28 (threshold 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.
render (cognitive 28) widgets/_src/contact-form.js:90— render has cognitive complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch ((anonymous), closeModal, confirmSent, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
restore-wiped-post-bodies.blanked (cognitive 26) tools/restore-wiped-post-bodies.py:42— restore-wiped-post-bodies.blanked has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 8, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cai-card-gallery.z (cognitive 26) widgets/cai-card-gallery.js:122— cai-card-gallery.z has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 12, ternaries 4 (8 pts), loops 2 (4 pts), if/else 2 (nesting depth added 6). Of this number, 24 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
cai-score-card.H (cognitive 26) widgets/cai-score-card.js:117— cai-score-card.H has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 12, ternaries 4 (8 pts), loops 2 (4 pts), if/else 2 (nesting depth added 6). Of this number, 24 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
render (cognitive 26) widgets/contact-form.js:152— render has cognitive complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch ((anonymous), x, k, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
paint (cognitive 26) widgets/_src/cai-survey-list.js:182— paint has cognitive complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RichTextHtml.ResolveLinks (cognitive 25) src/Imprint.Rendering/RichTextHtml.cs:23— RichTextHtml.ResolveLinks has cognitive complexity 25 (threshold 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.
rich-toolbar.normalize (cognitive 24) src/Imprint.Editor/wwwroot/js/rich-toolbar.js:81— rich-toolbar.normalize has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 1, loops 1 (nesting depth added 12). Most of this is not in the body itself: 0 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 93, 85). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
rich-toolbar.serializeInline (cognitive 23) src/Imprint.Editor/wwwroot/js/rich-toolbar.js:26— rich-toolbar.serializeInline has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 6, 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.
normalize::walk (cognitive 23) src/Imprint.Editor/wwwroot/js/rich-toolbar.js:93— normalize::walk has cognitive complexity 23 (threshold 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.
Migrator.IngestSvgFigures (cognitive 22) tools/ContentSeeder/Migrator.cs:279— Migrator.IngestSvgFigures has cognitive complexity 22 (threshold 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.
TranslationSeeder.Seed (cognitive 22) tools/ContentSeeder/TranslationSeeder.cs:29— TranslationSeeder.Seed has cognitive complexity 22 (threshold 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.
paint (cognitive 22) widgets/cai-survey-list.js:268— paint has cognitive complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
paint (cognitive 21) widgets/cai-language-board.js:284— paint has cognitive complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
#repoHtml (cognitive 21) widgets/_src/cai-findings.js:107— #repoHtml has cognitive complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeContentRules.Validate (cognitive 20) src/Imprint.Authoring/Domain/Pages/NodeContentRules.cs:17— NodeContentRules.Validate has cognitive complexity 20 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AuthoringNodeJson.ParseLink (cognitive 20) src/Imprint.Editor/Api/AuthoringNodeJson.cs:328— AuthoringNodeJson.ParseLink has cognitive complexity 20 (threshold 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.
Markdown.InlineToPlain (cognitive 20) tools/ContentSeeder/Markdown.cs:245— Markdown.InlineToPlain has cognitive complexity 20 (threshold 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.
paint (cognitive 20) widgets/_src/cai-language-board.js:201— paint has cognitive complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Site.ValidateNavigationItem (cognitive 19) src/Imprint.Authoring/Domain/Sites/Site.cs:312— Site.ValidateNavigationItem has cognitive complexity 19 (threshold 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.
Pass.NavItemsFor (cognitive 19) src/Imprint.Publishing/SitePublisher.cs:912— Pass.NavItemsFor has cognitive complexity 19 (threshold 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.
SvgPublishGuard.IsSafe (cognitive 19) src/Imprint.Publishing/SvgPublishGuard.cs:21— SvgPublishGuard.IsSafe has cognitive complexity 19 (threshold 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.
#r (cognitive 19) widgets/cai-findings.js:143— #r has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockDefinition.ValidatePlacement (cognitive 18) src/Imprint.Authoring/Domain/Blocks/BlockDefinition.cs:154— BlockDefinition.ValidatePlacement has cognitive complexity 18 (threshold 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.
Page.SeedLocale (cognitive 18) src/Imprint.Authoring/Domain/Pages/Page.cs:282— Page.SeedLocale has cognitive complexity 18 (threshold 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.
Inline.ToCanonicalInline (cognitive 18) tools/ContentSeeder/Inline.cs:35— Inline.ToCanonicalInline has cognitive complexity 18 (threshold 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.
Fetcher._fetch (cognitive 18) tools/site-scorecard/scorecard.py:99— Fetcher._fetch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (4 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 18) widgets/_src/cai-lens-gauges.js:47— render has cognitive complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Page.EnsureSpecInternallyValid (cognitive 17) src/Imprint.Authoring/Domain/Pages/Page.cs:594— Page.EnsureSpecInternallyValid has cognitive complexity 17 (threshold 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.
SlotPlanner.Plan (cognitive 17) src/Imprint.Authoring/Features/Pages/MoveNode/SlotPlanner.cs:30— SlotPlanner.Plan has cognitive complexity 17 (threshold 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.
MarkdownToNodes.Convert (cognitive 17) src/Imprint.Authoring/Markdown/MarkdownToNodes.cs:51— MarkdownToNodes.Convert has cognitive complexity 17 (threshold 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.
SiteContactRecipients.Find (cognitive 17) src/Imprint.Editor/Contact/SiteContactRecipients.cs:19— SiteContactRecipients.Find has cognitive complexity 17 (threshold 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.
Pass.ChromePageLinks (cognitive 17) src/Imprint.Publishing/SitePublisher.cs:428— Pass.ChromePageLinks has cognitive complexity 17 (threshold 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.
Page.jsonld_types (cognitive 17) tools/site-scorecard/scorecard.py:208— Page.jsonld_types has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseCard (cognitive 17) widgets/_src/scorecard.js:311— parseCard has cognitive complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cardFromGallery (cognitive 17) widgets/_src/live.js:64— cardFromGallery has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CanonicalHtml.ParseHref (cognitive 16) src/Imprint.Authoring/Domain/Pages/CanonicalHtml.cs:193— CanonicalHtml.ParseHref has cognitive complexity 16 (threshold 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.
AuthoringApi.TryParseEnvironments (cognitive 16) src/Imprint.Editor/Api/AuthoringApi.cs:1543— AuthoringApi.TryParseEnvironments has cognitive complexity 16 (threshold 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.
AuthoringNodeJson.ApplyProps (cognitive 16) src/Imprint.Editor/Api/AuthoringNodeJson.cs:384— AuthoringNodeJson.ApplyProps has cognitive complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
SvgSanitizer.SanitizeElement (cognitive 16) src/Imprint.Media/SvgSanitizer.cs:130— SvgSanitizer.SanitizeElement has cognitive complexity 16 (threshold 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.
BlockMapper.Features (cognitive 16) tools/ContentSeeder/BlockMapper.cs:295— BlockMapper.Features has cognitive complexity 16 (threshold 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.
BlockMapper.PlainHeading (cognitive 16) tools/ContentSeeder/BlockMapper.cs:1159— BlockMapper.PlainHeading has cognitive complexity 16 (threshold 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.
canvas-interop.trackGap (cognitive 16) src/Imprint.Editor/wwwroot/js/canvas-interop.js:462— canvas-interop.trackGap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 5). Of this number, 9 points are the body's own statements and 7 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.
live.cardFromGallery (cognitive 16) widgets/_src/live.js:64— live.cardFromGallery has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7, if/else 5, boolean chains 4. Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
R (cognitive 16) widgets/cai-score-card.js:218— R has cognitive complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
z (cognitive 16) widgets/cai-score-card.js:218— z has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
B (cognitive 16) widgets/cai-card-gallery.js:223— B has cognitive complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
U (cognitive 16) widgets/cai-card-gallery.js:223— U has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 1 floating ref(s) across 1 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
Workflow token permissions not restricted — No workflow declares a `permissions:` block, so every job runs with the repository's default GITHUB_TOKEN scope (1 workflow file(s) checked: deploy.yml). On a repository whose default is read/write, a compromised action or a malicious pull request inherits write access to code, issues, releases and packages. Declare a least-privilege `permissions:` block — `permissions: {contents: read}` at the top of each workflow, widened per job only where a job genuinely writes.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) tools/ContentSeeder/BlockMapper.cs:296— tools/ContentSeeder/BlockMapper.cs:296-358 | tools/ContentSeeder/BlockMapper.cs:382-437 | tools/ContentSeeder/BlockMapper.cs:440-480 | tools/ContentSeeder/BlockMapper.cs:483-534 | tools/ContentSeeder/BlockMapper.cs:537-631 | tools/ContentSeeder/BlockMapper.cs:791-848 | tools/ContentSeeder/BlockMapper.cs:851-867 | tools/ContentSeeder/BlockMapper.cs:870-890 | tools/ContentSeeder/BlockMapper.cs:900-949 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
Duplicated block (21–25 lines × 2) src/Imprint.Authoring/Features/Pages/CreatePage/CreatePageHandler.cs:12— src/Imprint.Authoring/Features/Pages/CreatePage/CreatePageHandler.cs:12-36 | src/Imprint.Authoring/Features/Posts/CreatePost/CreatePostHandler.cs:13-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Authoring/Features/Pages/CreatePage/CreatePageHandler.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `cmd` to `CreatePage` in one and `CreatePost` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (21 lines × 2) src/Imprint.Authoring/Domain/Widgets/WidgetSubmission.cs:272— src/Imprint.Authoring/Domain/Widgets/WidgetSubmission.cs:272-292 | src/Imprint.Rendering/Widgets.cs:133-153 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20–21 lines × 2) src/Imprint.Rendering/RichTextHtml.cs:61— src/Imprint.Rendering/RichTextHtml.cs:61-81 | src/Imprint.Rendering/RichTextHtml.cs:83-102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Rendering/RichTextHtml.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 2) tools/ContentSeeder/BlockMapper.cs:1161— tools/ContentSeeder/BlockMapper.cs:1161-1179 | tools/ContentSeeder/Markdown.cs:248-266 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:1161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–16 lines × 3) src/Imprint.Authoring/Features/Pages/ChangePageMeta/ChangePageMetaHandler.cs:12— src/Imprint.Authoring/Features/Pages/ChangePageMeta/ChangePageMetaHandler.cs:12-25 | src/Imprint.Authoring/Features/Pages/ChangePageTitle/ChangePageTitleHandler.cs:12-25 | src/Imprint.Authoring/Features/Pages/EditText/EditTextHandler.cs:12-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Authoring/Features/Pages/ChangePageMeta/ChangePageMetaHandler.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `cmd` to `ChangePageMeta` in one and `ChangePageTitle` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 3) tools/ContentSeeder/BlockMapper.cs:321— tools/ContentSeeder/BlockMapper.cs:321-336 | tools/ContentSeeder/BlockMapper.cs:401-416 | tools/ContentSeeder/BlockMapper.cs:499-514 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:321` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) tools/ContentSeeder/BlockMapper.cs:340— tools/ContentSeeder/BlockMapper.cs:340-355 | tools/ContentSeeder/BlockMapper.cs:462-477 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:340` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) tools/ContentSeeder/BlockMapper.cs:517— tools/ContentSeeder/BlockMapper.cs:517-531 | tools/ContentSeeder/BlockMapper.cs:609-622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:517` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) tools/ContentSeeder/BlockMapper.cs:660— tools/ContentSeeder/BlockMapper.cs:660-674 | tools/ContentSeeder/BlockMapper.cs:702-716 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:660` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 3) tools/ContentSeeder/BlockMapper.cs:346— tools/ContentSeeder/BlockMapper.cs:346-358 | tools/ContentSeeder/BlockMapper.cs:468-480 | tools/ContentSeeder/BlockMapper.cs:619-631 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tools/ContentSeeder/BlockMapper.cs:346` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 5) tools/ContentSeeder/BlockMapper.cs:324— tools/ContentSeeder/BlockMapper.cs:324-334 | tools/ContentSeeder/BlockMapper.cs:404-414 | tools/ContentSeeder/BlockMapper.cs:453-463 | tools/ContentSeeder/BlockMapper.cs:502-512 | tools/ContentSeeder/BlockMapper.cs:853-863 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) tools/ContentSeeder/BlockMapper.cs:318— tools/ContentSeeder/BlockMapper.cs:318-328 | tools/ContentSeeder/BlockMapper.cs:398-408 | tools/ContentSeeder/BlockMapper.cs:496-506 | tools/ContentSeeder/BlockMapper.cs:795-805 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–9 lines × 2) src/Imprint.Authoring/Domain/Pages/Page.cs:26— src/Imprint.Authoring/Domain/Pages/Page.cs:26-32 | src/Imprint.Authoring/Domain/Posts/Post.cs:35-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 3) src/Imprint.Editor/Api/AuthoringApi.cs:542— src/Imprint.Editor/Api/AuthoringApi.cs:542-549 | src/Imprint.Editor/Api/AuthoringApi.cs:580-587 | src/Imprint.Editor/Api/AuthoringApi.cs:651-658 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:542` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472— src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472-477 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:508-513 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:560-565 | src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:601-606 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Mcp/ImprintAuthoringMcpTools.cs:472` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 5) src/Imprint.Editor/Api/AuthoringApi.cs:535— src/Imprint.Editor/Api/AuthoringApi.cs:535-539 | src/Imprint.Editor/Api/AuthoringApi.cs:573-577 | src/Imprint.Editor/Api/AuthoringApi.cs:633-637 | src/Imprint.Editor/Api/AuthoringApi.cs:743-747 | src/Imprint.Editor/Api/AuthoringApi.cs:774-778 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:535` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–5 lines × 4) src/Imprint.Editor/Api/AuthoringApi.cs:895— src/Imprint.Editor/Api/AuthoringApi.cs:895-899 | src/Imprint.Editor/Api/AuthoringApi.cs:924-928 | src/Imprint.Editor/Api/AuthoringApi.cs:948-952 | src/Imprint.Editor/Api/AuthoringApi.cs:996-999 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Imprint.Editor/Api/AuthoringApi.cs:895` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Off the main sequence: Imprint.Authoring — Imprint.Authoring: abstractness 0.02, instability 0.17, distance 0.81 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Low cohesion: CanvasBridge (LCOM4 4) src/Imprint.Editor/Services/CanvasBridge.cs:21— CanvasBridge's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: the test suite built and its tests PASSED, but the run produced no coverage data — `--collect:"XPlat Code Coverage"` found no data collector, which is what a test project with no `coverlet.collector` PackageReference does. Nothing is wrong with the suite or the build; there is simply no coverage instrumentation wired up. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
Non-idempotent mutation: PublishPost.PublishPostHandler.Handle src/Imprint.Authoring/Features/Posts/PublishPost/PublishPostHandler.cs:14— `PublishPost.PublishPostHandler.Handle` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Duplicated block (44 lines × 2 locations) widgets/_src/cai-calculator.js:133— widgets/_src/cai-calculator.js:133 · widgets/_src/cai-verifier.js:80 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (11 lines × 2 locations) widgets/_src/cai-language-board.js:221— widgets/_src/cai-language-board.js:221 · widgets/_src/cai-survey-list.js:206 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (10 lines × 2 locations) widgets/_src/cai-lens-gauges.js:49— widgets/_src/cai-lens-gauges.js:49 · widgets/_src/cai-link-cards.js:78 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) widgets/_src/cai-c4-heat.js:165— widgets/_src/cai-c4-heat.js:165 · widgets/_src/cai-findings.js:172 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (8 lines × 2 locations) widgets/_src/cai-language-board.js:197— widgets/_src/cai-language-board.js:197 · widgets/_src/cai-trend.js:238 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) widgets/_src/cai-evidence-flow.js:44— widgets/_src/cai-evidence-flow.js:44 · widgets/_src/cai-lens-gauges.js:42 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (6 lines × 2 locations) widgets/_src/cai-report-index.js:172— widgets/_src/cai-report-index.js:172 · widgets/cai-report-index.js:145 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function render (cyclomatic 35, cognitive 48) widgets/_src/cai-dimensions.js:192— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 35, cognitive 43) widgets/cai-dimensions.js:173— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function scoreCardBodyHtml (cyclomatic 26, cognitive 38) widgets/_src/scorecard.js:130— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
R2 · Cyclomatic Complexity· Complex function z (cyclomatic 26, cognitive 35) · ×1
Complex function z (cyclomatic 26, cognitive 35) widgets/cai-card-gallery.js:122— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
R2 · Cyclomatic Complexity· Complex function H (cyclomatic 26, cognitive 35) · ×1
Complex function H (cyclomatic 26, cognitive 35) widgets/cai-score-card.js:117— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function #repoHtml (cyclomatic 20, cognitive 20) widgets/_src/cai-findings.js:107— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function #r (cyclomatic 20, cognitive 18) widgets/cai-findings.js:143— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 19, cognitive 21) widgets/_src/cai-score-card.js:72— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 19, cognitive 14) widgets/cai-score-card.js:221— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 18, cognitive 20) widgets/_src/cai-trend.js:139— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 18, cognitive 18) widgets/cai-trend.js:258— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function cardFromGallery (cyclomatic 18, cognitive 16) widgets/_src/live.js:64— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
R2 · Cyclomatic Complexity· Complex function U (cyclomatic 18, cognitive 15) · ×1
Complex function U (cyclomatic 18, cognitive 15) widgets/cai-card-gallery.js:223— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
R2 · Cyclomatic Complexity· Complex function z (cyclomatic 18, cognitive 15) · ×1
Complex function z (cyclomatic 18, cognitive 15) widgets/cai-score-card.js:218— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 16, cognitive 20) widgets/_src/cai-language-support.js:148— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function paint (cyclomatic 16, cognitive 20) widgets/_src/cai-survey-list.js:182— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 16, cognitive 19) widgets/_src/cai-language-board.js:136— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Complex function render (cyclomatic 16, cognitive 16) widgets/cai-language-support.js:158— Branch-heavy code is where defects cluster — extract decisions into smaller functions.
Dead file (~338 LoC) widgets/_src/scorecard.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (widgets/_src/cai-band-scale.js, widgets/_src/cai-card-gallery.js, widgets/_src/cai-language-board.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~325 LoC) widgets/_src/cai-language-board.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~322 LoC) widgets/_src/cai-dimensions.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~299 LoC) widgets/_src/live.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (widgets/_src/cai-band-scale.js, widgets/_src/cai-c4-heat.js, widgets/_src/cai-card-gallery.js and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~284 LoC) widgets/cai-language-board.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~275 LoC) widgets/_src/cai-trend.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~268 LoC) widgets/cai-survey-list.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~263 LoC) widgets/_src/tokens.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 20 in-repo import(s) from 20 other file(s) do name it (widgets/_src/cai-band-scale.js, widgets/_src/cai-c4-heat.js, widgets/_src/cai-calculator.js and 17 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~262 LoC) widgets/_src/cai-survey-list.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~258 LoC) widgets/cai-trend.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~238 LoC) widgets/_src/cai-calculator.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~236 LoC) widgets/cai-band-scale.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~235 LoC) widgets/cai-lens-gauges.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~228 LoC) widgets/cai-card-gallery.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~202 LoC) widgets/_src/cai-report-index.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~194 LoC) widgets/_src/cai-language-support.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~183 LoC) widgets/_src/cai-verifier.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~182 LoC) widgets/_src/cai-findings.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~178 LoC) widgets/_src/cai-public-reports.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~176 LoC) widgets/_src/cai-c4-heat.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~173 LoC) widgets/cai-dimensions.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~169 LoC) widgets/cai-public-reports.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~167 LoC) widgets/cai-verifier.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~162 LoC) widgets/_src/wd-embed.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~152 LoC) widgets/cai-report-index.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~147 LoC) widgets/cai-link-cards.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~144 LoC) widgets/cai-evidence-flow.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~143 LoC) widgets/cai-findings.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~140 LoC) widgets/x-theme-toggle.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~136 LoC) widgets/cai-c4-heat.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~130 LoC) widgets/_src/cai-composition-bar.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~128 LoC) widgets/cai-composition-bar.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~112 LoC) widgets/_src/cai-score-card.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~108 LoC) widgets/_src/cai-link-cards.js— no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×1
Disposable created and abandoned in the method that made it src/Imprint.Publishing/PublisherHostedService.cs:36— `pending` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `ExecuteAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var pending = …;`), which releases it at the end of the scope on every path including a throw.
Recommendation — 25 finding(s)
DM2 · Strongly-typed ids· Primitive id on a domain type · ×10
Primitive id on a domain type: Asset.OriginalStorageKey src/Imprint.Authoring/Domain/Assets/Asset.cs:29— `Asset.OriginalStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Asset.DerivedStorageKey src/Imprint.Authoring/Domain/Assets/Asset.cs:34— `Asset.DerivedStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Asset.DarkOriginalStorageKey src/Imprint.Authoring/Domain/Assets/Asset.cs:40— `Asset.DarkOriginalStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Asset.DarkDerivedStorageKey src/Imprint.Authoring/Domain/Assets/Asset.cs:46— `Asset.DarkDerivedStorageKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Asset.StreamId src/Imprint.Authoring/Domain/Assets/Asset.cs:60— `Asset.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: BlockDefinition.StreamId src/Imprint.Authoring/Domain/Blocks/BlockDefinition.cs:29— `BlockDefinition.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Page.StreamId src/Imprint.Authoring/Domain/Pages/Page.cs:40— `Page.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Post.StreamId src/Imprint.Authoring/Domain/Posts/Post.cs:68— `Post.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Site.StreamId src/Imprint.Authoring/Domain/Sites/Site.cs:113— `Site.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: WidgetSubmission.StreamId src/Imprint.Authoring/Domain/Widgets/WidgetSubmission.cs:38— `WidgetSubmission.StreamId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
D21 · Naming Consistency· The parameter name 'Node Copy' contains a space, which is non-standard for C# identifiers and likely a typo or copy-paste artifact. It refers to the same concept as the type 'Node' or a copy of it. · ×1
The parameter name 'Node Copy' contains a space, which is non-standard for C# identifiers and likely a typo or copy-paste artifact. It refers to the same concept as the type 'Node' or a copy of it. — Rename parameter to 'nodeCopy' or 'sourceNode' to follow standard camelCase naming conventions and remove the space. (symbols: Imprint.Authoring.Domain.Pages.Node Copy, Imprint.Authoring.Domain.Pages.Node)
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 25200 LoC across 15 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
Split Imprint.Authoring — A generic Authoring project whose namespaces are all domain pages/events, sites/events, assets/events, and posts/events under one cohesive authoring domain. Suggested:
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (`dotnet nuget sign` with a code-signing certificate for the NuGet packages (`dotnet nuget verify` checks it), or Authenticode via signtool for any executable you ship) so consumers can verify what you built.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`sbom-tool generate` (install it with `dotnet tool install --global Microsoft.Sbom.DotNetTool`) or `dotnet CycloneDX` over the solution, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Ship it with the artifact you distribute — for a package registry that means packing the document (`*.spdx.json` / `*.cdx.json`) into the package itself, so it cannot drift from what a consumer installs.
No dependency advisory monitoring — Nothing in this repository re-checks its pinned dependencies when an advisory is published: no Dependabot or Renovate configuration (`.github/dependabot.yml`, `renovate.json`), no advisory scanner invoked from CI and no committed scanner configuration (`deny.toml`, `.cargo/audit.toml`, `osv-scanner.toml`, `.snyk`). The manifests present — `nuget` (*.csproj) — pin versions that advisories are published against on the advisory database's clock, not this repository's, so every advisory that lands against a pinned version stays unseen until someone points a scanner at the tree (any already published are reported under D38, one row per package — this row names the control whose absence lets them accumulate). GitHub's Dependabot alerts, if switched on in the repository settings, notify but leave nothing in the tree; a committed configuration is what makes the control reviewable and carries it to a fork or mirror. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per manifest listed (or a `renovate.json`) so each advisory arrives as a pull request against the affected lockfile; or wire the ecosystem's own advisory scanner into CI on a `schedule:` trigger — nuget: `dotnet list package --vulnerable` failing on output, or promote the SDK's audit warnings to errors (`<WarningsAsErrors>NU1901;NU1902;NU1903;NU1904</WarningsAsErrors>`).
IL efficiency: 17 authored method(s) exceed the IL budget src/Imprint.Editor/Api/AuthoringNodeJson.cs:386— 17 of 2252 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Imprint.Editor.Api.AuthoringNodeJson.ApplyProps @ src/Imprint.Editor/Api/AuthoringNodeJson.cs:386, 498 IL instructions; that pulled this dimension to 9.8/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 6/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
…and 7 more — 7 further occurrence(s) are not listed individually; the score already reflects all 47.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 173/205 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.8 `!` suppressions per 1k syntax nodes — 109 suppression(s) across the 135067 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 01a07105-7534-7914-93cb-d9f53893e59d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 12 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 10 · Warnings: 632 · Recommendations: 25 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 05-09-2026 @ 10:02 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.