amasen02/freshcart-backend

Executive summary

amasen02/freshcart-backend scores 61 out of 100 and is rated Adequate, while eight of its nine lenses score higher still: Code Health at 92, rated Exemplary, Event-Driven at 88, Architecture at 83 and Performance at 72, all rated Strong, and Security and Compliance at 77, Domain Modelling at 71, Production Readiness at 63 and Accessibility at 62, all rated Adequate.

The score is lower than those eight because the weakest lens counts most, and here that is Maturity, which scores 55 and is rated Adequate. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to reconcile the README with reality: CONTRIBUTING.md names `tests/contract/`, but no file or folder `tests/contract` exists; CONTRIBUTING.md names `tests/load/`, but no file or folder `tests/load` exists; README.md runs `npm start`, but no package.json declares a `start` script; README.md links to `gitops/`, but `gitops` does not exist; docs/REQUIREMENTS.md names `tests/load/identity-sign-in.js`, but no file or folder `tests/load/identity-sign-in.js` exists and to grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made, and if Maturity rose to 70, the score would rise from 61 to about 65.

127 findings are critical: 44 in Secret Scanning, 40 in Static Analysis (SAST), 23 in IaC & Container Security, ten in Domain ↔ infrastructure boundary, four in Explicit Debt, two in Outbox / dual-write, two in Project dependency cycles and two in Secrets (history).

Watchdog couldn't measure 5 dimensions in this code, among them Code Coverage, Dependency Hygiene and IL Efficiency, so they are left out of the score. The product code is 25,543 lines, which would take an estimated 0.5 person-years, around €73,000, to rebuild.

Code Health 92 ★ Exemplary Architecture 83 Strong Maturity 55 Adequate, capped by Documentation accuracy Production Readiness 63 Adequate, capped by Secret Scanning and Schema migrations Security and Compliance 77 Adequate, capped by Static Analysis (SAST), IaC & Container Security and Supply-chain Provenance & Signing Domain Modelling 71 Adequate, capped by Strongly-typed ids Event-Driven 88 Strong Accessibility 62 Adequate Performance 72 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Maturity 55 · counts for 45%Accessibility 62 · counts for 25%Production Readiness 63 · counts for 14%Domain Modelling 71 · counts for 8%Performance 72 · counts for 4%Security and Compliance 77 · counts for 2%Architecture 83 · counts for 1%Event-Driven 88 · counts for 1%Code Health 92 · counts for 0%

If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 61 to about 65.

Code composition: what the lines of code are

Business logic 12%Supporting code 50%Tests 38%

Rebuild cost: about €73,000 · Estimate

Cost to rebuild	€24,000 to €120,000, for 403 to 1,279 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem	Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 25,543 lines of product code
Comment lines	The estimate prices 22,619 lines. Comment lines count towards the size of 25,543 lines but aren't priced as work.

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

Reconcile the README with reality: CONTRIBUTING.md names `tests/contract/`, but no file or folder `tests/contract` exists; CONTRIBUTING.md names `tests/load/`, but no file or folder `tests/load` exists; README.md runs `npm start`, but no package.json declares a `start` script; README.md links to `gitops/`, but `gitops` does not exist; docs/REQUIREMENTS.md names `tests/load/identity-sign-in.js`, but no file or folder `tests/load/identity-sign-in.js` exists.

Raises the score by about 5 points · Medium effort · Documentation accuracy

Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.

Raises the score by about 3 points · Medium effort · Architecture documentation

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.

Raises the score by about 2 points · Medium effort · Documentation (README)

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €73,000 to build again, about 0.5 person-years of work. Its weakest lens is Maturity, at 55 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.

Based on: the rebuild estimate · the Maturity grade · how much each lens counts

What to do: Start with the Maturity actions in Top priorities.

If you do one thing first · First action

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

209 modules, with 339 dependencies between them. 2 loops run through 5 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 169 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 Basket.Api.Domain	2 BuildingBlocks.CQRS	3 BuildingBlocks.Messaging.Events	4 BuildingBlocks.Pagination	5 Catalog.Api.Models	6 Delivery.Domain.Deliveries	7 Delivery.Domain.Slots	8 Delivery.Domain.Zones	9 Identity.Domain.Users	10 Ordering.Domain.Orders	11 Payment.Domain	12 Reporting.Domain.Invoices	13 Reporting.Domain.Kpis	14 Reporting.Domain.Sales	15 Basket.Api.Persistence	16 Basket.Api.Pricing	17 BuildingBlocks.Messaging.IntegrationEvents	19 Identity.Application.Common.Abstractions	22 Payment.Application.Payments.Models	23 Reporting.Application.Common.Models	29 Delivery.Application.Shipments	33 Reporting.Application.Common.Abstractions	34 Delivery.Application.Abstractions	39 Delivery.Infrastructure.Persistence
1 Basket.Api.Domain
2 BuildingBlocks.CQRS
3 BuildingBlocks.Messaging.Events
4 BuildingBlocks.Pagination
5 Catalog.Api.Models
6 Delivery.Domain.Deliveries
7 Delivery.Domain.Slots
8 Delivery.Domain.Zones
9 Identity.Domain.Users
10 Ordering.Domain.Orders
11 Payment.Domain
12 Reporting.Domain.Invoices
13 Reporting.Domain.Kpis
14 Reporting.Domain.Sales
15 Basket.Api.Persistence	9
16 Basket.Api.Pricing	1
17 BuildingBlocks.Messaging.IntegrationEvents			13
18 Catalog.Api.Data					6
19 Identity.Application.Common.Abstractions									1
20 Inventory.Api.Services				4
21 Ordering.Application.Abstractions				2						2
22 Payment.Application.Payments.Models											2
23 Reporting.Application.Common.Models														1
24 Reviews.Api.Persistence				4
25 Basket.Api.Features.ShoppingBaskets.AddItem	1	2													1
26 Basket.Api.Features.ShoppingBaskets.ApplyCoupon	1	2													1	1
27 Basket.Api.Features.ShoppingBaskets.Checkout	2	2													3	2	4
28 Basket.Api.Features.ShoppingBaskets.GetBasket	2	2													1	3
29 Delivery.Application.Shipments						2											2						1
30 Identity.Infrastructure.Persistence									1									1
31 Notification.Api.Notifications				2													7
32 Payment.Application.Abstractions				2															2
33 Reporting.Application.Common.Abstractions												4	2	6			5
34 Delivery.Application.Abstractions			1			3	1	3													1
35 Delivery.Infrastructure.Persistence.Mapping						2	1	3													1
36 Reporting.Application.Products.Queries		2											1	1						1		1
37 Reporting.Application.Sales.Queries		6											2	8						3		5
38 Reporting.Infrastructure.Persistence.Warehouse												6	2	6			5					11
39 Delivery.Infrastructure.Persistence			1			1																	1
40 Delivery.Infrastructure.Persistence.Repositories						1	1	2													1		5	5

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 92% · Exemplary ·

The Good

D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 10.0 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.5 D17 · .NET / C# Explicit Debt 9.6 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 7.8 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.7 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 10.0 X5 · Repo Nullable reference types 9.8

At a glance — Architecture · 83% · Strong ·

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.7 D7 · .NET / C# Architectural Integrity 8.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.1 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX7 · Repo Slice cohesion 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

The Ugly

AX10 · Repo Code composition 4.0

At a glance — Maturity · 55% · Adequate · gated by M4 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 9.4 D20 · .NET / C# ADR Quality 9.8 D21 · .NET / C# Naming Consistency 9.0 D24 · .NET / C# Comment Value 9.7 D25 · .NET / C# ADR Conformance 10.0 D34 · .NET / C# Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.3 M2 · Repo Architecture documentation 7.0 M3 · Repo Folder & project structure 10.0

The Ugly

M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 63% · Adequate · gated by D13, P8 ·

The Good

D9 · .NET / C# Test Distribution 9.4 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 9.6 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.9 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 10.0 P5 · Repo DR & Backup 7.0 P6 · Repo Release Hygiene 10.0 P7 · Repo Outbound HTTP resilience 10.0

The Ugly

D13 · .NET / C# Secret Scanning 0.0 P8 · Repo Schema migrations 3.0

At a glance — Security · 77% · Adequate · gated by D29, D31, D36 ·

The Good

D28 · .NET / C# Secrets (history) 8.0 D30 · .NET / C# Dependency Vulnerabilities 10.0 D37 · .NET / C# Vulnerability-disclosure Policy 10.0 D40 · .NET / C# Network Egress Confinement 10.0 D41 · .NET / C# Kernel & Syscall Confinement 8.0 D42 · .NET / C# Runtime Threat Enforcement 8.0 D43 · .NET / C# Malicious Dependencies 10.0 C2 · Repo Access Controls 10.0 C3 · Repo Audit Trail 10.0 C4 · Repo Data Retention 7.5 S1 · Repo Web-Security Posture 9.5 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

C1 · Repo Data Protection 6.5

The Ugly

D29 · .NET / C# Static Analysis (SAST) 0.8 D31 · .NET / C# IaC & Container Security 0.0 D36 · .NET / C# Supply-chain Provenance & Signing 2.5

At a glance — Domain Modelling · 71% · Adequate · gated by DM2 ·

The Good

DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 9.6 DM11 · Repo Constructible invalid state 10.0 DM12 · Repo Ambient inputs in the domain 10.0 DM3 · Repo Integration-event coupling 10.0 DM4 · Repo Rich vs anemic model 10.0 DM5 · Repo Encapsulated state 10.0 DM7 · Repo Repository granularity 10.0 DM8 · Repo Value-object opportunities 9.9 DM9 · Repo Scattered domain decisions 9.6

The Bad

DM6 · Repo Domain ↔ infrastructure boundary 5.2

The Ugly

DM2 · Repo Strongly-typed ids 3.0

At a glance — Event-Driven · 88% · Strong ·

The Good

ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0 ED3 · Repo Event naming 10.0 ED4 · Repo Outbox / dual-write 7.3

At a glance — Accessibility · 62% · Adequate ·

The Good

AC2 · Repo Forms & labels 10.0

The Bad

AC3 · Repo Page structure 6.8 AC6 · Repo Visual & motion safety 6.5

The Ugly

AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 72% · Strong ·

The Good

PF3 · Repo Async & latency hygiene 10.0

The Bad

PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.6

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A02:2025 — Security Misconfiguration	238	High / Critical
A05:2025 — Injection	51	High / Critical
A07:2025 — Authentication Failures	47	High / Critical
A03:2025 — Software Supply Chain Failures	16	Medium

Roadmap

First, reconcile all documentation to match the actual codebase by removing references to missing files and scripts, and add a quick-start section to the root README to help newcomers. Next, expand the architecture decision record log to eight entries to better capture significant design choices. Then, enforce accessibility by adding assertions to the existing test suite and gating them in CI to prevent regressions. Finally, resolve the forty-four leaked secrets found in configuration files to secure the environment.

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

Do this	Helps	Effort	Dimension
Reconcile the README with reality: CONTRIBUTING.md names `tests/contract/`, but no file or folder `tests/contract` exists; CONTRIBUTING.md names `tests/load/`, but no file or folder `tests/load` exists; README.md runs `npm start`, but no package.json declares a `start` script; README.md links to `gitops/`, but `gitops` does not exist; docs/REQUIREMENTS.md names `tests/load/identity-sign-in.js`, but no file or folder `tests/load/identity-sign-in.js` exists.	+5.0 pts	Medium	Documentation accuracy
Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.	+2.6 pts	Medium	Architecture documentation
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.	+2.3 pts	Medium	Documentation (README)
Resolve the 1 Inconsistent naming convention for private test setup fields and helper… finding(s) in Naming Consistency.	+0.9 pts	Low	Naming Consistency
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.	+1.7 pts	Medium	A11y enforcement
Resolve the 44 Leaked secret finding(s) in Secret Scanning — start with REDACTED (21), REDACTED (21), REDACTED (2).	+1.6 pts	Medium	Secret Scanning
Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.	+1.3 pts	Medium	Schema migrations
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.	+1.2 pts	Medium	Visual & motion safety

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Secret Scanning: Leaked secret: REDACTED
REDACTED	2.0	Slop	Secret Scanning: Leaked secret: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.5	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 127

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 268

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 142

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 6

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 105 of 112 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 7 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — 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 — 112 dimensions across the health lenses

D1D2D3D4D5D6D7D9D10D11D13D14D15D17D18D19D20D21D24D25D26D27D28D29D30D31D34D35D36D37D40D41D42D43AC2AC3AC6AC7AX1AX10AX2AX3AX4AX5AX6AX7AX8AX9C1C2C3C4DM1DM10DM11DM12DM2DM3DM4DM5DM6DM7DM8DM9ED1ED2ED3ED4ED5GD1IC1M1M2M3M4P1P2P3P4P5P6P7P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a16140-2552-7e3d-81ae-e3f1e9a934e3.

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

Run transparency — what happened this run

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

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — tests/e2e/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 748 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 5 test source file(s) (.ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 69 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (25,423 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs`, `src/AspireAppHost/FreshCart.AppHost/MongoDirectReadinessCheck.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/Outbox/OutboxPublisher.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/LoggingBehavior.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/ValidationBehavior.cs`, … (+156 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Deploy/helm/basket/templates/deployment.yaml:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2 and 2 more did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (src/AspireAppHost/FreshCart.AppHost/FreshCart.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.

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 — an in-process token-stream comparison over sliding windows, with type-aware normalization — so 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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (7): D19, D20, D21, D24, D25, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

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

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.

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

Do you agree with this assessment?

D4 · Code Duplication9.5 / 10Stronggated by 27 serious findings✓ Tool-verified

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

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

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

25 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:162

Duplicated block (22 lines × 2) · ×2src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs:41

Duplicated block (17 lines × 3) · ×2src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:163

Duplicated block (9 lines × 2) · ×2src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:17

Duplicated block (5 lines × 2) · ×2src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:35

+ 17 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DependencyInjection.cs, DapperSalesReadWarehouse.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with SqlConnectionFactory.cs, ClaimsPrincipalExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (17 lines × 3) finding(s) in Code Duplication — start with DependencyInjection.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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.

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

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

Off the main sequence: FreshCart.BuildingBlocks.Messaging · ×2src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/FreshCart.BuildingBlocks.Messaging.csproj:1

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.7 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

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

3 of 126 classes have LCOM4 above 3.

Low cohesion: CancelOrderOnPaymentFailureActivity (LCOM4 4) · ×3src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/CancelOrderOnPaymentFailureActivity.cs:14

What to do

Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with CancelOrderOnPaymentFailureActivity.cs, CancelOrderOnStockFailureActivity.cs, ConfirmOrderActivity.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D7 · Architectural Integrity8.0 / 10Strong✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

All 1 mechanizable ADR(s) are enforced: 0 by analyzers, 1 by tests. Cycles found: 0.

What to do

Enforce Architectural Integrity in CI to reach Prevented (currently Verified). — Hardens enforcement from Verified toward Prevented — provenance only; does not change the score.

Detailed fixes: d7_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

752 test methods: 146 unit, 602 integration, 0 BDD, 4 e2e. The JavaScript/TypeScript suite contributes 4 `it`/`test` case(s) across 3 test file(s) declaring at least one beside 748 .NET test method(s); its tier split is read from package names and paths only.

Inverted test pyramid

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.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.

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

0 skipped, 0 zero-assertion, 14 mock references across 748 tests. Measured on the C# suite only — at least 5 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.

Mock-dominated test: SeedsCategoriesBrandsAndProductsOnFirstDevelopmentStart · ×7src/Services/Catalog/FreshCart.Catalog.Tests/Seeding/CatalogDataSeederTests.cs:34

Mock framework: NSubstitute · ×14

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

22 secret(s) detected.

REDACTED

What to do

Resolve the 44 Leaked secret finding(s) in Secret Scanning — start with REDACTED (21), REDACTED (21), REDACTED (2). — One of this dimension's main actionable groups (44 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 90 direct `PackageReference`(s), and 160 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt9.6 / 10Adequategated by 4 critical findings✓ Tool-verified

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

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

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

4 deducted debt markers + 4 dead symbols across 25423 LoC in the .NET projects (0.2/KLoC) → score 9.6.

NoWarnInCsproj · ×4Directory.Build.props:23

Dead code: Deactivate · ×4src/Services/Delivery/FreshCart.Delivery.Domain/Drivers/Driver.cs:36

What to do

Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 Dead code finding(s) in Explicit Debt — start with Driver.cs (2), IDriverRepository.cs, IAgentAvailabilityRegistry.cs. — One of this dimension's main actionable groups (4 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

46 projects, 965 source files, 39251 hand-written lines of code (25423 production / 13828 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 86 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

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

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

The repository's root README is a single-page animated architecture guide with an overview, Try it now demo URLs, and a full outline (Boot the platform; Clone; Customer storefront ... License). The infra/README.md documents the Bicep infrastructure layout, deploy commands, secrets, and teardown. Each tests/README.md file documents its own directory rather than the repository root. All 16 README files are present and serve as per-directory documentation for their respective tiers. The FreshCart repository is well documented: the READMEs for each deploy/k8s service directory describe what they contain and give production deployment commands (Helm upgrade), plus a companion architecture document that covers C4 context, tenets, and a full class-diagram convention reference. The root README is not shown but the project's overview, installation/build steps, usage examples, contribution guidance, and licence are all present in the repository's internal documentation. The FreshCart project is well documented across a strong README quickstart guide (local development), an authoritative Requirements document with FR/NFR numbering and acceptance-criteria tables for every bounded context, a Google-standards audit & remediation review, and architecture design documents. The main gaps are the missing overview of what the repository does in the root README and the absence of any single-document architecture-design coverage (the ADRs/evolution docs are separate), both of which are present in the outline but not shown due to truncation.

XML-doc coverage: FreshCart.BuildingBlocks · ×32src/BuildingBlocks/FreshCart.BuildingBlocks/FreshCart.BuildingBlocks.csproj

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D20 · ADR QualityExemplary◐ Sampled · advisory

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

Evaluated 4 ADR(s) individually; mean quality 9.8/10 (consistently complete and clear). 0 flagged with a specific gap.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

1 naming inconsistencies across 200 sampled symbols.

Inconsistent naming convention for private test setup fields and helper methods. Some use the full class name of the dependency (e.g., `repository`, `catalogQueries`, `harness`, `consumer`, `mongoFixture`), while others use abbreviated or generic names (e.g., `CommandFor`, `Now`, `lazyChannel`, `ProductId`, `CustomerId`, `IdempotencyKey`, `CardMethod`). While `CustomerId` and `ProductId` are specific values rather than dependencies, the pattern of using the full type name for dependencies is inconsistent with the abbreviated forms used in other test classes.

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D24 · Comment ValueExemplary◐ Sampled · advisory

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

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

82 valuable / 0 redundant across 156 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

D25 · ADR ConformanceExemplary◐ Sampled · advisory

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.

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

4 conform / 0 violate across 4 ADRs.

✓ On the Gold path — maintain.

Detailed fixes: d25_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 of 46 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability9.1 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

91 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.8 / 10Critical✓ Tool-verified

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

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

51 finding(s): 0 critical, 40 high, 5 medium, 6 low. 27 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 351 file(s) — `.github/scripts/freshcart-e2e-stack.sh` (lines 2–144), `.github/scripts/test-freshcart-e2e-stack.sh` (lines 147–155), `deploy/helm/basket/Chart.yaml`, `deploy/helm/basket/templates/configmap.yaml`, `REDACTED`, … (+346 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 184 of those file(s) — `src/AspireAppHost/FreshCart.AppHost/MongoDirectReadinessCheck.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/Outbox/OutboxPublisher.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Tests/Security/OutboundUrlAllowListHandlerTests.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/LoggingBehavior.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/ValidationBehavior.cs`, … (+179 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `src/Services/Catalog/FreshCart.Catalog.Tests/Products/ProductQueryFiltersTests.cs`, `src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 27 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (27 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

Do you agree with this assessment?

D31 · IaC & Container Security0.0 / 10Critical✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

238 finding(s): 0 critical, 23 high, 188 medium, 27 low.

REDACTED

What to do

Resolve the 188 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (109), REDACTED (26), REDACTED (12). — One of this dimension's main actionable groups (188 warning-level).
Resolve the 23 High IaC finding(s) in IaC & Container Security — start with REDACTED (13), REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 27 Low IaC finding(s) in IaC & Container Security — start with REDACTED (14), REDACTED (13). — One of this dimension's main actionable groups (27 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 148 of the 748 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 13 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

D40 · Network Egress Confinement10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.

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

Kubernetes workloads are covered by a network policy that restricts egress.

✓ On the Gold path — maintain.

Detailed fixes: d40_recommendation.md.

Do you agree with this assessment?

D41 · Kernel & Syscall Confinement8.0 / 10Strong✓ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

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

12/12 workload(s) run every container under a seccomp profile; 0/12 declare an AppArmor/SELinux profile.

What to do

Improve Kernel & Syscall Confinement — currently 8.0/10. — 12/12 workload(s) run every container under a seccomp profile; 0/12 declare an AppArmor/SELinux profile.

Detailed fixes: d41_recommendation.md.

Do you agree with this assessment?

D42 · Runtime Threat Enforcement8.0 / 10Strong✓ Tool-verified

What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.

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

1/2 runtime-enforcement controls present (threat detection, admission control).

No runtime threat detection

What to do

Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

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

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

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

Do you agree with this assessment?

AC3 · Page structure6.8 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — REDACTED:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×6) — REDACTED:654, REDACTED:1055, REDACTED:1069, …

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC6 · Visual & motion safety6.5 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

`.mini-card` moves (`transition: transform .2s,border-color .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:59
<span> moves — its inline style sets `animation: pulse 1.8s infinite ease-in-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — REDACTED:246

What to do

Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

Do you agree with this assessment?

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

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.

Do you agree with this assessment?

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

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

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).

Do you agree with this assessment?

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

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

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

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

The namespaces FreshCart.Delivery.Application.Abstractions ↔ FreshCart.Delivery.Application.Shipments depend on each other. The lightest dependency in the cycle is FreshCart.Delivery.Application.Abstractions → FreshCart.Delivery.Application.Shipments (FreshCart.Delivery.Application.Abstractions.IPendingShipmentRepository → FreshCart.Delivery.Application.Shipments.PendingShipment, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Services/Delivery/FreshCart.Delivery.Application/Abstractions/IPendingShipmentRepository.cs:1
The namespaces FreshCart.Notification.Api.Channels ↔ FreshCart.Notification.Api.Hubs ↔ FreshCart.Notification.Api.Notifications depend on each other. The lightest dependency in the cycle is FreshCart.Notification.Api.Channels → FreshCart.Notification.Api.Hubs (FreshCart.Notification.Api.Channels.SignalRNotificationChannel → FreshCart.Notification.Api.Hubs.NotificationHub, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Services/Notification/FreshCart.Notification.Api/Channels/SignalRNotificationChannel.cs:1

What to do

Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

Do you agree with this assessment?

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

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

Do you agree with this assessment?

AX7 · Slice cohesion10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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 Protection6.5 / 10Adequate✓ Tool-verified

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

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

What to do

Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.

Do you agree with this assessment?

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

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.

Do you agree with this assessment?

C3 · Audit Trail10.0 / 10Exemplary✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

Do you agree with this assessment?

C4 · Data Retention7.5 / 10Strong✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).

What to do

Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.

Do you agree with this assessment?

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

Do you agree with this assessment?

DM10 · One transaction, one aggregate9.6 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

`MartenBasketUnitOfWork.CommitCheckoutAsync` saves `ArchivedBasket`, `OutboxMessage` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenBasketUnitOfWork.cs:13
`GenerateInvoiceCommandHandler.Handle` saves `IDocumentStore`, `IInvoiceRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommandHandler.cs:26

What to do

Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.

Do you agree with this assessment?

DM11 · Constructible invalid state10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

Do you agree with this assessment?

DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

Do you agree with this assessment?

DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

`Order.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:24
`Order.ReservationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:50
`Order.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:52
`OrderCancelledDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:6
`OrderCancelledDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:7
`OrderConfirmedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:7
`OrderConfirmedDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:9
`OrderRefundedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderRefundedDomainEvent.cs:6
`OrderSubmittedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:6
`OrderSubmittedDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:7
`Delivery.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:39
`Delivery.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:41
`Delivery.DriverId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:51
`DeliverySlot.ZoneId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Slots/DeliverySlot.cs:52
`ChatSession.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:32
`ChatSession.AgentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:36

What to do

Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.

Do you agree with this assessment?

DM3 · Integration-event coupling10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether cross-context integration events stay loosely coupled — no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.

Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.

Do you agree with this assessment?

DM4 · Rich vs anemic model10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

Do you agree with this assessment?

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary5.2 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

`ApplicationRole` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Identity/FreshCart.Identity.Domain/Roles/ApplicationRole.cs:14
`ApplicationUser` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Identity/FreshCart.Identity.Domain/Users/ApplicationUser.cs:14
`ProductReview` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:15
`ProductReview` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×3) — src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:32, src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:35, src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:38
`ProductReview` (domain layer) names `BsonIgnoreIfNullAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:39, src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:42
`PurchaseRecord` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:14
`PurchaseRecord` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:23

What to do

Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).

Do you agree with this assessment?

DM7 · Repository granularity10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

Do you agree with this assessment?

DM8 · Value-object opportunities9.9 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

The parameters [city, countrycode, line1, line2, postalcode] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Address.cs:3

What to do

Extract recurring primitive parameter clusters into value objects so the concept (and its rules) lives in one place.

Do you agree with this assessment?

DM9 · Scattered domain decisions9.6 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

FreshCart.Delivery.Domain.Zones.GeoCoordinate's [Latitude, Longitude] are built independently in FreshCart.Delivery.Infrastructure.Geocoding.DeterministicGeocodingAdapter, FreshCart.Delivery.Infrastructure.Seeding.DevelopmentSeedData — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.

What to do

Give each measurement ONE producer — the others call it. Centralising the judgement is not enough on its own: two producers of the same numbers can disagree while every rule reading them is correct.

Do you agree with this assessment?

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

Do you agree with this assessment?

ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

Do you agree with this assessment?

ED3 · Event naming10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

Do you agree with this assessment?

ED4 · Outbox / dual-write7.3 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

`CreateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:26
`UpdateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandHandler.cs:24

What to do

Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.

Do you agree with this assessment?

ED5 · Idempotency9.6 / 10Exemplary◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

`Checkout.CheckoutCommandHandler.Handle` mutates persistent state (a database save one hop away, in MartenBasketUnitOfWork.CommitCheckoutAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommandHandler.cs:29
`VerifyMultiFactorEnrollment.VerifyMultiFactorEnrollmentCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Services/Identity/FreshCart.Identity.Application/Account/Commands/VerifyMultiFactorEnrollment/VerifyMultiFactorEnrollmentCommandHandler.cs:20

What to do

Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

A placeholder e-mail address ("demo@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:30
A placeholder e-mail address ("support@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:31
A placeholder e-mail address ("admin@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:32

What to do

Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.

Do you agree with this assessment?

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

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a README to the 46 of 46 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation7.0 / 10Strong✓ Tool-verified

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

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

What to do

Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

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

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

CONTRIBUTING.md names `tests/contract/`, but no file or folder `tests/contract` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:53
CONTRIBUTING.md names `tests/load/`, but no file or folder `tests/load` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:54
README.md runs `npm start`, but no package.json declares a `start` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:45
README.md links to `gitops/`, but `gitops` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:266
docs/REQUIREMENTS.md names `tests/load/identity-sign-in.js`, but no file or folder `tests/load/identity-sign-in.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/REQUIREMENTS.md:44
tests/README.md names `tests/contract`, but no file or folder `tests/contract` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/README.md:15
tests/README.md names `tests/load`, but no file or folder `tests/load` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/README.md:16
tests/e2e/README.md runs `npm start -- --host 127.0.0.1 --port 4200 --ssl true`, but no package.json declares a `start` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/e2e/README.md:18

What to do

Reconcile the README with reality: CONTRIBUTING.md names `tests/contract/`, but no file or folder `tests/contract` exists; CONTRIBUTING.md names `tests/load/`, but no file or folder `tests/load` exists; README.md runs `npm start`, but no package.json declares a `start` script; README.md links to `gitops/`, but `gitops` does not exist; docs/REQUIREMENTS.md names `tests/load/identity-sign-in.js`, but no file or folder `tests/load/identity-sign-in.js` exists.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

P2 · Observability9.9 / 10Exemplary✓ Tool-verified

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

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

Only 26/27 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 27, 14 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.

Do you agree with this assessment?

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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.

What to do

Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Do you agree with this assessment?

P5 · DR & Backup7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

Do you agree with this assessment?

P8 · Schema migrations3.0 / 10Weak✓ Tool-verified

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; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

`EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. (×7) — src/Services/Pricing/FreshCart.Pricing.Grpc/Persistence/PricingDatabaseInitializer.cs:26, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/OrderingDatabaseInitializer.cs:22, src/Services/Inventory/FreshCart.Inventory.Api/Persistence/InventorySchemaInitializer.cs:17, …

What to do

Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.

Do you agree with this assessment?

PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).

Do you agree with this assessment?

PF2 · Allocation hygiene6.6 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 37 use(s) across 32,649 production line(s) (~1.1/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

Do you agree with this assessment?

S1 · Web-Security Posture9.5 / 10Exemplary✓ Tool-verified

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

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

Set: Content-Security-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, Permissions-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.) — src/BuildingBlocks/FreshCart.BuildingBlocks/Security/SecurityHeadersMiddleware.cs:24

What to do

Add Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.

Do you agree with this assessment?

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

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — src/Services/Reporting/FreshCart.Reporting.Application/Sales/Queries/GetRevenueBreakdownQueryHandler.cs:20

What to do

Sync-over-async (deadlock risk) through `.Result`

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X2 · Cancellation propagation9.7 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

Only 285/299 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. (×4) — src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:122, src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:161, src/Services/Notification/FreshCart.Notification.Api/Configuration/NotificationHealthChecks.cs:44, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×9) — REDACTED:22, REDACTED:55, src/Services/Inventory/FreshCart.Inventory.Api/Grpc/InventoryGrpcService.cs:14, …
No CancellationToken parameter, and the token `httpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpContext.RequestAborted` on, or take a CancellationToken. — src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs:83

What to do

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

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

Do you agree with this assessment?

X5 · Nullable reference types9.8 / 10Exemplary✓ Tool-verified

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.2 `!` suppressions per 1k syntax nodes — 31 suppression(s) across the 125649 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	92%	Exemplary	Strongest area.
Architecture	83%	Strong	Solid.
Maturity	55%	Adequate — gated by M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	63%	Adequate — gated by D13, P8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	77%	Adequate — gated by D29, D31, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	71%	Adequate — gated by DM2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven	88%	Strong	Solid.
Accessibility	62%	Adequate	Acceptable, with room to improve.
Performance	72%	Strong	Solid.

Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

X10 Duplicated predicate — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

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.

Not included — 19 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 — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D32 Data Compliance (PII/GDPR) — 161 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D8 Code Coverage — Coverage not measured — .NET and JavaScript/TypeScript suite
ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): an event-store package (Marten/EventStore); an append-only event-store seam (IEventStore/Append-of-events)
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

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.

Critical — 127 finding(s)

D13 · Secret Scanning · Leaked secret · ×44

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 19 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more in this group — see findings.md.

D31 · IaC & Container Security · High IaC · ×23

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×10

Domain depends on infrastructure: ApplicationRole src/Services/Identity/FreshCart.Identity.Domain/Roles/ApplicationRole.cs:14 — `ApplicationRole` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ApplicationUser src/Services/Identity/FreshCart.Identity.Domain/Users/ApplicationUser.cs:14 — `ApplicationUser` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:15 — `ProductReview` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:32 — `ProductReview` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:35 — `ProductReview` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:38 — `ProductReview` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:39 — `ProductReview` (domain layer) names `BsonIgnoreIfNullAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:42 — `ProductReview` (domain layer) names `BsonIgnoreIfNullAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: PurchaseRecord src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:14 — `PurchaseRecord` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: PurchaseRecord src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:23 — `PurchaseRecord` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · NoWarnInCsproj · ×4

NoWarnInCsproj Directory.Build.props:23 — CA1014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:23 — CA1716 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:23 — CA1707 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:26 — CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

AX3 · Project dependency cycles · Namespace dependency cycle · ×2

Namespace dependency cycle src/Services/Delivery/FreshCart.Delivery.Application/Abstractions/IPendingShipmentRepository.cs:1 — The namespaces FreshCart.Delivery.Application.Abstractions ↔ FreshCart.Delivery.Application.Shipments depend on each other. The lightest dependency in the cycle is FreshCart.Delivery.Application.Abstractions → FreshCart.Delivery.Application.Shipments (FreshCart.Delivery.Application.Abstractions.IPendingShipmentRepository → FreshCart.Delivery.Application.Shipments.PendingShipment, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Services/Notification/FreshCart.Notification.Api/Channels/SignalRNotificationChannel.cs:1 — The namespaces FreshCart.Notification.Api.Channels ↔ FreshCart.Notification.Api.Hubs ↔ FreshCart.Notification.Api.Notifications depend on each other. The lightest dependency in the cycle is FreshCart.Notification.Api.Channels → FreshCart.Notification.Api.Hubs (FreshCart.Notification.Api.Channels.SignalRNotificationChannel → FreshCart.Notification.Api.Hubs.NotificationHub, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.

D28 · Secrets (history) · High secret · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

ED4 · Outbox / dual-write · Dual write (no outbox) · ×2

Dual write (no outbox): CreateProductCommandHandler.Handle src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:26 — `CreateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): UpdateProductCommandHandler.Handle src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandHandler.cs:24 — `UpdateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

Serious — 268 finding(s)

D31 · IaC & Container Security · Medium IaC · ×188

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 163 more in this group — see findings.md.

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

P8 · Schema migrations · Schema created with EnsureCreated() (no migration path) · ×7

Schema created with EnsureCreated() (no migration path) src/Services/Pricing/FreshCart.Pricing.Grpc/Persistence/PricingDatabaseInitializer.cs:26 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/OrderingDatabaseInitializer.cs:22 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) src/Services/Inventory/FreshCart.Inventory.Api/Persistence/InventorySchemaInitializer.cs:17 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) src/Services/Payment/FreshCart.Payment.Infrastructure/PaymentPersistenceInitializer.cs:27 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/ReportingWarehouseInitializer.cs:30 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/ReportingWarehouseInitializer.cs:36 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:54 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.

AC3 · Page structure · Heading level jumps from h2 to h4 · ×6

Heading level jumps from h2 to h4 REDACTED:654 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 REDACTED:1055 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 REDACTED:1069 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 REDACTED:1084 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 REDACTED:1098 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 REDACTED:1717 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.

D29 · Static Analysis (SAST) · REDACTED · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

X2 · Cancellation propagation · Async method without CancellationToken · ×5

Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:122 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:161 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Notification/FreshCart.Notification.Api/Configuration/NotificationHealthChecks.cs:44 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Reviews/FreshCart.Reviews.Api/DependencyInjection.cs:84 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WriteAntiforgeryFailureAsync src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs:83 — No CancellationToken parameter, and the token `httpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpContext.RequestAborted` on, or take a CancellationToken.

D17 · Explicit Debt · Dead code · ×4

Dead code: Deactivate src/Services/Delivery/FreshCart.Delivery.Domain/Drivers/Driver.cs:36 — Method Deactivate — Roslyn's SymbolFinder walked every project the solution loads, including FreshCart.Delivery.Domain, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Reactivate src/Services/Delivery/FreshCart.Delivery.Domain/Drivers/Driver.cs:38 — Method Reactivate — Roslyn's SymbolFinder walked every project the solution loads, including FreshCart.Delivery.Domain, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: HasAnyDriversAsync src/Services/Delivery/FreshCart.Delivery.Application/Abstractions/IDriverRepository.cs:18 — Method HasAnyDriversAsync — Roslyn's SymbolFinder walked every project the solution loads, including FreshCart.Delivery.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CountOnlineAsync src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Assignment/IAgentAvailabilityRegistry.cs:19 — Method CountOnlineAsync — Roslyn's SymbolFinder walked every project the solution loads, including FreshCart.CustomerSupport.Api, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.

D6 · Cohesion (LCOM4) · Low cohesion · ×3

Low cohesion: CancelOrderOnPaymentFailureActivity (LCOM4 4) src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/CancelOrderOnPaymentFailureActivity.cs:14 — CancelOrderOnPaymentFailureActivity's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CancelOrderOnStockFailureActivity (LCOM4 4) src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/CancelOrderOnStockFailureActivity.cs:13 — CancelOrderOnStockFailureActivity's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ConfirmOrderActivity (LCOM4 4) src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/ConfirmOrderActivity.cs:13 — ConfirmOrderActivity's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2

Animation without a prefers-reduced-motion guard REDACTED:59 — `.mini-card` moves (`transition: transform .2s,border-color .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:246 — <span> moves — its inline style sets `animation: pulse 1.8s infinite ease-in-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (4 members, 50+ identical tokens) src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:162 — src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:162-183 | src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:123-144 | src/Services/Notification/FreshCart.Notification.Api/Configuration/NotificationHealthChecks.cs:45-66 | src/Services/Reviews/FreshCart.Reviews.Api/DependencyInjection.cs:85-106 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17 — src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17-59 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:65-110 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:115-141 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:146-172 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2

Duplicated block (22 lines × 2) src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs:41 — src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs:41-62 | src/Services/Payment/FreshCart.Payment.Infrastructure/ReadModel/SqlConnectionFactory.cs:41-62 — before extracting anything, compare `src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs` and `src/Services/Payment/FreshCart.Payment.Infrastructure/ReadModel/SqlConnectionFactory.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Authentication/ClaimsPrincipalExtensions.cs:17 — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Authentication/ClaimsPrincipalExtensions.cs:17-59 | src/Services/Reviews/FreshCart.Reviews.Api/Authentication/ClaimsPrincipalExtensions.cs:17-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×2

Duplicated block (17 lines × 3) src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:163 — src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:163-179 | src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:124-140 | src/Services/Reviews/FreshCart.Reviews.Api/DependencyInjection.cs:86-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) src/Services/Ordering/FreshCart.Ordering.Application/DependencyInjection.cs:13 — src/Services/Ordering/FreshCart.Ordering.Application/DependencyInjection.cs:13-29 | src/Services/Payment/FreshCart.Payment.Application/DependencyInjection.cs:13-29 | src/Services/Reporting/FreshCart.Reporting.Application/DependencyInjection.cs:13-29 — before extracting anything, compare `src/Services/Ordering/FreshCart.Ordering.Application/DependencyInjection.cs` and `src/Services/Payment/FreshCart.Payment.Application/DependencyInjection.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2

Duplicated block (9 lines × 2) src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:17 — src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:17-25 | src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/Invoice.cs:34-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Persistence/SupportChatGuidSerialization.cs:18 — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Persistence/SupportChatGuidSerialization.cs:18-26 | src/Services/Reviews/FreshCart.Reviews.Api/Persistence/ReviewsGuidSerialization.cs:18-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2

Duplicated block (5 lines × 2) src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:35 — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:35-39 | src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandHandler.cs:31-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `CreateProductCommand` in one and `UpdateProductCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Authentication/SupportUserIdProvider.cs:17 — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Authentication/SupportUserIdProvider.cs:17-21 | src/Services/Notification/FreshCart.Notification.Api/Hubs/SubjectUserIdProvider.cs:18-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×2

One operation mutates 2 aggregates: MartenBasketUnitOfWork.CommitCheckoutAsync src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenBasketUnitOfWork.cs:13 — `MartenBasketUnitOfWork.CommitCheckoutAsync` saves `ArchivedBasket`, `OutboxMessage` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: GenerateInvoiceCommandHandler.Handle src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommandHandler.cs:26 — `GenerateInvoiceCommandHandler.Handle` saves `IDocumentStore`, `IInvoiceRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.

ED5 · Idempotency · Non-idempotent mutation · ×2

Non-idempotent mutation: Checkout.CheckoutCommandHandler.Handle src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommandHandler.cs:29 — `Checkout.CheckoutCommandHandler.Handle` mutates persistent state (a database save one hop away, in MartenBasketUnitOfWork.CommitCheckoutAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Non-idempotent mutation: VerifyMultiFactorEnrollment.VerifyMultiFactorEnrollmentCommandHandler.Handle src/Services/Identity/FreshCart.Identity.Application/Account/Commands/VerifyMultiFactorEnrollment/VerifyMultiFactorEnrollmentCommandHandler.cs:20 — `VerifyMultiFactorEnrollment.VerifyMultiFactorEnrollmentCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.

AC3 · Page structure · Page without a main landmark · ×1

Page without a main landmark REDACTED:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1

Duplicated block (28–29 lines × 2) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperProductReadWarehouse.cs:15 — src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperProductReadWarehouse.cs:15-42 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperProductReadWarehouse.cs:48-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1

Duplicated block (28 lines × 2) src/Services/Identity/FreshCart.Identity.Application/Account/Commands/DisableMultiFactor/DisableMultiFactorCommandHandler.cs:21 — src/Services/Identity/FreshCart.Identity.Application/Account/Commands/DisableMultiFactor/DisableMultiFactorCommandHandler.cs:21-48 | src/Services/Identity/FreshCart.Identity.Application/Account/Commands/VerifyMultiFactorEnrollment/VerifyMultiFactorEnrollmentCommandHandler.cs:24-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `DisableMultiFactorCommand` in one and `VerifyMultiFactorEnrollmentCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1

Duplicated block (25 lines × 2) src/Services/Basket/FreshCart.Basket.Api/Pricing/PricingGrpcChannelFactory.cs:21 — src/Services/Basket/FreshCart.Basket.Api/Pricing/PricingGrpcChannelFactory.cs:21-45 | src/Services/Ordering/FreshCart.Ordering.Infrastructure/Inventory/InventoryGrpcChannelFactory.cs:21-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1

Duplicated block (22 lines × 3) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17 — src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17-42 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:115-136 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:146-167 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (13–21 lines × 2) · ×1

Duplicated block (13–21 lines × 2) src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:31 — src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:31-51 | src/Services/Ordering/FreshCart.Ordering.Api/Messaging/OrderingMessagingExtensions.cs:45-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×1

Duplicated block (20–21 lines × 2) src/ApiGateways/FreshCart.Gateway.Yarp/Configuration/GatewayAuthenticationConfiguration.cs:35 — src/ApiGateways/FreshCart.Gateway.Yarp/Configuration/GatewayAuthenticationConfiguration.cs:35-54 | src/Services/Identity/FreshCart.Identity.Api/Configuration/AuthenticationConfiguration.cs:57-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1

Duplicated block (17 lines × 2) src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:25 — src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:25-41 | src/Services/Ordering/FreshCart.Ordering.Infrastructure/Inventory/DevelopmentCertificateValidation.cs:25-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1

Duplicated block (14 lines × 4) src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:170 — src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:170-183 | src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:131-144 | src/Services/Notification/FreshCart.Notification.Api/Configuration/NotificationHealthChecks.cs:53-66 | src/Services/Reviews/FreshCart.Reviews.Api/DependencyInjection.cs:93-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:170` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1

Duplicated block (14 lines × 2) src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:41 — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:41-54 | src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs:34-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:41` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8–15 lines × 2) · ×1

Duplicated block (8–15 lines × 2) src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:12 — src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:12-19 | src/Services/Basket/FreshCart.Basket.Api/Domain/ArchivedBasket.cs:15-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:26 — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:26-36 | src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs:22-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:39` calls `InclusiveBetween`, `RuleFor` and `src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs:35` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1

Duplicated block (10 lines × 3) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:92 — src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:92-101 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:127-136 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:158-167 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1

Duplicated block (12 lines × 2) src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:21 — src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:21-32 | src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/EntityFrameworkOutboxStore.cs:19-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1

Duplicated block (10 lines × 4) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:33 — src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:33-42 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:92-101 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:127-136 | src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:158-167 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1

Duplicated block (16 lines × 2) src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:72 — src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:72-87 | src/Services/Ordering/FreshCart.Ordering.Api/Messaging/OrderingMessagingExtensions.cs:74-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1

Duplicated block (6 lines × 2) src/Services/Payment/FreshCart.Payment.Application/Payments/Commands/CapturePayment/CapturePaymentCommandHandler.cs:133 — src/Services/Payment/FreshCart.Payment.Application/Payments/Commands/CapturePayment/CapturePaymentCommandHandler.cs:133-138 | src/Services/Payment/FreshCart.Payment.Application/Payments/Commands/RefundPayment/RefundPaymentCommandHandler.cs:73-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1

Duplicated block (8 lines × 2) src/Services/Identity/FreshCart.Identity.Application/Account/Commands/DisableMultiFactor/DisableMultiFactorCommandValidator.cs:9 — src/Services/Identity/FreshCart.Identity.Application/Account/Commands/DisableMultiFactor/DisableMultiFactorCommandValidator.cs:9-16 | src/Services/Identity/FreshCart.Identity.Application/Account/Commands/VerifyMultiFactorEnrollment/VerifyMultiFactorEnrollmentCommandValidator.cs:10-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1

Sync-over-async (deadlock risk) through `.Result` src/Services/Reporting/FreshCart.Reporting.Application/Sales/Queries/GetRevenueBreakdownQueryHandler.cs:20 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.

Minor — 94 finding(s)

D31 · IaC & Container Security · Low IaC · ×27

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more in this group — see findings.md.

DM2 · Strongly-typed ids · Primitive id on a domain type · ×16

Primitive id on a domain type: Order.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:24 — `Order.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Order.ReservationId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:50 — `Order.ReservationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Order.PaymentId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:52 — `Order.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderCancelledDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:6 — `OrderCancelledDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderCancelledDomainEvent.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:7 — `OrderCancelledDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderConfirmedDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:7 — `OrderConfirmedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderConfirmedDomainEvent.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:9 — `OrderConfirmedDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderRefundedDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderRefundedDomainEvent.cs:6 — `OrderRefundedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderSubmittedDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:6 — `OrderSubmittedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OrderSubmittedDomainEvent.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:7 — `OrderSubmittedDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Delivery.OrderId src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:39 — `Delivery.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Delivery.CustomerId src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:41 — `Delivery.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Delivery.DriverId src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:51 — `Delivery.DriverId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: DeliverySlot.ZoneId src/Services/Delivery/FreshCart.Delivery.Domain/Slots/DeliverySlot.cs:52 — `DeliverySlot.ZoneId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: ChatSession.CustomerId src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:32 — `ChatSession.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: ChatSession.AgentId src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:36 — `ChatSession.AgentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.

X10 · Duplicated predicate · Duplicated predicate · ×12

Duplicated predicate src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs:49 — `attempt < MaxOpenAttempts && IsTransient(sqlException)` appears character-identically in 2 files — src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs, src/Services/Payment/FreshCart.Payment.Infrastructure/ReadModel/SqlConnectionFactory.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:50 — `attributes is null || attributes.Count <= ProductConstraints.MaxAttributeCount` appears character-identically in 2 files — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs, src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:37 — `candidateIds.Contains(message.Id) && message.ProcessedOnUtc == null && (message.ClaimId == null || message.ClaimedOnUtc < leaseExpiresBefore…` appears character-identically in 2 files — src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/EntityFrameworkOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:36 — `chain is null || chain.ChainStatus.All(status => status.Status is X509ChainStatusFlags.NoError or X509ChainStatusFlags.UntrustedRoot)` appears character-identically in 2 files — src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Inventory/DevelopmentCertificateValidation.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommandHandler.cs:34 — `customerBasket is null || customerBasket.IsEmpty` appears character-identically in 2 files — src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommandHandler.cs, src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/GetBasket/GetBasketQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:42 — `images is null || images.Count <= ProductConstraints.MaxImageCount` appears character-identically in 2 files — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs, src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:44 — `images is null || images.Count(image => image.IsPrimary) <= 1` appears character-identically in 2 files — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs, src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:45 — `message.ClaimId == claimId && message.ProcessedOnUtc == null` appears character-identically in 2 files — src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/EntityFrameworkOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:21 — `message.ProcessedOnUtc == null && (message.ClaimId == null || message.ClaimedOnUtc < leaseExpiresBefore)` appears character-identically in 2 files — src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/EntityFrameworkOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:39 — `onlyUntrustedRoot && inspectedCertificate.Extensions.Any(extension => string.Equals(extension.Oid?.Value, AspNetCoreHttpsDevelopmentCertific…` appears character-identically in 2 files — src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Inventory/DevelopmentCertificateValidation.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:30 — `sslPolicyErrors != SslPolicyErrors.RemoteCertificateChainErrors || certificate is not X509Certificate2 inspectedCertificate` appears character-identically in 2 files — src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Inventory/DevelopmentCertificateValidation.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:32 — `string.IsNullOrEmpty(currencyCode) || CurrencyCodeRegex().IsMatch(currencyCode)` appears character-identically in 2 files — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs, src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandValidator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

M4 · Documentation accuracy · README/code drift · ×8

README/code drift CONTRIBUTING.md:53 — CONTRIBUTING.md names `tests/contract/`, but no file or folder `tests/contract` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:54 — CONTRIBUTING.md names `tests/load/`, but no file or folder `tests/load` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:45 — README.md runs `npm start`, but no package.json declares a `start` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:266 — README.md links to `gitops/`, but `gitops` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/REQUIREMENTS.md:44 — docs/REQUIREMENTS.md names `tests/load/identity-sign-in.js`, but no file or folder `tests/load/identity-sign-in.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/README.md:15 — tests/README.md names `tests/contract`, but no file or folder `tests/contract` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/README.md:16 — tests/README.md names `tests/load`, but no file or folder `tests/load` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/e2e/README.md:18 — tests/e2e/README.md runs `npm start -- --host 127.0.0.1 --port 4200 --ssl true`, but no package.json declares a `start` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

D10 · Test Quality · Mock-dominated test · ×7

Mock-dominated test: SeedsCategoriesBrandsAndProductsOnFirstDevelopmentStart src/Services/Catalog/FreshCart.Catalog.Tests/Seeding/CatalogDataSeederTests.cs:34 — This test sets up 4 test doubles (for example `Substitute.For<IHostEnvironment>()`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: SkipsSeedingWhenTheCatalogAlreadyContainsCategoriesSoRestartsNeverDuplicate src/Services/Catalog/FreshCart.Catalog.Tests/Seeding/CatalogDataSeederTests.cs:60 — This test sets up 4 test doubles (for example `Substitute.For<IHostEnvironment>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: ArchiveOutboxMessageAndLiveBasketDeletionRideOneUnitOfWorkCommit src/Services/Basket/FreshCart.Basket.Tests/Features/Checkout/CheckoutCommandHandlerTests.cs:78 — This test sets up 3 test doubles (for example `Substitute.For<IBasketRepository>()`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: BasketIsRepricedBeforeTheCommitAndTheCacheIsEvictedAfterIt src/Services/Basket/FreshCart.Basket.Tests/Features/Checkout/CheckoutCommandHandlerTests.cs:97 — This test sets up 4 test doubles (for example `Substitute.For<IBasketRepository>()`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: SchedulesADeliveryAndStagesTheScheduledEventForADeliverableOrder src/Services/Delivery/FreshCart.Delivery.Tests/Application/OrderConfirmedConsumerTests.cs:57 — This test sets up 3 test doubles (for example `Substitute.For<ISlotRepository>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: SkipsADigitalOnlyOrderWithoutSchedulingOrStaging src/Services/Delivery/FreshCart.Delivery.Tests/Application/OrderConfirmedConsumerTests.cs:79 — This test sets up 3 test doubles (for example `Substitute.For<IDeliveryRepository>()`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: IsIdempotentWhenADeliveryAlreadyExistsForTheOrder src/Services/Delivery/FreshCart.Delivery.Tests/Application/OrderConfirmedConsumerTests.cs:119 — This test sets up 3 test doubles (for example `Substitute.For<IDeliveryRepository>()`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.

D29 · Static Analysis (SAST) · REDACTED · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

IC1 · Incompleteness & stubs · Placeholder data left in code · ×3

Placeholder data left in code src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:30 — A placeholder e-mail address ("demo@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
Placeholder data left in code src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:31 — A placeholder e-mail address ("support@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
Placeholder data left in code src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:32 — A placeholder e-mail address ("admin@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.

C4 · Data Retention · Partial data-retention evidence · ×1

Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).

D21 · Naming Consistency · Inconsistent naming convention for private test setup fields and helper methods. Some use the full class name of the dependency (e.g., `repository`, `catalogQueries`, `harness`, `consumer`, `mongoFixture`), while others use abbreviated or generic names (e.g., `CommandFor`, `Now`, `lazyChannel`, `ProductId`, `CustomerId`, `IdempotencyKey`, `CardMethod`). While `CustomerId` and `ProductId` are specific values rather than dependencies, the pattern of using the full type name for dependencies is inconsistent with the abbreviated forms used in other test classes. · ×1

Inconsistent naming convention for private test setup fields and helper methods. Some use the full class name of the dependency (e.g., `repository`, `catalogQueries`, `harness`, `consumer`, `mongoFixture`), while others use abbreviated or generic names (e.g., `CommandFor`, `Now`, `lazyChannel`, `ProductId`, `CustomerId`, `IdempotencyKey`, `CardMethod`). While `CustomerId` and `ProductId` are specific values rather than dependencies, the pattern of using the full type name for dependencies is inconsistent with the abbreviated forms used in other test classes. — Standardize on using the full type name (lowercased) for private test dependencies (e.g., `basketCheckoutStartedConsumer`, `mongoEventStore`, `catalogQueries`) to improve readability and consistency across test classes. (symbols: FreshCart.Delivery.Tests.Application.BasketCheckoutStartedConsumerTests.CustomerId, FreshCart.Payment.Tests.Application.CapturePaymentCommandHandlerTests.IdempotencyKey, FreshCart.Payment.Tests.Application.RefundPaymentCommandHandlerTests.CardMethod, FreshCart.Catalog.Tests.Brands.GetBrandsQueryHandlerTests.catalogQueries, FreshCart.Delivery.Tests.Infrastructure.MongoDeliveryRepositoryTests.deliveryRepository, FreshCart.Delivery.Tests.Infrastructure.MongoPendingShipmentRepositoryTests.repository, FreshCart.Notification.Tests.Consumers.OrderPlacedConsumerTests.harness, FreshCart.Reporting.Tests.Projections.DeliveryCompletedProjectionConsumerTests.consumer, FreshCart.Reporting.Tests.Projections.OrderConfirmedProjectionConsumerTests.consumer, FreshCart.Payment.Tests.Common.MongoEventStoreFixture.mongoFixture, FreshCart.Basket.Tests.Features.Checkout.CheckoutCommandHandlerTests.CommandFor, FreshCart.Ordering.Tests.Orders.RefundOrderCommandHandlerTests.Now, FreshCart.Basket.Api.Pricing.PricingGrpcChannelFactory.lazyChannel, FreshCart.Catalog.Tests.Products.DeleteProductCommandHandlerTests.ProductId)

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D42 · Runtime Threat Enforcement · No runtime threat detection · ×1

No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.

D9 · Test Distribution · Inverted test pyramid · ×1

Inverted test pyramid — Only 19 % of tests are unit tests (146 unit vs 602 integration, 0 BDD); a broader unit base gives faster, more localised feedback.

DM8 · Value-object opportunities · Primitive data clump · ×1

Primitive data clump: [city, countrycode, line1, line2, postalcode] src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Address.cs:3 — The parameters [city, countrycode, line1, line2, postalcode] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.

DM9 · Scattered domain decisions · Measurement [Latitude, Longitude] produced in 2 places · ×1

Measurement [Latitude, Longitude] produced in 2 places — FreshCart.Delivery.Domain.Zones.GeoCoordinate's [Latitude, Longitude] are built independently in FreshCart.Delivery.Infrastructure.Geocoding.DeterministicGeocodingAdapter, FreshCart.Delivery.Infrastructure.Seeding.DevelopmentSeedData — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 26/27 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 27, 14 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

PF1 · Benchmark discipline · No performance benchmarks · ×1

No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

S1 · Web-Security Posture · Security headers incomplete · ×1

Security headers incomplete src/BuildingBlocks/FreshCart.BuildingBlocks/Security/SecurityHeadersMiddleware.cs:24 — Set: Content-Security-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, Permissions-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.)

X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1

Not all async methods take a CancellationToken — Only 285/299 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.

X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1

Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.2 `!` suppressions per 1k syntax nodes — 31 suppression(s) across the 125649 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

X7 · Silent fallback defaults · Silent fallback default in catch · ×1

Silent fallback default in catch src/Services/Notification/FreshCart.Notification.Api/Notifications/Mongo/MongoNotificationStore.cs:66 — `AddAsync` swallows `MongoWriteException` into `return AddNotificationOutcome.DuplicateIgnored;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.

Minor — 48 finding(s)

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

XML-doc coverage: FreshCart.BuildingBlocks src/BuildingBlocks/FreshCart.BuildingBlocks/FreshCart.BuildingBlocks.csproj — FreshCart.BuildingBlocks: 49 % XML-doc coverage (27/55).
XML-doc coverage: FreshCart.BuildingBlocks.Messaging src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/FreshCart.BuildingBlocks.Messaging.csproj — FreshCart.BuildingBlocks.Messaging: 17 % XML-doc coverage (21/123).
XML-doc coverage: FreshCart.ServiceDefaults src/BuildingBlocks/FreshCart.ServiceDefaults/FreshCart.ServiceDefaults.csproj — FreshCart.ServiceDefaults: 78 % XML-doc coverage (7/9).
XML-doc coverage: FreshCart.Catalog.Api src/Services/Catalog/FreshCart.Catalog.Api/FreshCart.Catalog.Api.csproj — FreshCart.Catalog.Api: 11 % XML-doc coverage (23/201).
XML-doc coverage: FreshCart.Basket.Api src/Services/Basket/FreshCart.Basket.Api/FreshCart.Basket.Api.csproj — FreshCart.Basket.Api: 21 % XML-doc coverage (36/174).
XML-doc coverage: FreshCart.Pricing.Grpc src/Services/Pricing/FreshCart.Pricing.Grpc/FreshCart.Pricing.Grpc.csproj — FreshCart.Pricing.Grpc: 13 % XML-doc coverage (10/75).
XML-doc coverage: FreshCart.Ordering.Domain src/Services/Ordering/FreshCart.Ordering.Domain/FreshCart.Ordering.Domain.csproj — FreshCart.Ordering.Domain: 7 % XML-doc coverage (5/69).
XML-doc coverage: FreshCart.Ordering.Application src/Services/Ordering/FreshCart.Ordering.Application/FreshCart.Ordering.Application.csproj — FreshCart.Ordering.Application: 16 % XML-doc coverage (16/103).
XML-doc coverage: FreshCart.Ordering.Infrastructure src/Services/Ordering/FreshCart.Ordering.Infrastructure/FreshCart.Ordering.Infrastructure.csproj — FreshCart.Ordering.Infrastructure: 25 % XML-doc coverage (26/103).
XML-doc coverage: FreshCart.Ordering.Api src/Services/Ordering/FreshCart.Ordering.Api/FreshCart.Ordering.Api.csproj — FreshCart.Ordering.Api: 33 % XML-doc coverage (5/15).
XML-doc coverage: FreshCart.Inventory.Api src/Services/Inventory/FreshCart.Inventory.Api/FreshCart.Inventory.Api.csproj — FreshCart.Inventory.Api: 6 % XML-doc coverage (5/80).
XML-doc coverage: FreshCart.Payment.Domain src/Services/Payment/FreshCart.Payment.Domain/FreshCart.Payment.Domain.csproj — FreshCart.Payment.Domain: 7 % XML-doc coverage (2/29).
XML-doc coverage: FreshCart.Payment.Application src/Services/Payment/FreshCart.Payment.Application/FreshCart.Payment.Application.csproj — FreshCart.Payment.Application: 14 % XML-doc coverage (5/36).
XML-doc coverage: FreshCart.Payment.Infrastructure src/Services/Payment/FreshCart.Payment.Infrastructure/FreshCart.Payment.Infrastructure.csproj — FreshCart.Payment.Infrastructure: 19 % XML-doc coverage (13/67).
XML-doc coverage: FreshCart.Payment.Api src/Services/Payment/FreshCart.Payment.Api/FreshCart.Payment.Api.csproj — FreshCart.Payment.Api: 7 % XML-doc coverage (1/14).
XML-doc coverage: FreshCart.Delivery.Domain src/Services/Delivery/FreshCart.Delivery.Domain/FreshCart.Delivery.Domain.csproj — FreshCart.Delivery.Domain: 22 % XML-doc coverage (13/60).
XML-doc coverage: FreshCart.Delivery.Application src/Services/Delivery/FreshCart.Delivery.Application/FreshCart.Delivery.Application.csproj — FreshCart.Delivery.Application: 51 % XML-doc coverage (23/45).
XML-doc coverage: FreshCart.Delivery.Infrastructure src/Services/Delivery/FreshCart.Delivery.Infrastructure/FreshCart.Delivery.Infrastructure.csproj — FreshCart.Delivery.Infrastructure: 12 % XML-doc coverage (13/105).
XML-doc coverage: FreshCart.Delivery.Api src/Services/Delivery/FreshCart.Delivery.Api/FreshCart.Delivery.Api.csproj — FreshCart.Delivery.Api: 29 % XML-doc coverage (2/7).
XML-doc coverage: FreshCart.Notification.Api src/Services/Notification/FreshCart.Notification.Api/FreshCart.Notification.Api.csproj — FreshCart.Notification.Api: 34 % XML-doc coverage (38/111).
XML-doc coverage: FreshCart.Reporting.Domain src/Services/Reporting/FreshCart.Reporting.Domain/FreshCart.Reporting.Domain.csproj — FreshCart.Reporting.Domain: 26 % XML-doc coverage (16/62).
XML-doc coverage: FreshCart.Reporting.Application src/Services/Reporting/FreshCart.Reporting.Application/FreshCart.Reporting.Application.csproj — FreshCart.Reporting.Application: 56 % XML-doc coverage (44/78).
XML-doc coverage: FreshCart.Reporting.Infrastructure src/Services/Reporting/FreshCart.Reporting.Infrastructure/FreshCart.Reporting.Infrastructure.csproj — FreshCart.Reporting.Infrastructure: 18 % XML-doc coverage (17/96).
XML-doc coverage: FreshCart.Reporting.Api src/Services/Reporting/FreshCart.Reporting.Api/FreshCart.Reporting.Api.csproj — FreshCart.Reporting.Api: 27 % XML-doc coverage (4/15).
XML-doc coverage: FreshCart.CustomerSupport.Api src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/FreshCart.CustomerSupport.Api.csproj — FreshCart.CustomerSupport.Api: 25 % XML-doc coverage (41/165).
+ 7 more in this group — see findings.md.

D10 · Test Quality · Mock framework · ×14

Mock framework: NSubstitute — FreshCart.BuildingBlocks.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Catalog.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Basket.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Pricing.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Ordering.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Inventory.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Payment.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Delivery.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Notification.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Reporting.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.CustomerSupport.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Reviews.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Identity.Tests references NSubstitute.
Mock framework: NSubstitute — FreshCart.Gateway.Tests references NSubstitute.

D5 · Coupling · Off the main sequence · ×2

Off the main sequence: FreshCart.BuildingBlocks.Messaging src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/FreshCart.BuildingBlocks.Messaging.csproj:1 — FreshCart.BuildingBlocks.Messaging: abstractness 0.08, instability 0.00, distance 0.92 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: FreshCart.BuildingBlocks src/BuildingBlocks/FreshCart.BuildingBlocks/FreshCart.BuildingBlocks.csproj:1 — FreshCart.BuildingBlocks: abstractness 0.26, instability 0.00, distance 0.74 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2d80246da9534c86ae7f28493d649634/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2d80246da9534c86ae7f28493d649634/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	51	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	nuget	—	nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan	0	—
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	238	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 161 file(s) — `src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs`, `src/AspireAppHost/FreshCart.AppHost/MongoDirectReadinessCheck.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/Outbox/OutboxPublisher.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/LoggingBehavior.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/ValidationBehavior.cs`, … (+156 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a16140-2552-7e3d-81ae-e3f1e9a934e3 · 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 — 43 field(s) across 3 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, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Email — 23 field(s)

DownstreamPrincipal.Email src/ApiGateways/FreshCart.Gateway.Yarp/Auth/DownstreamPrincipal.cs:10
BasketCheckoutStartedIntegrationEvent.CustomerEmail src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:9
OrderPlacedIntegrationEvent.CustomerEmail src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/OrderPlacedIntegrationEvent.cs:9
CheckoutCommand.CustomerEmail src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommand.cs:8
CurrentUserResponse.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Account/CurrentUserResponse.cs:8
AuthenticationProfileDto.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/AuthenticationProfileDto.cs:8
SignInRequest.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/SignInRequest.cs:7
SignUpRequest.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/SignUpRequest.cs:8
SignUpResponse.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/SignUpResponse.cs:8
SignInCommand.Email src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignIn/SignInCommand.cs:11
SignUpCommand.Email src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignUp/SignUpCommand.cs:11
SignUpResult.Email src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignUp/SignUpResult.cs:10
AuthenticationProfile.Email src/Services/Identity/FreshCart.Identity.Application/Common/Models/AuthenticationProfile.cs:9
DemoAccount.Email src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:133
OrderDetailDto.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:11
OrderSubmittedDomainEvent.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:8
Order.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:26
OrderSubmission.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Domain/Orders/OrderSubmission.cs:14
OrderDetailRow.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/Reads/OrderDetailRow.cs:17
GenerateInvoiceRequest.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Api/Endpoints/Invoices/GenerateInvoiceRequest.cs:13
GenerateInvoiceCommand.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommand.cs:13
Invoice.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/Invoice.cs:24
InvoiceRecord.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/InvoiceRecord.cs:15

Address — 19 field(s)

BasketCheckoutStartedIntegrationEvent.BillingAddress src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:19
CheckoutAddress.PostalCode src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/CheckoutAddress.cs:3
CheckoutCommand.BillingAddress src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommand.cs:11
CheckoutRequest.BillingAddress src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutRequest.cs:7
DeliveryAddressDto.PostalCode src/Services/Delivery/FreshCart.Delivery.Application/Tracking/DeliveryAddressDto.cs:11
DeliveryAddress.PostalCode src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/DeliveryAddress.cs:35
AddressDocument.PostalCode src/Services/Delivery/FreshCart.Delivery.Infrastructure/Persistence/Documents/AddressDocument.cs:14
OrderAddressDto.PostalCode src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderAddressDto.cs:7
OrderDetailDto.BillingAddress src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:29
Address.PostalCode src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Address.cs:7
Order.BillingAddress src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:46
OrderSubmission.BillingAddress src/Services/Ordering/FreshCart.Ordering.Domain/Orders/OrderSubmission.cs:32
OrderDetailRow.BillingPostalCode src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/Reads/OrderDetailRow.cs:49
OrderDetailRow.ShippingPostalCode src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/Reads/OrderDetailRow.cs:59
GenerateInvoiceRequest.BillingAddress src/Services/Reporting/FreshCart.Reporting.Api/Endpoints/Invoices/GenerateInvoiceRequest.cs:16
GenerateInvoiceCommand.BillingAddress src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommand.cs:16
Invoice.BillingAddress src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/Invoice.cs:28
InvoiceAddress.PostalCode src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/InvoiceAddress.cs:12
InvoiceRecord.BillingAddress src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/InvoiceRecord.cs:17

Name — 1 field(s)

InvoiceAddress.FullName src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/InvoiceAddress.cs:7

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — bounded-context dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 92% · Exemplary ·

At a glance — Architecture · 83% · Strong ·

At a glance — Maturity · 55% · Adequate · gated by M4 ·

At a glance — Readiness · 63% · Adequate · gated by D13, P8 ·

At a glance — Security · 77% · Adequate · gated by D29, D31, D36 ·

At a glance — Domain Modelling · 71% · Adequate · gated by DM2 ·

At a glance — Event-Driven · 88% · Strong ·

At a glance — Accessibility · 62% · Adequate ·

At a glance — Performance · 72% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts