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.
AbdurasulDeveloper/cleanarchitecture carries serious risk (37%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.
The area that most needs attention is Readiness (22%) — operating, monitoring and recovering the system safely is harder. Maturity (46%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); `AddStandardResilienceHandler()` (or Polly policies) to your… (Outbound HTTP resilience); 1 No automated tests finding(s) in Code Coverage (Code Coverage).
For scale: Hobby (~1,507 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
Code Health
71%
Strong
Architecture
80%
Strong
Maturity
46%
Weak · gated by M2
Readiness
22% ⚠
Critical · gated by D8, D9, P1, P3, P7
Security
48%
Weak · gated by C1, C2
Accessibility
49%
Weak · gated by AC4
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 22% · 46% weightMaturity 46% · 25% weightSecurity 48% · 14% weightAccessibility 49% · 8% weightCode Health 71% · 4% weightArchitecture 80% · 2% weight
Raise Readiness 22 → 70 (the Healthy floor) ⇒ headline 37 → ~51.
Code composition — where the lines go
Business logic 6%Plumbing 48%Generated 46%
Rebuild cost & value ~ Modeled — €420–€2,100
| Cost to rebuild | €420–€2,100 |
| Domain complexity | Standard |
| Quality factor | 0.7× (at 37% quality) |
| Size & shape | Hobby · 25% boilerplate · 63% straight-line · 12% branching logic |
This codebase represents roughly ~0.1 person-years of build effort (about ~€1,300 to rebuild). Its weakest lens is Readiness at 22% — the part of that asset most exposed by the findings below.
Top priorities
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
2
Resolve the 1 No tests found finding(s) in Test Distribution.
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Diagnosis — what's actually going on
Highest-leverage move
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.
Improving trajectory
The headline is improving steadily (+3.2 pts/run over 9 runs) — whatever you're doing is working; keep the gate.
Trajectory
OverallCode HealthArchitectureMaturityReadinessSecurityAccessibility
Architecture — module dependency graph
At a glance — Code Health
The Good
D1 · .NET / C#
Cyclomatic Complexity
10.0
D2 · .NET / C#
Cognitive Complexity
10.0
D3 · .NET / C#
God Classes
10.0
D4 · .NET / C#
Code Duplication
10.0
D17 · .NET / C#
Explicit Debt
9.2
D18 · .NET / C#
Solution Shape
7.3
D39 · .NET / C#
IL Efficiency
10.0
GD1 · Repo
Unfinished & placeholder code
10.0
IC1 · Repo
Incompleteness & stubs
10.0
X1 · Repo
Async correctness
10.0
X4 · Repo
Structured logging
10.0
X5 · Repo
Nullable reference types
9.2
The Bad
At a glance — Architecture
The Good
D6 · .NET / C#
Cohesion (LCOM4)
10.0
D26 · .NET / C#
Project Cohesion
10.0
D27 · .NET / C#
Navigability
9.1
D35 · .NET / C#
Change Coupling
10.0
AX1 · Repo
Captive dependencies
10.0
AX3 · Repo
Project dependency cycles
10.0
AX4 · Repo
Dependency direction
10.0
AX5 · Repo
Architecture & structure
10.0
AX6 · Repo
Interface segregation
10.0
The Bad
The Ugly
At a glance — Maturity
The Good
The Ugly
At a glance — Readiness
The Good
The Bad
The Ugly
At a glance — Security
The Good
At a glance — Accessibility
The Good
The Ugly
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A06:2021 — Vulnerable & Outdated Components | 1 | Medium |
Roadmap
First, establish a continuous integration workflow to build and test every push or pull request. Next, implement resilience handlers for outbound HTTP calls to prevent flaky dependencies from taking down the application. Then, address the single gap in automated code coverage and ensure all tests are properly distributed. Finally, extend structured logging across all service-like projects to ensure full observability and diagnosability in production.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +13.3 pts | Low | Code Coverage |
| Resolve the 1 No tests found finding(s) in Test Distribution. | +13.3 pts | Low | Test Distribution |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +14.1 pts | Medium | CI/CD gates |
| Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down. | +13.9 pts | Medium | Outbound HTTP resilience |
| Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production. | +13.3 pts | Medium | Observability |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene. | +5.1 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.3 pts | Low | ADR Quality |
| Resolve the 1 No contribution section; no authors/acknowledgment or license info. finding(s) in Documentation Quality — start with README.md. | +1.8 pts | Low | Documentation Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Infrastructure/Repos/AccountRepository.cs | 7.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| WebAPI/Program.cs | 9.1 | Near-clean | Comment Value: redundant comment |
| README.md | 9.5 | Near-clean | Documentation Quality: No contribution section; no authors/acknowledgment or license info. |
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. 53 of 56 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 56 dimensions across the health lenses
D1D2D3D4D5D6D8D9D12D13D14D15D17D18D19D20D21D24D26D27D28D29D30D35D39AC2AC3AC4AC5AC6AC7AX1AX10AX3AX4AX5AX6C1C2GD1IC1M1M2M3M4P1P2P3P7P8S1X1X2X3X4X5
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, 11 of 38 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- 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.
Tools & methods
| 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 |
Run transparency — what happened this run
- 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.
- D33 JS/npm Dependency Vulnerabilities — 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.
- D38 OSV Dependency Vulnerabilities — 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.
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
- 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.
- D8 Code Coverage: Coverage is measured by building and running the suite (`dotnet test --collect`) inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (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.
- D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
Do you agree with this assessment?
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
Do you agree with this assessment?
D3 · God Classes
0 god class(es) detected.
Do you agree with this assessment?
D4 · Code Duplication
0 duplicated block group(s) detected.
Do you agree with this assessment?
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
Off the main sequence: Domain
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Do you agree with this assessment?
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
Do you agree with this assessment?
D8 · Code Coverage
No automated tests — the solution has no test code.
No automated tests
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Do you agree with this assessment?
D9 · Test Distribution
No test projects found.
No tests found
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D12 · Dependency Hygiene
13 outdated, 0 vulnerable, 1 deprecated packages.
Deprecated: Microsoft.AspNetCore.Identity
Outdated: Microsoft.AspNetCore.SignalR.Common
What to do
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Do you agree with this assessment?
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
Do you agree with this assessment?
D14 · License Compliance
0 of 13 packages use a banned license.
Do you agree with this assessment?
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
git history depth insufficient
Do you agree with this assessment?
D17 · Explicit Debt
1 deducted debt markers + 0 dead symbols across 655 LoC (0.4/KLoC) → score 9.2.
EmptyCatchBlockInfrastructure/Repos/AccountRepository.cs:127
Do you agree with this assessment?
D18 · Solution Shape
5 projects, 23 .cs files, 655 hand-written lines of code (655 production / 0 test), plus 1289 generated (EF migrations / designer / snapshots, excluded from quality), 5 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).
Do you agree with this assessment?
D19 · Documentation Quality
The CleanArchitecture project's single README is a very thin, procedural guide that lists only the barest steps for creating files, setting up integrations, inviting members, and deploying CI/CD. It omits any architecture description (domain layer, repositories, services), dependency list, test suite guidance, or contribution process, leaving no visible structure to judge from. The outline is clipped mid-document, so every listed section exists but the content is not shown.
No contribution section; no authors/acknowledgment or license info.README.md
XML-doc coverage: Application Application/Application.csproj
What to do
- Resolve the 1 No contribution section; no authors/acknowledgment or license info. finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D20 · ADR Quality
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).
Do you agree with this assessment?
D21 · Naming Consistency
0 naming inconsistencies across 172 sampled symbols.
Do you agree with this assessment?
D24 · Comment Value
0 valuable / 4 redundant across 4 sampled comments; 4 shown with locations.
redundant comment Infrastructure/Repos/AccountRepository.cs:248
What to do
- Resolve the 4 redundant comment finding(s) in Comment Value — start with Program.cs (3), AccountRepository.cs. — One of this dimension's main actionable groups (4 recommendation-level).
Do you agree with this assessment?
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
Do you agree with this assessment?
D27 · Navigability
98 % of calls cross a namespace and 1 % go through an interface, but 83 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
Do you agree with this assessment?
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
Do you agree with this assessment?
D29 · Static Analysis (SAST)
semgrep found no security issues.
Do you agree with this assessment?
D30 · Dependency Vulnerabilities
1 vulnerable package(s): 0 critical, 0 high, 1 medium, 0 low.
Medium CVE: System.Security.Cryptography.Xml 4.5.0
Do you agree with this assessment?
D35 · Change Coupling
No strong hidden change-coupling between production files.
git history depth insufficient
Do you agree with this assessment?
D39 · IL Efficiency
0 of 63 first-party methods have an oversized IL body.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AC2 · Forms & labels
Do you agree with this assessment?
AC3 · Page structure
Do you agree with this assessment?
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — NavMenu.razor:10
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Do you agree with this assessment?
AC5 · ARIA correctness
Do you agree with this assessment?
AC6 · Visual & motion safety
- 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. — NavMenu.razor.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 enforcement
- 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?
AX1 · Captive dependencies
Do you agree with this assessment?
AX10 · Code composition
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 cycles
Do you agree with this assessment?
AX4 · Dependency direction
Do you agree with this assessment?
AX5 · Architecture & structure
Do you agree with this assessment?
AX6 · Interface segregation
Do you agree with this assessment?
C1 · Data Protection
- 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 Controls
- Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.
What to do
- Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
Do you agree with this assessment?
GD1 · Unfinished & placeholder code
Do you agree with this assessment?
IC1 · Incompleteness & stubs
Do you agree with this assessment?
M1 · Documentation (README)
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 documentation
- 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 structure
- Projects aren't grouped under a src/ folder — production and tooling code are mixed at the root.
- Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.
- Only 1/5 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Do you agree with this assessment?
M4 · Documentation accuracy
- README advertises Kubernetes, but no Kubernetes manifest or chart exists
What to do
- Reconcile the README with reality: README advertises Kubernetes, but no Kubernetes manifest or chart exists.
Do you agree with this assessment?
P1 · CI/CD gates
- 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 · Observability
- Only 1/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 tooling
- 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?
P7 · Outbound HTTP resilience
- The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
What to do
- Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
Do you agree with this assessment?
P8 · Schema migrations
Do you agree with this assessment?
S1 · Web-Security Posture
- 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 correctness
Do you agree with this assessment?
X2 · Cancellation propagation
- Only 0/22 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. (×22) — AccountRepository.cs:25, AccountRepository.cs:27, AccountRepository.cs:32, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
Do you agree with this assessment?
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — AccountRepository.cs:127
What to do
- Swallowed exception (empty catch)
Do you agree with this assessment?
X4 · Structured logging
Do you agree with this assessment?
X5 · Nullable reference types
- ~1.0 `!` suppressions per 1k syntax nodes — each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| 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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | 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) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Strong | Solid. |
| Architecture | 80% | Strong | Strongest area. |
| Maturity | 46% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 22% | Critical — gated by D8, D9, P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 48% | Weak — gated by C1, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 49% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not included — 37 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AX2 Stateful singletons — no singleton implementations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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.
- D10 Test Quality — No tests in the analyzed solution to assess for quality.
- D11 Test Reliability — Test reliability not included
- D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — At only 655 LoC the codebase is tiny despite 5 projects, so its small size alone makes it exempt from needing explicit bounded contexts.
- 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.
- D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
- D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
- 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.
- D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not run — 0/3 markers found
- ED1 Event-Driven — not run — only 1/3 markers (a message-bus package)
- 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
- 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.
- SC1 Supply-chain hygiene — no data
- X6 Hand-rolled structured-format parsing — no data
- X7 Silent fallback defaults — no data
Appendix A — Findings (grouped)
Issue — 2 finding(s)
D17 · Explicit Debt
- EmptyCatchBlock Infrastructure/Repos/AccountRepository.cs:127
D8 · Code Coverage
- No automated tests
Warning — 5 finding(s)
D5 · Coupling
- Off the main sequence: Domain
- Off the main sequence: Application
D12 · Dependency Hygiene
- Deprecated: Microsoft.AspNetCore.Identity
D16 · Bus Factor
- single-maintainer — knowledge-concentration (bus factor) risk
D30 · Dependency Vulnerabilities
- Medium CVE: System.Security.Cryptography.Xml 4.5.0
Recommendation — 10 finding(s)
D24 · Comment Value
- redundant comment Infrastructure/Repos/AccountRepository.cs:248
- redundant comment WebAPI/Program.cs:13
- redundant comment WebAPI/Program.cs:16
- redundant comment WebAPI/Program.cs:21
D11 · Test Reliability
- Test reliability not included
D18 · Solution Shape
- Thin analysable surface across projects
D19 · Documentation Quality
- No contribution section; no authors/acknowledgment or license info. README.md
D20 · ADR Quality
- No ADRs found
D34 · Knowledge Freshness
- early-stage repository — too little history to judge knowledge freshness
D9 · Test Distribution
- No tests found
Info — 21 finding(s)
D12 · Dependency Hygiene
- Outdated: Microsoft.AspNetCore.SignalR.Common
- Outdated: Mapster
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.AspNetCore.Identity
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Microsoft.Extensions.Identity.Stores
- Outdated: Microsoft.AspNetCore.OpenApi
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Scalar.AspNetCore
- Outdated: Microsoft.AspNetCore.Components.WebAssembly
- Outdated: Microsoft.AspNetCore.Components.WebAssembly.DevServer
D19 · Documentation Quality
- XML-doc coverage: Application Application/Application.csproj
- XML-doc coverage: Infrastructure Infrastructure/Infrastructure.csproj
- XML-doc coverage: Domain Domain/Domain.csproj
- XML-doc coverage: WebAPI WebAPI/WebAPI.csproj
- XML-doc coverage: WebUI WebUI/WebUI.csproj
D15 · Churn × Complexity Hotspots
- git history depth insufficient
D22 · Internal API Consistency
- No exposed public API
D35 · Change Coupling
- git history depth insufficient
Appendix B — Reproduction & audit trail
| 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 CleanArchitecture.sln package --vulnerable --include-transitive --format json | 1 | 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: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan. | 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: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan. | 0 | — |
Appendix C — Personal-data map
Email — 4 field(s)
- ChangeUserRoleRequestDTO.UserEmail Application/DTOs/Request/Account/ChangeUserRoleRequestDTO.cs:9
- LoginDTO.EmailAddress Application/DTOs/Request/Account/LoginDTO.cs:10
- GetUsersWithRolesResponseDTO.Email Application/DTOs/Response/Account/GetUsersWithRolesResponseDTO.cs:12
- UserClaimsDTO.Email Application/DTOs/Response/Account/UserClaimsDTO.cs:4
Name — 1 field(s)
- UserClaimsDTO.FullName Application/DTOs/Response/Account/UserClaimsDTO.cs:4