unrealbg/BlazorShop

Executive summary

unrealbg/BlazorShop scores 44 out of 100 and is rated Weak, while five of its seven lenses score higher still: Architecture at 80 and Performance at 71, both rated Strong, and Security and Compliance at 66, Code Health at 63 and Maturity at 62, all rated Adequate.

The score is lower than those five because the weakest lens counts most, and here that is Production Readiness, which scores 33 and is rated Weak. Its Security & performance tooling dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 Leaked secret finding(s) in REDACTED Scanning and to resolve the 3 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 44 to about 54.

104 findings are critical: 40 in Forms & labels, 22 in Static Analysis (SAST), 13 in Explicit Debt, ten in Page structure, four in Dependency Vulnerabilities, four in Keyboard semantics, four in Project dependency cycles, three in IaC & Container Security, two in Text alternatives, one in REDACTED Scanning and one in Secrets (history).

Watchdog couldn't measure Runtime accessibility in this code, so that dimension is left out of the score. The product code is 28,033 lines, which would take an estimated 0.8 person-years, around €110,000, to rebuild.

Code Health 63 Adequate Architecture 80 Strong Maturity 62 Adequate, capped by Architecture documentation Production Readiness 33 Weak, capped by Security & performance tooling, DR & Backup and Outbound HTTP resilience Security and Compliance 66 Adequate, capped by Static Analysis (SAST), Supply-chain Provenance & Signing and Data Protection Accessibility 41 Weak, capped by Keyboard semantics Performance 71 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.

Production Readiness 33 · counts for 46%Accessibility 41 · counts for 25%Maturity 62 · counts for 14%Code Health 63 · counts for 8%Security and Compliance 66 · counts for 4%Performance 71 · counts for 2%Architecture 80 · counts for 1%

If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 44 to about 54.

Code composition: what the lines of code are

Business logic 18%Supporting code 30%Tests 32%Generated by tools 20%

Rebuild cost: about €110,000 · Estimate

Cost to rebuild	€36,000 to €180,000, for 600 to 1,935 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem	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.7 at a score of 44. 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: 28,033 lines of product code

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.

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.

Raises the score by about 8 points · Low effort · REDACTED Scanning

Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with BlazorShop.Web.csproj, BlazorShop.Tests.csproj, BlazorShop.E2E.csproj.

Raises the score by about 6 points · Low effort · Dependency Hygiene

Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED.

Raises the score by about 3 points · Low effort · Dependency Hygiene

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 €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Production Readiness, at 33 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

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

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

If you do one thing first · First action

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.

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

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

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.

120 modules, with 269 dependencies between them. 4 loops run through 8 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 80 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 Application.DTOs	2 Application.DTOs.Product.ProductVariant	3 Application.DTOs.Seo	4 Application.Options	5 Application.Services.Contracts.Logging	6 Domain.Entities	7 Domain.Entities.Identity	8 Domain.Entities.Payment	9 Web.Shared.Models.Seo	10 Web.Shared.Toast	11 Application.DTOs.Admin.Orders	12 Application.DTOs.Product	13 Application.Services.Contracts.Authentication	14 Domain.Contracts	15 Domain.Contracts.Payment	16 Infrastructure.Data	17 Infrastructure.Demo	18 Web.Shared.Models	19 Web.Shared.Models.Product	20 Application.DTOs.Category	21 Application.DTOs.Payment	23 Web.Services.Contracts	24 Web.Shared.Models.Category	25 Web.Shared.Models.Payment	26 Application.Services.Contracts	27 Application.Services.Contracts.Admin	28 Application.Services.Contracts.Payment	29 Storefront.Services.Contracts	30 Web.Shared.Services.Contracts	33 Infrastructure.Services	35 Storefront.Services	36 Web.Services
1 Application.DTOs
2 Application.DTOs.Product.ProductVariant
3 Application.DTOs.Seo
4 Application.Options
5 Application.Services.Contracts.Logging
6 Domain.Entities
7 Domain.Entities.Identity
8 Domain.Entities.Payment
9 Web.Shared.Models.Seo
10 Web.Shared.Toast
11 Application.DTOs.Admin.Orders								3
12 Application.DTOs.Product		1																		1
13 Application.Services.Contracts.Authentication	2
14 Domain.Contracts						4
15 Domain.Contracts.Payment								5
16 Infrastructure.Data						10	1	7
17 Infrastructure.Demo				1			1
18 Web.Shared.Models										2
19 Web.Shared.Models.Product																							1
20 Application.DTOs.Category												2
21 Application.DTOs.Payment	2					1		1							1
22 Application.Services.Authentication	2			2	1		1						1	1
23 Web.Services.Contracts										1								1														4
24 Web.Shared.Models.Category																			2
25 Web.Shared.Models.Payment															1
26 Application.Services.Contracts	9	3	12									8		4						5
27 Application.Services.Contracts.Admin	5										2			4							3
28 Application.Services.Contracts.Payment	1							6													13
29 Storefront.Services.Contracts			2																2				2								3
30 Web.Shared.Services.Contracts									8	6								36	8				3	8
31 Application.Services	9	3	12	1	1	9						8		21	1					5					22	6
32 Application.Services.Payment				4			1	6						2	6						16						8
33 Infrastructure.Services	2			2	1			20						2	6	9					9				1		7
34 Infrastructure.Services.Admin	11					4	1	1			2			4	2	5					3					9
35 Storefront.Services			7	3					1									1	5				4		1			17
36 Web.Services									2	5								3				6	1						5
37 Web.Shared.Services									8	5								36	8				3	8					23
38 API.Controllers	11	3	10	2							2	8	1	4	2		2			5	7				15	5	4			1
39 Web.Pages.Admin									8									3	4				4	1					8			2
40 Web.Pages.Public																			1			1	1	1								1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 63% · Adequate ·

The Good

D1 · .NET / C# Cyclomatic Complexity 8.6 D2 · .NET / C# Cognitive Complexity 8.2 D3 · .NET / C# God Classes 9.0 D4 · .NET / C# Code Duplication 8.8 D17 · .NET / C# Explicit Debt 8.7 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 9.8 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.1 X1 · Repo Async correctness 7.9 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 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 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X5 · Repo Nullable reference types 9.6

The Bad

X18 · Repo Disposal-pattern correctness 6.7 X2 · Repo Cancellation propagation 5.3 X3 · Repo Exception handling 5.4

The Ugly

X4 · Repo Structured logging 4.9

At a glance — Architecture · 80% · Strong ·

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 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 AX8 · Repo Test isolation 10.0

The Bad

D26 · .NET / C# Project Cohesion 5.4 D27 · .NET / C# Navigability 6.6

The Ugly

AX10 · Repo Code composition 4.0

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

The Good

D15 · .NET / C# Churn × Complexity Hotspots 9.9 D19 · .NET / C# Documentation Quality 10.0 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 7.9 D34 · .NET / C# Knowledge Freshness 10.0 M1 · Repo Documentation (README) 8.0 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 8.0

The Ugly

D20 · .NET / C# ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 33% · Weak · gated by P3, P5, P7 ·

The Good

D9 · .NET / C# Test Distribution 8.4 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D12 · .NET / C# Dependency Hygiene 7.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.2 P4 · Repo Deployment & Rollback 8.0 P8 · Repo Schema migrations 10.0

The Bad

D13 · .NET / C# REDACTED Scanning 5.0 P6 · Repo Release Hygiene 5.0

The Ugly

P3 · Repo Security & performance tooling 0.0 P5 · Repo DR & Backup 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 66% · Adequate · gated by D29, D36, C1 ·

The Good

D28 · .NET / C# Secrets (history) 9.0 D30 · .NET / C# Dependency Vulnerabilities 7.1 D31 · .NET / C# IaC & Container Security 8.2 D37 · .NET / C# Vulnerability-disclosure Policy 10.0 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 C3 · Repo Audit Trail 7.5 C4 · Repo Data Retention 10.0 S1 · Repo Web-Security Posture 8.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

The Ugly

D29 · .NET / C# Static Analysis (SAST) 1.3 D36 · .NET / C# Supply-chain Provenance & Signing 2.5 C1 · Repo Data Protection 3.0 X24 · Repo Document value interpolated into markup unescaped 4.1

At a glance — Accessibility · 41% · Weak · gated by AC4 ·

The Good

AC5 · Repo ARIA correctness 10.0

The Bad

AC1 · Repo Text alternatives 5.1 AC2 · Repo Forms & labels 5.1 AC3 · Repo Page structure 5.7

The Ugly

AC4 · Repo Keyboard semantics 1.6 AC6 · Repo Visual & motion safety 4.6 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 71% · Strong ·

The Good

PF3 · Repo Async & latency hygiene 10.0

The Bad

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

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
A05:2025 — Injection	56	High / Critical
A03:2025 — Software Supply Chain Failures	13	High / Critical
A02:2025 — Security Misconfiguration	13	High / Critical
A07:2025 — Authentication Failures	3	High / Critical

Roadmap

Immediately resolve the leaked secret in REDACTED and update deprecated dependencies in the web, test, and E2E projects to restore baseline hygiene. Integrate automated security scanning into the CI pipeline to prevent regressions, while codifying disaster recovery procedures with clear RTO and RPO documentation. Finally, improve accessibility by ensuring custom controls are fully keyboard-operable and anchors have valid hrefs.

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

Do this	Helps	Effort	Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.	+7.8 pts	Low	REDACTED Scanning
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with BlazorShop.Web.csproj, BlazorShop.Tests.csproj, BlazorShop.E2E.csproj.	+6.1 pts	Low	Dependency Hygiene
Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED.	+2.7 pts	Low	Dependency Hygiene
Resolve the 1 Inverted test pyramid finding(s) in Test Distribution.	+2.4 pts	Low	Test Distribution
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.	+4.7 pts	Medium	Security & performance tooling
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.	+4.7 pts	Medium	DR & Backup
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.	+3.1 pts	Medium	Keyboard semantics
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.	+3.0 pts	Medium	Outbound HTTP resilience

File quality

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

File	Score	Band	Worst signal
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.5	Slop	Dependency Vulnerabilities: High CVE: REDACTED
BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs	3.0	Slop	Explicit Debt: EmptyCatchBlock
REDACTED	3.0	Slop	Static Analysis (SAST): High: 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.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
BlazorShop.Infrastructure/Services/OrderTrackingService.cs	5.4	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	5.9	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	5.9	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.1	Mixed	Static Analysis (SAST): Medium: REDACTED
BlazorShop.Presentation/BlazorShop.Web/Layout/AccountLayout.razor	6.1	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	6.3	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.3	Mixed	Static Analysis (SAST): Medium: REDACTED
BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs	6.4	Mixed	Explicit Debt: EmptyCatchBlock
BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs	6.4	Mixed	Explicit Debt: Dead code: HomePage_Returns200WithExpectedCanonicalAndStructuredData
BlazorShop.Presentation/BlazorShop.Web.Shared/Toast/ToastBuilder.cs	6.6	Mixed	Explicit Debt: Dead code: WithIcon
BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs	6.7	Mixed	Explicit Debt: Dead code: GetAllowedFulfillmentStatuses

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 — 104

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 — 293

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 — 148

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

Could not be resolved — 2

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. 89 of 94 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.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 — 94 dimensions across the health lenses

D1D2D3D4D5D6D9D10D11D12D13D14D15D17D18D19D20D21D24D26D27D28D29D30D31D34D35D36D37D39D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8C1C2C3C4GD1IC1M1M2M3M4P1P2P3P4P5P6P7P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 474 of 545 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 01a16273-0eeb-794e-89bf-160d2582b9e7.

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.

D12 Dependency Hygiene — 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. This repository declares npm dependencies as well as NuGet ones — manifest: BlazorShop.Presentation/BlazorShop.Web/package.json — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read it, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
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 489 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 (27,352 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"]`.
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. `BlazorShop.Application/Services/MetricsService.cs`, `BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs`, `BlazorShop.Infrastructure/Repositories/Newsletters/NewsletterSubscriberRepository.cs`, `BlazorShop.Presentation/BlazorShop.API/Controllers/MetricsController.cs`, `BlazorShop.Presentation/BlazorShop.Storefront/Program.cs`, … (+3 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.
AC2 Forms & labels — 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. 60 further occurrence(s) are not listed individually; the score already reflects all 100.
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 (REDACTED). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
X2 Cancellation propagation — 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. 327 further occurrence(s) are not listed individually; the score already reflects all 367.

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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED 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.
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.
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A 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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
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.
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.
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 (5): D19, D21, D24, D26, 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 Complexity8.6 / 10Strong✓ 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 8.6 / 10 · rule-coverage 100% · ceiling Prevented

7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Program.Main at 34. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ProductRecommendationRepository.GetFrequentlyBoughtTogetherAsync at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs (ProductRecommendationRepository.GetFrequentlyBoughtTogetherAsync at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

Program.Main (cyclomatic 34)BlazorShop.Presentation/BlazorShop.API/Program.cs:40

CheckoutOrchestrator.InitializeStripeAsync (cyclomatic 29)BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:309

InventoryReservationTransitionOperation.ApplyAsync (cyclomatic 29)BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:12

InventoryReservationService.CreateOrderWithInventoryAsync (cyclomatic 27)BlazorShop.Infrastructure/Services/InventoryReservationService.cs:39

OrderTrackingService.TransitionFulfillmentAsync (cyclomatic 27)BlazorShop.Infrastructure/Services/OrderTrackingService.cs:86

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

What to do

Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Program.Main (cyclomatic 34), CheckoutOrchestrator.InitializeStripeAsync (cyclomatic 29), InventoryReservationTransitionOperation.ApplyAsync (cyclomatic 29). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity8.2 / 10Strong✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Prevented

10 method(s) exceeded the cognitive complexity threshold of 15; the worst was InventoryReservationService.CreateOrderWithInventoryAsync at 40.

InventoryReservationService.CreateOrderWithInventoryAsync (cognitive 40)BlazorShop.Infrastructure/Services/InventoryReservationService.cs:39

InventoryReservationTransitionOperation.ApplyAsync (cognitive 33)BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:12

CheckoutOrchestrator.InitializeStripeAsync (cognitive 32)BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:309

OrderTrackingService.TransitionFulfillmentAsync (cognitive 30)BlazorShop.Infrastructure/Services/OrderTrackingService.cs:86

Program.Main (cognitive 30)BlazorShop.Presentation/BlazorShop.API/Program.cs:40

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

What to do

Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with InventoryReservationService.CreateOrderWithInventoryAsync (cognitive 40), InventoryReservationTransitionOperation.ApplyAsync (cognitive 33), CheckoutOrchestrator.InitializeStripeAsync (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.0 / 10Strong✓ Tool-verified

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

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

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

8 god class(es) detected.

MethodTooLong: DevelopmentCatalogSeeder.SeedAsync · ×5BlazorShop.Infrastructure/Data/DevelopmentCatalogSeeder.cs:9

ClassTooLong: CheckoutOrchestratorBlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs

FileTooLong: Payment/CheckoutOrchestrator.csBlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs

TooManyMethods: ProductsBlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs

What to do

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

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

Do you agree with this assessment?

D4 · Code Duplication8.8 / 10Strong✓ 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 8.8 / 10 · rule-coverage 100% · ceiling Verified

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

Duplicated block (9 lines × 2) · ×6BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminAuditService.cs:57

Duplicated block (11 lines × 2) · ×5BlazorShop.Infrastructure/Services/InventoryReservationService.cs:185

Duplicated block (8 lines × 2) · ×5BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/NumberInput.cs:13

Duplicated block (21 lines × 2) · ×4BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:150

Duplicated block (15 lines × 2) · ×4BlazorShop.Infrastructure/Services/Admin/AdminAuditService.cs:60

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

What to do

Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AdminAuditService.cs, CheckoutIntentCanonicalizer.cs, SeoFieldsDto.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with InventoryReservationService.cs, StorefrontApiClient.cs, AdminInventoryQueryDto.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with NumberInput.cs, ProductInventoryTopologyRepository.cs, InventoryReservationService.cs. — One of this dimension's main actionable groups (5 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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

0 of 105 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution8.4 / 10Strong✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Documented

589 test methods: 0 unit, 585 integration, 0 BDD, 4 e2e.

Inverted test pyramid

What to do

Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

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 / 10Stronggated by 1 serious finding✓ 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, 1 zero-assertion, 1 mock references across 589 tests.

No assertions: SendEmailAsync_WhenDeliveryIsDisabled_CompletesWithoutConnectingBlazorShop.Tests/Infrastructure/Services/EmailServiceTests.cs:15

Mock-dominated test: HandleAuthSessionEventAsync_WhenSignedIn_RefreshesWithoutClearing · ×2BlazorShop.Tests/Presentation/Authentication/AuthenticationSessionSyncServiceTests.cs:16

Mock framework: Moq

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene7.0 / 10Strong✓ Tool-verified

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

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

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

46 outdated, 0 vulnerable, 2 deprecated packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.

Deprecated: Blazored.Typeahead · ×3BlazorShop.Presentation/BlazorShop.Web/BlazorShop.Web.csproj:10

Outdated: Stripe.netREDACTED:24

Deprecated: globREDACTED:598

Outdated: Microsoft.Extensions.Identity.Stores · ×45

What to do

Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with BlazorShop.Web.csproj, BlazorShop.Tests.csproj, BlazorShop.E2E.csproj. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D13 · REDACTED Scanning5.0 / 10Adequate✓ 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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED 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 259 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 51 direct `PackageReference`(s), and 199 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 Hotspots9.9 / 10Stronggated by 3 serious findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: BlazorShop.Presentation/BlazorShop.API/Program.cs (3×34=102); BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs (3×29=87); BlazorShop.Infrastructure/Services/InventoryReservationService.cs (3×27=81)

Hotspot: BlazorShop.Presentation/BlazorShop.API/Program.cs · ×3BlazorShop.Presentation/BlazorShop.API/Program.cs:40

What to do

Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with Program.cs, CheckoutOrchestrator.cs, InventoryReservationService.cs. — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

D17 · Explicit Debt8.7 / 10Adequategated by 13 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 8.7 / 10 · rule-coverage 100% · ceiling Prevented

15 deducted debt markers + 24 dead symbols across 27352 LoC in the .NET projects (0.7/KLoC) → score 8.7.

EmptyCatchBlock · ×12BlazorShop.Application/Services/NewsletterService.cs:53

WriteOnlyPrivateFieldBlazorShop.Infrastructure/Services/Admin/AdminUserService.cs:22

Dead code: GetUserClaimsFromToken · ×24BlazorShop.Domain/Contracts/Authentication/IAppTokenManager.cs:13

CommentedOutCode · ×2REDACTED.cs:83

What to do

Resolve the 12 EmptyCatchBlock finding(s) in Explicit Debt — start with HeaderBoxComponent.razor.cs (2), NewsletterService.cs, OrderTrackingService.cs. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AdminUserService.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 24 Dead code finding(s) in Explicit Debt — start with StorefrontSeoSmokeTests.cs (8), ToastBuilder.cs (4), DemoRequestContext.cs (2). — One of this dimension's main actionable groups (24 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

11 projects, 681 source files, 47422 hand-written lines of code (27352 production / 20070 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), plus 12253 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 19 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

BlazorShop's documentation is comprehensive: the root README (2319 words) gives a clear overview of what the project is, its technologies, requirements, and an exhaustive table of contents covering Introduction, Who Is It For?, Project Status, Features, Current Limitations, Technologies Used, Requirements, Getting Started, Browser E2E Tests, Demo, License, Acknowledgements, plus a dedicated BlazorShop v2 UI Template README (612 words) that documents the visual source of truth for the redesign and its route coverage, Art direction, review entry point, and an isolated end-to-end test suite (496 words), plus a dependency-security verification doc (dependency-security.md; 426 words) covering npm baseline findings, audit results, and CI policy. The repository also contains a staging-upgrade-rehearsal runbook (1033 words) that pins historical application baselines to upgrade targets and exercises the checkout-to-archive path, plus About.html and account-notifications.html for UI detail. All these documents are well-structured with headings and an outline; none is clipped. (14 of 25 sampled documents could not be assessed: 1 of 2 evaluation groups failed.)

XML-doc coverage: BlazorShop.Domain · ×8BlazorShop.Domain/BlazorShop.Domain.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 Quality0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming 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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D24 · Comment ValueStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

42 valuable / 0 redundant across 200 sampled comments.

What to do

Improve Comment Value — currently 7.9/10. — 42 valuable / 0 redundant across 200 sampled comments.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion5.4 / 10Adequate✓ 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 5.4 / 10 · rule-coverage 100% · ceiling Documented

3 of 12 projects flagged as possibly oversized/incoherent.

Split BlazorShop.Infrastructure

What to do

Resolve the 1 Split BlazorShop.Infrastructure finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D27 · Navigability6.6 / 10Adequate✓ 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 6.6 / 10 · rule-coverage 100% · ceiling Documented

72 % of calls cross a namespace and 34 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.

High interface indirection

Pass-through layerBlazorShop.Infrastructure/Services/LoggerAdapter.cs:7

What to do

Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Pass-through layer finding(s) in Navigability — start with LoggerAdapter.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

Method: REDACTED 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 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 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 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)1.3 / 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 1.3 / 10 · rule-coverage 100% · ceiling Documented

56 finding(s): 0 critical, 22 high, 32 medium, 2 low. 20 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 27 file(s) — `BlazorShop.Application/Services/MetricsService.cs` (line 11, line 12, line 14, …), `BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs` (line 575, line 1248), `BlazorShop.E2E/StorefrontCheckoutTests.cs` (line 10), `BlazorShop.Infrastructure/Repositories/Newsletters/NewsletterSubscriberRepository.cs` (lines 12–13, line 25), `BlazorShop.Presentation/BlazorShop.API/Controllers/MetricsController.cs` (lines 12–13, line 77), … (+22 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 5 of those file(s) — `BlazorShop.Application/Services/MetricsService.cs`, `BlazorShop.E2E/StorefrontCheckoutTests.cs`, `BlazorShop.Infrastructure/Repositories/Newsletters/NewsletterSubscriberRepository.cs`, `BlazorShop.Presentation/BlazorShop.API/Controllers/MetricsController.cs`, `BlazorShop.Presentation/BlazorShop.Web.Shared/Services/MetricsClient.cs` — 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) — `BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontStructuredDataComposer.cs`, `BlazorShop.Tests/Presentation/Storefront/StorefrontInternalLinkQaTests.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 1 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

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

What to do

Resolve the 23 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 20 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 (20 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 Vulnerabilities7.1 / 10Adequategated by 4 critical findings✓ Tool-verified

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 7.1 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 4 high, 2 medium, 0 low.

REDACTED

What to do

Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security8.2 / 10Adequategated by 3 critical findings✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Documented

13 finding(s): 0 critical, 3 high, 7 medium, 3 low.

REDACTED

What to do

Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 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 118 of the 529 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

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

What to do

Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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?

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

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

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

15 of 1967 first-party methods have an oversized IL body.

IL efficiency: 15 authored method(s) exceed the IL budgetBlazorShop.Application/Mapping/MappingConfig.cs:18

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

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

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

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

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor:29, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor:22
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:128, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:141

What to do

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

Do you agree with this assessment?

AC2 · Forms & labels5.1 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, 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.

This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×13) — BlazorShop.Presentation/BlazorShop.Web/Components/Header/SearchBarComponent.razor:8, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:14, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:15, …
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×16) — BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:6, BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:12, BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:17, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×11) — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:95, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:97, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:98, …

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure5.7 / 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.

A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). (×10) — BlazorShop.Presentation/BlazorShop.Web/Authentication/Components/Login.razor:4, BlazorShop.Presentation/BlazorShop.Web/Authentication/Components/Register.razor:3, BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:3, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×9) — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:82, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor:78, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:348, …

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?

AC4 · Keyboard semantics1.6 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor:2
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor:28, BlazorShop.Presentation/BlazorShop.Web/Components/ProductRecommendations.razor:10
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — BlazorShop.Presentation/BlazorShop.Web/Components/Shared/ModalDialog.razor:3
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. (×2) — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor:10, BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Banner.razor:4
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/index.html:63

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

Do you agree with this assessment?

AC6 · Visual & motion safety4.6 / 10Weak✓ 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.

<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor:95, BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:13
<div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — 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:. — BlazorShop.Presentation/BlazorShop.Web/App.razor:10
<select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:23, BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:38
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. — BlazorShop.Presentation/BlazorShop.Web/Pages/Account/Notifications.razor:47
<svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — 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:. — BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/Cart.razor:0
`.search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/ui-v2/styles.css:24
`.product-card` moves (`transition: transform .18s ease,box-shadow .18s ease,border-color .18s ease`) 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. — docs/ui-v2/polish.css:9
`.product-image img` moves (`transition: transform .25s ease`) 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. — docs/ui-v2/polish.css:9
`.skeleton` moves (`animation: pulse 1.5s infinite`) 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. — docs/ui-v2/styles.css:33
`#blazor-error-ui .error-content` moves (`animation: error-pop 200ms ease-out both`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:46
`.spinner` moves (`animation: spinner-rotate 1.1s linear infinite`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:135
`.custom-toast` moves (`animation: toast-in 180ms ease-out forwards`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:241
`.custom-toast::after` moves (`animation: toast-progress 5s linear forwards`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:262
`.sk-circle .sk-child:before` moves (`animation: sk-circleBounceDelay 1.2s infinite ease-in-out both`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:455
`.bs-card-link` moves (`transition: transform 180ms ease, box-shadow 180ms ease, border-color 180ms ease`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/input.css:506
`.bs-pill-link` moves (`transition: background-color 180ms ease, border-color 180ms ease, color 180ms ease, box-shadow 180ms ease, transform 180ms ease`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/input.css:536
`.animate-spin` moves (`animation: spin 1s linear infinite`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1
`.transition` moves (`transition-property: color,background-color,border-color,text-decoration-color,fill,stroke,opacity,box-shadow,transform,filter,backdrop-filter`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1
`.transition-transform` moves (`transition-property: transform`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1
`.bs-card-link` moves (`transition: transform .18s ease,box-shadow .18s ease,border-color .18s ease`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1
`.bs-pill-link` moves (`transition: background-color .18s ease,border-color .18s ease,color .18s ease,box-shadow .18s ease,transform .18s ease`) 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. — BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1
`.deal-card` moves (`transition: transform 0.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. — BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.css:12
`.fade-slide` moves (`animation: fadeSlideIn 450ms ease-in-out`) 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. — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.css:3
`.modal.fade .modal-dialog` moves (`transition: transform 0.3s ease-out`) 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. — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/ProductDetails.razor.css:28
`.product-image img` moves (`transition: transform 0.3s ease-in-out`) 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. — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/ProductDetails.razor.css:44
`.bs-toast-card` moves (`animation: bs-toast-in 180ms ease-out forwards`) 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.css:44

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 a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 85 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 toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.

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 BlazorShop.Application.DTOs.Category ↔ BlazorShop.Application.DTOs.Product depend on each other. The lightest dependency in the cycle is BlazorShop.Application.DTOs.Product → BlazorShop.Application.DTOs.Category (BlazorShop.Application.DTOs.Product.GetProduct → BlazorShop.Application.DTOs.Category.GetCategory, 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. — BlazorShop.Application/DTOs/Product/GetProduct.cs:5
The namespaces BlazorShop.Web.Shared.Models.Category ↔ BlazorShop.Web.Shared.Models.Product depend on each other. The lightest dependency in the cycle is BlazorShop.Web.Shared.Models.Product → BlazorShop.Web.Shared.Models.Category (BlazorShop.Web.Shared.Models.Product.GetProduct → BlazorShop.Web.Shared.Models.Category.GetCategory, 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. — BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:5
The namespaces BlazorShop.Storefront.Services ↔ BlazorShop.Storefront.Services.Contracts depend on each other. The lightest dependency in the cycle is BlazorShop.Storefront.Services.Contracts → BlazorShop.Storefront.Services (BlazorShop.Storefront.Services.Contracts.IStorefrontSitemapService → BlazorShop.Storefront.Services.StorefrontSitemapGenerationResult, 3 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. — BlazorShop.Presentation/BlazorShop.Storefront/Services/Contracts/IStorefrontSitemapService.cs:3
The namespaces BlazorShop.Web.Services ↔ BlazorShop.Web.Services.Contracts depend on each other. The lightest dependency in the cycle is BlazorShop.Web.Services.Contracts → BlazorShop.Web.Services (BlazorShop.Web.Services.Contracts.IStorefrontSeoMetadataBuilder → BlazorShop.Web.Services.StorefrontSeoMetadata, 4 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. — BlazorShop.Presentation/BlazorShop.Web/Services/Contracts/IStorefrontSeoMetadataBuilder.cs:3

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?

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

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

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

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

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

Other · Security — Whether access is authorized by default — 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 Trail7.5 / 10Strong✓ 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.

An audit mechanism is present, but the trail is not yet complete — missing: an EF SaveChanges interceptor (or equivalent write-side hook, e.g. an event-store append every change flows through), [Audited] per-entity coverage.

What to do

Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.

Do you agree with this assessment?

C4 · Data Retention10.0 / 10Exemplary✓ 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.

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 & stubs8.1 / 10Strong✓ Tool-verified

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

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, 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.

`CaptureAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — BlazorShop.Infrastructure/Services/PayPalPaymentService.cs:13
`GetTextColor` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — BlazorShop.Presentation/BlazorShop.Web/Components/Templates/Styles.cs:12
`GetTableFormat` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — BlazorShop.Presentation/BlazorShop.Web/Components/Templates/Styles.cs:13
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — BlazorShop.Application/Mapping/MappingConfig.cs:20

What to do

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

Do you agree with this assessment?

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure8.0 / 10Strong✓ 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.

Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

What to do

Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.

Do you agree with this assessment?

M4 · Documentation accuracy8.0 / 10Strong◐ 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.

docs/production-runbook.md links to `REDACTED`, but `docs/REDACTED` 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. — docs/production-runbook.md:177

What to do

Reconcile the README with reality: docs/production-runbook.md links to `REDACTED`, but `docs/REDACTED` does not exist.

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.2 / 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 6/8 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 8, 3 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 tooling0.0 / 10Critical✓ 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.

No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 15855 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ 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.

Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

Add an approval/environment gate (required reviewers / protection rules) before production promotion.

Do you agree with this assessment?

P5 · DR & Backup0.0 / 10Critical✓ 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.

A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

What to do

Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ 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.

No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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.

`new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — BlazorShop.Presentation/BlazorShop.Web/Program.cs:33
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — BlazorShop.Presentation/BlazorShop.Web/Program.cs:110

What to do

Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.

Do you agree with this assessment?

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

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

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; 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.

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.4 / 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 28 use(s) across 39,846 production line(s) (~0.7/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 Posture8.5 / 10Strong✓ 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: X-Content-Type-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options — 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. (−1.5 on this card.) — BlazorShop.Presentation/BlazorShop.API/Program.cs:418

What to do

Add Content-Security-Policy, Strict-Transport-Security, X-Frame-Options 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.9 / 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.

`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — REDACTED.cs:15

What to do

async void method: ShowToast

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

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.

`cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `SendEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw. — BlazorShop.Infrastructure/Services/EmailService.cs:44

What to do

Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.

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 propagation5.3 / 10Adequate✓ 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 103/469 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. (×39) — BlazorShop.Application/Services/Authentication/AuthenticationService.cs:62, BlazorShop.Application/Services/Authentication/AuthenticationService.cs:129, BlazorShop.Application/Services/Authentication/AuthenticationService.cs:190, …

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 unescaped4.1 / 10Weak✓ Tool-verified

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.

`Document.ToJson()` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — BlazorShop.Presentation/BlazorShop.Storefront/Components/Seo/JsonLdScript.razor:3
`title` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — BlazorShop.Presentation/BlazorShop.Storefront/Program.cs:86
`heading` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — BlazorShop.Presentation/BlazorShop.Storefront/Program.cs:90
`message` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — BlazorShop.Presentation/BlazorShop.Storefront/Program.cs:91
`toast.Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — REDACTED:18, REDACTED:46, REDACTED:74, …
`val.html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1523

What to do

Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.

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 handling5.4 / 10Adequate✓ Tool-verified

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.

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — BlazorShop.Application/Services/NewsletterService.cs:53, BlazorShop.Infrastructure/Services/OrderTrackingService.cs:203, BlazorShop.Presentation/BlazorShop.Web/Authentication/Providers/AuthenticationSessionEventPublisher.cs:47, …
`catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — BlazorShop.Infrastructure/Services/StripePaymentStateTransitionService.cs:239
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×2) — BlazorShop.Presentation/BlazorShop.Web/Authentication/Providers/AuthenticationSessionSyncService.cs:73, BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:134
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:91, BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:116, BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:257

What to do

Swallowed exception (empty catch)

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 logging4.9 / 10Weak✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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.

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×18) — BlazorShop.Application/Services/Authentication/AuthenticationService.cs:115, BlazorShop.Application/Services/Authentication/AuthenticationService.cs:276, BlazorShop.Application/Services/Authentication/AuthenticationService.cs:353, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types9.6 / 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.5 `!` suppressions per 1k syntax nodes — 118 suppression(s) across the 218364 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 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	63%	Adequate	Acceptable, with room to improve.
Architecture	80%	Strong	Strongest area.
Maturity	62%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	33%	Weak — gated by P3, P5, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	66%	Adequate — gated by D29, D36, C1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	41%	Weak — gated by AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	71%	Strong	Solid.

Unscored — 4 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.

P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 24 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 — 22 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — 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.
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.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 value object(s); a Domain/Aggregates/ValueObjects layer
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 29 integration event(s); 1 event handler(s)
ED5 Idempotency — 1 mutating command handler(s)/consumer(s) detected and 1 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X8 JS interop contract — 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 — 104 finding(s)

AC2 · Forms & labels · <input> without a programmatic label · ×20

<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Components/Header/SearchBarComponent.razor:8 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:14 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:15 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:16 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:95 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:97 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:211 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:215 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:219 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:353 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:354 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:355 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Inventory.razor:14 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Inventory.razor:17 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Inventory.razor:109 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Inventory.razor:123 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:14 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:167 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:169 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:173 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.

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

AC2 · Forms & labels · <label> that labels no control · ×16

<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:6 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:12 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:17 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:22 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:27 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:32 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:37 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Components/Seo/SeoFieldsEditor.razor:68 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Account/Settings.razor:29 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Account/Settings.razor:34 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Account/Settings.razor:39 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor:113 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:198 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:210 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:214 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:218 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.

D17 · Explicit Debt · EmptyCatchBlock · ×12

EmptyCatchBlock BlazorShop.Application/Services/NewsletterService.cs:53 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Infrastructure/Services/OrderTrackingService.cs:203 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AuthenticationService.cs:147 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Authentication/Providers/AuthenticationSessionEventPublisher.cs:47 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Authentication/Providers/AuthenticationSessionSyncService.cs:73 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:74 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:134 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:107 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Layout/MainLayout.razor:173 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Layout/AccountLayout.razor:118 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Banner.razor:152 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor:49 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.

AC3 · Page structure · Routed page without a <PageTitle> · ×10

Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Authentication/Components/Login.razor:4 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Authentication/Components/Register.razor:3 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:3 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor:4 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:5 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor:3 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Seo.razor:4 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/CancelPayment.razor:3 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/Cart.razor:5 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/SuccessPayment.razor:4 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).

AC2 · Forms & labels · <select> without a programmatic label · ×4

<select> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:98 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:199 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:356 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:176 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

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

Namespace dependency cycle BlazorShop.Application/DTOs/Product/GetProduct.cs:5 — The namespaces BlazorShop.Application.DTOs.Category ↔ BlazorShop.Application.DTOs.Product depend on each other. The lightest dependency in the cycle is BlazorShop.Application.DTOs.Product → BlazorShop.Application.DTOs.Category (BlazorShop.Application.DTOs.Product.GetProduct → BlazorShop.Application.DTOs.Category.GetCategory, 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 BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:5 — The namespaces BlazorShop.Web.Shared.Models.Category ↔ BlazorShop.Web.Shared.Models.Product depend on each other. The lightest dependency in the cycle is BlazorShop.Web.Shared.Models.Product → BlazorShop.Web.Shared.Models.Category (BlazorShop.Web.Shared.Models.Product.GetProduct → BlazorShop.Web.Shared.Models.Category.GetCategory, 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 BlazorShop.Presentation/BlazorShop.Storefront/Services/Contracts/IStorefrontSitemapService.cs:3 — The namespaces BlazorShop.Storefront.Services ↔ BlazorShop.Storefront.Services.Contracts depend on each other. The lightest dependency in the cycle is BlazorShop.Storefront.Services.Contracts → BlazorShop.Storefront.Services (BlazorShop.Storefront.Services.Contracts.IStorefrontSitemapService → BlazorShop.Storefront.Services.StorefrontSitemapGenerationResult, 3 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 BlazorShop.Presentation/BlazorShop.Web/Services/Contracts/IStorefrontSeoMetadataBuilder.cs:3 — The namespaces BlazorShop.Web.Services ↔ BlazorShop.Web.Services.Contracts depend on each other. The lightest dependency in the cycle is BlazorShop.Web.Services.Contracts → BlazorShop.Web.Services (BlazorShop.Web.Services.Contracts.IStorefrontSeoMetadataBuilder → BlazorShop.Web.Services.StorefrontSeoMetadata, 4 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.

D30 · Dependency Vulnerabilities · High CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

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

REDACTED
REDACTED
REDACTED

AC1 · Text alternatives · <img> without a text alternative · ×2

<img> without a text alternative BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor:29 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor:22 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.

AC4 · Keyboard semantics · Hover-only interaction on <div> · ×2

Hover-only interaction on <div> BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor:10 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Hover-only interaction on <div> BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Banner.razor:4 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×1

Click handler on a non-interactive <span> BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor:28 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.

AC4 · Keyboard semantics · Click handler on a non-interactive <article> · ×1

Click handler on a non-interactive <article> BlazorShop.Presentation/BlazorShop.Web/Components/ProductRecommendations.razor:10 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.

D13 · REDACTED Scanning · Leaked secret · ×1

REDACTED

D17 · Explicit Debt · WriteOnlyPrivateField · ×1

WriteOnlyPrivateField BlazorShop.Infrastructure/Services/Admin/AdminUserService.cs:22 — private AppDbContext _db — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.

D28 · Secrets (history) · REDACTED · ×1

REDACTED

Serious — 293 finding(s)

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

Async method without CancellationToken: CreateUser BlazorShop.Application/Services/Authentication/AuthenticationService.cs:62 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoginUser BlazorShop.Application/Services/Authentication/AuthenticationService.cs:129 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReviveToken BlazorShop.Application/Services/Authentication/AuthenticationService.cs:190 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Logout BlazorShop.Application/Services/Authentication/AuthenticationService.cs:243 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ChangePassword BlazorShop.Application/Services/Authentication/AuthenticationService.cs:254 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckPasswordAsync BlazorShop.Application/Services/Authentication/AuthenticationService.cs:281 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConfirmEmail BlazorShop.Application/Services/Authentication/AuthenticationService.cs:286 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendConfirmationEmail BlazorShop.Application/Services/Authentication/AuthenticationService.cs:303 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateProfile BlazorShop.Application/Services/Authentication/AuthenticationService.cs:308 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateConfirmationRequiredResponseAsync BlazorShop.Application/Services/Authentication/AuthenticationService.cs:341 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: TryConfirmUserForNonStrictRegistrationAsync BlazorShop.Application/Services/Authentication/AuthenticationService.cs:362 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RollbackCreatedUserAsync BlazorShop.Application/Services/Authentication/AuthenticationService.cs:384 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetByCategoryIdAsync BlazorShop.Application/Services/CategorySeoService.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync BlazorShop.Application/Services/CategorySeoService.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LogAsync BlazorShop.Application/Services/CategorySeoService.cs:173 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: EnsureRedirectAsync BlazorShop.Application/Services/CategorySeoService.cs:190 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync BlazorShop.Application/Services/CategoryService.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetByIdAsync BlazorShop.Application/Services/CategoryService.cs:38 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddAsync BlazorShop.Application/Services/CategoryService.cs:44 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync BlazorShop.Application/Services/CategoryService.cs:58 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync BlazorShop.Application/Services/CategoryService.cs:79 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetProductsByCategoryAsync BlazorShop.Application/Services/CategoryService.cs:93 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LogAsync BlazorShop.Application/Services/CategoryService.cs:99 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetSalesAsync BlazorShop.Application/Services/MetricsService.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetTrafficAsync BlazorShop.Application/Services/MetricsService.cs:27 — No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.

D17 · Explicit Debt · Dead code · ×24

Dead code: GetUserClaimsFromToken BlazorShop.Domain/Contracts/Authentication/IAppTokenManager.cs:13 — Method GetUserClaimsFromToken — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.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: GetRecentlyViewedProductsAsync BlazorShop.Domain/Contracts/IProductRecommendationRepository.cs:11 — Method GetRecentlyViewedProductsAsync — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.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: GetByReferenceAsync BlazorShop.Domain/Contracts/Payment/IOrderRepository.cs:11 — Method GetByReferenceAsync — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.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: FromMinorUnits BlazorShop.Application/Services/Payment/CurrencyMoney.cs:51 — Method FromMinorUnits — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.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: Capture BlazorShop.Infrastructure/Demo/DemoRequestContext.cs:34 — Method Capture — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Infrastructure, 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: Restore BlazorShop.Infrastructure/Demo/DemoRequestContext.cs:39 — Method Restore — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Infrastructure, 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: GetAllowedFulfillmentStatuses BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:177 — Method GetAllowedFulfillmentStatuses — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web, 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: ToggleCategories BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:36 — Method ToggleCategories — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web, 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: SubscribeResponse BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Newsletter/NewsletterModels.cs:5 — NamedType SubscribeResponse — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web.Shared, 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: WithIcon BlazorShop.Presentation/BlazorShop.Web.Shared/Toast/ToastBuilder.cs:15 — Method WithIcon — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web.Shared, 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: WithPosition BlazorShop.Presentation/BlazorShop.Web.Shared/Toast/ToastBuilder.cs:21 — Method WithPosition — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web.Shared, 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: Persisting BlazorShop.Presentation/BlazorShop.Web.Shared/Toast/ToastBuilder.cs:27 — Method Persisting — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web.Shared, 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: WithDuration BlazorShop.Presentation/BlazorShop.Web.Shared/Toast/ToastBuilder.cs:33 — Method WithDuration — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web.Shared, 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: ToastPositions BlazorShop.Presentation/BlazorShop.Web.Shared/Toast/ToastPositions.cs:3 — NamedType ToastPositions — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Web.Shared, 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: RegisterLoginRefreshAndLogout_RoundTrip_Succeeds BlazorShop.Tests/Presentation/Authentication/AuthSmokeTests.cs:14 — Method RegisterLoginRefreshAndLogout_RoundTrip_Succeeds — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: CheckoutHandoff_FollowsAuthenticationState BlazorShop.Tests/Presentation/Authentication/AuthSmokeTests.cs:44 — Method CheckoutHandoff_FollowsAuthenticationState — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: HomePage_Returns200WithExpectedCanonicalAndStructuredData BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:10 — Method HomePage_Returns200WithExpectedCanonicalAndStructuredData — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: StaticInformationalPage_Returns200WithExpectedCanonicalAndStructuredData BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:26 — Method StaticInformationalPage_Returns200WithExpectedCanonicalAndStructuredData — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: CategoryPage_Returns200WithExpectedCanonicalAndStructuredData BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:41 — Method CategoryPage_Returns200WithExpectedCanonicalAndStructuredData — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: ProductPage_Returns200WithExpectedCanonicalAndStructuredData BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:57 — Method ProductPage_Returns200WithExpectedCanonicalAndStructuredData — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: MissingRoute_Returns404WithoutCanonicalAndWithNoindexProtection BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:74 — Method MissingRoute_Returns404WithoutCanonicalAndWithNoindexProtection — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: Sitemap_ReturnsXmlAndContainsCriticalRoutes BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:85 — Method Sitemap_ReturnsXmlAndContainsCriticalRoutes — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: RobotsTxt_IsAvailableAndReferencesSitemap BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:102 — Method RobotsTxt_IsAvailableAndReferencesSitemap — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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: RedirectSource_ReturnsExpectedSingleHopCanonicalTarget BlazorShop.Tests/Presentation/Storefront/StorefrontSeoSmokeTests.cs:116 — Method RedirectSource_ReturnsExpectedSingleHopCanonicalTarget — Roslyn's SymbolFinder walked every project the solution loads, including BlazorShop.Tests, 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.

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

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

Animation without a prefers-reduced-motion guard BlazorShop.Presentation/BlazorShop.Web/App.razor:10 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — 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:.
Animation without a prefers-reduced-motion guard BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/Cart.razor — <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — 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:.
Animation without a prefers-reduced-motion guard docs/ui-v2/polish.css:9 — `.product-card` moves (`transition: transform .18s ease,box-shadow .18s ease,border-color .18s ease`) 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 docs/ui-v2/polish.css:9 — `.product-image img` moves (`transition: transform .25s ease`) 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 docs/ui-v2/styles.css:33 — `.skeleton` moves (`animation: pulse 1.5s infinite`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:46 — `#blazor-error-ui .error-content` moves (`animation: error-pop 200ms ease-out both`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:135 — `.spinner` moves (`animation: spinner-rotate 1.1s linear infinite`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:241 — `.custom-toast` moves (`animation: toast-in 180ms ease-out forwards`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:262 — `.custom-toast::after` moves (`animation: toast-progress 5s linear forwards`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/app.css:455 — `.sk-circle .sk-child:before` moves (`animation: sk-circleBounceDelay 1.2s infinite ease-in-out both`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/input.css:506 — `.bs-card-link` moves (`transition: transform 180ms ease, box-shadow 180ms ease, border-color 180ms ease`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/input.css:536 — `.bs-pill-link` moves (`transition: background-color 180ms ease, border-color 180ms ease, color 180ms ease, box-shadow 180ms ease, transform 180ms ease`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1 — `.animate-spin` moves (`animation: spin 1s linear infinite`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1 — `.transition` moves (`transition-property: color,background-color,border-color,text-decoration-color,fill,stroke,opacity,box-shadow,transform,filter,backdrop-filter`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1 — `.transition-transform` moves (`transition-property: transform`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1 — `.bs-card-link` moves (`transition: transform .18s ease,box-shadow .18s ease,border-color .18s ease`) 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 BlazorShop.Presentation/BlazorShop.Web/wwwroot/css/site.css:1 — `.bs-pill-link` moves (`transition: background-color .18s ease,border-color .18s ease,color .18s ease,box-shadow .18s ease,transform .18s ease`) 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 BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.css:12 — `.deal-card` moves (`transition: transform 0.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 BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.css:3 — `.fade-slide` moves (`animation: fadeSlideIn 450ms ease-in-out`) 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 BlazorShop.Presentation/BlazorShop.Web/Pages/Products/ProductDetails.razor.css:28 — `.modal.fade .modal-dialog` moves (`transition: transform 0.3s ease-out`) 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 BlazorShop.Presentation/BlazorShop.Web/Pages/Products/ProductDetails.razor.css:44 — `.product-image img` moves (`transition: transform 0.3s ease-in-out`) 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.css:44 — `.bs-toast-card` moves (`animation: bs-toast-in 180ms ease-out forwards`) 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.

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×9

Untrusted text written into markup unescaped BlazorShop.Presentation/BlazorShop.Storefront/Components/Seo/JsonLdScript.razor:3 — `Document.ToJson()` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped BlazorShop.Presentation/BlazorShop.Storefront/Program.cs:86 — `title` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped BlazorShop.Presentation/BlazorShop.Storefront/Program.cs:90 — `heading` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped BlazorShop.Presentation/BlazorShop.Storefront/Program.cs:91 — `message` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:18 — `toast.Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:46 — `toast.Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:74 — `toast.Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:102 — `toast.Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:1523 — `val.html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.

X3 · Exception handling · Swallowed exception (empty catch) · ×8

Swallowed exception (empty catch) BlazorShop.Application/Services/NewsletterService.cs:53 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) BlazorShop.Infrastructure/Services/OrderTrackingService.cs:203 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) BlazorShop.Presentation/BlazorShop.Web/Authentication/Providers/AuthenticationSessionEventPublisher.cs:47 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) BlazorShop.Presentation/BlazorShop.Web/Authentication/Providers/AuthenticationSessionSyncService.cs:73 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:74 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:134 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:107 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AuthenticationService.cs:147 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

Duplicated block (9 lines × 2) BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminAuditService.cs:57 — BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminAuditService.cs:57-65 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminOrderService.cs:77-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `AdminAuditQuery` in one and `AdminOrderQuery` 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 (9 lines × 2) BlazorShop.Application/Services/Payment/CheckoutIntentCanonicalizer.cs:62 — BlazorShop.Application/Services/Payment/CheckoutIntentCanonicalizer.cs:62-70 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/CheckoutAttemptStore.cs:105-113 — 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.
Duplicated block (9 lines × 2) BlazorShop.Application/DTOs/Seo/SeoFieldsDto.cs:28 — BlazorShop.Application/DTOs/Seo/SeoFieldsDto.cs:28-36 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/SeoFieldsBase.cs:26-34 — 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) BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:104 — BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:104-112 | BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:144-152 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:104` 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 (9 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor.cs:13 — BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor.cs:13-21 | BlazorShop.Presentation/BlazorShop.Web/Layout/CategoryComponent.razor.cs:15-23 — 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.
Duplicated block (9 lines × 2) BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs:74 — BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs:74-82 | BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontPublicUrlResolver.cs:90-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.

AC3 · Page structure · Heading level jumps from h2 to h5 · ×5

Heading level jumps from h2 to h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor:78 — 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 h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:348 — 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 h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:162 — 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 h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor:126 — 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 h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Seo.razor:216 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.

D3 · God Classes · MethodTooLong · ×5

MethodTooLong: DevelopmentCatalogSeeder.SeedAsync BlazorShop.Infrastructure/Data/DevelopmentCatalogSeeder.cs:9 — MethodTooLong — SeedAsync runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CheckoutOrchestrator.InitializeStripeAsync BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:309 — MethodTooLong — InitializeStripeAsync runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InventoryReservationService.CreateOrderWithInventoryAsync BlazorShop.Infrastructure/Services/InventoryReservationService.cs:39 — MethodTooLong — CreateOrderWithInventoryAsync runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StripePaymentReconciliationService.ReconcileWithinTransactionAsync BlazorShop.Infrastructure/Services/StripePaymentReconciliationService.cs:43 — MethodTooLong — ReconcileWithinTransactionAsync runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Program.Main BlazorShop.Presentation/BlazorShop.API/Program.cs:40 — MethodTooLong — Main runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

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

Duplicated block (11 lines × 2) BlazorShop.Infrastructure/Services/InventoryReservationService.cs:185 — BlazorShop.Infrastructure/Services/InventoryReservationService.cs:185-195 | BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:113-123 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Services/InventoryReservationService.cs:185` 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.
Duplicated block (11 lines × 2) BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:100 — BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:100-110 | BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:129-139 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:100` 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.
Duplicated block (11 lines × 2) BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryQueryDto.cs:5 — BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryQueryDto.cs:5-15 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Inventory/AdminInventoryModels.cs:5-15 — 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 (11 lines × 2) BlazorShop.Application/DTOs/Demo/DemoSessionModels.cs:10 — BlazorShop.Application/DTOs/Demo/DemoSessionModels.cs:10-20 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/DemoSessionModel.cs:5-15 — 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 (11 lines × 2) BlazorShop.Application/DTOs/Seo/SeoRedirectDto.cs:11 — BlazorShop.Application/DTOs/Seo/SeoRedirectDto.cs:11-21 | BlazorShop.Application/DTOs/Seo/UpsertSeoRedirectDto.cs:9-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

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

Duplicated block (8 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/NumberInput.cs:13 — BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/NumberInput.cs:13-20 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/TextInput.cs:22-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) BlazorShop.Infrastructure/Repositories/ProductInventoryTopologyRepository.cs:102 — BlazorShop.Infrastructure/Repositories/ProductInventoryTopologyRepository.cs:102-109 | BlazorShop.Infrastructure/Repositories/ProductInventoryTopologyRepository.cs:179-186 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Repositories/ProductInventoryTopologyRepository.cs:102` 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 (8 lines × 2) BlazorShop.Infrastructure/Services/InventoryReservationService.cs:138 — BlazorShop.Infrastructure/Services/InventoryReservationService.cs:138-146 | BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:80-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Services/InventoryReservationService.cs:138` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) BlazorShop.Presentation/BlazorShop.API/Controllers/AdminInventoryController.cs:44 — BlazorShop.Presentation/BlazorShop.API/Controllers/AdminInventoryController.cs:44-51 | BlazorShop.Presentation/BlazorShop.API/Controllers/AdminSettingsController.cs:51-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (8 lines × 2) BlazorShop.Presentation/BlazorShop.Web.Shared/Helper/ApiCallHelper.cs:308 — BlazorShop.Presentation/BlazorShop.Web.Shared/Helper/ApiCallHelper.cs:308-315 | BlazorShop.Presentation/BlazorShop.Web/Program.cs:137-144 — 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.

AC6 · Visual & motion safety · Focus outline removed inline · ×4

Focus outline removed inline BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor:95 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:13 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:23 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor:38 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×4

Duplicated block (21 lines × 2) BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:150 — BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs:150-170 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/ProductService.cs:131-151 — 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 (21 lines × 2) BlazorShop.Application/Services/SeoMetadataBuilder.cs:82 — BlazorShop.Application/Services/SeoMetadataBuilder.cs:82-102 | BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.cs:82-102 — before extracting anything, compare `BlazorShop.Application/Services/SeoMetadataBuilder.cs` and `BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (21 lines × 2) BlazorShop.Application/DTOs/Payment/GetOrderLine.cs:3 — BlazorShop.Application/DTOs/Payment/GetOrderLine.cs:3-23 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrderLine.cs:3-23 — before extracting anything, compare `BlazorShop.Application/DTOs/Payment/GetOrderLine.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrderLine.cs` as WHOLE FILES: 91% 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Application/DTOs/Payment/GetOrderLine.cs:3` 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 (21 lines × 2) BlazorShop.Application/DTOs/Product/ProductVariant/CreateProductVariant.cs:7 — BlazorShop.Application/DTOs/Product/ProductVariant/CreateProductVariant.cs:7-27 | BlazorShop.Application/DTOs/Product/ProductVariant/UpdateProductVariant.cs:10-30 — before extracting anything, compare `BlazorShop.Application/DTOs/Product/ProductVariant/CreateProductVariant.cs` and `BlazorShop.Application/DTOs/Product/ProductVariant/UpdateProductVariant.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4

Duplicated block (15 lines × 2) BlazorShop.Infrastructure/Services/Admin/AdminAuditService.cs:60 — BlazorShop.Infrastructure/Services/Admin/AdminAuditService.cs:60-74 | BlazorShop.Infrastructure/Services/Admin/AdminOrderService.cs:70-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `AdminAuditQueryDto` in one and `AdminOrderQueryDto` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BlazorShop.Infrastructure/Services/Admin/AdminAuditService.cs:75` calls `Select`, `Map` and `BlazorShop.Infrastructure/Services/Admin/AdminOrderService.cs:85` does not — after which the two agree again for 3 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.
Duplicated block (15 lines × 2) BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryItemDto.cs:5 — BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryItemDto.cs:5-19 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Inventory/AdminInventoryModels.cs:20-34 — 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 (15 lines × 2) BlazorShop.Application/DTOs/Admin/Audit/AdminAuditQueryDto.cs:5 — BlazorShop.Application/DTOs/Admin/Audit/AdminAuditQueryDto.cs:5-19 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Audit/AdminAuditModels.cs:30-44 — 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 (15 lines × 2) BlazorShop.Application/Services/CategorySeoService.cs:192 — BlazorShop.Application/Services/CategorySeoService.cs:192-206 | BlazorShop.Application/Services/ProductSeoService.cs:204-218 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (7 lines × 2) · ×4

Duplicated block (7 lines × 2) BlazorShop.Infrastructure/Services/StripePaymentReconciliationService.cs:486 — BlazorShop.Infrastructure/Services/StripePaymentReconciliationService.cs:486-492 | BlazorShop.Infrastructure/Services/StripePaymentStateTransitionService.cs:260-266 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (7 lines × 2) BlazorShop.Application/Services/MetricsService.cs:151 — BlazorShop.Application/Services/MetricsService.cs:151-157 | BlazorShop.Presentation/BlazorShop.API/Controllers/MetricsController.cs:69-75 — 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.
Duplicated block (7 lines × 2) BlazorShop.Infrastructure/Services/Admin/AdminAuditService.cs:138 — BlazorShop.Infrastructure/Services/Admin/AdminAuditService.cs:138-144 | BlazorShop.Infrastructure/Services/Admin/AdminOrderService.cs:267-273 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (7 lines × 2) BlazorShop.Presentation/BlazorShop.Storefront/Components/Catalog/ProductCard.razor:127 — BlazorShop.Presentation/BlazorShop.Storefront/Components/Catalog/ProductCard.razor:127-133 | BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontSeoComposer.cs:183-189 — 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.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4

Swallowed exception (caught, then discarded) BlazorShop.Infrastructure/Services/StripePaymentStateTransitionService.cs:239 — `catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:91 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:116 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:257 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.

AC3 · Page structure · Heading level jumps from h1 to h5 · ×3

Heading level jumps from h1 to h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Audit.razor:82 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Inventory.razor:105 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h5 BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Users.razor:132 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.

D12 · Dependency Hygiene · Deprecated · ×3

Deprecated: Blazored.Typeahead BlazorShop.Presentation/BlazorShop.Web/BlazorShop.Web.csproj:10 — Blazored.Typeahead 4.7.0 — Legacy
Deprecated: xunit BlazorShop.Tests/BlazorShop.Tests.csproj:23 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit BlazorShop.E2E/BlazorShop.E2E.csproj:15 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.

D15 · Churn × Complexity Hotspots · Hotspot · ×3

Hotspot: BlazorShop.Presentation/BlazorShop.API/Program.cs BlazorShop.Presentation/BlazorShop.API/Program.cs:40 — BlazorShop.Presentation/BlazorShop.API/Program.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in Program.Main at line 40. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 01:21:46 +03:00' --until='2026-09-10 01:21:46 +03:00' --full-history --no-merges -- BlazorShop.Presentation/BlazorShop.API/Program.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:309 — BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in CheckoutOrchestrator.InitializeStripeAsync at line 309. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 01:21:46 +03:00' --until='2026-09-10 01:21:46 +03:00' --full-history --no-merges -- BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: BlazorShop.Infrastructure/Services/InventoryReservationService.cs BlazorShop.Infrastructure/Services/InventoryReservationService.cs:39 — BlazorShop.Infrastructure/Services/InventoryReservationService.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in InventoryReservationService.CreateOrderWithInventoryAsync at line 39. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 01:21:46 +03:00' --until='2026-09-10 01:21:46 +03:00' --full-history --no-merges -- BlazorShop.Infrastructure/Services/InventoryReservationService.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

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

Duplicated block (19 lines × 2) BlazorShop.Domain/Entities/Category.cs:14 — BlazorShop.Domain/Entities/Category.cs:14-32 | BlazorShop.Domain/Entities/Product.cs:26-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryVariantDto.cs:5 — BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryVariantDto.cs:5-23 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Inventory/AdminInventoryModels.cs:41-59 — before extracting anything, compare `BlazorShop.Application/DTOs/Admin/Inventory/AdminInventoryVariantDto.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Inventory/AdminInventoryModels.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.
Duplicated block (19 lines × 2) BlazorShop.Application/DTOs/Admin/Users/AdminUserListItemDto.cs:5 — BlazorShop.Application/DTOs/Admin/Users/AdminUserListItemDto.cs:5-23 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Users/AdminUserModels.cs:5-23 — before extracting anything, compare `BlazorShop.Application/DTOs/Admin/Users/AdminUserListItemDto.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Users/AdminUserModels.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.

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

Duplicated block (17 lines × 2) BlazorShop.Application/DTOs/Seo/SeoMetadataDto.cs:5 — BlazorShop.Application/DTOs/Seo/SeoMetadataDto.cs:5-21 | BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadata.cs:8-24 — 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 (17 lines × 2) BlazorShop.Application/Services/SeoMetadataBuilder.cs:37 — BlazorShop.Application/Services/SeoMetadataBuilder.cs:37-53 | BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.cs:37-53 — before extracting anything, compare `BlazorShop.Application/Services/SeoMetadataBuilder.cs` and `BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (17 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:179 — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:179-195 | BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Orders.razor:343-359 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:179` 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 (11 lines × 3) · ×3

Duplicated block (11 lines × 3) BlazorShop.Application/DTOs/Payment/GetOrder.cs:17 — BlazorShop.Application/DTOs/Payment/GetOrder.cs:17-27 | BlazorShop.Domain/Entities/Payment/Order.cs:23-33 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrder.cs:17-27 — before extracting anything, compare `BlazorShop.Application/DTOs/Payment/GetOrder.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrder.cs` as WHOLE FILES: 96% 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 2 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.
Duplicated block (11 lines × 3) BlazorShop.Application/DTOs/Admin/Settings/StoreSettingsDto.cs:7 — BlazorShop.Application/DTOs/Admin/Settings/StoreSettingsDto.cs:7-17 | BlazorShop.Domain/Entities/AdminSettings.cs:9-19 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Settings/AdminSettingsModels.cs:18-28 — 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.
Duplicated block (11 lines × 3) BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor.cs:181 — BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor.cs:181-191 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrderLine.cs:29-39 | BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/CheckoutCartLine.cs:21-31 — 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. 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 (12 lines × 2) · ×3

Duplicated block (12 lines × 2) BlazorShop.Domain/Constants/SeoConstraints.cs:5 — BlazorShop.Domain/Constants/SeoConstraints.cs:5-16 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/SeoValidationConstraints.cs:5-16 — before extracting anything, compare `BlazorShop.Domain/Constants/SeoConstraints.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/SeoValidationConstraints.cs` as WHOLE FILES: 85% 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.
Duplicated block (12 lines × 2) BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:40 — BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:40-51 | BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:149-160 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:40` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) BlazorShop.Application/Services/SeoMetadataBuilder.cs:62 — BlazorShop.Application/Services/SeoMetadataBuilder.cs:62-73 | BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.cs:62-73 — before extracting anything, compare `BlazorShop.Application/Services/SeoMetadataBuilder.cs` and `BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.

IC1 · Incompleteness & stubs · Hollow method · ×3

Hollow method — returns a constant without doing the work BlazorShop.Infrastructure/Services/PayPalPaymentService.cs:13 — `CaptureAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work BlazorShop.Presentation/BlazorShop.Web/Components/Templates/Styles.cs:12 — `GetTextColor` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work BlazorShop.Presentation/BlazorShop.Web/Components/Templates/Styles.cs:13 — `GetTableFormat` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

AC1 · Text alternatives · <canvas> without a text alternative · ×2

<canvas> without a text alternative BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:128 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor:141 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.

D17 · Explicit Debt · CommentedOutCode · ×2

CommentedOutCode REDACTED.cs:83 — 11 consecutive commented-code lines
CommentedOutCode BlazorShop.ServiceDefaults/Extensions.cs:83 — 5 consecutive commented-code lines

D30 · Dependency Vulnerabilities · Medium CVE · ×2

REDACTED
REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED

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

Duplicated block (38 lines × 2) BlazorShop.Application/DTOs/Seo/SeoSettingsDto.cs:11 — BlazorShop.Application/DTOs/Seo/SeoSettingsDto.cs:11-48 | BlazorShop.Application/DTOs/Seo/UpdateSeoSettingsDto.cs:9-46 — before extracting anything, compare `BlazorShop.Application/DTOs/Seo/SeoSettingsDto.cs` and `BlazorShop.Application/DTOs/Seo/UpdateSeoSettingsDto.cs` as WHOLE FILES: 96% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (38 lines × 2) BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/GetSeoSettings.cs:9 — BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/GetSeoSettings.cs:9-46 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/UpdateSeoSettings.cs:7-44 — before extracting anything, compare `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/GetSeoSettings.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/UpdateSeoSettings.cs` as WHOLE FILES: 89% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

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

Duplicated block (15 lines × 3) BlazorShop.Application/DTOs/Product/ProductVariant/GetProductVariant.cs:7 — BlazorShop.Application/DTOs/Product/ProductVariant/GetProductVariant.cs:7-21 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProductVariant.cs:7-21 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/Contracts/CreateOrUpdateProductVariant.cs:7-21 — before extracting anything, compare `BlazorShop.Application/DTOs/Product/ProductVariant/GetProductVariant.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProductVariant.cs` as WHOLE FILES: 90% 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.
Duplicated block (15 lines × 3) BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:33 — BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:33-47 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingTextAreaInput.cs:32-46 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/TextInput.cs:32-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:30` calls `AddAttribute` and `BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingTextAreaInput.cs:29` 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 (13 lines × 2) · ×2

Duplicated block (13 lines × 2) BlazorShop.Application/Services/CategorySeoService.cs:81 — BlazorShop.Application/Services/CategorySeoService.cs:81-93 | BlazorShop.Application/Services/ProductSeoService.cs:80-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.
Duplicated block (13 lines × 2) BlazorShop.Application/Services/SeoRedirectPathUtility.cs:13 — BlazorShop.Application/Services/SeoRedirectPathUtility.cs:13-25 | BlazorShop.Application/Validations/Seo/SeoValidationRules.cs:24-36 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BlazorShop.Application/Services/SeoRedirectPathUtility.cs:27` calls `PathsEqual`, `Equals` and `BlazorShop.Application/Validations/Seo/SeoValidationRules.cs:37` 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 (5 lines × 2) · ×2

Duplicated block (5 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor.cs:217 — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor.cs:217-221 | BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:607-611 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (5 lines × 2) BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminAuditService.cs:72 — BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminAuditService.cs:72-76 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AdminOrderService.cs:92-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.

P12 · CI test-gate honesty · Test project never run by CI · ×2

Test project never run by CI BlazorShop.E2E/BlazorShop.E2E.csproj:1 — `BlazorShop.E2E/BlazorShop.E2E.csproj` declares 3 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI BlazorShop.StagingRehearsal/BlazorShop.StagingRehearsal.csproj:1 — `BlazorShop.StagingRehearsal/BlazorShop.StagingRehearsal.csproj` declares 1 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2

Outbound HTTP without resilience BlazorShop.Presentation/BlazorShop.Web/Program.cs:33 — `new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience BlazorShop.Presentation/BlazorShop.Web/Program.cs:110 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).

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

Heading level jumps from h2 to h4 BlazorShop.Presentation/BlazorShop.Web/Pages/Public/MainPage.razor:15 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.

AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×1

Link used as a button (placeholder href) BlazorShop.Presentation/BlazorShop.Web/Components/Header/SideNavComponent.razor:2 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.

AC4 · Keyboard semantics · Modal dialog does not manage focus · ×1

Modal dialog does not manage focus BlazorShop.Presentation/BlazorShop.Web/Components/Shared/ModalDialog.razor:3 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.

AC4 · Keyboard semantics · Anchor without href · ×1

Anchor without href BlazorShop.Presentation/BlazorShop.Web/wwwroot/index.html:63 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.

AC6 · Visual & motion safety · Low contrast Tailwind colour pair (4.3 · ×1

Low contrast Tailwind colour pair (4.3:1) BlazorShop.Presentation/BlazorShop.Web/Pages/Account/Notifications.razor:47 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.

AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1

Focus outline removed in CSS without a :focus replacement docs/ui-v2/styles.css:24 — `.search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.

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

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 85 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.

C1 · Data Protection · No data-protection/encryption · ×1

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

D1 · Cyclomatic Complexity · Program.Main (cyclomatic 34) · ×1

Program.Main (cyclomatic 34) BlazorShop.Presentation/BlazorShop.API/Program.cs:40 — Program.Main has cyclomatic complexity 34 (threshold 15). Of this number, 22 points are the body's own statements and 12 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · CheckoutOrchestrator.InitializeStripeAsync (cyclomatic 29) · ×1

CheckoutOrchestrator.InitializeStripeAsync (cyclomatic 29) BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:309 — CheckoutOrchestrator.InitializeStripeAsync has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InventoryReservationTransitionOperation.ApplyAsync (cyclomatic 29) · ×1

InventoryReservationTransitionOperation.ApplyAsync (cyclomatic 29) BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:12 — InventoryReservationTransitionOperation.ApplyAsync has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InventoryReservationService.CreateOrderWithInventoryAsync (cyclomatic 27) · ×1

InventoryReservationService.CreateOrderWithInventoryAsync (cyclomatic 27) BlazorShop.Infrastructure/Services/InventoryReservationService.cs:39 — InventoryReservationService.CreateOrderWithInventoryAsync has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 63). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · OrderTrackingService.TransitionFulfillmentAsync (cyclomatic 27) · ×1

OrderTrackingService.TransitionFulfillmentAsync (cyclomatic 27) BlazorShop.Infrastructure/Services/OrderTrackingService.cs:86 — OrderTrackingService.TransitionFulfillmentAsync has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · MappingConfig.MappingConfig.ctor (cyclomatic 22) · ×1

MappingConfig.MappingConfig.ctor (cyclomatic 22) BlazorShop.Application/Mapping/MappingConfig.cs:18 — MappingConfig.MappingConfig.ctor has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 21 function literals inside it that branch (lines 24, 25, 26, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · StripePaymentReconciliationService.BindOrValidateProviderIdentityAsync (cyclomatic 20) · ×1

StripePaymentReconciliationService.BindOrValidateProviderIdentityAsync (cyclomatic 20) BlazorShop.Infrastructure/Services/StripePaymentReconciliationService.cs:337 — StripePaymentReconciliationService.BindOrValidateProviderIdentityAsync has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D10 · Test Quality · No assertions · ×1

No assertions: SendEmailAsync_WhenDeliveryIsDisabled_CompletesWithoutConnecting BlazorShop.Tests/Infrastructure/Services/EmailServiceTests.cs:15 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.

D2 · Cognitive Complexity · InventoryReservationService.CreateOrderWithInventoryAsync (cognitive 40) · ×1

InventoryReservationService.CreateOrderWithInventoryAsync (cognitive 40) BlazorShop.Infrastructure/Services/InventoryReservationService.cs:39 — InventoryReservationService.CreateOrderWithInventoryAsync has cognitive complexity 40 (threshold 15). Most of this is not in the body itself: 2 of the 40 points are its own statements and the rest belongs to one function literal inside it that branches (line 63). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · InventoryReservationTransitionOperation.ApplyAsync (cognitive 33) · ×1

InventoryReservationTransitionOperation.ApplyAsync (cognitive 33) BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:12 — InventoryReservationTransitionOperation.ApplyAsync has cognitive complexity 33 (threshold 15). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CheckoutOrchestrator.InitializeStripeAsync (cognitive 32) · ×1

CheckoutOrchestrator.InitializeStripeAsync (cognitive 32) BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:309 — CheckoutOrchestrator.InitializeStripeAsync has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · OrderTrackingService.TransitionFulfillmentAsync (cognitive 30) · ×1

OrderTrackingService.TransitionFulfillmentAsync (cognitive 30) BlazorShop.Infrastructure/Services/OrderTrackingService.cs:86 — OrderTrackingService.TransitionFulfillmentAsync has cognitive complexity 30 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · Program.Main (cognitive 30) · ×1

Program.Main (cognitive 30) BlazorShop.Presentation/BlazorShop.API/Program.cs:40 — Program.Main has cognitive complexity 30 (threshold 15). Of this number, 25 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · CheckoutOrchestrator.ResolveCartLinesAsync (cognitive 28) · ×1

CheckoutOrchestrator.ResolveCartLinesAsync (cognitive 28) BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:939 — CheckoutOrchestrator.ResolveCartLinesAsync has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · StripePaymentReconciliationService.BindOrValidateProviderIdentityAsync (cognitive 23) · ×1

StripePaymentReconciliationService.BindOrValidateProviderIdentityAsync (cognitive 23) BlazorShop.Infrastructure/Services/StripePaymentReconciliationService.cs:337 — StripePaymentReconciliationService.BindOrValidateProviderIdentityAsync has cognitive complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CartPage.BuildLines (cognitive 22) · ×1

CartPage.BuildLines (cognitive 22) BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor.cs:92 — CartPage.BuildLines has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MappingConfig.MappingConfig.ctor (cognitive 21) · ×1

MappingConfig.MappingConfig.ctor (cognitive 21) BlazorShop.Application/Mapping/MappingConfig.cs:18 — MappingConfig.MappingConfig.ctor has cognitive complexity 21 (threshold 15). None of this is in the body itself: all 21 points belong to 21 function literals inside it that branch (lines 24, 25, 26, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · CheckoutIdempotencyStore.ObserveOrAcquireAsync (cognitive 18) · ×1

CheckoutIdempotencyStore.ObserveOrAcquireAsync (cognitive 18) BlazorShop.Infrastructure/Services/CheckoutIdempotencyStore.cs:219 — CheckoutIdempotencyStore.ObserveOrAcquireAsync has cognitive complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: CheckoutOrchestrator BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs — ClassTooLong — 917 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 517 over it, 2.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · FileTooLong · ×1

FileTooLong: Payment/CheckoutOrchestrator.cs BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs — FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 435 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

D3 · God Classes · TooManyMethods · ×1

TooManyMethods: Products BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs — TooManyMethods — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

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

REDACTED

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

Members sharing a duplicated core (5 members, 50+ identical tokens) BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:162 — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:162-200 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:140-174 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs:62-96 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.cs:59-93 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/MainPage.razor.cs:99-133 — These 5 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 5 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 5 times.

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

Members sharing a duplicated core (4 members, 50+ identical tokens) BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:177 — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:177-193 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs:99-115 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.cs:96-112 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/MainPage.razor.cs:136-152 — 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 (53 lines × 2) · ×1

Duplicated block (53 lines × 2) BlazorShop.Application/DTOs/Payment/GetOrder.cs:3 — BlazorShop.Application/DTOs/Payment/GetOrder.cs:3-55 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrder.cs:3-55 — before extracting anything, compare `BlazorShop.Application/DTOs/Payment/GetOrder.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrder.cs` as WHOLE FILES: 96% 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 2 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Application/DTOs/Payment/GetOrder.cs:3` 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 (34 lines × 4) · ×1

Duplicated block (34 lines × 4) BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:141 — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:141-174 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs:63-96 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.cs:60-93 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/MainPage.razor.cs:100-133 — before extracting anything, compare `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs` and `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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 (32 lines × 2) · ×1

Duplicated block (32 lines × 2) BlazorShop.Infrastructure/Data/Configurations/CategoryConfiguration.cs:17 — BlazorShop.Infrastructure/Data/Configurations/CategoryConfiguration.cs:17-48 | BlazorShop.Infrastructure/Data/Configurations/ProductConfiguration.cs:26-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Data/Configurations/CategoryConfiguration.cs:17` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<Category>` in one and `EntityTypeBuilder<Product>` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BlazorShop.Infrastructure/Data/Configurations/ProductConfiguration.cs:22` calls `Property`, `IsConcurrencyToken` and `BlazorShop.Infrastructure/Data/Configurations/CategoryConfiguration.cs:14` 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 (34 lines × 2) · ×1

Duplicated block (34 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:456 — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:456-489 | BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:525-558 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:456` 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 (27 lines × 2) · ×1

Duplicated block (27 lines × 2) BlazorShop.Presentation/BlazorShop.API/DatabaseMigrationBootstrapper.cs:281 — BlazorShop.Presentation/BlazorShop.API/DatabaseMigrationBootstrapper.cs:281-307 | BlazorShop.Presentation/BlazorShop.API/DatabaseMigrationBootstrapper.cs:328-354 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.API/DatabaseMigrationBootstrapper.cs:281` 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 (28 lines × 2) · ×1

Duplicated block (28 lines × 2) BlazorShop.Application/DTOs/Product/GetProduct.cs:8 — BlazorShop.Application/DTOs/Product/GetProduct.cs:8-35 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:7-34 — before extracting anything, compare `BlazorShop.Application/DTOs/Product/GetProduct.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Application/DTOs/Product/GetProduct.cs:8` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:36` calls `Subtract` and `BlazorShop.Application/DTOs/Product/GetProduct.cs:37` does not — after which the two agree again for 3 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 (25 lines × 2) · ×1

Duplicated block (25 lines × 2) BlazorShop.Application/DTOs/Category/GetCategory.cs:5 — BlazorShop.Application/DTOs/Category/GetCategory.cs:5-29 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Category/GetCategory.cs:5-29 — before extracting anything, compare `BlazorShop.Application/DTOs/Category/GetCategory.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Category/GetCategory.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Application/DTOs/Category/GetCategory.cs:5` 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 (24 lines × 2) · ×1

Duplicated block (24 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:498 — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:498-521 | BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:560-583 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:498` 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 (21 lines × 4) · ×1

Duplicated block (21 lines × 4) BlazorShop.Application/DTOs/Category/GetCategory.cs:7 — BlazorShop.Application/DTOs/Category/GetCategory.cs:7-27 | BlazorShop.Application/DTOs/Product/GetProduct.cs:11-31 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Category/GetCategory.cs:7-27 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:10-30 — before extracting anything, compare `BlazorShop.Application/DTOs/Category/GetCategory.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Category/GetCategory.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:36` calls `Subtract` and `BlazorShop.Application/DTOs/Product/GetProduct.cs:37` 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 (18 lines × 2) · ×1

Duplicated block (18 lines × 2) BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:609 — BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:609-626 | BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:805-822 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs:609` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

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

Duplicated block (17 lines × 3) BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs:7 — BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs:7-23 | BlazorShop.Domain/Entities/AdminAuditLog.cs:7-23 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Audit/AdminAuditModels.cs:7-23 — before extracting anything, compare `BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Audit/AdminAuditModels.cs` as WHOLE FILES: 84% 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 2 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.

D4 · Code Duplication · Duplicated block (13–18 lines × 5) · ×1

Duplicated block (13–18 lines × 5) BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:170 — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:170-187 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:148-160 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs:70-82 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.cs:67-79 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/MainPage.razor.cs:107-119 — before extracting anything, compare `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs` and `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:170` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

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

Duplicated block (16 lines × 4) BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:178 — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:178-193 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs:100-115 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.cs:97-112 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/MainPage.razor.cs:137-152 — before extracting anything, compare `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs` and `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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 (16 lines × 2) · ×1

Duplicated block (16 lines × 2) BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs:55 — BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs:55-70 | BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontPublicUrlResolver.cs:71-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (12–15 lines × 4) · ×1

Duplicated block (12–15 lines × 4) BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:31 — BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:31-45 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingTextAreaInput.cs:30-44 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingTextInput.cs:41-52 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/TextInput.cs:30-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:30` calls `AddAttribute` and `BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingTextAreaInput.cs:29` does not — after which the two agree again for 4 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 (14 lines × 2) · ×1

Duplicated block (14 lines × 2) BlazorShop.Application/DTOs/Product/GetCatalogProduct.cs:12 — BlazorShop.Application/DTOs/Product/GetCatalogProduct.cs:12-25 | BlazorShop.Application/DTOs/Product/ProductBase.cs:7-20 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

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

Duplicated block (14–15 lines × 2) BlazorShop.Infrastructure/Services/InventoryReservationService.cs:156 — BlazorShop.Infrastructure/Services/InventoryReservationService.cs:156-170 | BlazorShop.Infrastructure/Services/InventoryReservationTransitionOperation.cs:91-104 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Infrastructure/Services/InventoryReservationService.cs:156` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

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

Duplicated block (11 lines × 7) BlazorShop.Application/DTOs/Category/GetCategory.cs:11 — BlazorShop.Application/DTOs/Category/GetCategory.cs:11-21 | BlazorShop.Application/DTOs/Product/GetProduct.cs:15-25 | BlazorShop.Domain/Entities/Category.cs:14-24 | BlazorShop.Domain/Entities/Product.cs:26-36 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Category/GetCategory.cs:11-21 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Product/GetProduct.cs:14-24 | BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadata.cs:29-39 — before extracting anything, compare `BlazorShop.Application/DTOs/Category/GetCategory.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Category/GetCategory.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.

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

Duplicated block (10 lines × 2) BlazorShop.Application/DTOs/UserIdentity/ChangePassword.cs:7 — BlazorShop.Application/DTOs/UserIdentity/ChangePassword.cs:7-16 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/PasswordChangeModel.cs:7-16 — 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 (9 lines × 4) · ×1

Duplicated block (9 lines × 4) BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs:11 — BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs:11-19 | BlazorShop.Application/DTOs/Admin/Audit/CreateAdminAuditLogDto.cs:5-13 | BlazorShop.Domain/Entities/AdminAuditLog.cs:11-19 | BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Audit/AdminAuditModels.cs:11-19 — before extracting anything, compare `BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs` and `BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Audit/AdminAuditModels.cs` as WHOLE FILES: 84% 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 2 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.

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

Duplicated block (8–9 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:24 — BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/FloatingNumberInput.cs:24-31 | BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/NumberInput.cs:15-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.Presentation/BlazorShop.Web/Components/FormControls/NumberInput.cs:15` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

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

Duplicated block (6 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor.cs:225 — BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor.cs:225-230 | BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:615-620 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (23 lines × 2) · ×1

Duplicated block (23 lines × 2) BlazorShop.Presentation/BlazorShop.Web/Layout/AccountLayout.razor:100 — BlazorShop.Presentation/BlazorShop.Web/Layout/AccountLayout.razor:100-122 | BlazorShop.Presentation/BlazorShop.Web/Layout/MainLayout.razor:155-177 — before extracting anything, compare `BlazorShop.Presentation/BlazorShop.Web/Layout/AccountLayout.razor` and `BlazorShop.Presentation/BlazorShop.Web/Layout/MainLayout.razor` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

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

Duplicated block (9 lines × 3) BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:202 — BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs:202-210 | BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs:124-132 | BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.cs:121-129 — before extracting anything, compare `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs` and `BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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 (14 lines × 3) · ×1

Duplicated block (14 lines × 3) BlazorShop.Presentation/BlazorShop.Web.Shared/Services/CategoryService.cs:113 — BlazorShop.Presentation/BlazorShop.Web.Shared/Services/CategoryService.cs:113-128 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/ProductService.cs:112-127 | BlazorShop.Presentation/BlazorShop.Web.Shared/Services/ProductVariantService.cs:71-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.

P5 · DR & Backup · No DR/backup evidence · ×1

No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1

NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.

X1 · Async correctness · async void method · ×1

async void method: ShowToast REDACTED.cs:15 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.

X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×1

Disposable created and abandoned in the method that made it BlazorShop.Infrastructure/Services/EmailService.cs:44 — `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `SendEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw.

Minor — 94 finding(s)

X10 · Duplicated predicate · Duplicated predicate · ×19

Duplicated predicate BlazorShop.Presentation/BlazorShop.Web/Program.cs:99 — `!string.IsNullOrWhiteSpace(configuredBaseAddress) && Uri.TryCreate(configuredBaseAddress, UriKind.Absolute, out var configuredUri)` appears character-identically in 2 files — BlazorShop.Presentation/BlazorShop.Storefront/Program.cs, BlazorShop.Presentation/BlazorShop.Web/Program.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 BlazorShop.Infrastructure/Services/Admin/AdminOrderService.cs:44 — `(user.Email != null && user.Email.ToLower().Contains(search)) || (user.UserName != null && user.UserName.ToLower().Contains(search)) || user…` appears character-identically in 2 files — BlazorShop.Infrastructure/Services/Admin/AdminOrderService.cs, BlazorShop.Infrastructure/Services/Admin/AdminUserService.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 BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs:34 — `Uri.TryCreate(relativeOrAbsoluteUrl.Trim(), UriKind.Absolute, out var absoluteUri) && IsSupportedAbsoluteUri(absoluteUri)` appears character-identically in 2 files — BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs, BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontPublicUrlResolver.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 BlazorShop.Application/Services/SeoMetadataBuilder.cs:87 — `Uri.TryCreate(value, UriKind.Absolute, out var absoluteValue) && IsSupportedAbsoluteUri(absoluteValue)` appears character-identically in 2 files — BlazorShop.Application/Services/SeoMetadataBuilder.cs, BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.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 BlazorShop.Application/Validations/Seo/SeoValidationRules.cs:12 — `Uri.TryCreate(value, UriKind.Absolute, out var uri) && (uri.Scheme == Uri.UriSchemeHttp || uri.Scheme == Uri.UriSchemeHttps)` appears character-identically in 2 files — BlazorShop.Application/Validations/Seo/SeoValidationRules.cs, BlazorShop.Presentation/BlazorShop.Storefront/Configuration/StorefrontOptionsValidators.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 BlazorShop.Presentation/BlazorShop.API/Program.cs:255 — `e.InnerException is AddressInUseException || e.Message.Contains("address already in use", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — BlazorShop.AppHost/Program.cs, BlazorShop.Presentation/BlazorShop.API/Program.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 BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/CheckoutCartLineMapper.cs:16 — `item.ProductId != Guid.Empty && item.Quantity > 0` appears character-identically in 2 files — BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Payments/CheckoutCartLineMapper.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 BlazorShop.Infrastructure/Repositories/ProductReadRepository.cs:247 — `query.CategoryId.HasValue && query.CategoryId.Value != Guid.Empty` appears character-identically in 3 files — BlazorShop.Infrastructure/Repositories/ProductReadRepository.cs, BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.cs, BlazorShop.Presentation/BlazorShop.Web.Shared/Services/ProductService.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 BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AuthenticationService.cs:62 — `result is null || !result.IsSuccessStatusCode` appears character-identically in 5 files — BlazorShop.Presentation/BlazorShop.Web.Shared/Services/AuthenticationService.cs, BlazorShop.Presentation/BlazorShop.Web.Shared/Services/CategoryService.cs, BlazorShop.Presentation/BlazorShop.Web.Shared/Services/NewsletterService.cs, BlazorShop.Presentation/BlazorShop.Web.Shared/Services/ProductService.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 BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor.cs:83 — `result.IsSuccess && result.Value is not null` appears character-identically in 2 files — BlazorShop.Presentation/BlazorShop.Storefront/Pages/CartPage.razor.cs, BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontApiClient.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 BlazorShop.Presentation/BlazorShop.Web/Program.cs:142 — `string.Equals(mediaType, "application/json", StringComparison.OrdinalIgnoreCase) || mediaType.EndsWith("+json", StringComparison.OrdinalIgno…` appears character-identically in 2 files — BlazorShop.Presentation/BlazorShop.Web.Shared/Helper/ApiCallHelper.cs, BlazorShop.Presentation/BlazorShop.Web/Program.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 BlazorShop.Application/Services/SeoMetadataBuilder.cs:93 — `string.IsNullOrWhiteSpace(baseCanonicalUrl) || !Uri.TryCreate(baseCanonicalUrl, UriKind.Absolute, out var baseUri) || !IsSupportedAbsoluteUr…` appears character-identically in 2 files — BlazorShop.Application/Services/SeoMetadataBuilder.cs, BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.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 BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs:55 — `string.IsNullOrWhiteSpace(candidate) || !Uri.TryCreate(candidate.Trim(), UriKind.Absolute, out var absoluteUri) || !IsSupportedAbsoluteUri(a…` appears character-identically in 2 files — BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs, BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontPublicUrlResolver.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 BlazorShop.Application/Services/CategorySeoService.cs:192 — `string.IsNullOrWhiteSpace(oldPublicPath) || string.IsNullOrWhiteSpace(newPublicPath) || SeoRedirectPathUtility.PathsEqual(oldPublicPath, new…` appears character-identically in 2 files — BlazorShop.Application/Services/CategorySeoService.cs, BlazorShop.Application/Services/ProductSeoService.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 BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:171 — `this.QueryFailureNotifier.TryNotifyFailure(productResult, "Cart", ToastPosition.BottomRight) || productResult.Data is null` appears character-identically in 5 files — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.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 BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:147 — `this.QueryFailureNotifier.TryNotifyFailure(productResult, "Product details") || productResult.Data is null` appears character-identically in 4 files — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.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 BlazorShop.Application/Services/SeoMetadataBuilder.cs:106 — `uri.Scheme == Uri.UriSchemeHttp || uri.Scheme == Uri.UriSchemeHttps` appears character-identically in 4 files — BlazorShop.Application/Services/SeoMetadataBuilder.cs, BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontClientAppUrlResolver.cs, BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontPublicUrlResolver.cs, BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoMetadataBuilder.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 BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:204 — `x.ProductId == payload.ProductId && x.VariantId == payload.VariantId` appears character-identically in 5 files — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.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 BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:169 — `x.ProductId == productId && x.VariantId == null` appears character-identically in 5 files — BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/LatestProducts.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Products/NewReleases.razor.cs, BlazorShop.Presentation/BlazorShop.Web/Pages/Public/Deals/TodaysDeals.razor.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.

X4 · Structured logging · Interpolated log message defeats structured logging · ×18

Interpolated log message defeats structured logging BlazorShop.Application/Services/Authentication/AuthenticationService.cs:115 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/Authentication/AuthenticationService.cs:276 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/Authentication/AuthenticationService.cs:353 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/Authentication/AuthenticationService.cs:375 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/Authentication/AuthenticationService.cs:380 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/ProductRecommendationService.cs:55 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/ProductRecommendationService.cs:59 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/ProductRecommendationService.cs:64 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/ProductRecommendationService.cs:99 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/ProductRecommendationService.cs:103 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Application/Services/ProductRecommendationService.cs:110 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:31 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:51 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:65 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:97 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:118 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:140 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging BlazorShop.Infrastructure/Repositories/ProductRecommendationRepository.cs:160 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.

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

Silent fallback default in catch BlazorShop.Infrastructure/Configuration/EmailSettingsOptionsValidator.cs:71 — `IsValidEmailAddress` swallows `FormatException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Infrastructure/Services/Admin/AdminSettingsService.cs:262 — `ValidateStore` swallows `CultureNotFoundException` into `return "Default culture is invalid.";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Infrastructure/Services/Admin/AdminSettingsService.cs:307 — `IsEmail` swallows `FormatException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Infrastructure/Services/StripePaymentReconciliationService.cs:309 — `ValidateMonetaryIdentity` swallows `Exception` into `return "The immutable order amount cannot be represented in its currency.";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.API/Demo/DemoSessionMiddleware.cs:135 — `ReadDemoSessionClaim` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:91 — `UpdateCountFromJson` swallows every exception and sets `_cartCount = 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web/Components/Header/HeaderBoxComponent.razor.cs:116 — `LoadCartCountAsync` swallows every exception and sets `_cartCount = 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Dashboard.razor.cs:257 — `LoadMetricsAsync` swallows every exception and sets `_metricsError = "Analytics data is unavailable right now. Try again.";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web/Program.cs:125 — `IsRelativeApiAvailableAsync` swallows `HttpRequestException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web/Services/StorefrontSeoService.cs:58 — `GetSettingsAsync` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web.Shared/Helper/TokenService.cs:21 — `GetJwtTokenAsync` swallows every exception into `return string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Web.Shared/Services/MetricsClient.cs:41 — `GetAsync` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Storefront/Services/StorefrontSessionResolver.cs:120 — `ParseSession` swallows every exception into `return StorefrontSessionInfo.Anonymous;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch BlazorShop.Presentation/BlazorShop.Storefront/wwwroot/js/storefrontCommerce.js:84 — `parseCart` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

X7 · Silent fallback defaults · Silent fallback default on parse failure · ×10

Silent fallback default on parse failure BlazorShop.Infrastructure/Repositories/Authentication/AppTokenManager.cs:174 — `GetRefreshTokenLifetimeDays` falls back to `RefreshTokenLifetimeDaysDefault` when `int.TryParse(_config["Runtime:Security:RefreshTokenLifetimeDays"], out var confi…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure REDACTED:212 — `GetRefreshTokenCookieSameSiteMode` falls back to `SameSiteMode.Strict` when `Enum.TryParse<SameSiteMode>(_runtimeOptions.Security.RefreshTokenCookieSameSite,…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Components/Header/SearchBarComponent.razor.cs:57 — `FilterAsync` falls back to `[]` when `result.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:51 — `OnParametersSetAsync` falls back to `ProductCatalogSortBy.NameAscending` when `Enum.TryParse<ProductCatalogSortBy>(Sort, ignoreCase: true, out var parsedSort)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Components/Search/SearchResult.razor.cs:104 — `ChangeSort` falls back to `ProductCatalogSortBy.NameAscending` when `Enum.TryParse<ProductCatalogSortBy>(args.Value?.ToString(), out var parsedSort)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor.cs:217 — `ShowToast` falls back to `ToastLevel.Error` when `result.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Categories.razor.cs:225 — `ShowToast` falls back to `ToastLevel.Error` when `result.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:607 — `ShowToast` falls back to `ToastLevel.Error` when `result.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Products.razor.cs:615 — `ShowToast` falls back to `ToastLevel.Error` when `result.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure BlazorShop.Presentation/BlazorShop.Web/Pages/Admin/Seo.razor.cs:263 — `ShowToast` falls back to `ToastLevel.Error` when `result.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.

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

REDACTED
REDACTED
REDACTED

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

Mock-dominated test: HandleAuthSessionEventAsync_WhenSignedIn_RefreshesWithoutClearing BlazorShop.Tests/Presentation/Authentication/AuthenticationSessionSyncServiceTests.cs:16 — This test sets up 5 test doubles (for example `new Mock<IAuthenticationSessionRefresher>()`) 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: HandleAuthSessionEventAsync_WhenSignedOut_ClearsSessionStateAndNotifies BlazorShop.Tests/Presentation/Authentication/AuthenticationSessionSyncServiceTests.cs:37 — This test sets up 5 test doubles (for example `new Mock<IAuthenticationSessionRefresher>()`) against 1 real object(s) of its own, and its only verification is 4 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 · ×2

REDACTED
REDACTED

C3 · Audit Trail · Partial audit-trail evidence · ×1

Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an EF SaveChanges interceptor (or equivalent write-side hook, e.g. an event-store append every change flows through), [Audited] per-entity coverage.

D12 · Dependency Hygiene · Outdated · ×1

Outdated: Stripe.net REDACTED:24 — Stripe.net 50.0.0 → 53.0.0 available (referenced by BlazorShop.Infrastructure).

D12 · Dependency Hygiene · Deprecated · ×1

Deprecated: glob REDACTED:598 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split BlazorShop.Infrastructure · ×1

Split BlazorShop.Infrastructure — The Infrastructure project is huge at 6922 LoC and sprawls over 14 namespaces (Services, Demo, Repositories, Data, Authentication), a classic sprawling infrastructure grab-bag. Suggested: split into cohesive domain-specific repositories across the listed Services/Repositories namespaces

D27 · Navigability · High interface indirection · ×1

High interface indirection — 34 % of calls go through an interface — tracing a call means resolving the implementation each hop. Prefer concrete types where there's a single implementation.

D27 · Navigability · Pass-through layer · ×1

Pass-through layer BlazorShop.Infrastructure/Services/LoggerAdapter.cs:7 — LoggerAdapter: all 3 public methods forward their arguments unchanged to _logger and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _logger directly, or give the layer a job.

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

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

REDACTED

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

REDACTED

D39 · IL Efficiency · IL efficiency · ×1

IL efficiency: 15 authored method(s) exceed the IL budget BlazorShop.Application/Mapping/MappingConfig.cs:18 — 15 of 1967 first-party methods compile to oversized IL bodies (> 250 instructions); worst: BlazorShop.Application.Mapping.MappingConfig..ctor @ BlazorShop.Application/Mapping/MappingConfig.cs:18, 918 IL instructions; that pulled this dimension to 9.8/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.

D9 · Test Distribution · Inverted test pyramid · ×1

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

IC1 · Incompleteness & stubs · Commented-out code · ×1

Commented-out code BlazorShop.Application/Mapping/MappingConfig.cs:20 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

M3 · Folder & project structure · No src/ separation · ×1

No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

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

README/code drift docs/production-runbook.md:177 — docs/production-runbook.md links to `REDACTED`, but `docs/REDACTED` 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.

P2 · Observability · Logging is not universal · ×1

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

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 15855 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

P4 · Deployment & Rollback · No release approval gate · ×1

No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

P6 · Release Hygiene · No changelog · ×1

No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

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 BlazorShop.Presentation/BlazorShop.API/Program.cs:418 — Set: X-Content-Type-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options — 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. (−1.5 on this card.)

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

Not all async methods take a CancellationToken — Only 103/469 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.5 `!` suppressions per 1k syntax nodes — 118 suppression(s) across the 218364 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.

Minor — 54 finding(s)

D12 · Dependency Hygiene · Outdated · ×45

Outdated: Microsoft.Extensions.Identity.Stores — Microsoft.Extensions.Identity.Stores 10.0.0 → 10.0.13 available (referenced by BlazorShop.Domain).
Outdated: AutoMapper — AutoMapper 16.1.1 → 16.2.0 available (referenced by BlazorShop.Application).
Outdated: FluentValidation — FluentValidation 12.1.1 → 12.2.0 available (referenced by BlazorShop.Application).
Outdated: FluentValidation.DependencyInjectionExtensions — FluentValidation.DependencyInjectionExtensions 12.1.1 → 12.2.0 available (referenced by BlazorShop.Application).
Outdated: Microsoft.Extensions.Configuration.Abstractions — Microsoft.Extensions.Configuration.Abstractions 10.0.0 → 10.0.13 available (referenced by BlazorShop.Application).
Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 10.0.0 → 10.0.13 available (referenced by BlazorShop.Application).
Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.0 → 10.0.13 available (referenced by BlazorShop.Application).
Outdated: Microsoft.Extensions.Options.ConfigurationExtensions — Microsoft.Extensions.Options.ConfigurationExtensions 10.0.0 → 10.0.13 available (referenced by BlazorShop.Application).
Outdated: MailKit — MailKit 4.16.0 → 4.18.1 available (referenced by BlazorShop.Infrastructure).
Outdated: Microsoft.AspNetCore.Authentication.JwtBearer — Microsoft.AspNetCore.Authentication.JwtBearer 10.0.5 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 10.0.5 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
Outdated: Microsoft.AspNetCore.Identity.UI — Microsoft.AspNetCore.Identity.UI 10.0.5 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 10.0.5 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
Outdated: Microsoft.Extensions.Configuration.UserSecrets — Microsoft.Extensions.Configuration.UserSecrets 10.0.5 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
Outdated: MimeKit — MimeKit 4.16.0 → 4.18.2 available (referenced by BlazorShop.Infrastructure).
Outdated: Npgsql.EntityFrameworkCore.PostgreSQL — Npgsql.EntityFrameworkCore.PostgreSQL 10.0.1 → 10.0.3 available (referenced by BlazorShop.Infrastructure).
Outdated: Serilog — Serilog 4.3.0 → 4.4.0 available (referenced by BlazorShop.Infrastructure).
Outdated: Microsoft.AspNetCore.OpenApi — Microsoft.AspNetCore.OpenApi 10.0.10 → 10.0.13 available (referenced by BlazorShop.API).
Outdated: Microsoft.EntityFrameworkCore.Tools — Microsoft.EntityFrameworkCore.Tools 10.0.5 → 10.0.13 available (referenced by BlazorShop.API).
Outdated: Swashbuckle.AspNetCore — Swashbuckle.AspNetCore 10.2.3 → 10.3.1 available (referenced by BlazorShop.API).
Outdated: Humanizer.Core — Humanizer.Core 3.0.1 → 3.0.10 available (referenced by BlazorShop.Web).
Outdated: Microsoft.AspNetCore.Components.Authorization — Microsoft.AspNetCore.Components.Authorization 10.0.6 → 10.0.13 available (referenced by BlazorShop.Web).
Outdated: Microsoft.AspNetCore.Components.WebAssembly — Microsoft.AspNetCore.Components.WebAssembly 10.0.6 → 10.0.13 available (referenced by BlazorShop.Web).
Outdated: Microsoft.AspNetCore.Components.WebAssembly.DevServer — Microsoft.AspNetCore.Components.WebAssembly.DevServer 10.0.6 → 10.0.13 available (referenced by BlazorShop.Web).
Outdated: System.IdentityModel.Tokens.Jwt — System.IdentityModel.Tokens.Jwt 8.15.0 → 8.23.0 available (referenced by BlazorShop.Web).
+ 20 more in this group — see findings.md.

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

XML-doc coverage: BlazorShop.Domain BlazorShop.Domain/BlazorShop.Domain.csproj — BlazorShop.Domain: 0 % XML-doc coverage (0/325).
XML-doc coverage: BlazorShop.Application BlazorShop.Application/BlazorShop.Application.csproj — BlazorShop.Application: 1 % XML-doc coverage (5/718).
XML-doc coverage: BlazorShop.Infrastructure REDACTED — BlazorShop.Infrastructure: 4 % XML-doc coverage (12/303).
XML-doc coverage: BlazorShop.API BlazorShop.Presentation/BlazorShop.API/BlazorShop.API.csproj — BlazorShop.API: 18 % XML-doc coverage (33/180).
XML-doc coverage: BlazorShop.Web BlazorShop.Presentation/BlazorShop.Web/BlazorShop.Web.csproj — BlazorShop.Web: 0 % XML-doc coverage (0/232).
XML-doc coverage: BlazorShop.Web.Shared BlazorShop.Presentation/BlazorShop.Web.Shared/BlazorShop.Web.Shared.csproj — BlazorShop.Web.Shared: 0 % XML-doc coverage (0/777).
XML-doc coverage: BlazorShop.ServiceDefaults BlazorShop.ServiceDefaults/BlazorShop.ServiceDefaults.csproj — BlazorShop.ServiceDefaults: 0 % XML-doc coverage (0/5).
XML-doc coverage: BlazorShop.Storefront BlazorShop.Presentation/BlazorShop.Storefront/BlazorShop.Storefront.csproj — BlazorShop.Storefront: 0 % XML-doc coverage (0/136).

D10 · Test Quality · Mock framework · ×1

Mock framework: Moq — BlazorShop.Tests references Moq.

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-3948a838d1004dcfb3f447a7f9533f54/history.json --exit-code 0 --source .	1	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-3948a838d1004dcfb3f447a7f9533f54/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 .	56	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list BlazorShop.sln package --vulnerable --include-transitive --format json	6	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	13	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 8 file(s) — `BlazorShop.Application/Services/MetricsService.cs`, `BlazorShop.Application/Services/Payment/CheckoutOrchestrator.cs`, `BlazorShop.Infrastructure/Repositories/Newsletters/NewsletterSubscriberRepository.cs`, `BlazorShop.Presentation/BlazorShop.API/Controllers/MetricsController.cs`, `BlazorShop.Presentation/BlazorShop.Storefront/Program.cs`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
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 01a16273-0eeb-794e-89bf-160d2582b9e7 · 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 — 61 field(s) across 6 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 — 36 field(s)

AdminAuditLogDto.ActorEmail BlazorShop.Application/DTOs/Admin/Audit/AdminAuditLogDto.cs:9
NotificationSettingsDto.SmtpFromEmail BlazorShop.Application/DTOs/Admin/Settings/NotificationSettingsDto.cs:7
StoreSettingsDto.StoreSupportEmail BlazorShop.Application/DTOs/Admin/Settings/StoreSettingsDto.cs:7
UpdateNotificationSettingsDto.SmtpFromEmail BlazorShop.Application/DTOs/Admin/Settings/UpdateNotificationSettingsDto.cs:7
AdminUserListItemDto.Email BlazorShop.Application/DTOs/Admin/Users/AdminUserListItemDto.cs:7
DemoSessionResponse.Email BlazorShop.Application/DTOs/Demo/DemoSessionModels.cs:14
GetOrder.CustomerEmail BlazorShop.Application/DTOs/Payment/GetOrder.cs:45
SeoSettingsDto.CompanyEmail BlazorShop.Application/DTOs/Seo/SeoSettingsDto.cs:36
UpdateSeoSettingsDto.CompanyEmail BlazorShop.Application/DTOs/Seo/UpdateSeoSettingsDto.cs:34
BaseModel.Email BlazorShop.Application/DTOs/UserIdentity/BaseModel.cs:5
UpdateProfile.Email BlazorShop.Application/DTOs/UserIdentity/UpdateProfile.cs:12
DemoOptions.CustomerEmail BlazorShop.Application/Options/DemoOptions.cs:19
DemoOptions.AdminEmail BlazorShop.Application/Options/DemoOptions.cs:21
AdminAuditLog.ActorEmail BlazorShop.Domain/Entities/AdminAuditLog.cs:9
AdminSettings.StoreSupportEmail BlazorShop.Domain/Entities/AdminSettings.cs:9
AdminSettings.SmtpFromEmail BlazorShop.Domain/Entities/AdminSettings.cs:31
NewsletterSubscriber.Email BlazorShop.Domain/Entities/NewsletterSubscriber.cs:7
Order.CustomerEmailSnapshot BlazorShop.Domain/Entities/Payment/Order.cs:39
SeoSettings.CompanyEmail BlazorShop.Domain/Entities/SeoSettings.cs:26
AdminSettingsService._emailSettings BlazorShop.Infrastructure/Services/Admin/AdminSettingsService.cs:36
EmailService._emailSettings BlazorShop.Infrastructure/Services/EmailService.cs:15
SubscribeEmailDto.Email REDACTED:32
StorefrontSessionInfo.Email BlazorShop.Presentation/BlazorShop.Storefront/Services/Contracts/IStorefrontSessionResolver.cs:8
AdminAuditLog.ActorEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Audit/AdminAuditModels.cs:9
StoreSettingsModel.StoreSupportEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Settings/AdminSettingsModels.cs:18
NotificationSettingsModel.SmtpFromEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Settings/AdminSettingsModels.cs:63
UpdateNotificationSettings.SmtpFromEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Settings/AdminSettingsModels.cs:74
AdminUserListItem.Email BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Users/AdminUserModels.cs:7
AuthenticationBase.Email BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/AuthenticationBase.cs:8
DemoSessionModel.Email BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/DemoSessionModel.cs:9
UpdateProfileModel.Email BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/UpdateProfileModel.cs:12
SubscribeRequest.Email BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Newsletter/NewsletterModels.cs:3
GetOrder.CustomerEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrder.cs:45
GetSeoSettings.CompanyEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/GetSeoSettings.cs:34
UpdateSeoSettings.CompanyEmail BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/UpdateSeoSettings.cs:32
CustomerService.CustomerEmail BlazorShop.Presentation/BlazorShop.Web/Pages/Public/CustomerService.razor.cs:7

Phone — 12 field(s)

StoreSettingsDto.StoreSupportPhone BlazorShop.Application/DTOs/Admin/Settings/StoreSettingsDto.cs:9
AdminUserDetailsDto.PhoneNumber BlazorShop.Application/DTOs/Admin/Users/AdminUserDetailsDto.cs:5
SeoSettingsDto.CompanyPhone BlazorShop.Application/DTOs/Seo/SeoSettingsDto.cs:33
UpdateSeoSettingsDto.CompanyPhone BlazorShop.Application/DTOs/Seo/UpdateSeoSettingsDto.cs:31
UpdateProfile.PhoneNumber BlazorShop.Application/DTOs/UserIdentity/UpdateProfile.cs:15
AdminSettings.StoreSupportPhone BlazorShop.Domain/Entities/AdminSettings.cs:11
SeoSettings.CompanyPhone BlazorShop.Domain/Entities/SeoSettings.cs:24
StoreSettingsModel.StoreSupportPhone BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Settings/AdminSettingsModels.cs:20
AdminUserDetails.PhoneNumber BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Users/AdminUserModels.cs:28
UpdateProfileModel.PhoneNumber BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/UpdateProfileModel.cs:15
GetSeoSettings.CompanyPhone BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/GetSeoSettings.cs:31
UpdateSeoSettings.CompanyPhone BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Seo/UpdateSeoSettings.cs:29

Name — 7 field(s)

AdminUserListItemDto.FullName BlazorShop.Application/DTOs/Admin/Users/AdminUserListItemDto.cs:11
CreateUser.FullName BlazorShop.Application/DTOs/UserIdentity/CreateUser.cs:5
UpdateProfile.FullName BlazorShop.Application/DTOs/UserIdentity/UpdateProfile.cs:8
AppUser.FullName BlazorShop.Domain/Entities/Identity/AppUser.cs:7
AdminUserListItem.FullName BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Admin/Users/AdminUserModels.cs:11
CreateUser.FullName BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/CreateUser.cs:8
UpdateProfileModel.FullName BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Authentication/UpdateProfileModel.cs:8

Financial (card / IBAN) — 3 field(s)

BankTransferInfo.Iban BlazorShop.Application/DTOs/Payment/BankTransferInfo.cs:5
BankTransferSettings.Iban BlazorShop.Application/DTOs/Payment/BankTransferSettings.cs:5
BankTransferInfo.Iban BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/CheckoutResult.cs:15

Address — 2 field(s)

GetOrder.BillingAddress BlazorShop.Application/DTOs/Payment/GetOrder.cs:49
GetOrder.BillingAddress BlazorShop.Presentation/BlazorShop.Web.Shared/Models/Payment/GetOrder.cs:49

Government ID (SSN / passport / tax) — 1 field(s)

Order.BillingAddressSnapshot BlazorShop.Domain/Entities/Payment/Order.cs:43

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 63% · Adequate ·

At a glance — Architecture · 80% · Strong ·

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

At a glance — Readiness · 33% · Weak · gated by P3, P5, P7 ·

At a glance — Security · 66% · Adequate · gated by D29, D36, C1 ·

At a glance — Accessibility · 41% · Weak · gated by AC4 ·

At a glance — Performance · 71% · 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