Public report — saastack, published 29 Jun 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
493findings with an exact file:lineof 548 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
83/111dimensions across the health lenses88544 LoC · 142 projects — wide & deep
Executive summary
Read through the Template lens: this is a template / kata / sample / demo — code meant to be read or copied, not operated. The ship-it and operate-it dimensions (CI/CD, observability, ADRs, architecture docs, deployment security) are N/A, and the colour bands on what remains are relaxed to what an example needs. Code correctness stays near-strict; the score is absolute and comparable across repos.
SaaStacked/saastack is in a workable but fragile state (56%). It is not in crisis, but it carries material risk that makes change slower and incidents harder to contain if left unaddressed.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (48%) — operating, monitoring and recovering the system safely is harder. Performance (60%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: Extend structured logging to the remaining service-like… (Observability); Codify backups + geo-recovery in IaC… (DR & Backup); missing tooling (eslint (Tooling).
For scale: Medium (~88,544 production lines); rebuilding it from scratch would take roughly ~2.6 person-years (~1–6 engineers). Approximate, ±~30%.
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.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
Rebuild cost & value ~ Modeled — €130,000–€650,000
~509 LoC unreachable (10 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.6 person-years of build effort (about ~€390,000 to rebuild). Its weakest lens is Readiness at 48% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.5) — service/app, DDD/clean architecture, domain model, high decision density × a 0.8× 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 2 Leaked secret finding(s) in Secret Scanning — start with EndUserRoot.cs, WebsiteTestingExtensions.cs.
Value concentrated against a weak lens · Medium · Value at risk
This is a Medium asset (~2.6 person-years to rebuild), and its weakest lens is Readiness at 48%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Root cause: an un-encapsulated domain · Medium · Root cause
50 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: Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.
Improving trajectory · Info · Trajectory
The headline is improving steadily (+6.9 pts/run over 4 runs) — whatever you're doing is working; keep the gate.
Evidence: trajectory: +6.9 pts/run over 4 runs
Trajectory
Where this codebase is heading — something a one-shot snapshot cannot show. 56, unchanged across 4 runs.
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
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
A06:2021 — Vulnerable & Outdated Components
44
High / Critical
A02:2021 — Cryptographic Failures
7
High / Critical
Roadmap
First, extend structured logging across all service-like projects to ensure full production diagnosability. Next, codify backups and geo-recovery in infrastructure-as-code to support disaster recovery plans. Then, integrate missing tooling such as eslint and tsc into CI pipelines to enforce code quality. After that, resolve the two leaked secret findings to eliminate immediate security risks. Finally, implement readiness probes and automated rollback strategies to safely manage deployments.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with EndUserRoot.cs, WebsiteTestingExtensions.cs.
Test Quality: No assertions: WhenAllProperties_ThenSucceeds
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. 78 of 83 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 83 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, 493 of 548 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D31 IaC & Container Security — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D36 Supply-chain Provenance & Signing — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
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 (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (EF migrations, designer files, snapshots) 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.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
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.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
The LLM boundary
LLM-set scores this run (5): D20, D21, D24, D25, 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.
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 LocalMachineFileStoreExtensions.FromFileProperty (cyclomatic 46) finding(s) in Cyclomatic Complexity — start with LocalMachineJsonFileStore.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EndUserRoot.OnStateChanged (cyclomatic 45) finding(s) in Cyclomatic Complexity — start with EndUserRoot.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SubscriptionRoot.OnStateChanged (cyclomatic 45) finding(s) in Cyclomatic Complexity — start with SubscriptionRoot.cs. — One of this dimension's main actionable groups (1 warning-level).
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.
+ 55 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 RequestTenantDetective.ParseTenantIdFromRequestBodyAsync (cognitive 66) finding(s) in Cognitive Complexity — start with RequestTenantDetective.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SubscriptionRoot.OnStateChanged (cognitive 65) finding(s) in Cognitive Complexity — start with SubscriptionRoot.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SubscriptionsApplication.ResyncSubscriptionTierQuotasInternalAsync… finding(s) in Cognitive Complexity — start with SubscriptionsApplication_Quotas.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 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 14 TooManyMethods finding(s) in God Classes — start with DateTimeExtensions.cs, EndUserRoot.RolesAndFeatures.cs, InProcessInMemStore.IBlobStore.cs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 5 FileTooLong finding(s) in God Classes — start with Annotations.cs, OrganizationsApplication.cs, PersonCredentialRoot.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes — start with AncillaryApplication.Auditing.cs, EndUsersApplication.DomainEventHandlers.cs, NativeIdentityServerCredentialsService.Mfa.cs. — One of this dimension's main actionable groups (4 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.
+ 22 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.3 / 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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
Of 23 mechanizable ADRs, 20 are prevented by analyzers, 3 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
4559 test methods: 4104 unit, 455 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.4 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 199 zero-assertion, 2 mock references across 4559 tests (2 harness-style project(s) excluded from the assertion penalty).
No assertions: WhenAllProperties_ThenSucceeds · ×170src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/AdditionalValidatorSpec.cs:22
No direct assertions: WhenAllProperties_ThenSucceeds · ×29src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Audits/DeliverAuditRequestValidatorSpec.cs:25
Mock framework: Moq · ×2
✓ On the Gold path — maintain.
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.
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: not included — too large to re-run within its budget; other: measured (0 flaky).
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.
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with EndUserRoot.cs, WebsiteTestingExtensions.cs. — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor3.5 / 10Weak✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
234 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.cs.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
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.
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality / 10Strong◐ Sampled · advisory
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
Evaluated 50 ADR(s) individually; mean quality 7.9/10 (mixed — many ADRs miss context or consequences). 3 flagged with a specific gap.
Context/problem and consequences/trade-offs are absent from the visible textdocs/design-principles/0020-api-framework.md
Decision is a thin implementation heading with no context/problem and no consequences; the title 'Dependency Injection' names only the subjectdocs/design-principles/0060-dependency-injection.md
Context/problem and consequences/trade-offs are absent; only how-to sections with no rationaledocs/design-principles/0210-javascript-forms.md
What to do
Resolve the 1 Context/problem and consequences/trade-offs are absent from the visible… finding(s) in ADR Quality — start with 0020-api-framework.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Decision is a thin implementation heading with no context/problem and no… finding(s) in ADR Quality — start with 0060-dependency-injection.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Context/problem and consequences/trade-offs are absent; only how-to… finding(s) in ADR Quality — start with 0210-javascript-forms.md. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment Value / 10Adequate◐ 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: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
4 of 142 projects flagged as possibly oversized/incoherent.
Split Common
Split Infrastructure.Web.Api.Operations.Shared
Split Domain.Events.Shared
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.5 / 10Strong✓ Tool-verified
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.
79 % of calls cross a namespace and 1 % go through an interface, but 89 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 8.5/10. — 79 % of calls cross a namespace and 1 % go through an interface, but 89 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality 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.
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: private-key · ×4src/ApiHost1/appsettings.json:104detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 4 Secret finding(s) in Secrets (history) — start with EndUserRoot.cs (2), appsettings.json (2). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep --config auto across the repo; severity rules (ERROR/WARNING/INFO) map to a 0-10 wide normalizer. 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).
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.
279 of 361 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Framework/Common/Annotations.cs.
Dormant codebase
What to do
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — npm and other lockfile ecosystems, parsed natively. Complements D33 (npm via trivy) and D30 (.NET via dotnet).
Method: npm/multi-ecosystem CVE scan via osv-scanner (queries the osv.dev database + parses lockfiles natively: package-lock/yarn/pnpm/bun); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable without a JS lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×20src/Hosts/WebsiteHost/ClientApp/package-lock.jsondetected by osv-scanner finding
Critical CVE: [GHSA redacted]src/Hosts/WebsiteHost/ClientApp/package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×12src/Hosts/WebsiteHost/ClientApp/package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×3src/Hosts/WebsiteHost/ClientApp/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 20 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (20). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 12 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (12). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 1 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_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 alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels5.7 / 10Adequate✓ 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.
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child. — FormAction.tsx:85
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.
Do you agree with this assessment?
AC3 · Page structure6.6 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — UnhandledError.tsx:81
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — Index.cshtml:0
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — Index.cshtml:0
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, 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.
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.
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. — ThemeToggle.tsx:8
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) configured, and axe/pa11y/Lighthouse wired into tests or CI — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) configured, and axe/pa11y/Lighthouse in tests or CI, graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y (or vuejs-accessibility), assert with jest-axe / playwright-axe in tests, then gate axe/pa11y/Lighthouse in CI.
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.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
`SubscriptionsDomain.UnitTests` is a Domain project but references `Application.Interfaces`, a Application project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
`ImagesDomain.UnitTests` is a Domain project but references `Application.Interfaces`, a Application project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
`EventNotificationsApplication` is a Application project but references `Infrastructure.Eventing.Interfaces`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
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 interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`IRecorder` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IRecorder.cs:9
`ICallerContext` declares 18 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — ICallerContext.cs:8
`IIdentityServerCredentialsService` declares 18 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IIdentityServerCredentialsService.cs:10
`IAncillaryApplication` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IAncillaryApplication.Auditing.cs:7
`IPersonCredentialsApplication` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IPersonCredentialsApplication.cs:7
`IOrganizationsApplication` declares 29 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IOrganizationsApplication.cs:8
`ISubscriptionsApplication` declares 29 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — ISubscriptionsApplication.cs:7
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ 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.
`IntegrationTesting.WebApi.Common` (production) references the test project `UnitTesting.Common`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Other · Security — Whether access is authorized by default — [Authorize]/policies 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.
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. 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.
`ITombstoneEvent.DeletedById` is a raw `String` — give it a strongly-typed id (`readonly record struct DeletedById { String Value }`). — ITombstoneEvent.cs:8
`DomainEvent.RootId` is a raw `String` — give it a strongly-typed id (`readonly record struct RootId { String Value }`). — DomainEvent.cs:30
`TombstoneDomainEvent.DeletedById` is a raw `String` — give it a strongly-typed id (`readonly record struct DeletedById { String Value }`). — TombstoneDomainEvent.cs:29
`Created.AgainstId` is a raw `String` — give it a strongly-typed id (`readonly record struct AgainstId { String Value }`). — Created.cs:19
`Created.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). (×5) — Created.cs:27, Created.cs:23, Created.cs:23, …
`Created.MessageId` is a raw `String` — give it a strongly-typed id (`readonly record struct MessageId { String Value }`). (×2) — Created.cs:21, Created.cs:21
`DeliveryConfirmed.ReceiptId` is a raw `String` — give it a strongly-typed id (`readonly record struct ReceiptId { String Value }`). (×2) — DeliveryConfirmed.cs:18, DeliveryConfirmed.cs:18
`DeliveryFailureConfirmed.ReceiptId` is a raw `String` — give it a strongly-typed id (`readonly record struct ReceiptId { String Value }`). (×2) — DeliveryFailureConfirmed.cs:20, DeliveryFailureConfirmed.cs:20
`EmailDetailsChanged.TemplateId` is a raw `String` — give it a strongly-typed id (`readonly record struct TemplateId { String Value }`). — EmailDetailsChanged.cs:29
`SendingSucceeded.ReceiptId` is a raw `String` — give it a strongly-typed id (`readonly record struct ReceiptId { String Value }`). (×2) — SendingSucceeded.cs:18, SendingSucceeded.cs:18
`CarChanged.CarId` is a raw `String` — give it a strongly-typed id (`readonly record struct CarId { String Value }`). — CarChanged.cs:18
`CarChanged.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — CarChanged.cs:20
`ReservationMade.BorrowerId` is a raw `String` — give it a strongly-typed id (`readonly record struct BorrowerId { String Value }`). — ReservationMade.cs:20
`ReservationMade.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — ReservationMade.cs:24
`TripAdded.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — TripAdded.cs:18
`TripAdded.TripId` is a raw `String` — give it a strongly-typed id (`readonly record struct TripId { String Value }`). — TripAdded.cs:20
`TripBegan.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — TripBegan.cs:24
`TripBegan.TripId` is a raw `String` — give it a strongly-typed id (`readonly record struct TripId { String Value }`). — TripBegan.cs:26
`TripEnded.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — TripEnded.cs:26
`TripEnded.TripId` is a raw `String` — give it a strongly-typed id (`readonly record struct TripId { String Value }`). — TripEnded.cs:28
`Deleted.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — Deleted.cs:18
`ManufacturerChanged.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — ManufacturerChanged.cs:22
`OwnershipChanged.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — OwnershipChanged.cs:20
`RegistrationChanged.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — RegistrationChanged.cs:23
`UnavailabilitySlotAdded.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — UnavailabilitySlotAdded.cs:25
`UnavailabilitySlotAdded.UnavailabilityId` is a raw `String` — give it a strongly-typed id (`readonly record struct UnavailabilityId { String Value }`). — UnavailabilitySlotAdded.cs:29
`UnavailabilitySlotRemoved.OrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct OrganizationId { String Value }`). — UnavailabilitySlotRemoved.cs:18
`UnavailabilitySlotRemoved.UnavailabilityId` is a raw `String` — give it a strongly-typed id (`readonly record struct UnavailabilityId { String Value }`). — UnavailabilitySlotRemoved.cs:20
`DefaultMembershipChanged.FromMembershipId` is a raw `String` — give it a strongly-typed id (`readonly record struct FromMembershipId { String Value }`). — DefaultMembershipChanged.cs:20
`DefaultMembershipChanged.ToMembershipId` is a raw `String` — give it a strongly-typed id (`readonly record struct ToMembershipId { String Value }`). — DefaultMembershipChanged.cs:24
`DefaultMembershipChanged.ToOrganizationId` is a raw `String` — give it a strongly-typed id (`readonly record struct ToOrganizationId { String Value }`). — DefaultMembershipChanged.cs:26
`GuestInvitationCreated.InvitedById` is a raw `String` — give it a strongly-typed id (`readonly record struct InvitedById { String Value }`). — GuestInvitationCreated.cs:20
136 further occurrence(s) are not listed individually; the score already reflects all 176.
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Other · Domain Modelling — Whether cross-context integration events stay loosely coupled — no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.
Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.
Do you agree with this assessment?
DM4 · Rich vs anemic model7.5 / 10Strong✓ 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.
`BookingRoot` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BookingRoot.cs:17
`AuditRoot` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — AuditRoot.cs:14
`AuthTokensRoot` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — AuthTokensRoot.cs:28
`OAuth2ClientConsentRoot` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — OAuth2ClientConsentRoot.cs:15
`OAuth2ClientRoot` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — OAuth2ClientRoot.cs:17
`ProviderAuthTokensRoot` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ProviderAuthTokensRoot.cs:23
`SSOUserRoot` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SSOUserRoot.cs:20
`OrganizationOnboardingRoot` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — OrganizationOnboardingRoot.cs:52
`SubscriptionQuotaUsageRoot` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SubscriptionQuotaUsageRoot.cs:23
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) instead of exposing public setters that bypass invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): public setters on entities detected; 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 · 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.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — BeffeIdentifierFactory.cs:21
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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.
`Create` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — EmptyIdentifierFactory.cs:12
`GetAllFlagsAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — EmptyFeatureFlags.cs:11
`Create` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — BeffeIdentifierFactory.cs:19
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 137 of 142 project(s) that lack one — worth up to 1.9 pts.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.
Only 31/142 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
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
README advertises a microservices architecture, but the repo is a single project with no service manifests
What to do
Reconcile the README with reality: README advertises Docker containerisation, but no Dockerfile/compose file exists; README advertises a microservices architecture, but the repo is a single project with no service manifests.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Codify backups + geo-recovery in IaC (snapshot/replication/geo-redundant) to back the DR plan.
Readiness · Performance — Whether the library protects its performance with benchmarks — a BenchmarkDotNet suite, an allocation MemoryDiagnoser, 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 BenchmarkDotNet suite was found. For a performance-sensitive library, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a BenchmarkDotNet project for the hot paths (with [MemoryDiagnoser] to track allocations), and run it in CI to catch regressions.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's GC — Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask, value-type structs 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 16 use(s) across 113,728 production line(s) (~0.1/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
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.
7 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
Do you agree with this assessment?
R1 · Type Safety9.9 / 10Exemplary✓ 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.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
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. (×8) — client.gen.ts:78, client.gen.ts:78, serverSentEvents.gen.ts:108, …
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.5 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many components/modules exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
What to do
Split the oversized components into smaller, focused ones.
Do you agree with this assessment?
R4 · Test Coverage6.8 / 10Strong✓ 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.
No test imports this module directly or transitively — its behavior is unverified. (×8) — schemas.gen.ts, schemas.gen.ts, mockServiceWorker.js, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗
What to do
Add the missing tooling (eslint, tsc) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code7.6 / 10Strong✓ 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 3 application, 6 tooling and 50 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (3 application, 6 tooling, 50 test roots considered) (×7) — mockServiceWorker.js, setup.ts, getFeatureFlag.ts, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in src/Hosts/WebsiteHost/ClientApp/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports3.6 / 10Weak✓ Tool-verified
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).
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
What to do
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
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.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Make the caller `async` and `await` instead. (×8) — JsonClient.cs:542, QueuedAuditReporter.cs:54, WebApplicationExtensions.cs:129, …
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 883/953 async methods accept a CancellationToken, so requests can't be cancelled cleanly under load or on client disconnect. In Blazor Server circuits and other short-write hosts, omitting it can be an accepted convention — judge against your hosting model.
No CancellationToken parameter — work can't be cancelled cleanly on disconnect/shutdown. (×25) — Tasks.cs:8, Repeat.cs:28, Repeat.cs:37, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.
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.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. (×2) — StubCloudWorkerService.cs:80, StubCloudWorkerService.cs:87
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.
~1.3 `!` suppressions per 1k syntax nodes — 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.
Not included — 29 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.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — no data
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
D19 Documentation Quality — LLM evaluation failed
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, 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.
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a NuGet package, a container image, a GitHub release).
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D8 Code Coverage — Coverage not measured — test suite did not build
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — applicable but skipped (2/3 markers — below the conservative bar): 2 integration event(s); 1 event handler(s)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — only 1/3 markers (an append-only event-store seam (IEventStore/Append-of-events))
P12 CI test-gate honesty — no data
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.
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 — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
SC1 Supply-chain hygiene — no data
X6 Hand-rolled structured-format parsing — no data
X7 Silent fallback defaults — no data
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 — 40 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×20
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— @nevware21/ts-utils: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— defu: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— lodash: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— minimatch: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— minimatch: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— minimatch: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— picomatch: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— react-router: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— react-router: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— react-router: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— react-router: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— rollup: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— storybook: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— tar: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— tar: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— tar: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— vite: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— vite: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— vite: [GHSA redacted]
High CVE: [GHSA redacted] src/Hosts/WebsiteHost/ClientApp/package-lock.json— ws: [GHSA redacted]
High CVE: Newtonsoft.Json 12.0.2 — Newtonsoft.Json 12.0.2 (transitive) has a High advisory; affects 64 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory; affects 71 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory; affects 71 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Linq.Dynamic.Core 1.5.1 — System.Linq.Dynamic.Core 1.5.1 (transitive) has a High advisory; affects 116 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: NuGet.Common 5.6.0 — NuGet.Common 5.6.0 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: NuGet.Protocol 5.6.0 — NuGet.Protocol 5.6.0 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: NuGet.Protocol 5.6.0 — NuGet.Protocol 5.6.0 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
No assertions: WhenAllProperties_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/AdditionalValidatorSpec.cs:22— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAnyValueIsNull_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/AdditionalValidatorSpec.cs:43— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAnyStringValueIsValid_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/AdditionalValidatorSpec.cs:56— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllPropertiesValid_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasGetOptionsValidatorSpec.cs:22— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenEmbedIsNull_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasGetOptionsValidatorSpec.cs:28— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenEmbedIsOff_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasGetOptionsValidatorSpec.cs:36— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenEmbedIsTopLevelField_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasGetOptionsValidatorSpec.cs:44— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenEmbedIsChildLevelField_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasGetOptionsValidatorSpec.cs:52— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenEmbedIsGrandChildLevelField_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasGetOptionsValidatorSpec.cs:60— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllPropertiesValid_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:29— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenLimitIsNull_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:35— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenLimitIsMin_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:43— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenLimitIsLessThanMax_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:51— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenOffsetIsNull_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:79— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenOffsetIsMin_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:87— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenOffsetIsLessThanMax_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:95— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenSortIsNull_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:123— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenFilterIsNull_ThenSucceeds src/Framework/Infrastructure/Infrastructure.Web.Api.Common.UnitTests/Validation/HasSearchOptionsValidatorSpec.cs:141— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/DeleteCarRequestValidatorSpec.cs:29— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/GetCarRequestValidatorSpec.cs:29— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSuccess src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/RegisterCarRequestValidatorSpec.cs:30— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/ReleaseCarAvailabilityRequestValidatorSpec.cs:34— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/ReserveIfAvailableCarRequestValidatorSpec.cs:35— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/ScheduleMaintenanceCarRequestValidatorSpec.cs:34— Test method exercises code but verifies nothing — add an assertion.
No assertions: WhenAllProperties_ThenSuccess src/Subdomains/Core/CarsInfrastructure.UnitTests/Api/Cars/SearchAllAvailableCarsRequestValidatorSpec.cs:25— Test method exercises code but verifies nothing — add an assertion.
Off the main sequence: Tools.Generators.Common — Tools.Generators.Common: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Tools.Analyzers.Common — Tools.Analyzers.Common: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.External.Common — Infrastructure.External.Common: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Tools.Generators.Web.Api.Authorization — Tools.Generators.Web.Api.Authorization: abstractness 0.01, instability 0.00, distance 0.99 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Tools.Generators.Workers — Tools.Generators.Workers: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Web.Interfaces — Infrastructure.Web.Interfaces: abstractness 0.00, instability 0.02, distance 0.98 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Domain.Shared — Domain.Shared: abstractness 0.00, instability 0.03, distance 0.97 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Application.Common — Application.Common: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Application.Resources.Shared — Application.Resources.Shared: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Application.Persistence.Common — Application.Persistence.Common: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Common — Common: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Domain.Events.Shared — Domain.Events.Shared: abstractness 0.00, instability 0.08, distance 0.92 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Application.Interfaces — Application.Interfaces: abstractness 0.09, instability 0.02, distance 0.90 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Web.Common — Infrastructure.Web.Common: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Persistence.Common — Infrastructure.Persistence.Common: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Web.Api.Operations.Shared — Infrastructure.Web.Api.Operations.Shared: abstractness 0.00, instability 0.18, distance 0.82 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Persistence.Shared — Infrastructure.Persistence.Shared: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Shared — Infrastructure.Shared: abstractness 0.00, instability 0.24, distance 0.76 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.External.Persistence.Common — Infrastructure.External.Persistence.Common: abstractness 0.00, instability 0.24, distance 0.76 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Common — Infrastructure.Common: abstractness 0.00, instability 0.24, distance 0.76 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.External.Persistence.TestingOnly — Infrastructure.External.Persistence.TestingOnly: abstractness 0.00, instability 0.26, distance 0.74 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: EndUsersDomain — EndUsersDomain: abstractness 0.00, instability 0.28, distance 0.72 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure.Eventing.Common — Infrastructure.Eventing.Common: abstractness 0.00, instability 0.28, distance 0.72 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: UserProfilesDomain — UserProfilesDomain: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: CarsDomain — CarsDomain: abstractness 0.00, instability 0.30, distance 0.70 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
HackComment src/ExternalAdapters/Infrastructure.External.Persistence.TestingOnly/ApplicationServices/InProcessInMemStore.IEventStore.cs:88— //HACK: we use QueryEntity.ToDto() here, since EventSourcedChangeEvent can be rehydrated without a IDomainFactory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/ExternalAdapters/Infrastructure.External.Persistence.TestingOnly/ApplicationServices/LocalMachineJsonFileStore.IEventStore.cs:95— //HACK: we use QueryEntity.ToDto() here, since EventSourcedChangeEvent can be rehydrated without a IDomainFactory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Framework/Infrastructure/Infrastructure.Web.Api.Common/Extensions/HttpRequestExtensions.cs:48— //HACK: we assume that an empty JSON request was signed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Framework/Tools/Tools.Generators.Common.UnitTests/FeatureFlagGeneratorSpec.cs:19— //HACK: required to analyze custom attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Framework/Tools/Tools.Generators.Web.Api.Authorization.UnitTests/AuthorizationAttributeGeneratorSpec.cs:18— //HACK: required to analyze custom attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Framework/Tools/Tools.Generators.Web.Api.UnitTests/MinimalApiGeneratorSpec.cs:23— //HACK: required to analyze custom attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Framework/Tools/Tools.Generators.Web.Api.UnitTests/WebApiAssemblyVisitorSpec.cs:25— //HACK: required to analyze use custom attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Hosts/ApiHost1.IntegrationTests/GeneralApiSpec.cs:76— //HACK: notice that all enum values in the route or query must be case sensitive! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Hosts/ApiHost1.IntegrationTests/GeneralApiSpec.cs:144— //HACK: notice that all enum values in the route or query must be case sensitive! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Hosts/ApiHost1.IntegrationTests/GeneralApiSpec.cs:211— //HACK: notice that all enum values in the route or query must be case sensitive! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Hosts/WebsiteHost.IntegrationTests/AuthNApiSpec.cs:40— //HACK: to ensure that the new token is not the same (in time) as the old token — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Subdomains/Generic/IdentityInfrastructure.IntegrationTests/AuthTokensApiSpec.cs:56— //HACK: to ensure that the new token is not the same (in time) as the old token — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Subdomains/Generic/IdentityInfrastructure.IntegrationTests/AuthTokensApiSpec.cs:73— //HACK: to ensure that the new token is not the same (in time) as the old token — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Subdomains/Generic/ImagesApplication/ImagesApplication.cs:72— //HACK: possibly a better way to buffer this data in memory? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/Subdomains/Generic/SubscriptionsApplication/SubscriptionApplication_ProviderNotifications.cs:273— // HACK: what to do if we don't have a subscription? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Hotspot: src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.cs src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.cs— src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.cs changed 3 times in last 90 days, max complexity 45. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: src/Subdomains/Generic/EndUsersDomain/EndUserRoot.cs src/Subdomains/Generic/EndUsersDomain/EndUserRoot.cs— src/Subdomains/Generic/EndUsersDomain/EndUserRoot.cs changed 3 times in last 90 days, max complexity 45. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: src/Subdomains/Generic/IdentityDomain/PersonCredentialRoot.cs src/Subdomains/Generic/IdentityDomain/PersonCredentialRoot.cs— src/Subdomains/Generic/IdentityDomain/PersonCredentialRoot.cs changed 3 times in last 90 days, max complexity 41. 3 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: src/Subdomains/Generic/AncillaryApplication/AncillaryApplication.Emailing.cs src/Subdomains/Generic/AncillaryApplication/AncillaryApplication.Emailing.cs— src/Subdomains/Generic/AncillaryApplication/AncillaryApplication.Emailing.cs changed 2 times in last 90 days, max complexity 32. 2 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: src/Subdomains/Generic/SubscriptionsApplication/SubscriptionsApplication_DomainEventHandlers.cs src/Subdomains/Generic/SubscriptionsApplication/SubscriptionsApplication_DomainEventHandlers.cs— src/Subdomains/Generic/SubscriptionsApplication/SubscriptionsApplication_DomainEventHandlers.cs changed 2 times in last 90 days, max complexity 24.
Hotspot: src/ExternalAdapters/Infrastructure.External.Persistence.TestingOnly/ApplicationServices/LocalMachineJsonFileStore.cs src/ExternalAdapters/Infrastructure.External.Persistence.TestingOnly/ApplicationServices/LocalMachineJsonFileStore.cs— src/ExternalAdapters/Infrastructure.External.Persistence.TestingOnly/ApplicationServices/LocalMachineJsonFileStore.cs changed 1 times in last 90 days, max complexity 46. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.Trials.cs src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.Trials.cs— src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.Trials.cs changed 2 times in last 90 days, max complexity 21.
Hotspot: src/Subdomains/Generic/EndUsersInfrastructure/Persistence/ReadModels/EndUserProjection.cs src/Subdomains/Generic/EndUsersInfrastructure/Persistence/ReadModels/EndUserProjection.cs— src/Subdomains/Generic/EndUsersInfrastructure/Persistence/ReadModels/EndUserProjection.cs changed 1 times in last 90 days, max complexity 40.
Hotspot: src/Framework/Infrastructure/Infrastructure.Web.Hosting.Common/Extensions/HostExtensions.cs src/Framework/Infrastructure/Infrastructure.Web.Hosting.Common/Extensions/HostExtensions.cs— src/Framework/Infrastructure/Infrastructure.Web.Hosting.Common/Extensions/HostExtensions.cs changed 1 times in last 90 days, max complexity 39. 1 of those changes were fix/bug commits — a defect-dense hotspot worth prioritising.
Hotspot: src/Subdomains/Generic/SubscriptionsApplication/SubscriptionsApplication_Quotas.cs src/Subdomains/Generic/SubscriptionsApplication/SubscriptionsApplication_Quotas.cs— src/Subdomains/Generic/SubscriptionsApplication/SubscriptionsApplication_Quotas.cs changed 1 times in last 90 days, max complexity 38.
Low cohesion: TestingWebApi (LCOM4 34) src/Hosts/ApiHost1/Api/TestingOnly/TestingWebApi.cs:16— TestingWebApi's methods form 34 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.
Low cohesion: EmailDeliveryRoot (LCOM4 5) src/Subdomains/Generic/AncillaryDomain/EmailDeliveryRoot.cs:16— EmailDeliveryRoot's methods form 5 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.
Low cohesion: SmsDeliveryRoot (LCOM4 4) src/Subdomains/Generic/AncillaryDomain/SmsDeliveryRoot.cs:15— SmsDeliveryRoot'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.
Low cohesion: MfaService (LCOM4 4) src/Subdomains/Generic/IdentityInfrastructure/ApplicationServices/MfaService.cs:17— MfaService'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.
TodoComment src/Subdomains/Generic/SubscriptionsDomain/SubscriptionQuotaUsageRoot.cs:107— //TODO: add your other invariant rules here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[0].suggestion | LineNumber: 0 | BytePositionInLine: 1076.
D20 · ADR Quality· Context/problem and consequences/trade-offs are absent from the visible text · ×1
Context/problem and consequences/trade-offs are absent from the visible text docs/design-principles/0020-api-framework.md— Add a Context section explaining why ASP.NET Minimal API was chosen over controllers (e.g. testability, pluggable modules) and a Consequences section covering trade-offs such as loss of routing flexibility or boilerplate for source generators
D20 · ADR Quality· Decision is a thin implementation heading with no context/problem and no consequences; the title 'Dependency Injection' names only the subject · ×1
Decision is a thin implementation heading with no context/problem and no consequences; the title 'Dependency Injection' names only the subject docs/design-principles/0060-dependency-injection.md— Add Context: why dependency injection was chosen over alternatives (e.g. coupling vs testability), and Consequences: trade-offs like boilerplate or breaking existing code
D20 · ADR Quality· Context/problem and consequences/trade-offs are absent; only how-to sections with no rationale · ×1
Context/problem and consequences/trade-offs are absent; only how-to sections with no rationale docs/design-principles/0210-javascript-forms.md— Add a Context section explaining why forms need this ID-based testing/styling system (e.g. accessibility, component reuse) and a Consequences section on trade-offs such as requiring id attributes on every HTML element
Coverage not measured — test suite did not build — Coverage NOT MEASURED: the repo's own test suite did not build (a C#/MSBuild compiler error in the test code), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. Fix the test build, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage will be measured.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Audits/DeliverAuditRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Audits/SearchAuditsRequestValidatorSpec.cs:21— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenOrganizationIdExists_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Audits/SearchAuditsRequestValidatorSpec.cs:27— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Emails/SearchAllEmailDeliveriesRequestValidatorSpec.cs:24— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenOrganizationIdExists_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Emails/SearchAllEmailDeliveriesRequestValidatorSpec.cs:30— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenSinceUtcIsPast_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Emails/SearchAllEmailDeliveriesRequestValidatorSpec.cs:47— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenTagIsValid_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Emails/SearchAllEmailDeliveriesRequestValidatorSpec.cs:65— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Emails/SendEmailRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/FeatureFlags/GetFeatureFlagForCallerRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/FeatureFlags/GetFeatureFlagRequestValidatorSpec.cs:33— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenTenantIdIsEmpty_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/FeatureFlags/GetFeatureFlagRequestValidatorSpec.cs:49— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Provisionings/NotifyProvisioningRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Recording/RecordMeasureRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAdditionalIsNull_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Recording/RecordMeasureRequestValidatorSpec.cs:41— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Recording/RecordUsageRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAdditionalIsNull_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Recording/RecordUsageRequestValidatorSpec.cs:41— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Smses/SearchAllSmsDeliveriesRequestValidatorSpec.cs:24— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenOrganizationIdExists_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Smses/SearchAllSmsDeliveriesRequestValidatorSpec.cs:30— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenSinceUtcIsPast_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Smses/SearchAllSmsDeliveriesRequestValidatorSpec.cs:47— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenTagIsValid_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Smses/SearchAllSmsDeliveriesRequestValidatorSpec.cs:65— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Smses/SendSmsRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/AncillaryInfrastructure.UnitTests/Api/Usages/DeliverUsageRequestValidatorSpec.cs:25— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/ImagesInfrastructure.UnitTests/Api/Images/DeleteImageRequestValidatorSpec.cs:24— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/ImagesInfrastructure.UnitTests/Api/Images/DownloadImageRequestValidatorSpec.cs:24— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
No direct assertions: WhenAllProperties_ThenSucceeds src/Subdomains/Generic/ImagesInfrastructure.UnitTests/Api/Images/GetImageRequestValidatorSpec.cs:24— In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
Shell project: UnitTesting.CodeAnalysis.Common src/Framework/Testing/UnitTesting.CodeAnalysis.Common/UnitTesting.CodeAnalysis.Common.csproj— `UnitTesting.CodeAnalysis.Common` contributes only 9 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Infrastructure.External.Common src/Framework/Infrastructure/Infrastructure.External.Common/Infrastructure.External.Common.csproj— `Infrastructure.External.Common` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 234 significant file(s) lose their only recent owner (largest: src/Subdomains/Generic/SubscriptionsDomain/SubscriptionRoot.cs). Pair on, review, or document these before any departure.
Thin analysable surface across projects — 3 project(s) carry only a thin slice of real code (e.g. `Tools.Generators.Web.Api.UnitTests.TestData` with 12 significant line(s)). The mean analysable-surface weight is 97 %, lowering Solution Shape by about 0.2 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 88k LoC across 142 projects the codebase is both large and multi-module, so explicit bounded contexts are needed. Declare architecture.contexts (≥2) in config to assess cross-boundary type coupling.
Split Common — Generic catch-all name at 6906 LoC and 167 types across 6 namespaces is a sprawling grab-bag. Suggested: by namespace: split the 6 namespaces into focused shared libraries
Split Infrastructure.Web.Api.Operations.Shared — Generic Infrastructure name at 3384 LoC and 286 types across 18 namespaces is a large sprawling grab-bag. Suggested: by namespace: split the 18 namespaces into focused shared libraries
Split Domain.Events.Shared — Generic Domain name at 2788 LoC and 157 types across 22 namespaces is a large grab-bag. Suggested: by namespace: split the 22 namespaces into focused shared libraries
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.)
Dormant codebase — 279 of 361 significant files have no living knowledge — the codebase as a whole is dormant, not 279 separate risks. Re-engage owners or document before change.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a NuGet package, a container image, a GitHub release).
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
Run 019f1546-8266-7faf-8d80-b8ec9f5da038 · 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 — 131 field(s) across 4 categories, 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: 40 · Warnings: 462 · Recommendations: 43 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-06-2026 @ 21:26 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.