aspnetrun/run-aspnetcore-cqrs

Executive summary

Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.

aspnetrun/run-aspnetcore-cqrs carries serious risk (40%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.

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 (25%) — operating, monitoring and recovering the system safely is harder. Accessibility (45%) is the next concern — it raises ongoing delivery and operational cost.

Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); unused dependencies, declare unlisted imports explicitly,… (Dependency Hygiene); 8 Deprecated finding(s) in Dependency Hygiene (Dependency Hygiene).

For scale: Small (~5,488 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.

Code Health 63% Adequate Architecture 80% Strong Maturity 54% Adequate · gated by M2 Readiness 25% Weak · gated by D12, R8, P1, P3 Security 56% Adequate · gated by D30, D38, C1 Accessibility 45% Weak

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

Readiness 25% · 46% weightAccessibility 45% · 25% weightMaturity 54% · 14% weightSecurity 56% · 8% weightCode Health 63% · 4% weightArchitecture 80% · 2% weight

Raise Readiness 25 → 70 (the Healthy floor) ⇒ headline 40 → ~52.

Code composition — where the lines go

Business logic 8%Plumbing 69%Tests 0%Generated 23%

Rebuild cost & value ~ Modeled — €1,800–€8,800

Cost to rebuild	€1,800–€8,800 (0.1 person-years (30–93 h), ~1 engineer)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.7× (at 40% quality) — the last 20% of quality is most of the work
Size & shape	Small · 43% boilerplate · 46% straight-line · 11% branching logic
Dead frontend code	~20 LoC unreachable (1 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 ~0.1 person-years of build effort (about ~€5,300 to rebuild). Its weakest lens is Readiness at 25% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — service/app, CQRS × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

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

Resolve the 8 Deprecated finding(s) in Dependency Hygiene.

+13.0 pts · Low effort · Dependency Hygiene

Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.

+9.4 pts · Low effort · Dependency Hygiene

Add a CI workflow that builds and runs the test suite on every push/PR.

+13.5 pts · Medium effort · CI/CD gates

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk

This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Readiness at 25%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Small, ~0.1 person-years rebuild (5,488 LoC) · weakest lens: Readiness 25%

→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.

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

→ Add a CI workflow that builds and runs the test suite on every push/PR.

Improving trajectory · Info · Trajectory

The headline is improving steadily (+8.6 pts/run over 5 runs) — whatever you're doing is working; keep the gate.

Evidence: trajectory: +8.6 pts/run over 5 runs

Trajectory

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A06:2021 — Vulnerable & Outdated Components	72	High / Critical

Roadmap

First, establish a continuous integration pipeline to build and test every change immediately. Next, clean up the dependency tree by removing unused packages, explicitly declaring imports, and moving type and test-only packages to development dependencies. Then, address the eight deprecated dependency warnings to improve security and stability. After that, extend structured logging across all service-like projects to ensure full observability in production. Finally, add missing tooling such as eslint and tsc as package scripts and integrate them into the CI process.

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

Do this	Helps	Effort	Dimension
Resolve the 8 Deprecated finding(s) in Dependency Hygiene.	+13.0 pts	Low	Dependency Hygiene
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.	+9.4 pts	Low	Dependency Hygiene
Add a CI workflow that builds and runs the test suite on every push/PR.	+13.5 pts	Medium	CI/CD gates
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+13.5 pts	Medium	Dependency Hygiene
Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.	+12.4 pts	Medium	Observability
Add the missing tooling (eslint, tsc) as package.json scripts and run them in CI.	+11.9 pts	Medium	Tooling
Bump outdated dependencies to current versions to limit upgrade debt.	+11.6 pts	Medium	Dependency Freshness
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs.	+5.8 pts	Low	Test Quality

File quality

Per-file score 0–10 — a quality signature. Of 11 files carrying findings, judged against the Production bar: 0% slop · 36% mixed · 64% near-clean.

File	Score	Band	Worst signal
src/AspnetRun.Web/package-lock.json	4.4	Mixed	OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted]
src/AspnetRun.Infrastructure/Repository/ProductRepository.cs	6.4	Mixed	Explicit Debt: TodoComment
src/AspnetRun.Infrastructure/Misc/AppDomainTypeFinder.cs	6.7	Mixed	Explicit Debt: CommentedOutCode
src/AspnetRun.Infrastructure/Data/AspnetRunContextSeed.cs	6.7	Mixed	Explicit Debt: TodoComment
test/AspnetRun.Tests/UnitTest1.cs	8.0	Near-clean	Test Quality: No assertions (empty test): Test1
src/AspnetRun.Application/Services/CustomerService.cs	8.2	Near-clean	Explicit Debt: CommentedOutCode
src/AspnetRun.Application/Services/ProductService.cs	8.2	Near-clean	Explicit Debt: TodoComment
src/AspnetRun.Core/Specifications/Base/ISpecification.cs	8.2	Near-clean	Explicit Debt: TodoComment
src/AspnetRun.Infrastructure/Data/AspnetRunCustomModelBuilder.cs	8.2	Near-clean	Explicit Debt: Dead code: AspnetRunCustomModelBuilder
src/AspnetRun.Infrastructure/Misc/AppFileProvider.cs	8.5	Near-clean	God Classes: TooManyMethods: AppFileProvider
src/AspnetRun.Web/src/app/shared/shared.module.ts	8.5	Near-clean	Change Coupling: Change coupling: shared.module.ts ↔ product-list.component.ts

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. 64 of 66 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 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 — 66 dimensions across the health lenses

D1D2D3D4D5D6D9D10D11D12D13D14D15D16D17D18D19D20D21D26D27D28D29D30D33D34D35D38D39AC1AC2AC3AC5AC6AC7AX10AX3AX5AX6AX8C1C2GD1IC1M1M2M3M4P1P2P3P8R1R10R2R3R5R6R7R8R9S1X1X2X3X4

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 019f1552-2195-75f2-a34c-1087a30a6257.

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

Run transparency — what happened this run

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

D24 Comment Value — 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.
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.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
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.
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.
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.
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.

The LLM boundary

LLM-set scores this run (4): D19, D20, D21, 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.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity9.2 / 10Exemplary✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was AppDomainTypeFinder.FindClassesOfType at 30.

AppDomainTypeFinder.FindClassesOfType (cognitive 30)src/AspnetRun.Infrastructure/Misc/AppDomainTypeFinder.cs:224

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D3 · God Classes8.4 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

2 god class(es) detected.

ClassTooLong: AspnetRunContextSeedsrc/AspnetRun.Infrastructure/Data/AspnetRunContextSeed.cs:0

TooManyMethods: AppFileProvidersrc/AspnetRun.Infrastructure/Misc/AppFileProvider.cs:0

What to do

Resolve the 1 ClassTooLong finding(s) in God Classes — start with AspnetRunContextSeed.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TooManyMethods finding(s) in God Classes — start with AppFileProvider.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 duplicated block group(s) detected.

✓ On the Gold path — maintain.

Detailed fixes: d4_recommendation.md.

Do you agree with this assessment?

D5 · Coupling10.0 / 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.

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

5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Layer violation: Application → Infrastructure

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

0 of 12 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_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.

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

1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality6.2 / 10Adequate✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests.

No assertions (empty test): Test1test/AspnetRun.Tests/UnitTest1.cs:8

What to do

Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs. — One of this dimension's main actionable groups (1 issue-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). unit: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene2.5 / 10Critical✓ Tool-verified

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

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

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

13 outdated, 3 vulnerable, 8 deprecated packages.

Vulnerable: Microsoft.NETCore.App · ×3

Deprecated: Microsoft.AspNetCore.Hosting · ×8

Outdated: Autofac.Extensions.DependencyInjection · ×13

What to do

Resolve the 8 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 issue-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 13 packages use a banned license.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

No source file's living knowledge is concentrated in a single author.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt9.5 / 10Exemplary✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

8 deducted debt markers + 1 dead symbols across 4353 LoC (0.2/KLoC) → score 9.5.

TodoComment · ×5src/AspnetRun.Application/Services/ProductService.cs:40

CommentedOutCode · ×3src/AspnetRun.Application/Services/CustomerService.cs:14

Dead code: AspnetRunCustomModelBuildersrc/AspnetRun.Infrastructure/Data/AspnetRunCustomModelBuilder.cs:6

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D18 · Solution Shape8.5 / 10Strong✓ Tool-verified

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.

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

5 projects, 101 .cs files, 4369 hand-written lines of code (4353 production / 16 test), plus 1616 generated (EF migrations / designer / snapshots, excluded from quality), 6 inter-project edges.

Thin analysable surface across projects

What to do

Resolve the 1 Thin analysable surface across projects finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D19 · Documentation Quality / 10Adequate◐ Sampled · advisory

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

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

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

The AspnetRun project has a strong README with an excellent What-is-AspnetRun section and a dedicated AspnetRun Repositories list that is clipped mid-sentence (the full outline exists), plus a standalone Angular CLI README covering dev server, scaffolding, build, test commands. The repository's XML-doc coverage is low: only 60% for the Infrastructure layer and zero for Application/Api/Core layers, so much of the project's domain-specific content is undocumented.

XML-doc coverage: AspnetRun.Infrastructure · ×4src/AspnetRun.Infrastructure/AspnetRun.Infrastructure.csproj

What to do

Improve Documentation Quality — currently 6.0/10. — The AspnetRun project has a strong README with an excellent What-is-AspnetRun section and a dedicated AspnetRun Repositories list that is clipped mid-sentence (the full outline exists), plus a standalone Angular CLI README covering dev server, scaffolding, build, test commands. The repository's XML-doc coverage is low: only 60% for the Infrastructure layer and zero for Application/Api/Core layers, so much of the project's domain-specific content is undocumented.

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

Do you agree with this assessment?

D20 · ADR Quality / 10Critical◐ 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.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming Consistency / 10Exemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 5 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability9.7 / 10Exemplary✓ 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.

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

96 % of calls cross a namespace and 5 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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

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

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

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

22 vulnerable package(s): 2 critical, 11 high, 9 medium, 0 low.

REDACTED

What to do

Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (11 issue-level).
Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (2 issue-level).

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

Do you agree with this assessment?

D33 · JS/npm Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether JavaScript/npm dependencies have known published vulnerabilities (CVEs) — the npm ecosystem's biggest risk.

Method: JS/npm CVE scan via trivy fs --scanners vuln over JS manifests (package.json/yarn.lock/pnpm-lock/bun.lockb); 0-10 tight normalizer. NotApplicable without JS manifests. Exhaustive, deterministic.

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

No known-vulnerable JS/npm dependencies.

✓ On the Gold path — maintain.

Detailed fixes: d33_recommendation.md.

Do you agree with this assessment?

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

Every significant source file has living knowledge — recently and meaningfully worked.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

Do you agree with this assessment?

D35 · Change Coupling9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.

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

Strongest change-coupling: shared.module.ts↔product-list.component.ts 60%

Change coupling: shared.module.ts ↔ product-list.component.tssrc/AspnetRun.Web/src/app/shared/shared.module.ts

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D38 · OSV Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

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

225 finding(s): 24 critical, 88 high, 88 medium, 25 low.

High CVE: [GHSA redacted] · ×26src/AspnetRun.Web/package-lock.jsondetected by osv-scanner finding

Critical CVE: [GHSA redacted] · ×24src/AspnetRun.Web/package-lock.jsondetected by osv-scanner finding

What to do

Resolve the 26 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (26). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 24 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (24). — One of this dimension's main actionable groups (24 issue-level).

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

Do you agree with this assessment?

D39 · IL Efficiency9.8 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

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

3 of 254 first-party methods have an oversized IL body.

IL efficiency: 3 authored method(s) exceed the IL budgetsrc/AspnetRun.Infrastructure/Repository/ProductRepository.cs:42

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — customer-detail.component.html:26

What to do

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, and a captions <track> on video.

Do you agree with this assessment?

AC2 · Forms & labels4.4 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×9) — customer-cart.component.html:84, 404.component.html:14, 500.component.html:14, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×10) — customer-edit.component.html:5, customer-edit.component.html:10, customer-edit.component.html:15, …

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 structure4.5 / 10Weak✓ 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. (×4) — customer-cart.component.html:23, customer-cart.component.html:55, 404.component.html:7, …
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — customer-order.component.html:5
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — product-delete-modal.component.html:6
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — index.html:2

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.

Do you agree with this assessment?

AC5 · ARIA correctness5.5 / 10Adequate✓ Tool-verified

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.

aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. — product-delete-modal.component.html:1

What to do

Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.

Do you agree with this assessment?

AC6 · Visual & motion safety5.4 / 10Adequate✓ Tool-verified

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.

A CSS rule's foreground/background colour pair falls below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — customer-list.component.css:0, customer-detail.component.css:0

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.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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.

Do you agree with this assessment?

AX10 · Code composition4.0 / 10Weak✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.

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

Do you agree with this assessment?

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX6 · Interface segregation9.5 / 10Exemplary✓ Tool-verified

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.

`IAppFileProvider` declares 33 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. — IAppFileProvider.cs:12
`ISpecification` declares 16 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. — ISpecification.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 isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

C1 · Data Protection3.0 / 10Weak✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).

Do you agree with this assessment?

C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code9.8 / 10Exemplary✓ Tool-verified

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 placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. (×25) — AspnetRunContextSeed.cs:117, AspnetRunContextSeed.cs:118, AspnetRunContextSeed.cs:129, …

What to do

Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.4 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

`GetCustomers` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — CustomerController.cs:30
`GetCustomerById` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — CustomerController.cs:80
`GetCustomerList` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — CustomerService.cs:28
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×11) — CustomerController.cs:35, CustomerController.cs:85, Startup.cs:123, …
A placeholder value ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — sample/mock data that was never replaced with the real thing. (×16) — AspnetRunContextSeed.cs:117, AspnetRunContextSeed.cs:118, AspnetRunContextSeed.cs:129, …

What to do

Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.

Do you agree with this assessment?

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

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

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

What to do

Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — decisions aren't captured for future maintainers.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.

What to do

Start an ADR log (docs/adr/) recording significant decisions and their rationale.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M4 · Documentation accuracy6.0 / 10Adequate◐ Sampled · advisory

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

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

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.

Do you agree with this assessment?

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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

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

No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

Add a CI workflow that builds and runs the test suite on every push/PR.

Do you agree with this assessment?

P2 · Observability6.0 / 10Adequate✓ Tool-verified

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

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

Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log).

What to do

Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.

No static application security testing (CodeQL / security analyzers / codehealth) detected.

What to do

Add a SAST step (e.g. CodeQL) or a security analyzer package.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage. Exhaustive per project, deterministic.

Do you agree with this assessment?

R1 · Type Safety9.6 / 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.

Do you agree with this assessment?

R10 · Code Duplication5.9 / 10Adequate✓ Tool-verified

React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).

Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.

src/AspnetRun.Web/src/app/views/category/category-list/category-list.component.ts:9 · src/AspnetRun.Web/src/app/views/product/product-list/product-list.component.ts:9 — category-list.component.ts:9
src/AspnetRun.Web/src/app/views/category/category-list/category-list.component.ts:69 · src/AspnetRun.Web/src/app/views/product/product-list/product-list.component.ts:70 — category-list.component.ts:69
src/AspnetRun.Web/src/app/app.module.ts:11 · src/AspnetRun.Web/src/app/shared/shared.module.ts:5 — app.module.ts:11
src/AspnetRun.Web/src/app/views/product/product-detail/product-detail.component.ts:1 · src/AspnetRun.Web/src/app/views/product/product-edit/product-edit.component.ts:4 — product-detail.component.ts:1
src/AspnetRun.Web/src/app/core/services/category-data.service.ts:5 · src/AspnetRun.Web/src/app/core/services/customer-data.services.ts:6 · src/AspnetRun.Web/src/app/core/services/product-data.service.ts:5 — category-data.service.ts:5
src/AspnetRun.Web/src/app/views/category/category-routing.module.ts:11 · src/AspnetRun.Web/src/app/views/customer/customer-routing.module.ts:21 · src/AspnetRun.Web/src/app/views/product/product-routing.module.ts:17 — category-routing.module.ts:11
src/AspnetRun.Web/src/app/views/customer/customer-routing.module.ts:4 · src/AspnetRun.Web/src/app/views/product/product-routing.module.ts:2 — customer-routing.module.ts:4
src/AspnetRun.Web/src/app/app-routing.module.ts:2 · src/AspnetRun.Web/src/app/app.module.ts:1 · src/AspnetRun.Web/src/app/core/core.module.ts:2 · src/AspnetRun.Web/src/app/core/core.module.ts:15 — app-routing.module.ts:2

What to do

Extract the duplicated blocks into shared functions/components.

Do you agree with this assessment?

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

R3 · Large Files10.0 / 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.

Do you agree with this assessment?

R5 · Dependency Freshness7.0 / 10Strong✓ Tool-verified

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 · Tooling6.7 / 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 Code9.4 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

Unreachable from the 1 application, 5 tooling and 3 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 (1 application, 5 tooling, 3 test roots considered) — test.ts
Nothing imports this binding — it is safe to review for removal. (×3) — category.module.ts:13, customer.module.ts:17, product.module.ts:13

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene1.5 / 10Critical✓ Tool-verified

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/AspnetRun.Web/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×3)

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 Imports10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

S1 · Web-Security Posture6.5 / 10Adequate✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. Deterministic.

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.)
No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)

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.
Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.

Do you agree with this assessment?

X1 · Async correctness7.1 / 10Strong✓ Tool-verified

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. — Program.cs:24

What to do

Sync-over-async (deadlock risk)

Do you agree with this assessment?

X2 · Cancellation propagation4.5 / 10Weak✓ Tool-verified

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 4/51 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) — AspnetRunContext.cs:37, AspnetRunContext.cs:42, AspnetRunContextSeed.cs:47, …

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

Do you agree with this assessment?

X4 · Structured logging4.6 / 10Weak✓ Tool-verified

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)`. (×3) — TransactionBehaviour.cs:32, TransactionBehaviour.cs:40, TransactionBehaviour.cs:47

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

Not statically assessed — these 42 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	63%	Adequate	Acceptable, with room to improve.
Architecture	80%	Strong	Strongest area.
Maturity	54%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	25%	Weak — gated by D12, R8, P1, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	56%	Adequate — gated by D30, D38, C1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	45%	Weak	Below par — needs attention.

Not included — 39 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.

AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
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 — 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.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
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 — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — not run — 0/3 markers found
ED1 Event-Driven — applicable but skipped (2/3 markers — below the conservative bar): a message-bus package; 3 CQRS handler(s)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — 0/3 markers found
P12 CI test-gate honesty — no CI workflow found
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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
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
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 3 test file(s) reach none of 49 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — no data
X5 Nullable reference types — no NRT-eligible projects
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 — 68 finding(s)

D38 · OSV Dependency Vulnerabilities · High CVE · ×26

High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/common: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/common: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/common: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/common: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/common: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/compiler: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/compiler: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/core: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @angular/core: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — acorn: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — ansi-html: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — ansi-regex: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — async: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — body-parser: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — braces: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — browserify-sign: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — cross-spawn: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — decode-uri-component: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — dns-packet: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — dompurify: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — dompurify: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — elliptic: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — engine.io: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — flatted: [GHSA redacted]
High CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — flatted: [GHSA redacted]
+ 1 more in this group — see findings.md.

D38 · OSV Dependency Vulnerabilities · Critical CVE · ×24

Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — @babel/traverse: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — cipher-base: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — dompurify: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — dompurify: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — elliptic: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — eventsource: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — form-data: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — fsevents: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — handlebars: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — handlebars: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — handlebars: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — json-schema: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — loader-utils: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — minimist: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — mixin-deep: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — pbkdf2: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — pbkdf2: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — set-value: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — sha.js: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — socket.io-parser: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — tree-kill: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — url-parse: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — xmlhttprequest-ssl: [GHSA redacted]
Critical CVE: [GHSA redacted] src/AspnetRun.Web/package-lock.json — xmlhttprequest-ssl: [GHSA redacted]

D30 · Dependency Vulnerabilities · High CVE · ×11

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D12 · Dependency Hygiene · Vulnerable · ×3

Vulnerable: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) severity. 2.2.0
Vulnerable: AutoMapper — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Microsoft.AspNetCore.App — Microsoft.AspNetCore.App [2.2.0, — ) severity. 2.2.0

D30 · Dependency Vulnerabilities · Critical CVE · ×2

REDACTED
REDACTED

D10 · Test Quality · No assertions (empty test) · ×1

No assertions (empty test): Test1 test/AspnetRun.Tests/UnitTest1.cs:8 — Test method has an empty body — it asserts nothing and exercises no code.

D5 · Coupling · Layer violation · ×1

Layer violation: Application → Infrastructure — AspnetRun.Application (Application) references AspnetRun.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).

Warning — 32 finding(s)

D30 · Dependency Vulnerabilities · Medium CVE · ×9

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D12 · Dependency Hygiene · Deprecated · ×8

Deprecated: Microsoft.AspNetCore.Hosting — Microsoft.AspNetCore.Hosting 2.2.0 — Other,Legacy
Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 2.2.0 — Other,Legacy
Deprecated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 2.2.4 — Other,Legacy
Deprecated: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) 2.2.0 Other,Legacy
Deprecated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 8.4.0 — Legacy
Deprecated: Microsoft.AspNetCore.App — Microsoft.AspNetCore.App [2.2.0, — ) 2.2.0 Other,Legacy
Deprecated: xunit — xunit 2.4.1 — Legacy xunit.v3 >= 0.0.0
Deprecated: Microsoft.Extensions.Identity.Stores — Microsoft.Extensions.Identity.Stores 2.2.0 — Other,Legacy

D17 · Explicit Debt · TodoComment · ×5

TodoComment src/AspnetRun.Application/Services/ProductService.cs:40 — //TODO: PagedList<TSource> will be mapped to PagedList<TDestination>; — 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.
TodoComment src/AspnetRun.Core/Specifications/Base/ISpecification.cs:19 — // TODO: Paging should be optimized — 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.
TodoComment src/AspnetRun.Infrastructure/Data/AspnetRunContextSeed.cs:49 — // TODO: Only run this if using a real database — 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.
TodoComment src/AspnetRun.Infrastructure/Repository/ProductRepository.cs:26 — //TODO: should be refactored — 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.
TodoComment src/AspnetRun.Infrastructure/Repository/ProductRepository.cs:73 — //TODO: FilteringOption.Operator will be handled — 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.

D17 · Explicit Debt · CommentedOutCode · ×3

CommentedOutCode src/AspnetRun.Application/Services/CustomerService.cs:14 — 5 consecutive commented-code lines
CommentedOutCode src/AspnetRun.Infrastructure/Misc/AppDomainTypeFinder.cs:137 — 5 consecutive commented-code lines
CommentedOutCode src/AspnetRun.Infrastructure/Repository/ProductRepository.cs:112 — 3 consecutive commented-code lines

D17 · Explicit Debt · Dead code · ×1

Dead code: AspnetRunCustomModelBuilder src/AspnetRun.Infrastructure/Data/AspnetRunCustomModelBuilder.cs:6 — NamedType AspnetRunCustomModelBuilder — no references found in solution.

D2 · Cognitive Complexity · AppDomainTypeFinder.FindClassesOfType (cognitive 30) · ×1

AppDomainTypeFinder.FindClassesOfType (cognitive 30) src/AspnetRun.Infrastructure/Misc/AppDomainTypeFinder.cs:224 — AppDomainTypeFinder.FindClassesOfType has cognitive complexity 30 (threshold 15).

D24 · Comment Value · LLM evaluation failed · ×1

LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.notable[4].suggestion | LineNumber: 0 | BytePositionInLine: 1002.

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: AspnetRunContextSeed src/AspnetRun.Infrastructure/Data/AspnetRunContextSeed.cs:0 — ClassTooLong — 447 lines, 8 methods.

D3 · God Classes · TooManyMethods · ×1

TooManyMethods: AppFileProvider src/AspnetRun.Infrastructure/Misc/AppFileProvider.cs:0 — TooManyMethods — 117 lines, 35 methods.

D35 · Change Coupling · Change coupling · ×1

Change coupling: shared.module.ts ↔ product-list.component.ts src/AspnetRun.Web/src/app/shared/shared.module.ts — `src/AspnetRun.Web/src/app/shared/shared.module.ts` and `src/AspnetRun.Web/src/app/views/product/product-list/product-list.component.ts` change together 60% of the time (9 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. Commit the Cobertura/OpenCover/lcov report your CI already produces (anywhere in the repo), or make the suite runnable in-image, and real coverage will be measured.

Recommendation — 4 finding(s)

D18 · Solution Shape · Thin analysable surface across projects · ×1

Thin analysable surface across projects — 1 project(s) carry only a thin slice of real code (e.g. `AspnetRun.Tests` with 12 significant line(s)). The mean analysable-surface weight is 81 %, lowering Solution Shape by about 1.5 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found at common paths; consider documenting architectural decisions in Docs/ADL/ or similar.

D23 · Boundary Type-Coupling · Bounded contexts not declared · ×1

Bounded contexts not declared — At 4353 LoC across 5 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Declare architecture.contexts (≥2) in config to assess cross-boundary type coupling.

D39 · IL Efficiency · IL efficiency · ×1

IL efficiency: 3 authored method(s) exceed the IL budget src/AspnetRun.Infrastructure/Repository/ProductRepository.cs:42 — 3 of 254 first-party methods compile to oversized IL bodies (> 250 instructions); worst: AspnetRun.Infrastructure.Repository.ProductRepository.SearchProductsAsync @ src/AspnetRun.Infrastructure/Repository/ProductRepository.cs:42, 436 IL instructions; large bodies don't JIT-inline, which pulled this dimension to 9.8/10; splitting the hottest bodies recovers the most.

Info — 18 finding(s)

D12 · Dependency Hygiene · Outdated · ×13

Outdated: Autofac.Extensions.DependencyInjection — Autofac.Extensions.DependencyInjection 4.4.0 → 11.0.1 available.
Outdated: MediatR — MediatR 7.0.0 → 14.1.0 available.
Outdated: Microsoft.AspNetCore.Hosting — Microsoft.AspNetCore.Hosting 2.2.0 → 2.3.11 available.
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 2.2.0 → 10.0.9 available.
Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 2.2.4 → 10.0.9 available.
Outdated: System.IO.FileSystem.AccessControl — System.IO.FileSystem.AccessControl 4.5.0 → 5.0.0 available.
Outdated: AutoMapper — REDACTED → 16.1.1 available.
Outdated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 8.4.0 → 11.3.1 available.
Outdated: NSwag.AspNetCore — NSwag.AspNetCore 12.2.5 → 14.7.1 available.
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 16.1.0 → 18.7.0 available.
Outdated: xunit — xunit 2.4.1 → 2.9.3 available.
Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.4.1 → 3.1.5 available.
Outdated: Microsoft.Extensions.Identity.Stores — Microsoft.Extensions.Identity.Stores 2.2.0 → 10.0.9 available.

D19 · Documentation Quality · XML-doc coverage · ×4

XML-doc coverage: AspnetRun.Infrastructure src/AspnetRun.Infrastructure/AspnetRun.Infrastructure.csproj — AspnetRun.Infrastructure: 49 % XML-doc coverage (60/123).
XML-doc coverage: AspnetRun.Application src/AspnetRun.Application/AspnetRun.Application.csproj — AspnetRun.Application: 0 % XML-doc coverage (0/49).
XML-doc coverage: AspnetRun.Api src/AspnetRun.Api/AspnetRun.Api.csproj — AspnetRun.Api: 0 % XML-doc coverage (0/86).
XML-doc coverage: AspnetRun.Core src/AspnetRun.Core/AspnetRun.Core.csproj — AspnetRun.Core: 3 % XML-doc coverage (5/175).

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config auto --json --quiet --timeout 0 --metrics off .	0	—
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list AspnetRunAngularRealWorld.sln package --vulnerable --include-transitive --format json	22	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.	0	—
D33 · JS/npm Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	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.	0	—
D38 · OSV Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	225	artifacts/raw/osv-scanner.json

Run 019f1552-2195-75f2-a34c-1087a30a6257 · 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 — 17 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.

Name — 7 field(s)

CustomerModel.FirstName src/AspnetRun.Application/Models/CustomerModel.cs:7
CustomerModel.LastName src/AspnetRun.Application/Models/CustomerModel.cs:8
Address.FirstName src/AspnetRun.Core/Entities/Address.cs:8
Address.LastName src/AspnetRun.Core/Entities/Address.cs:9
AspnetRunUser.FirstName src/AspnetRun.Core/Entities/AspnetRunUser.cs:9
AspnetRunUser.LastName src/AspnetRun.Core/Entities/AspnetRunUser.cs:11
Customer.Surname src/AspnetRun.Core/Entities/Customer.cs:9

Address — 5 field(s)

Address.ZipCode src/AspnetRun.Core/Entities/Address.cs:17
Contract.BillingAddressId src/AspnetRun.Core/Entities/Contract.cs:10
Contract.BillingAddress src/AspnetRun.Core/Entities/Contract.cs:11
Order.BillingAddressId src/AspnetRun.Core/Entities/Order.cs:10
Order.BillingAddress src/AspnetRun.Core/Entities/Order.cs:11

Email — 3 field(s)

LoginRequest.Email src/AspnetRun.Api/Requests/LoginRequest.cs:5
Address.EmailAddress src/AspnetRun.Core/Entities/Address.cs:10
Customer.Email src/AspnetRun.Core/Entities/Customer.cs:13

Phone — 2 field(s)

Address.PhoneNo src/AspnetRun.Core/Entities/Address.cs:11
Customer.Phone src/AspnetRun.Core/Entities/Customer.cs:10

Executive summary

Top priorities

Diagnosis — what's actually going on

Trajectory

Architecture — module dependency graph

At a glance — Code Health · 63% · Adequate

At a glance — Architecture · 80% · Strong

At a glance — Maturity · 54% · Adequate · gated by M2

At a glance — Readiness · 25% · Weak · gated by D12, R8, P1, P3

At a glance — Security · 56% · Adequate · gated by D30, D38, C1

At a glance — Accessibility · 45% · Weak

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts