Public report — clean-architecture-azure-cosmos-db, published 29 Jul 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
53findings with an exact file:lineof 150 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
61/114dimensions across the health lenses4295 LoC · 5 projects — wide & deep
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.
ShawnShiSS/clean-architecture-azure-cosmos-db carries serious risk (43%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Architecture (84%) is solid too.
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 (24%) — operating, monitoring and recovering the system safely is harder. Code Health (54%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: 16 Deprecated finding(s) in Dependency Hygiene (Dependency Hygiene); CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); eslint and `tsc --noEmit` as package.json scripts and run them… (Tooling).
For scale: Small (~4,295 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Domain Modelling foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
D38 · High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
~10 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 ~€3,000 to rebuild). Its weakest lens is Readiness at 24% — 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.
1
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.
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 24%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Resolve the 16 Deprecated finding(s) in Dependency Hygiene. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 16 Deprecated finding(s) in Dependency Hygiene.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
At a glance — Code Health · 54% · Adequate · gated by X4, X5
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
69
High / Critical
Roadmap
First, resolve the 16 deprecated dependencies to improve security and stability. Next, establish a continuous integration pipeline that builds the code and runs tests on every push or pull request. Then, configure linting and type-checking scripts to ensure code quality is enforced in the development workflow. Finally, extend structured logging across all service-like projects to ensure full observability and diagnosability in production.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.
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. 60 of 61 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 61 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 53 of 150 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
The LLM boundary
LLM-set scores this run (3): 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.
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.
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.
0 method(s) exceeded the cognitive complexity threshold of 15.
✓ On the Gold path — maintain.
Detailed fixes: d2_recommendation.md.
Do you agree with this assessment?
D3 · God Classes10.0 / 10Exemplary✓ 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.
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.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.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.
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.
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.
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 Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
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.
Resolve the 16 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 issue-level).
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape8.8 / 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.
5 projects, 84 source files, 3842 hand-written lines of code (3818 production / 24 test), plus 724 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 6 inter-project edges (build failed).
Thin analysable surface across projects
Build did not complete in the analyzer
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.
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.
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.
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.
97 % of calls cross a namespace and 7 % 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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
23 of 23 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/CleanArchitectureCosmosDB.Infrastructure/CosmosDbData/Repository/CosmosDbRepository.cs.
Dormant codebase
What to do
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×30src/CleanArchitectureCosmosDB.ClientApp/yarn.lockdetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×18src/CleanArchitectureCosmosDB.ClientApp/yarn.lockdetected by osv-scanner finding
Critical vulnerability: [GHSA redacted]src/CleanArchitectureCosmosDB.ClientApp/yarn.lockdetected by osv-scanner finding
High vulnerability: [GHSA redacted]src/CleanArchitectureCosmosDB.ClientApp/yarn.lockdetected by osv-scanner finding
What to do
Resolve the 30 High CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (30). — One of this dimension's main actionable groups (30 issue-level).
Resolve the 18 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (18). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 1 Critical vulnerability finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
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.).
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — TokenService.cs:66
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`RefreshToken` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — TokenService.cs:64
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — Startup.cs:40, TokenResponse.cs:16, TokenService.cs:48, …
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.
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 'Testing' section to the root README — how to run the test suite.
Add a README to the 1 of 5 project(s) that lack one — worth up to 0.4 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README advertises Docker containerisation, but no Dockerfile/compose file exists
What to do
Reconcile the README with reality: README advertises Docker containerisation, but no Dockerfile/compose file exists.
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 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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 Safety10.0 / 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.
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 Files7.3 / 10Strong✓ Tool-verified
React / JS · Code Health — How many components/modules exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
What to do
Split the oversized components into smaller, focused ones.
Do you agree with this assessment?
R4 · Test Coverage7.7 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively — its behavior is unverified. (×3) — index.tsx, reportWebVitals.ts, Alert.tsx
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ 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 eslint and `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.8 / 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 2 application, 1 tooling and 2 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 (2 application, 1 tooling, 2 test roots considered) — Alert.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — ToDoCreate.tsx:16
Declared in src/CleanArchitectureCosmosDB.ClientApp/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×2)
Only test files import it — move it to devDependencies. — App.test.tsx:2
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
What to do
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Make the caller `async` and `await` instead. (×3) — IApplicationBuilderExtensions.cs:29, Startup.cs:95, Startup.cs:98
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 15/34 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×19) — CosmosDbRepository.cs:171, ToDoItemRepository.cs:38, ToDoItemRepository.cs:54, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — StarterFunction.cs:31
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/4 projects enable <Nullable>enable</Nullable>. NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 53 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
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
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.
D11 Test Reliability — Test runner surfaced no tests
D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
D19 Documentation Quality — LLM evaluation failed
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 ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea 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/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Aggregate boundaries — not gated in TS source-only: aggregate-vs-value-object classification is not 0-FP-separable (every class-holding-class reads alike) — advisory (the Swift/Dart/Rust parity)
DM2 Strongly-typed ids — not gated in TS source-only for the Stage-D scaffold: the branded-type idiom (`type Id = string & {__brand}`) is idiom-rare in TS (4 calibration carriers), so a bare-string-id gap is advisory — Stage-E diversification target (tsjs-stageC.md LESSON-A)
DM3 Integration-event coupling — not gated in TS source-only: a cross-package domain leak is not 0-FP-separable from a legitimate shared-kernel package, and most calibration repos are single-package — advisory (candidate-demote)
DM4 Rich vs anemic model — not gated in TS source-only for the Stage-D scaffold: the anemic-vs-rich gate is candidate-DETERMINISTIC for TS (behaviour + the component/DTO/readonly-VO exemptions) but the calibration corpus is high-quality (0 witnesses) — advisory, settled at the Stage-E holdout (the Rust/Swift/Dart precedent)
DM5 Encapsulated state — not gated in TS source-only for the Stage-D scaffold: TS idiom favours #private/private/readonly (idiom-rare public-mutable break), so DM5 is advisory pending Stage-E messier-repo witnesses (the Rust/Swift/Dart precedent)
DM7 Repository granularity — not gated in TS source-only: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable; the softest gated dim — advisory
ED1 Event-Driven — applicable but skipped (2/3 markers — below the conservative bar): a message-bus package; 11 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 — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
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.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
SC1 Supply-chain hygiene — no data
X6 Hand-rolled structured-format parsing — no data
X7 Silent fallback defaults — no data
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Issue — 63 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×30
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— @babel/plugin-transform-modules-systemjs 7.12.1: [GHSA redacted] — @babel/plugin-transform-modules-systemjs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/plugin-transform-modules-systemjs to 7.29.4 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— ansi-html 0.0.7: [GHSA redacted] — ansi-html is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ansi-html to 0.0.8 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— ansi-regex 4.1.0: [GHSA redacted] — ansi-regex is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ansi-regex to 4.1.1 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— async 2.6.3: [GHSA redacted] — async is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin async to 2.6.4 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— body-parser 1.19.0: [GHSA redacted] — body-parser is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin body-parser to 1.20.3 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories this scan raises against body-parser 1.19.0, and their fixed versions do not agree — anything below 1.20.6 still leaves at least one of them open, so 1.20.6 is the floor for this package, not this row's target alone. One upgrade of body-parser 1.19.0 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— brace-expansion 1.1.11: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 4 advisories this scan raises against brace-expansion 1.1.11, and their fixed versions do not agree — anything below 1.1.16 still leaves at least one of them open, so 1.1.16 is the floor for this package, not this row's target alone. One upgrade of brace-expansion 1.1.11 clears all 4 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— braces 2.3.2: [GHSA redacted] — braces is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.0.3 is a MAJOR ahead of the resolved 2.3.2, so an `overrides` pin would force a breaking version under a dependent written against 2.3.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— browserify-sign 4.2.1: [GHSA redacted] — browserify-sign is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin browserify-sign to 4.2.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— canvg 3.0.7: [GHSA redacted] — canvg is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin canvg to 3.0.11 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— cross-spawn 6.0.5: [GHSA redacted] — cross-spawn is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin cross-spawn to 6.0.6 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— decode-uri-component 0.2.0: [GHSA redacted] — decode-uri-component is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin decode-uri-component to 0.2.1 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— dns-packet 1.3.1: [GHSA redacted] — dns-packet is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin dns-packet to 1.3.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— flatted 2.0.2: [GHSA redacted] — flatted is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.4.0 is a MAJOR ahead of the resolved 2.0.2, so an `overrides` pin would force a breaking version under a dependent written against 2.0.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories this scan raises against flatted 2.0.2, and their fixed versions do not agree — anything below 3.4.2 still leaves at least one of them open, so 3.4.2 is the floor for this package, not this row's target alone. One upgrade of flatted 2.0.2 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— follow-redirects 1.13.0: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.14.7 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories this scan raises against follow-redirects 1.13.0, and their fixed versions do not agree — anything below 1.16.0 still leaves at least one of them open, so 1.16.0 is the floor for this package, not this row's target alone. One upgrade of follow-redirects 1.13.0 clears all 5 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— glob-parent 5.1.1: [GHSA redacted] — glob-parent is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin glob-parent to 5.1.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— http-proxy-middleware 0.19.1: [GHSA redacted] — http-proxy-middleware is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 2.0.7 is a MAJOR ahead of the resolved 0.19.1, so an `overrides` pin would force a breaking version under a dependent written against 0.19.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories this scan raises against http-proxy-middleware 0.19.1, and their fixed versions do not agree — anything below 2.0.10 still leaves at least one of them open, so 2.0.10 is the floor for this package, not this row's target alone. One upgrade of http-proxy-middleware 0.19.1 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— ini 1.3.5: [GHSA redacted] — ini is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ini to 1.3.6 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— ip 1.1.5: [GHSA redacted] — no fixed version has been published yet. Track the advisory, and remove or replace ip if the exposure is not acceptable until one lands. One upgrade of ip 1.1.5 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— is-svg 3.0.0: [GHSA redacted] — is-svg is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.2.2 is a MAJOR ahead of the resolved 3.0.0, so an `overrides` pin would force a breaking version under a dependent written against 3.0.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories this scan raises against is-svg 3.0.0, and their fixed versions do not agree — anything below 4.3.0 still leaves at least one of them open, so 4.3.0 is the floor for this package, not this row's target alone. One upgrade of is-svg 3.0.0 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— js-yaml 3.14.0: [GHSA redacted] — js-yaml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin js-yaml to 3.15.0 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories this scan raises against js-yaml 3.14.0, and their fixed versions do not agree — anything below 3.15.0 still leaves at least one of them open, so 3.15.0 is the floor for this package, not this row's target alone. One upgrade of js-yaml 3.14.0 clears all 3 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— json5 1.0.1: [GHSA redacted] — json5 is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json5 to 1.0.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— lodash 4.17.20: [GHSA redacted] — lodash is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash to 4.17.21 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories this scan raises against lodash 4.17.20, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open, so 4.18.0 is the floor for this package, not this row's target alone. One upgrade of lodash 4.17.20 clears all 3 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— lodash-es 4.17.15: [GHSA redacted] — lodash-es is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash-es to 4.17.20 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 4 advisories this scan raises against lodash-es 4.17.15, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open, so 4.18.0 is the floor for this package, not this row's target alone.
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— minimatch 3.0.4: [GHSA redacted] — minimatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimatch to 3.1.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 4 advisories this scan raises against minimatch 3.0.4, and their fixed versions do not agree — anything below 3.1.4 still leaves at least one of them open, so 3.1.4 is the floor for this package, not this row's target alone. One upgrade of minimatch 3.0.4 clears all 4 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— node-forge 0.10.0: [GHSA redacted] — node-forge is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 1.4.0 is a MAJOR ahead of the resolved 0.10.0, so an `overrides` pin would force a breaking version under a dependent written against 0.10.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 13 advisories this scan raises against node-forge 0.10.0, and their fixed versions do not agree — anything below 1.4.0 still leaves at least one of them open, so 1.4.0 is the floor for this package, not this row's target alone. One upgrade of node-forge 0.10.0 clears all 13 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— @babel/traverse 7.12.1: [GHSA redacted] — @babel/traverse is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/traverse to 7.23.2 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— cipher-base 1.0.4: [GHSA redacted] — cipher-base is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin cipher-base to 1.0.5 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— dompurify 2.2.2: [GHSA redacted] — dompurify is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin dompurify to 2.4.2 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 17 advisories this scan raises against dompurify 2.2.2, and their fixed versions do not agree — anything below 2.5.4 still leaves at least one of them open, so 2.5.4 is the floor for this package, not this row's target alone. One upgrade of dompurify 2.2.2 clears all 18 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— ejs 2.7.4: [GHSA redacted] — ejs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.1.7 is a MAJOR ahead of the resolved 2.7.4, so an `overrides` pin would force a breaking version under a dependent written against 2.7.4; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories this scan raises against ejs 2.7.4, and their fixed versions do not agree — anything below 3.1.10 still leaves at least one of them open, so 3.1.10 is the floor for this package, not this row's target alone. One upgrade of ejs 2.7.4 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— eventsource 1.0.7: [GHSA redacted] — eventsource is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin eventsource to 1.1.1 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— form-data 2.3.3: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 2.5.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories this scan raises against form-data 2.3.3, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open, so 2.5.6 is the floor for this package, not this row's target alone. One upgrade of form-data 2.3.3 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— immer 7.0.9: [GHSA redacted] — immer is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 9.0.6 is a MAJOR ahead of the resolved 7.0.9, so an `overrides` pin would force a breaking version under a dependent written against 7.0.9; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 3 advisories this scan raises against immer 7.0.9, and their fixed versions do not agree — anything below 9.0.6 still leaves at least one of them open, so 9.0.6 is the floor for this package, not this row's target alone. One upgrade of immer 7.0.9 clears all 3 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— json-schema 0.2.3: [GHSA redacted] — json-schema is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json-schema to 0.4.0 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— jspdf 2.1.0: [GHSA redacted] — jspdf is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.0.0 is a MAJOR ahead of the resolved 2.1.0, so an `overrides` pin would force a breaking version under a dependent written against 2.1.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). One upgrade of jspdf 2.1.0 clears all 13 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— loader-utils 1.2.3: [GHSA redacted] — loader-utils is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin loader-utils to 1.4.1 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories this scan raises against loader-utils 1.2.3, and their fixed versions do not agree — anything below 1.4.2 still leaves at least one of them open, so 1.4.2 is the floor for this package, not this row's target alone. One upgrade of loader-utils 1.2.3 clears all 3 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— merge-deep 3.0.2: [GHSA redacted] — merge-deep is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin merge-deep to 3.0.3 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— minimist 1.2.5: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 1.2.6 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— pbkdf2 3.1.1: [GHSA redacted] — pbkdf2 is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin pbkdf2 to 3.1.3 with an `overrides` entry (`resolutions` if you use Yarn)). One upgrade of pbkdf2 3.1.1 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— sha.js 2.4.11: [GHSA redacted] — sha.js is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin sha.js to 2.4.12 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— shell-quote 1.7.2: [GHSA redacted] — shell-quote is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin shell-quote to 1.7.3 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories this scan raises against shell-quote 1.7.2, and their fixed versions do not agree — anything below 1.9.0 still leaves at least one of them open, so 1.9.0 is the floor for this package, not this row's target alone. One upgrade of shell-quote 1.7.2 clears all 3 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— tar 6.0.5: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.5.19 is a MAJOR ahead of the resolved 6.0.5, so an `overrides` pin would force a breaking version under a dependent written against 6.0.5; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 18 advisories this scan raises against tar 6.0.5, and their fixed versions do not agree — anything below 6.2.1 still leaves at least one of them open, so 6.2.1 is the floor for this package, not this row's target alone. One upgrade of tar 6.0.5 clears all 18 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— url-parse 1.4.7: [GHSA redacted] — url-parse is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin url-parse to 1.5.8 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 6 advisories this scan raises against url-parse 1.4.7, and their fixed versions do not agree — anything below 1.5.9 still leaves at least one of them open, so 1.5.9 is the floor for this package, not this row's target alone. One upgrade of url-parse 1.4.7 clears all 6 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— websocket-driver 0.6.5: [GHSA redacted] — websocket-driver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin websocket-driver to 0.7.5 with an `overrides` entry (`resolutions` if you use Yarn)). One upgrade of websocket-driver 0.6.5 clears all 2 advisories it raises: [GHSA redacted], [GHSA redacted].
High CVE: Newtonsoft.Json 12.0.3 — Newtonsoft.Json 12.0.3 (direct) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 13.0.1
High CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 4.3.4
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 4.3.1
High CVE: Azure.Identity 1.1.0 — Azure.Identity 1.1.0 (transitive) has a High advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 1.10.2
High CVE: Microsoft.Data.SqlClient 2.0.1 — Microsoft.Data.SqlClient 2.0.1 (transitive) has a High advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 2.1.7
High CVE: AutoMapper 10.0.0 — AutoMapper 10.0.0 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 15.1.1
High CVE: Microsoft.AspNetCore.Mvc.Core 1.0.4 — Microsoft.AspNetCore.Mvc.Core 1.0.4 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 1.0.6
Critical vulnerability: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— elliptic 6.5.3: [GHSA redacted] — elliptic is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin elliptic to 6.6.1 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 7 advisories this scan raises against elliptic 6.5.3, and their fixed versions do not agree — anything below 6.6.1 still leaves at least one of them open, so 6.6.1 is the floor for this package, not this row's target alone. One upgrade of elliptic 6.5.3 clears all 8 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] src/CleanArchitectureCosmosDB.ClientApp/yarn.lock— d3-color 1.4.1: [GHSA redacted] — d3-color is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.1.0 is a MAJOR ahead of the resolved 1.4.1, so an `overrides` pin would force a breaking version under a dependent written against 1.4.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: Azure.Identity 1.1.0 — Azure.Identity 1.1.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 1.11.0
Medium CVE: Azure.Identity 1.1.0 — Azure.Identity 1.1.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 1.11.4
Medium CVE: Azure.Storage.Blobs 12.1.0 — Azure.Storage.Blobs 12.1.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 12.13.0
Medium CVE: Microsoft.Data.SqlClient 2.0.1 — Microsoft.Data.SqlClient 2.0.1 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 2.1.2
Medium CVE: Microsoft.IdentityModel.JsonWebTokens 5.6.0 — Microsoft.IdentityModel.JsonWebTokens 5.6.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 5.7.0
Medium CVE: System.IdentityModel.Tokens.Jwt 5.6.0 — System.IdentityModel.Tokens.Jwt 5.6.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Security.Cryptography.Xml 4.5.0 — System.Security.Cryptography.Xml 4.5.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted] — upgrade to 4.7.1
Medium CVE: Microsoft.AspNetCore.Authentication.JwtBearer 3.1.13 — Microsoft.AspNetCore.Authentication.JwtBearer 3.1.13 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 3.1.18
Medium CVE: Swashbuckle.AspNetCore.SwaggerUI 5.6.3 — Swashbuckle.AspNetCore.SwaggerUI 5.6.3 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 6.3.0
TodoComment src/CleanArchitectureCosmosDB.Infrastructure/CosmosDbData/Constants/CosmosDbConfigConstants.cs:5— // TODO : consider retrieving this from appsettings using IOptions, instead of defining it as a constant — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/CleanArchitectureCosmosDB.Infrastructure/Services/SendGridEmailService.cs:44— // TODO : consider adding support for HTML content — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1] | LineNumber: 0 | BytePositionInLine: 1169.
LLM evaluation failed — JSON parse error: Expected depth to be zero at the end of the JSON payload. There is an open JSON object or array that should be closed. Path: $.notable[5].suggestion | LineNumber: 0 | BytePositionInLine: 963.
Duplicated block (11 lines × 2) src/CleanArchitectureCosmosDB.Core/Specifications/ToDoItemSearchAggregationSpecification.cs:20— src/CleanArchitectureCosmosDB.Core/Specifications/ToDoItemSearchAggregationSpecification.cs:20-30 | src/CleanArchitectureCosmosDB.Core/Specifications/ToDoItemSearchSpecification.cs:16-26 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Coverage not measured — analyzer environment — Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, commit the Cobertura/OpenCover/lcov report your CI already produces and real coverage will be read.
Recommendation — 5 finding(s)
D11 · Test Reliability· Test runner surfaced no tests · ×1
Test runner surfaced no tests — Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 1 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
Thin analysable surface across projects — 1 project(s) carry only a thin slice of real code (e.g. `CleanArchitectureCosmosDB.UnitTests` with 19 significant line(s)). The mean analysable-surface weight is 84 %, lowering Solution Shape by about 1.2 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.
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 3818 LoC across 5 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["Acme.Billing"]`, `Catalog: ["Acme.Catalog"]`.
Dormant codebase — 23 of 23 significant files have no living knowledge — the codebase as a whole is dormant, not 23 separate risks. Re-engage owners or document before change.
Outdated: Ardalis.Specification — Ardalis.Specification 4.1.0 → 9.3.1 available (referenced by CleanArchitectureCosmosDB.Core).
Outdated: Microsoft.AspNetCore.Http — Microsoft.AspNetCore.Http 2.2.2 → 2.3.11 available (referenced by CleanArchitectureCosmosDB.Core).
Outdated: Newtonsoft.Json — Newtonsoft.Json 12.0.3 → 13.0.4 available (referenced by CleanArchitectureCosmosDB.Core).
Outdated: Microsoft.AspNetCore.Http.Abstractions — Microsoft.AspNetCore.Http.Abstractions 2.2.0 → 2.3.11 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.AspNetCore.Identity — Microsoft.AspNetCore.Identity 2.2.0 → 2.3.11 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 5.0.1 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.Azure.Cosmos — Microsoft.Azure.Cosmos 3.12.0 → 3.62.0 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 5.0.1 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 5.0.1 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.EntityFrameworkCore.Tools — Microsoft.EntityFrameworkCore.Tools 5.0.1 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 5.0.0 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.Extensions.Configuration.FileExtensions — Microsoft.Extensions.Configuration.FileExtensions 5.0.0 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 5.0.0 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 5.0.1 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 5.0.0 → 10.0.10 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: SendGrid — SendGrid 9.21.0 → 9.29.3 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Storage.Net — Storage.Net 9.2.7 → 9.3.0 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: Storage.Net.Microsoft.Azure.Storage.Blobs — Storage.Net.Microsoft.Azure.Storage.Blobs 9.2.7 → 9.3.0 available (referenced by CleanArchitectureCosmosDB.Infrastructure).
Outdated: AutoMapper — AutoMapper 10.0.0 → 16.2.0 available (referenced by CleanArchitectureCosmosDB.WebAPI).
Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection — AutoMapper.Extensions.Microsoft.DependencyInjection 8.0.1 → 12.0.1 available (referenced by CleanArchitectureCosmosDB.WebAPI).
Outdated: FluentValidation — FluentValidation 9.2.2 → 12.1.1 available (referenced by CleanArchitectureCosmosDB.WebAPI).
Outdated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 9.2.0 → 11.3.1 available (referenced by CleanArchitectureCosmosDB.WebAPI).
Outdated: FluentValidation.DependencyInjectionExtensions — FluentValidation.DependencyInjectionExtensions 9.2.0 → 12.1.1 available (referenced by CleanArchitectureCosmosDB.WebAPI).
Outdated: MediatR — MediatR 8.1.0 → 14.2.0 available (referenced by CleanArchitectureCosmosDB.WebAPI).
Outdated: MediatR.Extensions.Microsoft.DependencyInjection — MediatR.Extensions.Microsoft.DependencyInjection 8.1.0 → 11.1.0 available (referenced by CleanArchitectureCosmosDB.WebAPI).
+ 23 more in this group — see findings.md.
D18 · Solution Shape· Build did not complete in the analyzer · ×1
Build did not complete in the analyzer — `dotnet build` reported 2 error(s) but no compiler diagnostic — an SDK / target-framework / restore mismatch in the analyzer environment, not a code defect (common for an older codebase whose target framework the analyzer's SDK can't build). Solution Shape is scored on structure and is NOT capped; the semantic analysis of your source loads independently and is unaffected.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019faf79-2ca5-7d90-8110-88b3f2a5ed3b · 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 — 9 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 63 · Warnings: 32 · Recommendations: 5 · Info: 50 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-07-2026 @ 20:03 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.