Public report of JBeni/BlazorShop, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 03:40 UTC · Survey ID cd_1490c785995441b2bed03853cb6d28f0

JBeni/BlazorShop

Measured 22 October 2026, 03:35 UTC, at code version 26a1b08

Supply-chain provenance & signing: not measured

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 43out of 100 At risk Down 4 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Event-Driven 100 Exemplary Performance 100 Exemplary Architecture 83 Strong Code Health 77 Strong Security and Compliance 60 Adequate Domain Modelling 51 Adequate Accessibility 50 Adequate Maturity 38 Weak Production Readiness 37 Weak

A small codebase: 18,952 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 37

Findings by how serious they are

64 critical 399 serious 557 minor

6 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 03:35 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

96of 102 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
984of 1020 findings point to an exact file and line, so you can open each one in the code. The other 36 concern the repository as a whole, such as missing documentation.
102dimensions across 9 lenses, read from 18,952 lines of product code in 7 projects.
Chapters

Executive summary

JBeni/BlazorShop scores 43 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 37 and is rated Weak. Its Secret Scanning 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 2 Leaked secret finding(s) in Secret Scanning and to resolve the 2 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 43 to about 48.

64 findings are critical: 19 in Explicit Debt, 11 in Domain ↔ infrastructure boundary, ten in Dependency Vulnerabilities, five in Page structure, five in Static Analysis (SAST), three in Keyboard semantics, two in ARIA correctness, two in Dependency Hygiene, two in Forms & labels, two in Secret Scanning, one in Captive dependencies, one in Test Quality and one in Text alternatives.

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

Code Health 77 Strong Architecture 83 Strong Maturity 38 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 37 Weak, capped by Code Coverage, Dependency Hygiene, Secret Scanning, Outbound HTTP resilience and Domain vs controller coverage Security and Compliance 60 Adequate, capped by Dependency Vulnerabilities and Data Protection Domain Modelling 51 Adequate, capped by Strongly-typed ids, Rich vs anemic model and Domain ↔ infrastructure boundary Event-Driven 100 ★ Exemplary Accessibility 50 Adequate Performance 100 ★ Exemplary

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 37 · counts for 45%Maturity 38 · counts for 25%Accessibility 50 · counts for 14%Domain Modelling 51 · counts for 8%Security and Compliance 60 · counts for 4%Code Health 77 · counts for 2%Architecture 83 · counts for 1%Event-Driven 100 · counts for 1%Performance 100 · counts for 0%

If Production Readiness rose from 37 to 70, the lowest score rated Strong, the score would rise from 43 to about 48.

Code composition: what the lines of code are
Business logic 9%Supporting code 34%Tests 30%Generated by tools 27%
New since the last survey: 57 findings

These 57 critical or serious findings weren't in the previous survey, on 7 October 2026.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 5 findings

These 5 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.

  • Coupling · Off the main sequence: BlazorShop.Domain
  • Supply-chain Provenance & Signing REDACTED
  • Web-Security Posture · Middleware order
  • Visual & motion safety · Animation without a prefers-reduced-motion guard BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor
  • Visual & motion safety · Animation without a prefers-reduced-motion guard BlazorShop.WebClient/Pages/Musics/MusicDetails.razor
Rebuild cost: about €32,000 · Estimate
Cost to rebuild€11,000 to €54,000, for 178 to 565 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemVery 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 43. 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.
SizeSmall: 18,952 lines of product code
Comment linesThe estimate prices 13,109 lines. Comment lines count towards the size of 18,952 lines but aren't priced as work.

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

Top priorities

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

1
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
Raises the score by about 5 points · Low effort · Secret Scanning
2
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.
Raises the score by about 4 points · Low effort · Dependency Hygiene
3
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED (2), REDACTED.
Raises the score by about 4 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 €32,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 37 (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.
One cause behind 22 Domain Modelling findings · Common cause
22 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (10 findings) · Rich vs anemic model (10 findings) · Strongly-typed ids (2 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 2 Secret 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.

arch BlazorShop.Application Application BlazorShop.Domain Domain BlazorShop.Application->BlazorShop.Domain BlazorShop.Infrastructure Infrastructure BlazorShop.Infrastructure->BlazorShop.Application BlazorShop.WebApi WebApi BlazorShop.WebApi->BlazorShop.Infrastructure BlazorShop.WebClient WebClient BlazorShop.WebClient->BlazorShop.Application BlazorShop.WorkerService WorkerService BlazorShop.WorkerService->BlazorShop.Infrastructure

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.

98 modules, with 159 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 58 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.Commands.AccountCommand2 Application.Commands.RoleCommand3 Application.Commands.TodoItemCommand4 Application.Commands.UserCommand5 Application.Common.Models6 Application.Queries.UserQuery7 Application.Responses8 Domain.Entities.Identity9 Domain.Entities10 WebClient.Interfaces11 Application.Common.Interfaces12 WebClient.Services13 Application.Handlers.Commands.AccountHandler14 Application.Handlers.Commands.CartHandler15 Application.Handlers.Commands.ClotheHandler16 Application.Handlers.Commands.InvoiceHandler17 Application.Handlers.Commands.MusicHandler18 Application.Handlers.Commands.OrderHandler19 Application.Handlers.Commands.ReceiptHandler20 Application.Handlers.Commands.RoleHandler21 Application.Handlers.Commands.SubscriberHandler22 Application.Handlers.Commands.SubscriptionHandler23 Application.Handlers.Commands.TodoItemHandler24 Application.Handlers.Commands.TodoListHandler25 Application.Handlers.Commands.UserHandler26 Application.Handlers.Queries.CartHandler27 Application.Handlers.Queries.ClotheHandler28 Application.Handlers.Queries.InvoiceHandler29 Application.Handlers.Queries.MusicHandler30 Application.Handlers.Queries.OrderHandler31 Application.Handlers.Queries.ReceiptHandler32 Application.Handlers.Queries.RoleHandler33 Application.Handlers.Queries.SubscriberHandler34 Application.Handlers.Queries.SubscriptionHandler35 Application.Handlers.Queries.TodoItemHandler36 Application.Handlers.Queries.TodoListHandler37 Application.Handlers.Queries.UserHandler38 Infrastructure.Persistence39 Infrastructure.Services40 WebApi.Controllers
1 Application.Commands.AccountCommand
2 Application.Commands.RoleCommand
3 Application.Commands.TodoItemCommand
4 Application.Commands.UserCommand
5 Application.Common.Models
6 Application.Queries.UserQuery
7 Application.Responses
8 Domain.Entities.Identity
9 Domain.Entities2
10 WebClient.Interfaces211211
11 Application.Common.Interfaces425543410
12 WebClient.Services21121113
13 Application.Handlers.Commands.AccountHandler444
14 Application.Handlers.Commands.CartHandler414
15 Application.Handlers.Commands.ClotheHandler33
16 Application.Handlers.Commands.InvoiceHandler33
17 Application.Handlers.Commands.MusicHandler33
18 Application.Handlers.Commands.OrderHandler33
19 Application.Handlers.Commands.ReceiptHandler33
20 Application.Handlers.Commands.RoleHandler333
21 Application.Handlers.Commands.SubscriberHandler57
22 Application.Handlers.Commands.SubscriptionHandler33
23 Application.Handlers.Commands.TodoItemHandler3313
24 Application.Handlers.Commands.TodoListHandler313
25 Application.Handlers.Commands.UserHandler666
26 Application.Handlers.Queries.CartHandler223
27 Application.Handlers.Queries.ClotheHandler222
28 Application.Handlers.Queries.InvoiceHandler222
29 Application.Handlers.Queries.MusicHandler222
30 Application.Handlers.Queries.OrderHandler222
31 Application.Handlers.Queries.ReceiptHandler222
32 Application.Handlers.Queries.RoleHandler444
33 Application.Handlers.Queries.SubscriberHandler333
34 Application.Handlers.Queries.SubscriptionHandler222
35 Application.Handlers.Queries.TodoItemHandler222
36 Application.Handlers.Queries.TodoListHandler222
37 Application.Handlers.Queries.UserHandler4444
38 Infrastructure.Persistence2101
39 Infrastructure.Services42554256
40 WebApi.Controllers422411
Uses a module listed above itPart of a loopThe module itself
1 Application.Commands.AccountCommand2 Application.Commands.RoleCommand3 Application.Commands.TodoItemCommand4 Application.Commands.UserCommand5 Application.Common.Models6 Application.Queries.UserQuery7 Application.Responses8 Domain.Entities.Identity9 Domain.Entities10 WebClient.Interfaces11 Application.Common.Interfaces12 WebClient.Services13 Application.Handlers.Commands.AccountHandler14 Application.Handlers.Commands.CartHandler15 Application.Handlers.Commands.ClotheHandler16 Application.Handlers.Commands.InvoiceHandler17 Application.Handlers.Commands.MusicHandler18 Application.Handlers.Commands.OrderHandler19 Application.Handlers.Commands.ReceiptHandler20 Application.Handlers.Commands.RoleHandler21 Application.Handlers.Commands.SubscriberHandler22 Application.Handlers.Commands.SubscriptionHandler23 Application.Handlers.Commands.TodoItemHandler24 Application.Handlers.Commands.TodoListHandler25 Application.Handlers.Commands.UserHandler26 Application.Handlers.Queries.CartHandler27 Application.Handlers.Queries.ClotheHandler28 Application.Handlers.Queries.InvoiceHandler29 Application.Handlers.Queries.MusicHandler30 Application.Handlers.Queries.OrderHandler31 Application.Handlers.Queries.ReceiptHandler32 Application.Handlers.Queries.RoleHandler33 Application.Handlers.Queries.SubscriberHandler34 Application.Handlers.Queries.SubscriptionHandler35 Application.Handlers.Queries.TodoItemHandler36 Application.Handlers.Queries.TodoListHandler37 Application.Handlers.Queries.UserHandler38 Infrastructure.Persistence39 Infrastructure.Services40 WebApi.ControllersApplication.Commands.AccountCommand1Application.Commands.RoleCommand2Application.Commands.TodoItemCommand3Application.Commands.UserCommand4Application.Common.Models5Application.Queries.UserQuery6Application.Responses7Domain.Entities.Identity8Domain.Entities9WebClient.Interfaces10Application.Common.Interfaces11WebClient.Services12Application.Handlers.Commands.AccountHandler13Application.Handlers.Commands.CartHandler14Application.Handlers.Commands.ClotheHandler15Application.Handlers.Commands.InvoiceHandler16Application.Handlers.Commands.MusicHandler17Application.Handlers.Commands.OrderHandler18Application.Handlers.Commands.ReceiptHandler19Application.Handlers.Commands.RoleHandler20Application.Handlers.Commands.SubscriberHandler21Application.Handlers.Commands.SubscriptionHandler22Application.Handlers.Commands.TodoItemHandler23Application.Handlers.Commands.TodoListHandler24Application.Handlers.Commands.UserHandler25Application.Handlers.Queries.CartHandler26Application.Handlers.Queries.ClotheHandler27Application.Handlers.Queries.InvoiceHandler28Application.Handlers.Queries.MusicHandler29Application.Handlers.Queries.OrderHandler30Application.Handlers.Queries.ReceiptHandler31Application.Handlers.Queries.RoleHandler32Application.Handlers.Queries.SubscriberHandler33Application.Handlers.Queries.SubscriptionHandler34Application.Handlers.Queries.TodoItemHandler35Application.Handlers.Queries.TodoListHandler36Application.Handlers.Queries.UserHandler37Infrastructure.Persistence38Infrastructure.Services39WebApi.Controllers402211211425543410211211134444143333333333333573333133136662232222222222222224443332222222224444210142554256422411+58 more modules (most-connected shown)

At a glance — Code Health · 77% · Strong ·

The Good
D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.2 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 8.7 D17 · .NET / C# Explicit Debt 8.1 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 10.0 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 X4 · Repo Structured logging 10.0 X5 · Repo Nullable reference types 10.0
The Bad
X18 · Repo Disposal-pattern correctness 5.5 X2 · Repo Cancellation propagation 5.8 X3 · Repo Exception handling 6.0

At a glance — Architecture · 83% · Strong ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 7.1 D27 · .NET / C# Navigability 9.5 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 8.1 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 AX9 · Repo CQS / query purity 10.0
The Bad
AX1 · Repo Captive dependencies 5.3

At a glance — Maturity · 38% · Weak · gated by D34, M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 9.0 D24 · .NET / C# Comment Value 8.0 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0
The Bad
M1 · Repo Documentation (README) 6.0
The Ugly
D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 37% · Weak · gated by D8, D12, D13, P7, P9 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 9.9 D11 · .NET / C# Test Reliability 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 9.8 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.4 P8 · Repo Schema migrations 10.0
The Ugly
D8 · .NET / C# Code Coverage 3.6 D12 · .NET / C# Dependency Hygiene 1.5 D13 · .NET / C# Secret Scanning 0.0 P3 · Repo Security & performance tooling 4.0 P7 · Repo Outbound HTTP resilience 3.0 P9 · Repo Domain vs controller coverage 1.9

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

The Good
D28 · .NET / C# Secrets (history) 10.0 D32 · .NET / C# Data Compliance (PII/GDPR) 9.0 C2 · Repo Access Controls 10.0 C3 · Repo Audit Trail 7.5 S1 · Repo Web-Security Posture 7.5 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D29 · .NET / C# Static Analysis (SAST) 5.8 D44 · .NET / C# Platform End-of-Life 6.0
The Ugly
D30 · .NET / C# Dependency Vulnerabilities 1.4 C1 · Repo Data Protection 3.0

At a glance — Domain Modelling · 51% · Adequate · gated by DM2, DM4, DM6 ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 10.0 DM11 · Repo Constructible invalid state 10.0 DM12 · Repo Ambient inputs in the domain 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0
The Bad
DM5 · Repo Encapsulated state 6.0
The Ugly
DM2 · Repo Strongly-typed ids 3.0 DM4 · Repo Rich vs anemic model 3.0 DM6 · Repo Domain ↔ infrastructure boundary 3.5

At a glance — Event-Driven · 100% · Exemplary ·

The Good
ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0 ED4 · Repo Outbox / dual-write 10.0

At a glance — Accessibility · 50% · Adequate ·

The Bad
AC1 · Repo Text alternatives 6.5 AC2 · Repo Forms & labels 5.1 AC3 · Repo Page structure 5.3 AC5 · Repo ARIA correctness 6.6 AC6 · Repo Visual & motion safety 6.5
The Ugly
AC4 · Repo Keyboard semantics 4.7 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

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 categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures16High / Critical
A05:2025 — Injection12High / Critical
A07:2025 — Authentication Failures2High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

Begin by updating outdated dependencies in the WebApi, WebClient, and Infrastructure projects to ensure system stability. Immediately address the two leaked secrets in REDACTED to secure sensitive credentials. Next, clean up the 150 orphaned files, prioritizing UserService, RoleService, and Program, to improve code maintainability. Finally, resolve the two vulnerable dependencies and six deprecated items across the client, API, and test projects to reduce technical debt.

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

Do thisHelpsEffortDimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).+5.4 ptsLowSecret Scanning
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.+4.3 ptsLowDependency Hygiene
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED (2), REDACTED.+4.1 ptsLowDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.+3.9 ptsLowADR Quality
Resolve the 22 Outdated finding(s) in Dependency Hygiene — start with REDACTED (7), REDACTED (5), REDACTED (4).+5.6 ptsMediumDependency Hygiene
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.+4.0 ptsMediumArchitecture documentation
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with AccountServiceTests.cs.+1.6 ptsLowTest Quality
Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.+2.4 ptsMediumDomain vs controller coverage

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.5SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.4SlopDependency Vulnerabilities: High CVE: REDACTED
BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs3.9SlopExplicit Debt: EmptyCatchBlock
BlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs4.0SlopTest Quality: Assertions commented out: ChangePasswordUserAsync_ShouldCallChangePasswordAsync_WhenAllConditionsAreMet
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
BlazorShop.Application/Validators/AccountValidator/RegisterCommandValidator.cs4.6MixedExplicit Debt: EmptyCatchBlock
REDACTED5.1MixedSecret Scanning: Leaked secret: REDACTED
.editorconfig5.2MixedExplicit Debt: AnalyzerSeverityNone
REDACTED5.4MixedStatic Analysis (SAST): Medium: REDACTED
BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs5.7MixedCode Duplication: Duplicated block (34 lines × 2)
BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs5.7MixedCode Duplication: Duplicated block (15 lines × 2)
BlazorShop.Application/Validators/UserValidator/CreateUserCommandValidator.cs6.1MixedExplicit Debt: EmptyCatchBlock
BlazorShop.Application/Validators/UserValidator/GetUserByEmailQueryValidator.cs6.1MixedExplicit Debt: EmptyCatchBlock
BlazorShop.Application/Validators/UserValidator/UpdateUserEmailCommandValidator.cs6.1MixedExplicit Debt: EmptyCatchBlock
BlazorShop.Application/Validators/AccountValidator/ResetPasswordCommandValidator.cs6.1MixedExplicit Debt: EmptyCatchBlock
BlazorShop.Application/Common/Behaviours/AuthorizationBehaviour.cs6.3MixedCognitive Complexity: AuthorizationBehaviour.Handle (cognitive 29)
BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs6.3MixedCode Duplication: Duplicated block (20 lines × 2)

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

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

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

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

Could not be resolved — 6

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

Methodology & how to trust this report

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

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
  1. 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, 984 of 1020 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.)
  2. 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.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a161ad-7506-7f1a-a8fe-9d24dc06d647.

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.

  • 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-maintainer repository — bus factor is not applicable (2 contributor(s) across 782 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'REDACTED' with message: Detected package version outside of dependency constraint: Duende.IdentityServer.EntityFramework.Storage 6.0.4 requires AutoMapper (>= 11.0.0 && < 12.0.0) but version REDACTED was resolved.
  • 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.
  • 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. User interface: 43 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: the service booted and answers HTTP at http://127.0.0.1:33849, but serves no HTML page — nothing for the accessibility crawl.
  • 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. 119 further occurrence(s) are not listed individually; the score already reflects all 159.

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.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • 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.
  • 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 Dockerfile (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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.

The LLM boundary

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

Dimensions

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity9.2 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was AuthorizationBehaviour.Handle at 29.

AuthorizationBehaviour.Handle (cognitive 29)BlazorShop.Application/Common/Behaviours/AuthorizationBehaviour.cs:50

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with AuthorizationBehaviour.Handle (cognitive 29). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
  2. 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.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

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

53 duplicated block group(s) detected.

Duplicated block (11 lines × 2) · ×6BlazorShop.WebClient/Services/CartService.cs:119
Duplicated block (5 lines × 2) · ×6BlazorShop.Application/Validators/ClotheValidator/CreateClotheCommandValidator.cs:60
Duplicated block (34 lines × 2) · ×3BlazorShop.Application/Commands/SubscriptionCommand/CreateSubscriptionCommand.cs:12
Duplicated block (20 lines × 2) · ×3BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:20
Duplicated block (11 lines × 3) · ×3BlazorShop.WebClient/Services/RoleService.cs:95

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

What to do

  1. Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with CartService.cs, ClotheService.cs, MusicService.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 6 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with CreateClotheCommandValidator.cs, CreateInvoiceCommandValidator.cs, CreateMusicCommandValidator.cs. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 3 Duplicated block (34 lines × 2) finding(s) in Code Duplication — start with CreateSubscriptionCommand.cs, CreateClotheCommand.cs, CreateMusicCommandValidator.cs. — One of this dimension's main actionable groups (3 warning-level).
  4. 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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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 23 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage3.6 / 10Weak✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 14.3% — 205 file(s) below 50% · 7 method(s) over the CRAP-30 risk line.

Low coverage: BlazorShop.WorkerService/Worker.cs · ×205BlazorShop.WorkerService/Worker.cs:1
CRAP 30: UpdateCreatedSubscriberCommandHandler.Handle · ×4BlazorShop.Application/Handlers/Commands/SubscriberHandler/UpdateCreatedSubscriberCommandHandler.cs:47
CRAP 132: AuthorizationBehaviour.HandleBlazorShop.Application/Common/Behaviours/AuthorizationBehaviour.cs:50
CRAP 72: CustomerRoleHandler.HandleRequirementAsyncBlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs:18
CRAP 42: MappingProfile.ApplyMappingsFromAssemblyV2BlazorShop.Application/Common/Mappings/MappingProfile.cs:41

What to do

  1. Resolve the 205 Low coverage finding(s) in Code Coverage — start with AccountService.cs (2), RoleService.cs (2), UserService.cs (2). — One of this dimension's main actionable groups (205 warning-level).
  2. Resolve the 4 CRAP 30 finding(s) in Code Coverage — start with UpdateCreatedSubscriberCommandHandler.cs, AdminRoleHandler.cs, DefaultRoleHandler.cs. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 CRAP 132 finding(s) in Code Coverage — start with AuthorizationBehaviour.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.9 / 10Adequategated by 1 critical 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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 321 zero-assertion, 1 mock references across 353 tests (1 harness-style project(s) excluded from the assertion penalty).

Assertions commented out: ChangePasswordUserAsync_ShouldCallChangePasswordAsync_WhenAllConditionsAreMetBlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs:127
No direct assertions: Handle · ×320BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/CreateCartCommandHandlerTests.cs:53
Mock framework: Moq

What to do

  1. Resolve the 1 Assertions commented out finding(s) in Test Quality — start with AccountServiceTests.cs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 320 No direct assertions finding(s) in Test Quality — start with UserServiceTests.cs (23), RoleServiceTests.cs (20), UsersControllerTests.cs (8). — One of this dimension's main actionable groups (320 recommendation-level).
  3. 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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

41 outdated, 2 vulnerable, 6 deprecated packages.

Vulnerable: System.IdentityModel.Tokens.Jwt · ×2
Deprecated: Blazored.LocalStorage · ×6REDACTED:19
Outdated: Microsoft.AspNetCore.Components.Authorization · ×22REDACTED:23
Outdated: FluentValidation · ×19

What to do

  1. Resolve the 22 Outdated finding(s) in Dependency Hygiene — start with REDACTED (7), REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (22 recommendation-level).
  2. Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

2 secret(s) detected.

REDACTED

What to do

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

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

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 46 direct `PackageReference`(s), and 204 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.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

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

24 deducted debt markers + unmeasured dead symbols across 18942 LoC in the .NET projects (1.0/KLoC) → score 8.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

AnalyzerSeverityNone · ×13.editorconfig:4
EmptyCatchBlock · ×6BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:42
CommentedOutCode · ×5BlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs:94

What to do

  1. Resolve the 13 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (13). — One of this dimension's main actionable groups (13 issue-level).
  2. Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with LoginCommandValidator.cs, RegisterCommandValidator.cs, ResetPasswordCommandValidator.cs. — One of this dimension's main actionable groups (6 issue-level).
  3. Resolve the 5 CommentedOutCode finding(s) in Explicit Debt — start with AccountServiceTests.cs (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
  4. 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.

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

7 projects, 509 source files, 27966 hand-written lines of code (18942 production / 9024 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 8358 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 8 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

The repository has two README files (the root Blazor Shop Store and the CSS directory Open Iconic README) plus architecture/Docs markdown docs. The root README is a well-written overview of what the project is (an online shop built with Razor components on Net 6 C#10, CQRS/Mediator server), setup steps (update-database, seed fields, run application), and an outline that all sections exist; it also documents the Web API worker service and the Unit of Work project under development. The CSS directory README is a focused documentation of Open Iconic's features, usage, and sprite integration with Bootstrap/Foundation. Both are clear but thin on concrete examples for readers who cannot read ticket references or internal jargon.

XML-doc coverage: BlazorShop.WebClient · ×6REDACTED

What to do

  1. Improve Documentation Quality — currently 8.0/10. — The repository has two README files (the root Blazor Shop Store and the CSS directory Open Iconic README) plus architecture/Docs markdown docs. The root README is a well-written overview of what the project is (an online shop built with Razor components on Net 6 C#10, CQRS/Mediator server), setup steps (update-database, seed fields, run application), and an outline that all sections exist; it also documents the Web API worker service and the Unit of Work project under development. The CSS directory README is a focused documentation of Open Iconic's features, usage, and sprite integration with Bootstrap/Foundation. Both are clear but thin on concrete examples for readers who cannot read ticket references or internal jargon.

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

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

1 naming inconsistencies across 200 sampled symbols.

Inconsistent pluralization in response type naming. Most response types use the singular form of the entity name (e.g., UserResponse, MusicResponse, ReceiptResponse), but 'ClotheResponse' uses the singular form of a noun that is typically pluralized in this context (Clothes), or is grammatically awkward as a singular count noun without an article. Additionally, the entity type is 'Clothe' (singular) while the query is 'GetClothesQuery' (plural) and the service is 'ClotheService' (singular). The inconsistency lies in 'Clothe' vs the standard pattern of singular entity names mapping to singular response names, but 'Clothe' itself is non-standard compared to 'Music', 'User', etc. However, the most glaring inconsistency is between the entity name 'Clothe' and the query/service naming 'Clothes'/'Clothe'. Let's look closer. The entity is `BlazorShop.Domain.Entities.TodoItem` (Singular). The response is `TodoItemResponse` (Singular). The entity for clothing is not explicitly listed as a Type, but `ClotheResponse` exists. The query is `GetClothesQuery`. The service is `ClotheService`. The handler is `ClotheHandler`. The command is `CreateClotheCommand`. The entity name seems to be `Clothe` (singular, non-standard) or `Clothes` (plural, standard). Given `GetClothesQuery` uses plural, but `CreateClotheCommand` uses singular, there is an inconsistency in the entity name usage itself. But looking at the list, `ClotheResponse` is the outlier in terms of standard English noun usage if we assume the entity is 'Clothes'. If the entity is 'Clothe', it's consistent with 'Music' (singular). But 'Clothe' is a verb or a rare singular noun. 'Clothes' is the standard noun. The query `GetClothesQuery` suggests the domain concept is 'Clothes'. The command `CreateClotheCommand` suggests the domain concept is 'Clothe'. This is a naming inconsistency within the domain model itself.

✓ On the Gold path — maintain.

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

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

16 valuable / 0 redundant across 69 sampled comments.

What to do

  1. Improve Comment Value — currently 8.0/10. — 16 valuable / 0 redundant across 69 sampled comments.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion7.1 / 10Strong✓ 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 7.1 / 10 · rule-coverage 100% · ceiling Documented

1 of 7 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion 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.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)5.8 / 10Adequate✓ 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 5.8 / 10 · rule-coverage 100% · ceiling Documented

12 finding(s): 0 critical, 5 high, 7 medium, 0 low. 4 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities1.4 / 10Critical✓ 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 1.4 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

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

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

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

151 of 151 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is BlazorShop.Infrastructure/Persistence/ApplicationDbContextSeed.cs. Counted over 151 of the 383 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×150BlazorShop.Application/Utils/ErrorsManager.cs:1
Dormant codebase
Most significant orphaned fileBlazorShop.Infrastructure/Persistence/ApplicationDbContextSeed.cs:1

What to do

  1. Resolve the 150 Orphaned file finding(s) in Knowledge Freshness — start with UserService.cs (2), RoleService.cs (2), Program.cs (2). — One of this dimension's main actionable groups (150 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with ApplicationDbContextSeed.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

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.

D39 · IL Efficiency10.0 / 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

2 of 1014 first-party methods have an oversized IL body.

IL efficiency: 2 authored method(s) exceed the IL budgetBlazorShop.Application/Responses/SubscriberResponse.cs:93

✓ On the Gold path — maintain.

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

D44 · Platform End-of-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 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.

End-of-life runtime: .NET net7.0BlazorShop.WorkerService/BlazorShop.WorkerService.csproj:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with BlazorShop.WorkerService.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives6.5 / 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. — BlazorShop.WebClient/Pages/User/Profile.razor:22

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

  • A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×11) — BlazorShop.WebClient/Pages/Account/Login.razor:21, BlazorShop.WebClient/Pages/Account/Login.razor:29, BlazorShop.WebClient/Pages/Account/Login.razor:41, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:22, BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:33

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

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — BlazorShop.WebApi/Views/Error.html:2, BlazorShop.WebApi/Views/Home.html:2
  • An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. (×2) — BlazorShop.WebApi/Views/Error.html:2, BlazorShop.WebApi/Views/Home.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — BlazorShop.WebApi/Views/Error.html:2, BlazorShop.WebApi/Views/Home.html:2
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×16) — BlazorShop.WebClient/Pages/Admin/Clothes/Clothes.razor:26, BlazorShop.WebClient/Pages/Admin/Musics/Musics.razor:26, BlazorShop.WebClient/Pages/Admin/Roles/Roles.razor:26, …
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — BlazorShop.WebClient/wwwroot/index.html:5

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.
AC4 · Keyboard semantics4.7 / 10Weak✓ 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".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:27, BlazorShop.WebClient/Pages/Admin/Todos/TodoLists.razor:18, BlazorShop.WebClient/Shared/NavMenu.razor:16
  • 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.WebClient/wwwroot/index.html:25

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness6.6 / 10Adequate✓ Tool-verified

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

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

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.

  • aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. (×2) — BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:44, BlazorShop.WebClient/Pages/Admin/Todos/TodoLists.razor:25

What to do

  • Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety6.5 / 10Adequate✓ Tool-verified

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

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

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

  • `.product-img` moves (`animation: fade-in 1s forwards 1`) 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. (×2) — BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:129, BlazorShop.WebClient/Pages/Musics/MusicDetails.razor:101
  • `.product-listing` moves (`animation: fade-in 1s forwards 1`) 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. (×2) — BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:157, BlazorShop.WebClient/Pages/Musics/MusicDetails.razor:129
  • 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. (×3) — BlazorShop.WebClient/Pages/Orders/MyOrders.razor:17, BlazorShop.WebClient/Pages/Receipts/Receipts.razor:16, BlazorShop.WebClient/Pages/Subscriptions/MySubscriptions.razor:20

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.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

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

What to do

  • Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies5.3 / 10Adequate✓ 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.

  • `Worker` is registered as a SINGLETON but its constructor takes `HttpClient httpClient`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `HttpClient` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — BlazorShop.WorkerService/Worker.cs:18

What to do

  • Don't inject scoped/transient services into singletons; resolve them per-use via IServiceScopeFactory or a factory delegate, or align the lifetimes.
AX10 · Code composition8.1 / 10Strong✓ 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).
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.

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.

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.

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.

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.

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.

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

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

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

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 immutable audit-log / audit-trail type to write to, [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.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

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

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

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

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

  • `Subscriber.StripeSubscriberSubscriptionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BlazorShop.Domain/Entities/Subscriber.cs:35
  • `Subscription.StripeSubscriptionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BlazorShop.Domain/Entities/Subscription.cs:15

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified

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

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

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

  • `Cart` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Cart.cs:10
  • `Clothe` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Clothe.cs:10
  • `Invoice` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Invoice.cs:10
  • `Music` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Music.cs:10
  • `Order` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Order.cs:10
  • `Receipt` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Receipt.cs:10
  • `Subscriber` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Subscriber.cs:10
  • `Subscription` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/Subscription.cs:10
  • `TodoItem` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/TodoItem.cs:10
  • `TodoList` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BlazorShop.Domain/Entities/TodoList.cs:10

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state6.0 / 10Adequate✓ Tool-verified

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

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

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

  • `Cart` exposes publicly writable state (Name, Price, Amount, Clothe, User). — BlazorShop.Domain/Entities/Cart.cs:10
  • `Clothe` exposes publicly writable state (Name, Description, Price, Amount, ImageName, ImagePath, and 1 more). — BlazorShop.Domain/Entities/Clothe.cs:10
  • `Invoice` exposes publicly writable state (UserEmail, Name, AmountSubTotal, AmountTotal, Quantity). — BlazorShop.Domain/Entities/Invoice.cs:10
  • `Music` exposes publicly writable state (Title, Description, Author, DateRelease, ImageName, ImagePath, and 1 more). — BlazorShop.Domain/Entities/Music.cs:10
  • `Order` exposes publicly writable state (UserEmail, OrderName, OrderDate, LineItems, AmountTotal). — BlazorShop.Domain/Entities/Order.cs:10
  • `Receipt` exposes publicly writable state (UserEmail, ReceiptDate, ReceiptName, ReceiptUrl). — BlazorShop.Domain/Entities/Receipt.cs:10
  • `Subscriber` exposes publicly writable state (Status, DateStart, CurrentPeriodEnd, CurrentPeriodStart, StripeSubscriberSubscriptionId, HostedInvoiceUrl, and 2 more). — BlazorShop.Domain/Entities/Subscriber.cs:10
  • `Subscription` exposes publicly writable state (StripeSubscriptionId, Name, Price, Currency, CurrencySymbol, ChargeType, and 3 more). — BlazorShop.Domain/Entities/Subscription.cs:10
  • `TodoItem` exposes publicly writable state (Title, Note, Priority, State, Done, List). — BlazorShop.Domain/Entities/TodoItem.cs:10
  • `TodoList` exposes publicly writable state (Title, Items). — BlazorShop.Domain/Entities/TodoList.cs:10

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary3.5 / 10Weak✓ Tool-verified

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

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

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

  • `EntityBase` (domain layer) names `NotMappedAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Common/EntityBase.cs:27
  • `Cart` (domain layer) names `User` from `BlazorShop.Domain.Entities.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Cart.cs:35
  • `Role` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/Role.cs:10
  • `RoleClaim` (domain layer) names `IdentityRoleClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/RoleClaim.cs:10
  • `User` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/User.cs:10
  • `UserClaim` (domain layer) names `IdentityUserClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/UserClaim.cs:10
  • `UserLogin` (domain layer) names `IdentityUserLogin` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/UserLogin.cs:10
  • `UserRole` (domain layer) names `IdentityUserRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/UserRole.cs:10
  • `UserToken` (domain layer) names `IdentityUserToken` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Identity/UserToken.cs:10
  • `Subscriber` (domain layer) names `User` from `BlazorShop.Domain.Entities.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — BlazorShop.Domain/Entities/Subscriber.cs:45
  • The domain project `BlazorShop.Domain` references `Microsoft.AspNetCore.Identity.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — BlazorShop.Domain/BlazorShop.Domain.csproj:19

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

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

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

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

  • `OrderHandler.CreateOrderCommandHandler.Handle` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — BlazorShop.Application/Handlers/Commands/OrderHandler/CreateOrderCommandHandler.cs:40

What to do

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

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

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

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

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — BlazorShop.Infrastructure/Files/Maps/TodoItemRecordMap.cs:23, BlazorShop.Infrastructure/Persistence/ApplicationDbContext.cs:115, REDACTED:102
  • 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — REDACTED:236
  • 9 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — REDACTED:240

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 7 of 7 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — 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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

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.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
M4 · Documentation accuracy10.0 / 10Exemplary◐ 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.

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.

P2 · Observability7.4 / 10Strong✓ 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.

  • `REDACTED` reports through `Console.Write…` at line 65 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:65
  • `REDACTED` reports through `Console.Write…` at line 92 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:92
  • `REDACTED` reports through `Console.Write…` at line 141 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:141
  • `REDACTED` reports through `Console.Write…` at line 258 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:258

What to do

  • Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
  • Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

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

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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("https://localhost:44351/api/"), }` 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.WebClient/Program.cs:15
  • `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. 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.WorkerService/Program.cs:13

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

P9 · Domain vs controller coverage1.9 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.

Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.

  • Domain coverage is 11%, against a bar of 50% for this row — the layer carrying the business rules is the least covered part of the codebase that matters most. Measured over the types this analyzer classifies as domain (aggregates, value objects, domain services), so code the classifier does not place in the domain is neither counted for nor against this figure.

What to do

  • Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.
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.

S1 · Web-Security Posture7.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: Permissions-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.0 on this card.) — BlazorShop.WebApi/Program.cs:158
  • UseAuthorization appears before UseAuthentication — authorization runs without an authenticated principal. — BlazorShop.WebApi/Program.cs:145

What to do

  • Add Content-Security-Policy, Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
  • Order the pipeline so UseAuthentication precedes UseAuthorization.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

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.

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.

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.

X18 · Disposal-pattern correctness5.5 / 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.

  • `att` is a `Attachment`, which implements `IDisposable`, and it is created here (line 59). Every use of it in `AddImageLogo` 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 att = …;`), which releases it at the end of the scope on every path including a throw. — BlazorShop.Infrastructure/Services/EmailService.cs:59

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

X2 · Cancellation propagation5.8 / 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 66/224 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.WebClient/Auth/AuthenticationService.cs:52, BlazorShop.WebClient/Auth/AuthenticationService.cs:89, BlazorShop.WebClient/Auth/AuthenticationService.cs:130, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.

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.

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.

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.

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

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

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

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.

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.

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.

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.

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.

X3 · Exception handling6.0 / 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/Validators/AccountValidator/LoginCommandValidator.cs:42, BlazorShop.Application/Validators/AccountValidator/RegisterCommandValidator.cs:58, BlazorShop.Application/Validators/AccountValidator/ResetPasswordCommandValidator.cs:48, …
  • `catch (Exception)` 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.WebApi/Filters/JwtTokenMiddleware.cs:77

What to do

  • Swallowed exception (empty catch)
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.

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.

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

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

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

X5 · Nullable reference types10.0 / 10Exemplary○ Nothing flagged

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.

  • This method contradicts itself about `subscription`: line 220 assigns it with `as Subscription`, which hands back null rather than throwing when the value is not a `Subscription`, but line 222 then dereferences it directly as `subscription.LatestInvoiceId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `subscription` once before the first use and handle the null case, or cast with `(Subscription)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:222
  • This method contradicts itself about `sessionData`: line 270 assigns it with `as Session`, which hands back null rather than throwing when the value is not a `Session`, but line 272 then dereferences it directly as `sessionData.PaymentIntentId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `sessionData` once before the first use and handle the null case, or cast with `(Session)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:272

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement 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.

LensScoreRatingImpact
Code Health77%StrongSolid.
Architecture83%StrongSolid.
Maturity38%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness37%Weak — gated by D8, D12, D13, P7, P9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security60%Adequate — gated by D30, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling51%Adequate — gated by DM2, DM4, DM6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven100%ExemplaryStrongest area.
Accessibility50%AdequateAcceptable, with room to improve.
Performance100%ExemplarySolid.
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.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • 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 — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X8 JS interop contract — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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.

  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 25 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
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — The runtime tier booted this repository's service, but the service booted and answers HTTP at http://127.0.0.1:33849, but serves no HTML page — nothing for the accessibility crawl. This repository also has a user interface (43 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (18,942 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED3 Event naming — no domain or integration events detected — event-naming check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — 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 — 64 finding(s)
D17 · Explicit Debt · AnalyzerSeverityNone · ×13
  • AnalyzerSeverityNone .editorconfig:4 — CS8603 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:7 — CS8604 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:10 — CS8619 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:13 — CS8618 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:16 — CS8714 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:19 — IDE0008 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:22 — CS8602 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:25 — CA1822 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:28 — SYSLIB0022 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:31 — CA2208 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:34 — CS8600 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:37 — IDE0051 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:40 — CS8601 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×11
  • Domain depends on infrastructure: EntityBase BlazorShop.Domain/Common/EntityBase.cs:27 — `EntityBase` (domain layer) names `NotMappedAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Cart BlazorShop.Domain/Entities/Cart.cs:35 — `Cart` (domain layer) names `User` from `BlazorShop.Domain.Entities.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Role BlazorShop.Domain/Entities/Identity/Role.cs:10 — `Role` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleClaim BlazorShop.Domain/Entities/Identity/RoleClaim.cs:10 — `RoleClaim` (domain layer) names `IdentityRoleClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: User BlazorShop.Domain/Entities/Identity/User.cs:10 — `User` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: UserClaim BlazorShop.Domain/Entities/Identity/UserClaim.cs:10 — `UserClaim` (domain layer) names `IdentityUserClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: UserLogin BlazorShop.Domain/Entities/Identity/UserLogin.cs:10 — `UserLogin` (domain layer) names `IdentityUserLogin` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: UserRole BlazorShop.Domain/Entities/Identity/UserRole.cs:10 — `UserRole` (domain layer) names `IdentityUserRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: UserToken BlazorShop.Domain/Entities/Identity/UserToken.cs:10 — `UserToken` (domain layer) names `IdentityUserToken` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Subscriber BlazorShop.Domain/Entities/Subscriber.cs:45 — `Subscriber` (domain layer) names `User` from `BlazorShop.Domain.Entities.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: BlazorShop.Domain BlazorShop.Domain/BlazorShop.Domain.csproj:19 — The domain project `BlazorShop.Domain` references `Microsoft.AspNetCore.Identity.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it.
D30 · Dependency Vulnerabilities · High CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×6
  • EmptyCatchBlock BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:42 — 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.Application/Validators/AccountValidator/RegisterCommandValidator.cs:58 — 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.Application/Validators/AccountValidator/ResetPasswordCommandValidator.cs:48 — 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.Application/Validators/UserValidator/CreateUserCommandValidator.cs:52 — 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.Application/Validators/UserValidator/GetUserByEmailQueryValidator.cs:37 — 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.Application/Validators/UserValidator/UpdateUserEmailCommandValidator.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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×2
  • <input> without a programmatic label BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:22 — 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.WebClient/Pages/Admin/Todos/TodoItems.razor:33 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang BlazorShop.WebApi/Views/Error.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang BlazorShop.WebApi/Views/Home.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document <title> is empty · ×2
  • Document <title> is empty BlazorShop.WebApi/Views/Error.html:2 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
  • Document <title> is empty BlazorShop.WebApi/Views/Home.html:2 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×2
  • Click handler on a non-interactive <div> BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:27 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> BlazorShop.WebClient/Shared/NavMenu.razor:16 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC5 · ARIA correctness · aria-hidden hides a focusable element · ×2
  • aria-hidden hides a focusable element BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:44 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
  • aria-hidden hides a focusable element BlazorShop.WebClient/Pages/Admin/Todos/TodoLists.razor:25 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
D12 · Dependency Hygiene · Vulnerable · ×2
  • Vulnerable: System.IdentityModel.Tokens.Jwt — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: AutoMapper — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
D13 · Secret Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×1
  • <img> without a text alternative BlazorShop.WebClient/Pages/User/Profile.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.
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom BlazorShop.WebClient/wwwroot/index.html:5 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×1
  • Click handler on a non-interactive <li> BlazorShop.WebClient/Pages/Admin/Todos/TodoLists.razor:18 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AX1 · Captive dependencies · Captive dependency · ×1
  • Captive dependency: singleton Worker captures scoped HttpClient BlazorShop.WorkerService/Worker.cs:18 — `Worker` is registered as a SINGLETON but its constructor takes `HttpClient httpClient`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `HttpClient` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
D10 · Test Quality · Assertions commented out · ×1
  • Assertions commented out: ChangePasswordUserAsync_ShouldCallChangePasswordAsync_WhenAllConditionsAreMet BlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs:127 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 399 finding(s)
D8 · Code Coverage · Low coverage · ×205
  • Low coverage: BlazorShop.WorkerService/Worker.cs BlazorShop.WorkerService/Worker.cs:1 — 17.1% line coverage (6/35).
  • Low coverage: BlazorShop.WebClient/Services/AccountService.cs BlazorShop.WebClient/Services/AccountService.cs:1 — 12.2% line coverage (6/49).
  • Low coverage: BlazorShop.WebClient/Services/CartService.cs BlazorShop.WebClient/Services/CartService.cs:1 — 4.1% line coverage (6/148).
  • Low coverage: BlazorShop.WebClient/Services/ClotheService.cs BlazorShop.WebClient/Services/ClotheService.cs:1 — 6.5% line coverage (6/92).
  • Low coverage: BlazorShop.WebClient/Services/MusicService.cs BlazorShop.WebClient/Services/MusicService.cs:1 — 6.5% line coverage (6/92).
  • Low coverage: BlazorShop.WebClient/Services/OrderService.cs BlazorShop.WebClient/Services/OrderService.cs:1 — 6.5% line coverage (6/92).
  • Low coverage: BlazorShop.WebClient/Services/ReceiptService.cs BlazorShop.WebClient/Services/ReceiptService.cs:1 — 6.5% line coverage (6/92).
  • Low coverage: BlazorShop.WebClient/Services/RoleService.cs BlazorShop.WebClient/Services/RoleService.cs:1 — 5.3% line coverage (6/113).
  • Low coverage: BlazorShop.WebClient/Services/SessionStorageService.cs BlazorShop.WebClient/Services/SessionStorageService.cs:1 — 22.2% line coverage (6/27).
  • Low coverage: BlazorShop.WebClient/Services/StripeService.cs BlazorShop.WebClient/Services/StripeService.cs:1 — 27.3% line coverage (6/22).
  • Low coverage: BlazorShop.WebClient/Services/SubscriberService.cs BlazorShop.WebClient/Services/SubscriberService.cs:1 — 5.6% line coverage (6/108).
  • Low coverage: BlazorShop.WebClient/Services/SubscriptionService.cs BlazorShop.WebClient/Services/SubscriptionService.cs:1 — 6.5% line coverage (6/92).
  • Low coverage: BlazorShop.WebClient/Services/TodoItemService.cs BlazorShop.WebClient/Services/TodoItemService.cs:1 — 7.7% line coverage (6/78).
  • Low coverage: BlazorShop.WebClient/Services/TodoListService.cs BlazorShop.WebClient/Services/TodoListService.cs:1 — 6.4% line coverage (6/94).
  • Low coverage: BlazorShop.WebClient/Services/UserService.cs BlazorShop.WebClient/Services/UserService.cs:1 — 3.8% line coverage (6/160).
  • Low coverage: BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor.cs BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor.cs:1 — 0.0% line coverage (0/60).
  • Low coverage: BlazorShop.WebClient/Pages/Admin/Todos/TodoLists.razor.cs BlazorShop.WebClient/Pages/Admin/Todos/TodoLists.razor.cs:1 — 0.0% line coverage (0/27).
  • Low coverage: BlazorShop.WebClient/Interceptor/HttpInterceptorService.cs BlazorShop.WebClient/Interceptor/HttpInterceptorService.cs:1 — 17.9% line coverage (5/28).
  • Low coverage: BlazorShop.WebClient/Interceptor/HttpResponseException.cs BlazorShop.WebClient/Interceptor/HttpResponseException.cs:1 — 0.0% line coverage (0/12).
  • Low coverage: BlazorShop.WebClient/AuthPolicies/AdminRoleHandler.cs BlazorShop.WebClient/AuthPolicies/AdminRoleHandler.cs:1 — 0.0% line coverage (0/11).
  • Low coverage: BlazorShop.WebClient/AuthPolicies/AdminRoleRequirement.cs BlazorShop.WebClient/AuthPolicies/AdminRoleRequirement.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: BlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs BlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs:1 — 0.0% line coverage (0/16).
  • Low coverage: BlazorShop.WebClient/AuthPolicies/CustomerRoleRequirement.cs BlazorShop.WebClient/AuthPolicies/CustomerRoleRequirement.cs:1 — 0.0% line coverage (0/8).
  • Low coverage: BlazorShop.WebClient/AuthPolicies/DefaultRoleHandler.cs BlazorShop.WebClient/AuthPolicies/DefaultRoleHandler.cs:1 — 0.0% line coverage (0/11).
  • Low coverage: BlazorShop.WebClient/AuthPolicies/DefaultRoleRequirement.cs BlazorShop.WebClient/AuthPolicies/DefaultRoleRequirement.cs:1 — 0.0% line coverage (0/5).
  • + 180 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: Login BlazorShop.WebClient/Auth/AuthenticationService.cs:52 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Register BlazorShop.WebClient/Auth/AuthenticationService.cs:89 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Logout BlazorShop.WebClient/Auth/AuthenticationService.cs:130 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteList BlazorShop.WebClient/Pages/Admin/Todos/TodoState.razor.cs:83 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ChangePassword BlazorShop.WebClient/Services/AccountService.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ResetPassword BlazorShop.WebClient/Services/AccountService.cs:64 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddCart BlazorShop.WebClient/Services/CartService.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteCart BlazorShop.WebClient/Services/CartService.cs:64 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: EmptyCart BlazorShop.WebClient/Services/CartService.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCart BlazorShop.WebClient/Services/CartService.cs:112 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCartCounts BlazorShop.WebClient/Services/CartService.cs:134 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCarts BlazorShop.WebClient/Services/CartService.cs:161 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateCart BlazorShop.WebClient/Services/CartService.cs:183 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Checkout BlazorShop.WebClient/Services/CartService.cs:207 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetClothes BlazorShop.WebClient/Services/ClotheService.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetClothe BlazorShop.WebClient/Services/ClotheService.cs:62 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddClothe BlazorShop.WebClient/Services/ClotheService.cs:84 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateClothe BlazorShop.WebClient/Services/ClotheService.cs:108 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteClothe BlazorShop.WebClient/Services/ClotheService.cs:132 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetMusics BlazorShop.WebClient/Services/MusicService.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetMusic BlazorShop.WebClient/Services/MusicService.cs:62 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddMusic BlazorShop.WebClient/Services/MusicService.cs:84 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateMusic BlazorShop.WebClient/Services/MusicService.cs:108 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteMusic BlazorShop.WebClient/Services/MusicService.cs:132 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetOrders BlazorShop.WebClient/Services/OrderService.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
AC3 · Page structure · Heading level jumps from h1 to h4 · ×12
  • Heading level jumps from h1 to h4 BlazorShop.WebClient/Pages/Admin/Clothes/Clothes.razor:26 — 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 h4 BlazorShop.WebClient/Pages/Admin/Musics/Musics.razor:26 — 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 h4 BlazorShop.WebClient/Pages/Admin/Roles/Roles.razor:26 — 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 h4 BlazorShop.WebClient/Pages/Admin/Subscriptions/Subscriptions.razor:26 — 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 h4 BlazorShop.WebClient/Pages/Admin/Users/Users.razor:26 — 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 h4 BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:47 — 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 h4 BlazorShop.WebClient/Pages/Musics/Index.razor:141 — 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 h4 BlazorShop.WebClient/Pages/Musics/MusicDetails.razor:41 — 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 h4 BlazorShop.WebClient/Pages/Orders/MyOrders.razor:41 — 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 h4 BlazorShop.WebClient/Pages/Receipts/Receipts.razor:40 — 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 h4 BlazorShop.WebClient/Pages/Subscriptions/MySubscriptions.razor:92 — 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 h4 BlazorShop.WebClient/Pages/User/Profile.razor:35 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC2 · Forms & labels · <fieldset> without a <legend> · ×11
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Login.razor:21 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Login.razor:29 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Login.razor:41 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Register.razor:23 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Register.razor:31 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Register.razor:39 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Register.razor:47 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/Register.razor:55 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/ResetPassword.razor:22 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/ResetPassword.razor:30 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> BlazorShop.WebClient/Pages/Account/ResetPassword.razor:38 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
DM4 · Rich vs anemic model · Anemic entity · ×10
  • Anemic entity: Cart BlazorShop.Domain/Entities/Cart.cs:10 — `Cart` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Clothe BlazorShop.Domain/Entities/Clothe.cs:10 — `Clothe` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Invoice BlazorShop.Domain/Entities/Invoice.cs:10 — `Invoice` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Music BlazorShop.Domain/Entities/Music.cs:10 — `Music` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Order BlazorShop.Domain/Entities/Order.cs:10 — `Order` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Receipt BlazorShop.Domain/Entities/Receipt.cs:10 — `Receipt` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Subscriber BlazorShop.Domain/Entities/Subscriber.cs:10 — `Subscriber` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Subscription BlazorShop.Domain/Entities/Subscription.cs:10 — `Subscription` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: TodoItem BlazorShop.Domain/Entities/TodoItem.cs:10 — `TodoItem` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: TodoList BlazorShop.Domain/Entities/TodoList.cs:10 — `TodoList` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
D12 · Dependency Hygiene · Deprecated · ×6
  • Deprecated: Blazored.LocalStorage REDACTED:19 — Blazored.LocalStorage 4.3.0 — Legacy
  • Deprecated: Microsoft.IdentityModel.Tokens REDACTED:26 — Microsoft.IdentityModel.Tokens 6.27.0 — Legacy
  • Deprecated: System.IdentityModel.Tokens.Jwt REDACTED:35 — REDACTED — Legacy
  • Deprecated: FluentValidation.AspNetCore REDACTED:19 — FluentValidation.AspNetCore 11.2.2 — Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc.Abstractions REDACTED:23 — Microsoft.AspNetCore.Mvc.Abstractions 2.2.0 — Other,Legacy
  • Deprecated: xunit REDACTED:45 — xunit 2.4.2 — 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×6
  • Duplicated block (11 lines × 2) BlazorShop.WebClient/Services/CartService.cs:119 — BlazorShop.WebClient/Services/CartService.cs:119-129 | BlazorShop.WebClient/Services/CartService.cs:168-178 — 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. 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 (11 lines × 2) BlazorShop.WebClient/Services/ClotheService.cs:47 — BlazorShop.WebClient/Services/ClotheService.cs:47-57 | BlazorShop.WebClient/Services/ClotheService.cs:69-79 — 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. 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 (11 lines × 2) BlazorShop.WebClient/Services/MusicService.cs:47 — BlazorShop.WebClient/Services/MusicService.cs:47-57 | BlazorShop.WebClient/Services/MusicService.cs:69-79 — 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. 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 (11 lines × 2) BlazorShop.WebClient/Services/OrderService.cs:47 — BlazorShop.WebClient/Services/OrderService.cs:47-57 | BlazorShop.WebClient/Services/OrderService.cs:69-79 — 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. 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 (11 lines × 2) BlazorShop.WebClient/Services/ReceiptService.cs:47 — BlazorShop.WebClient/Services/ReceiptService.cs:47-57 | BlazorShop.WebClient/Services/ReceiptService.cs:69-79 — 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. 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 (11 lines × 2) BlazorShop.WebClient/Services/SubscriptionService.cs:47 — BlazorShop.WebClient/Services/SubscriptionService.cs:47-57 | BlazorShop.WebClient/Services/SubscriptionService.cs:69-79 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×6
  • Duplicated block (5 lines × 2) BlazorShop.Application/Validators/ClotheValidator/CreateClotheCommandValidator.cs:60 — BlazorShop.Application/Validators/ClotheValidator/CreateClotheCommandValidator.cs:60-64 | BlazorShop.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:63-67 — 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 (5 lines × 2) BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:53 — BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:53-57 | BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:56-60 — before extracting anything, compare `BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs` and `BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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.
  • Duplicated block (5 lines × 2) BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:70 — BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:70-74 | BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs:70-74 — before extracting anything, compare `BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs` and `BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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.
  • Duplicated block (5 lines × 2) BlazorShop.Application/Validators/OrderValidator/GetOrdersQueryValidator.cs:17 — BlazorShop.Application/Validators/OrderValidator/GetOrdersQueryValidator.cs:17-21 | BlazorShop.Application/Validators/ReceiptValidator/GetReceiptsQueryValidator.cs:17-21 — 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 (5 lines × 2) BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:58 — BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:58-62 | BlazorShop.Application/Validators/TodoItemValidator/UpdateTodoItemCommandValidator.cs:59-63 — 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 (5 lines × 2) BlazorShop.Application/Validators/TodoListValidator/CreateTodoListCommandValidator.cs:42 — BlazorShop.Application/Validators/TodoListValidator/CreateTodoListCommandValidator.cs:42-46 | BlazorShop.Application/Validators/TodoListValidator/UpdateTodoListCommandValidator.cs:42-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 both call sites, so a change lands once.
X3 · Exception handling · Swallowed exception (empty catch) · ×6
  • Swallowed exception (empty catch) BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:42 — 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.Application/Validators/AccountValidator/RegisterCommandValidator.cs:58 — 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.Application/Validators/AccountValidator/ResetPasswordCommandValidator.cs:48 — 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.Application/Validators/UserValidator/CreateUserCommandValidator.cs:52 — 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.Application/Validators/UserValidator/GetUserByEmailQueryValidator.cs:37 — 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.Application/Validators/UserValidator/UpdateUserEmailCommandValidator.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.
D17 · Explicit Debt · CommentedOutCode · ×5
  • CommentedOutCode BlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs:94 — 4 consecutive commented-code lines
  • CommentedOutCode BlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs:112 — 4 consecutive commented-code lines
  • CommentedOutCode BlazorShop.UnitTests/Infrastructure/AccountServiceTests.cs:130 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:236 — 3 consecutive commented-code lines
  • CommentedOutCode REDACTED:240 — 9 consecutive commented-code lines
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×4
  • Animation without a prefers-reduced-motion guard BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:129 — `.product-img` moves (`animation: fade-in 1s forwards 1`) 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.WebClient/Pages/Clothes/ClotheDetails.razor:157 — `.product-listing` moves (`animation: fade-in 1s forwards 1`) 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.WebClient/Pages/Musics/MusicDetails.razor:101 — `.product-img` moves (`animation: fade-in 1s forwards 1`) 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.WebClient/Pages/Musics/MusicDetails.razor:129 — `.product-listing` moves (`animation: fade-in 1s forwards 1`) 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D8 · Code Coverage · CRAP 30 · ×4
  • CRAP 30: UpdateCreatedSubscriberCommandHandler.Handle BlazorShop.Application/Handlers/Commands/SubscriberHandler/UpdateCreatedSubscriberCommandHandler.cs:47 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
  • CRAP 30: AdminRoleHandler.HandleRequirementAsync BlazorShop.WebClient/AuthPolicies/AdminRoleHandler.cs:18 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
  • CRAP 30: DefaultRoleHandler.HandleRequirementAsync BlazorShop.WebClient/AuthPolicies/DefaultRoleHandler.cs:18 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
  • CRAP 30: UserRoleHandler.HandleRequirementAsync BlazorShop.WebClient/AuthPolicies/UserRoleHandler.cs:18 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (1.0 · ×3
  • Low contrast Tailwind colour pair (1.0:1) BlazorShop.WebClient/Pages/Orders/MyOrders.razor:17 — 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.
  • Low contrast Tailwind colour pair (1.0:1) BlazorShop.WebClient/Pages/Receipts/Receipts.razor:16 — 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.
  • Low contrast Tailwind colour pair (1.0:1) BlazorShop.WebClient/Pages/Subscriptions/MySubscriptions.razor:20 — 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×3
  • Duplicated block (34 lines × 2) BlazorShop.Application/Commands/SubscriptionCommand/CreateSubscriptionCommand.cs:12 — BlazorShop.Application/Commands/SubscriptionCommand/CreateSubscriptionCommand.cs:12-45 | BlazorShop.Application/Commands/SubscriptionCommand/UpdateSubscriptionCommand.cs:12-45 — before extracting anything, compare `BlazorShop.Application/Commands/SubscriptionCommand/CreateSubscriptionCommand.cs` and `BlazorShop.Application/Commands/SubscriptionCommand/UpdateSubscriptionCommand.cs` as WHOLE FILES: 88% 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 (34 lines × 2) BlazorShop.Application/Commands/ClotheCommand/CreateClotheCommand.cs:12 — BlazorShop.Application/Commands/ClotheCommand/CreateClotheCommand.cs:12-45 | BlazorShop.Domain/Entities/Clothe.cs:12-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (34 lines × 2) BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:23 — BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:23-56 | BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs:23-56 — before extracting anything, compare `BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs` and `BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:23` 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 (20 lines × 2) · ×3
  • Duplicated block (20 lines × 2) BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:20 — BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:20-39 | BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:23-42 — before extracting anything, compare `BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs` and `BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:20` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:20` calls `RuleFor`, `GreaterThan`, `WithMessage` and `BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:18` 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.
  • Duplicated block (20 lines × 2) BlazorShop.Application/Validators/ReceiptValidator/CreateReceiptCommandValidator.cs:17 — BlazorShop.Application/Validators/ReceiptValidator/CreateReceiptCommandValidator.cs:17-36 | BlazorShop.Application/Validators/ReceiptValidator/UpdateReceiptCommandValidator.cs:20-39 — 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.Application/Validators/ReceiptValidator/UpdateReceiptCommandValidator.cs:20` 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.
  • Duplicated block (20 lines × 2) BlazorShop.WebClient/Pages/Subscriptions/SubscriptionSuccess.razor:30 — BlazorShop.WebClient/Pages/Subscriptions/SubscriptionSuccess.razor:30-49 | BlazorShop.WebClient/Pages/Subscriptions/UpdateSubscriptionSuccess.razor:30-49 — before extracting anything, compare `BlazorShop.WebClient/Pages/Subscriptions/SubscriptionSuccess.razor` and `BlazorShop.WebClient/Pages/Subscriptions/UpdateSubscriptionSuccess.razor` 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. 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 (11 lines × 3) · ×3
  • Duplicated block (11 lines × 3) BlazorShop.WebClient/Services/RoleService.cs:95 — BlazorShop.WebClient/Services/RoleService.cs:95-105 | BlazorShop.WebClient/Services/RoleService.cs:117-127 | BlazorShop.WebClient/Services/RoleService.cs:139-149 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 (11 lines × 3) BlazorShop.WebClient/Services/SubscriberService.cs:47 — BlazorShop.WebClient/Services/SubscriberService.cs:47-57 | BlazorShop.WebClient/Services/SubscriberService.cs:69-79 | BlazorShop.WebClient/Services/SubscriberService.cs:91-101 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 (11 lines × 3) BlazorShop.WebClient/Services/UserService.cs:132 — BlazorShop.WebClient/Services/UserService.cs:132-142 | BlazorShop.WebClient/Services/UserService.cs:154-164 | BlazorShop.WebClient/Services/UserService.cs:176-186 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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.
AC3 · Page structure · Page without a main landmark · ×2
  • Page without a main landmark BlazorShop.WebApi/Views/Error.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark BlazorShop.WebApi/Views/Home.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure · Heading level jumps from h2 to h5 · ×2
  • Heading level jumps from h2 to h5 BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor:48 — 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.WebClient/Pages/Admin/Todos/TodoLists.razor:29 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) BlazorShop.WebClient/Pages/Musics/Index.razor:215 — BlazorShop.WebClient/Pages/Musics/Index.razor:215-233 | BlazorShop.WebClient/Pages/Subscriptions/MySubscriptions.razor:300-318 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BlazorShop.WebClient/Pages/Musics/Index.razor:215` 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 (19 lines × 2) BlazorShop.Application/Validators/SubscriberValidator/CreateSubscriberCommandValidator.cs:20 — BlazorShop.Application/Validators/SubscriberValidator/CreateSubscriberCommandValidator.cs:20-38 | BlazorShop.Application/Validators/SubscriberValidator/UpdateSubscriberCommandValidator.cs:20-38 — 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 (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) BlazorShop.Application/Validators/OrderValidator/CreateOrderCommandValidator.cs:17 — BlazorShop.Application/Validators/OrderValidator/CreateOrderCommandValidator.cs:17-34 | BlazorShop.Application/Validators/OrderValidator/UpdateOrderCommandValidator.cs:20-37 — 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.Application/Validators/OrderValidator/UpdateOrderCommandValidator.cs:20` 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.
  • Duplicated block (18 lines × 2) BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:26 — BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:26-43 | BlazorShop.Application/Validators/TodoItemValidator/UpdateTodoItemCommandValidator.cs:23-40 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BlazorShop.Application/Validators/TodoItemValidator/UpdateTodoItemCommandValidator.cs:42` calls `RuleFor`, `NotEmpty`, `WithMessage` and `BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:44` 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.WebClient/Services/RoleService.cs:117 — BlazorShop.WebClient/Services/RoleService.cs:117-129 | BlazorShop.WebClient/Services/RoleService.cs:139-151 — 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.WebClient/Services/RoleService.cs:117` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The 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.WebClient/Services/UserService.cs:154 — BlazorShop.WebClient/Services/UserService.cs:154-166 | BlazorShop.WebClient/Services/UserService.cs:176-188 — 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.WebClient/Services/UserService.cs:154` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:18 — BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:18-27 | BlazorShop.Application/Validators/TodoListValidator/CreateTodoListCommandValidator.cs:18-27 — 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 (10 lines × 2) BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:88 — BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:88-97 | BlazorShop.WebClient/Pages/Clothes/Index.razor:121-130 — 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 × 4) · ×2
  • Duplicated block (7 lines × 4) BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:27 — BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:27-33 | BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs:30-36 | BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs:28-34 | BlazorShop.Application/Validators/SubscriptionValidator/UpdateSubscriptionCommandValidator.cs:28-34 — before extracting anything, compare `BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs` and `BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 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.Application/Validators/CartValidator/CreateCartCommandValidator.cs:27` 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 (7 lines × 4) BlazorShop.Application/Validators/OrderValidator/GetOrderByIdQueryValidator.cs:17 — BlazorShop.Application/Validators/OrderValidator/GetOrderByIdQueryValidator.cs:17-23 | BlazorShop.Application/Validators/OrderValidator/UpdateOrderCommandValidator.cs:17-23 | BlazorShop.Application/Validators/ReceiptValidator/GetReceiptByIdQueryValidator.cs:17-23 | BlazorShop.Application/Validators/ReceiptValidator/UpdateReceiptCommandValidator.cs:17-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×2
  • Duplicated block (5 lines × 4) BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:23 — BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:23-27 | BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs:23-27 | BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:26-30 | BlazorShop.Application/Validators/TodoItemValidator/UpdateTodoItemCommandValidator.cs:23-27 — before extracting anything, compare `BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs` and `BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BlazorShop.Application/Validators/TodoItemValidator/CreateTodoItemCommandValidator.cs:23` calls `RuleFor`, `GreaterThan`, `WithMessage` and `BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:21` 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 (5 lines × 4) BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:51 — BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:51-55 | BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs:54-58 | BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs:64-68 | BlazorShop.Application/Validators/SubscriptionValidator/UpdateSubscriptionCommandValidator.cs:64-68 — before extracting anything, compare `BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs` and `BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×2
  • Duplicated block (7 lines × 3) BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:20 — BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:20-26 | BlazorShop.Application/Validators/OrderValidator/UpdateOrderCommandValidator.cs:17-23 | BlazorShop.Application/Validators/ReceiptValidator/UpdateReceiptCommandValidator.cs:17-23 — 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 (7 lines × 3) BlazorShop.WebClient/Pages/Account/Login.razor:66 — BlazorShop.WebClient/Pages/Account/Login.razor:66-72 | BlazorShop.WebClient/Pages/Account/Register.razor:82-88 | BlazorShop.WebClient/Pages/Account/ResetPassword.razor:65-71 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) BlazorShop.WebClient/Pages/Cart/Cart.razor:119 — BlazorShop.WebClient/Pages/Cart/Cart.razor:119-124 | BlazorShop.WebClient/Pages/Orders/MyOrders.razor:103-108 — 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 (6 lines × 2) BlazorShop.Application/Validators/CartValidator/DeleteCartCommandValidator.cs:17 — BlazorShop.Application/Validators/CartValidator/DeleteCartCommandValidator.cs:17-22 | BlazorShop.Application/Validators/CartValidator/GetCartByIdQueryValidator.cs:17-22 — 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.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience BlazorShop.WebClient/Program.cs:15 — `new HttpClient { BaseAddress = new Uri("https://localhost:44351/api/"), }` 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.WorkerService/Program.cs:13 — `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. 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).
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×2
  • Symbol treated as nullable, then dereferenced unguarded REDACTED:222 — This method contradicts itself about `subscription`: line 220 assigns it with `as Subscription`, which hands back null rather than throwing when the value is not a `Subscription`, but line 222 then dereferences it directly as `subscription.LatestInvoiceId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `subscription` once before the first use and handle the null case, or cast with `(Subscription)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded REDACTED:272 — This method contradicts itself about `sessionData`: line 270 assigns it with `as Session`, which hands back null rather than throwing when the value is not a `Session`, but line 272 then dereferences it directly as `sessionData.PaymentIntentId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `sessionData` once before the first use and handle the null case, or cast with `(Session)` so the failure is reported where it happens — rather than leaving the two readings side by side.
X8 · JS interop contract · Unresolved JS interop binding · ×2
  • Unresolved JS interop binding BlazorShop.WebClient/Services/SessionStorageService.cs:41 — `BlazorShop.getSessionStorage` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 0 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 45 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `BlazorShop.getSessionStorage`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding BlazorShop.WebClient/Services/SessionStorageService.cs:59 — `BlazorShop.setSessionStorage` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 0 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 45 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `BlazorShop.setSessionStorage`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 BlazorShop.WebClient/Pages/Admin/Users/Users.razor:144 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h1 to h5 · ×1
  • Heading level jumps from h1 to h5 BlazorShop.WebClient/Pages/Cart/Cart.razor:58 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics · Anchor without href · ×1
  • Anchor without href BlazorShop.WebClient/wwwroot/index.html:25 — 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.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 43 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.
D2 · Cognitive Complexity · AuthorizationBehaviour.Handle (cognitive 29) · ×1
  • AuthorizationBehaviour.Handle (cognitive 29) BlazorShop.Application/Common/Behaviours/AuthorizationBehaviour.cs:50 — AuthorizationBehaviour.Handle has cognitive complexity 29 (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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (39 lines × 3) · ×1
  • Duplicated block (39 lines × 3) BlazorShop.Application/Commands/MusicCommand/CreateMusicCommand.cs:12 — BlazorShop.Application/Commands/MusicCommand/CreateMusicCommand.cs:12-50 | BlazorShop.Application/Commands/MusicCommand/UpdateMusicCommand.cs:12-50 | BlazorShop.Application/Responses/MusicResponse.cs:12-50 — before extracting anything, compare `BlazorShop.Application/Commands/MusicCommand/CreateMusicCommand.cs` and `BlazorShop.Application/Commands/MusicCommand/UpdateMusicCommand.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 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. 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 (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) BlazorShop.Application/Responses/SubscriptionResponse.cs:20 — BlazorShop.Application/Responses/SubscriptionResponse.cs:20-60 | BlazorShop.Domain/Entities/Subscription.cs:15-55 — 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 (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) REDACTED:37 — REDACTED:37-68 | REDACTED:113-144 — 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 `REDACTED:113` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `req` to `CreateSubscriberCommand` in one and `UpdateSubscriberCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (31 lines × 4) · ×1
  • Duplicated block (31 lines × 4) BlazorShop.Application/Commands/MusicCommand/CreateMusicCommand.cs:20 — BlazorShop.Application/Commands/MusicCommand/CreateMusicCommand.cs:20-50 | BlazorShop.Application/Commands/MusicCommand/UpdateMusicCommand.cs:20-50 | BlazorShop.Application/Responses/MusicResponse.cs:20-50 | BlazorShop.Domain/Entities/Music.cs:15-45 — before extracting anything, compare `BlazorShop.Application/Commands/MusicCommand/CreateMusicCommand.cs` and `BlazorShop.Application/Commands/MusicCommand/UpdateMusicCommand.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 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. 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 (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) BlazorShop.Application/Commands/SubscriberCommand/CreateSubscriberCommand.cs:12 — BlazorShop.Application/Commands/SubscriberCommand/CreateSubscriberCommand.cs:12-40 | BlazorShop.Application/Commands/SubscriberCommand/UpdateSubscriberCommand.cs:12-40 — before extracting anything, compare `BlazorShop.Application/Commands/SubscriberCommand/CreateSubscriberCommand.cs` and `BlazorShop.Application/Commands/SubscriberCommand/UpdateSubscriberCommand.cs` as WHOLE FILES: 87% 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 (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) BlazorShop.WebClient/Auth/AuthenticationService.cs:61 — BlazorShop.WebClient/Auth/AuthenticationService.cs:61-86 | BlazorShop.WebClient/Auth/AuthenticationService.cs:102-127 — 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.WebClient/Auth/AuthenticationService.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs:23 — BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs:23-47 | BlazorShop.Application/Validators/SubscriptionValidator/UpdateSubscriptionCommandValidator.cs:23-47 — before extracting anything, compare `BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs` and `BlazorShop.Application/Validators/SubscriptionValidator/UpdateSubscriptionCommandValidator.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:23 — BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:23-37 | BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs:26-40 — before extracting anything, compare `BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs` and `BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 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.Application/Validators/CartValidator/CreateCartCommandValidator.cs:23` 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 (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) BlazorShop.Application/Validators/AccountValidator/RegisterCommandValidator.cs:23 — BlazorShop.Application/Validators/AccountValidator/RegisterCommandValidator.cs:23-31 | BlazorShop.Application/Validators/UserValidator/CreateUserCommandValidator.cs:23-31 | BlazorShop.Application/Validators/UserValidator/UpdateUserCommandValidator.cs:20-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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) BlazorShop.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:41 — BlazorShop.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:41-48 | BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:45-52 | BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs:45-52 | BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs:42-49 | BlazorShop.Application/Validators/SubscriptionValidator/UpdateSubscriptionCommandValidator.cs:42-49 — before extracting anything, compare `BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs` and `BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:41` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BlazorShop.Application/Validators/MusicValidator/CreateMusicCommandValidator.cs:54` calls `RuleFor`, `GreaterThan`, `WithMessage` and `BlazorShop.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs:18 — BlazorShop.Application/Validators/MusicValidator/UpdateMusicCommandValidator.cs:18-27 | BlazorShop.Application/Validators/TodoItemValidator/UpdateTodoItemCommandValidator.cs:18-27 | BlazorShop.Application/Validators/TodoListValidator/UpdateTodoListCommandValidator.cs:18-27 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×1
  • Duplicated block (9 lines × 7) BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:24 — BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:24-32 | BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs:27-35 | BlazorShop.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:21-29 | BlazorShop.Application/Validators/InvoiceValidator/CreateInvoiceCommandValidator.cs:23-31 | BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:26-34 | BlazorShop.Application/Validators/SubscriptionValidator/CreateSubscriptionCommandValidator.cs:25-33 | BlazorShop.Application/Validators/SubscriptionValidator/UpdateSubscriptionCommandValidator.cs:25-33 — before extracting anything, compare `BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs` and `BlazorShop.Application/Validators/CartValidator/UpdateCartCommandValidator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 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.Application/Validators/CartValidator/CreateCartCommandValidator.cs:24` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BlazorShop.Application/Validators/CartValidator/CreateCartCommandValidator.cs:20` calls `RuleFor`, `GreaterThan`, `WithMessage` and `BlazorShop.Application/Validators/ClotheValidator/UpdateClotheCommandValidator.cs:18` 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 × 3) · ×1
  • Duplicated block (5 lines × 3) BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:17 — BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:17-21 | BlazorShop.Application/Validators/AccountValidator/RegisterCommandValidator.cs:17-21 | BlazorShop.Application/Validators/UserValidator/CreateUserCommandValidator.cs:17-21 — 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:20 — BlazorShop.Application/Validators/InvoiceValidator/UpdateInvoiceCommandValidator.cs:20-26 | BlazorShop.Application/Validators/OrderValidator/GetOrderByIdQueryValidator.cs:17-23 | BlazorShop.Application/Validators/OrderValidator/UpdateOrderCommandValidator.cs:17-23 | BlazorShop.Application/Validators/ReceiptValidator/GetReceiptByIdQueryValidator.cs:17-23 | BlazorShop.Application/Validators/ReceiptValidator/UpdateReceiptCommandValidator.cs:17-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:64 — BlazorShop.WebClient/Pages/Clothes/ClotheDetails.razor:64-69 | BlazorShop.WebClient/Pages/Musics/Index.razor:185-190 | BlazorShop.WebClient/Pages/User/Profile.razor:219-224 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×1
  • Duplicated block (12 lines × 6) BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:36 — BlazorShop.Application/Validators/AccountValidator/LoginCommandValidator.cs:36-47 | BlazorShop.Application/Validators/AccountValidator/RegisterCommandValidator.cs:52-63 | BlazorShop.Application/Validators/AccountValidator/ResetPasswordCommandValidator.cs:42-53 | BlazorShop.Application/Validators/UserValidator/CreateUserCommandValidator.cs:46-57 | BlazorShop.Application/Validators/UserValidator/GetUserByEmailQueryValidator.cs:31-42 | BlazorShop.Application/Validators/UserValidator/UpdateUserEmailCommandValidator.cs:41-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 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.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net7.0 BlazorShop.WorkerService/BlazorShop.WorkerService.csproj:4 — BlazorShop.WorkerService/BlazorShop.WorkerService.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D8 · Code Coverage · CRAP 132 · ×1
  • CRAP 132: AuthorizationBehaviour.Handle BlazorShop.Application/Common/Behaviours/AuthorizationBehaviour.cs:50 — Cyclomatic 11 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 72 · ×1
  • CRAP 72: CustomerRoleHandler.HandleRequirementAsync BlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs:18 — Cyclomatic 8 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 42 · ×1
  • CRAP 42: MappingProfile.ApplyMappingsFromAssemblyV2 BlazorShop.Application/Common/Mappings/MappingProfile.cs:41 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
ED5 · Idempotency · Non-idempotent mutation · ×1
  • Non-idempotent mutation: OrderHandler.CreateOrderCommandHandler.Handle BlazorShop.Application/Handlers/Commands/OrderHandler/CreateOrderCommandHandler.cs:40 — `OrderHandler.CreateOrderCommandHandler.Handle` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
P9 · Domain vs controller coverage · Low domain coverage · ×1
  • Low domain coverage — Domain coverage is 11%, against a bar of 50% for this row — the layer carrying the business rules is the least covered part of the codebase that matters most. Measured over the types this analyzer classifies as domain (aggregates, value objects, domain services), so code the classifier does not place in the domain is neither counted for nor against this figure.
S1 · Web-Security Posture · Middleware order · ×1
  • Middleware order BlazorShop.WebApi/Program.cs:145 — UseAuthorization appears before UseAuthentication — authorization runs without an authenticated principal.
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.
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:59 — `att` is a `Attachment`, which implements `IDisposable`, and it is created here (line 59). Every use of it in `AddImageLogo` 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 att = …;`), which releases it at the end of the scope on every path including a throw.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) BlazorShop.WebApi/Filters/JwtTokenMiddleware.cs:77 — `catch (Exception)` 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.
Minor — 531 finding(s)
D10 · Test Quality · No direct assertions · ×320
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/CreateCartCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/CreateCartCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/DeleteAllCartsCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/DeleteAllCartsCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/DeleteCartCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/DeleteCartCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/UpdateCartCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/CartHandler/UpdateCartCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/InvoiceHandler/CreateInvoiceCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/InvoiceHandler/CreateInvoiceCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/InvoiceHandler/DeleteInvoiceCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/InvoiceHandler/DeleteInvoiceCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/InvoiceHandler/UpdateInvoiceCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/InvoiceHandler/UpdateInvoiceCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/MusicHandler/CreateMusicCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/MusicHandler/CreateMusicCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/MusicHandler/DeleteMusicCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/MusicHandler/DeleteMusicCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/MusicHandler/UpdateMusicCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/MusicHandler/UpdateMusicCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/OrderHandler/CreateOrderCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/OrderHandler/CreateOrderCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/OrderHandler/DeleteOrderCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle_ThrowException BlazorShop.UnitTests/Application/Handlers/Commands/OrderHandler/DeleteOrderCommandHandlerTests.cs:63 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Handle BlazorShop.UnitTests/Application/Handlers/Commands/OrderHandler/UpdateOrderCommandHandlerTests.cs:53 — No conventional assertion call was detected, and 321 of 353 tests in `BlazorShop.UnitTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • + 295 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×150
  • Orphaned file BlazorShop.Application/Utils/ErrorsManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.Infrastructure/Services/UserService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/UserService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/CartService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.Infrastructure/Services/RoleService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebApi/Program.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.Infrastructure/Services/AccountService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/SubscriberService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/RoleService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/SubscriptionService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/TodoListService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/ReceiptService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/OrderService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/ClotheService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/MusicService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebApi/Controllers/UsersController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Auth/AuthenticationService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Services/TodoItemService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebClient/Pages/Admin/Todos/TodoItems.razor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebApi/Controllers/CartsController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.Application/Common/Behaviours/AuthorizationBehaviour.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.WebApi/Controllers/SubscribersController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.Infrastructure/Persistence/ApplicationDbContext.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BlazorShop.Application/Responses/SubscriberResponse.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 125 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×22
  • Outdated: Microsoft.AspNetCore.Components.Authorization REDACTED:23 — Microsoft.AspNetCore.Components.Authorization 7.0.3 → 10.0.13 available (referenced by BlazorShop.WebClient).
  • Outdated: Microsoft.AspNetCore.Components.WebAssembly REDACTED:24 — Microsoft.AspNetCore.Components.WebAssembly 7.0.3 → 10.0.13 available (referenced by BlazorShop.WebClient).
  • Outdated: Microsoft.AspNetCore.Components.WebAssembly.DevServer REDACTED:25 — Microsoft.AspNetCore.Components.WebAssembly.DevServer 7.0.3 → 10.0.13 available (referenced by BlazorShop.WebClient).
  • Outdated: MudBlazor REDACTED:27 — MudBlazor 6.0.7 → 9.11.0 available (referenced by BlazorShop.WebClient).
  • Outdated: Radzen.Blazor REDACTED:29 — Radzen.Blazor 3.14.2 → 12.1.5 available (referenced by BlazorShop.WebClient).
  • Outdated: Microsoft.EntityFrameworkCore REDACTED:19 — Microsoft.EntityFrameworkCore 7.0.3 → 10.0.13 available (referenced by BlazorShop.Application).
  • Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore BlazorShop.Domain/BlazorShop.Domain.csproj:19 — Microsoft.AspNetCore.Identity.EntityFrameworkCore 7.0.3 → 10.0.13 available (referenced by BlazorShop.Domain).
  • Outdated: CsvHelper REDACTED:17 — CsvHelper 30.0.1 → 33.1.0 available (referenced by BlazorShop.Infrastructure).
  • Outdated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:18 — Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore 7.0.3 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
  • Outdated: Microsoft.EntityFrameworkCore.InMemory REDACTED:19 — Microsoft.EntityFrameworkCore.InMemory 7.0.3 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:20 — Microsoft.EntityFrameworkCore.SqlServer 7.0.3 → 10.0.13 available (referenced by BlazorShop.Infrastructure).
  • Outdated: AutoMapper REDACTED:18 — REDACTED → 16.2.0 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:21 — Microsoft.AspNetCore.Authentication.JwtBearer 7.0.3 → 10.0.13 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.AspNetCore.Identity.UI REDACTED:22 — Microsoft.AspNetCore.Identity.UI 7.0.3 → 10.0.13 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:24 — Microsoft.EntityFrameworkCore.Tools 7.0.3 → 10.0.13 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.Extensions.Configuration.UserSecrets REDACTED:28 — Microsoft.Extensions.Configuration.UserSecrets 7.0.0 → 10.0.13 available (referenced by BlazorShop.WebApi).
  • Outdated: Serilog.AspNetCore REDACTED:30 — Serilog.AspNetCore 6.1.0 → 10.0.0 available (referenced by BlazorShop.WebApi).
  • Outdated: Stripe.net REDACTED:31 — Stripe.net 40.0.0 → 53.0.0 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.Extensions.Hosting BlazorShop.WorkerService/BlazorShop.WorkerService.csproj:18 — Microsoft.Extensions.Hosting 7.0.1 → 10.0.13 available (referenced by BlazorShop.WorkerService).
  • Outdated: coverlet.collector REDACTED:30 — coverlet.collector 3.2.0 → 10.1.0 available (referenced by BlazorShop.UnitTests).
  • Outdated: Microsoft.Extensions.Http.Polly REDACTED:35 — Microsoft.Extensions.Http.Polly 7.0.3 → 10.0.13 available (referenced by BlazorShop.UnitTests).
  • Outdated: Moq.EntityFrameworkCore REDACTED:38 — Moq.EntityFrameworkCore 7.0.0.2 → 10.0.0.2 available (referenced by BlazorShop.UnitTests).
DM5 · Encapsulated state · Mutable entity · ×10
  • Mutable entity: Cart BlazorShop.Domain/Entities/Cart.cs:10 — `Cart` exposes publicly writable state (Name, Price, Amount, Clothe, User).
  • Mutable entity: Clothe BlazorShop.Domain/Entities/Clothe.cs:10 — `Clothe` exposes publicly writable state (Name, Description, Price, Amount, ImageName, ImagePath, and 1 more).
  • Mutable entity: Invoice BlazorShop.Domain/Entities/Invoice.cs:10 — `Invoice` exposes publicly writable state (UserEmail, Name, AmountSubTotal, AmountTotal, Quantity).
  • Mutable entity: Music BlazorShop.Domain/Entities/Music.cs:10 — `Music` exposes publicly writable state (Title, Description, Author, DateRelease, ImageName, ImagePath, and 1 more).
  • Mutable entity: Order BlazorShop.Domain/Entities/Order.cs:10 — `Order` exposes publicly writable state (UserEmail, OrderName, OrderDate, LineItems, AmountTotal).
  • Mutable entity: Receipt BlazorShop.Domain/Entities/Receipt.cs:10 — `Receipt` exposes publicly writable state (UserEmail, ReceiptDate, ReceiptName, ReceiptUrl).
  • Mutable entity: Subscriber BlazorShop.Domain/Entities/Subscriber.cs:10 — `Subscriber` exposes publicly writable state (Status, DateStart, CurrentPeriodEnd, CurrentPeriodStart, StripeSubscriberSubscriptionId, HostedInvoiceUrl, and 2 more).
  • Mutable entity: Subscription BlazorShop.Domain/Entities/Subscription.cs:10 — `Subscription` exposes publicly writable state (StripeSubscriptionId, Name, Price, Currency, CurrencySymbol, ChargeType, and 3 more).
  • Mutable entity: TodoItem BlazorShop.Domain/Entities/TodoItem.cs:10 — `TodoItem` exposes publicly writable state (Title, Note, Priority, State, Done, List).
  • Mutable entity: TodoList BlazorShop.Domain/Entities/TodoList.cs:10 — `TodoList` exposes publicly writable state (Title, Items).
IC1 · Incompleteness & stubs · Commented-out code · ×5
  • Commented-out code BlazorShop.Infrastructure/Files/Maps/TodoItemRecordMap.cs:23 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BlazorShop.Infrastructure/Persistence/ApplicationDbContext.cs:115 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:102 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:236 — 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:240 — 9 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
X10 · Duplicated predicate · Duplicated predicate · ×5
  • Duplicated predicate BlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs:22 — `c.Type == StringRoleResources.RoleClaim && c.Value == StringRoleResources.Default` appears character-identically in 2 files — BlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs, BlazorShop.WebClient/AuthPolicies/DefaultRoleHandler.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.WebClient/AuthPolicies/CustomerRoleHandler.cs:23 — `c.Type == StringRoleResources.RoleClaim && c.Value == StringRoleResources.User` appears character-identically in 2 files — BlazorShop.WebClient/AuthPolicies/CustomerRoleHandler.cs, BlazorShop.WebClient/AuthPolicies/UserRoleHandler.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/Handlers/Commands/ClotheHandler/DeleteClotheCommandHandler.cs:48 — `d.Id == request.Id && d.IsActive == true` appears character-identically in 2 files — BlazorShop.Application/Handlers/Commands/ClotheHandler/DeleteClotheCommandHandler.cs, BlazorShop.Application/Handlers/Commands/ClotheHandler/UpdateClotheCommandHandler.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.WebClient/AuthPolicies/AdminRoleHandler.cs:24 — `userRole != null && userRole.Value.Equals(requirement.Role)` appears character-identically in 3 files — BlazorShop.WebClient/AuthPolicies/AdminRoleHandler.cs, BlazorShop.WebClient/AuthPolicies/DefaultRoleHandler.cs, BlazorShop.WebClient/AuthPolicies/UserRoleHandler.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/Handlers/Commands/CartHandler/DeleteCartCommandHandler.cs:48 — `x.Id == request.Id && x.User.Id == request.UserId` appears character-identically in 3 files — BlazorShop.Application/Handlers/Commands/CartHandler/DeleteCartCommandHandler.cs, BlazorShop.Application/Handlers/Commands/CartHandler/UpdateCartCommandHandler.cs, BlazorShop.Application/Handlers/Queries/CartHandler/GetCartByIdQueryHandler.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.
P2 · Observability · Console output used as the logging channel · ×4
  • Console output used as the logging channel REDACTED:65 — `REDACTED` reports through `Console.Write…` at line 65 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:92 — `REDACTED` reports through `Console.Write…` at line 92 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:141 — `REDACTED` reports through `Console.Write…` at line 141 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:258 — `REDACTED` reports through `Console.Write…` at line 258 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
DM2 · Strongly-typed ids · Primitive id on a domain type · ×2
  • Primitive id on a domain type: Subscriber.StripeSubscriberSubscriptionId BlazorShop.Domain/Entities/Subscriber.cs:35 — `Subscriber.StripeSubscriberSubscriptionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Subscription.StripeSubscriptionId BlazorShop.Domain/Entities/Subscription.cs:15 — `Subscription.StripeSubscriptionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
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 immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
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/`.
D21 · Naming Consistency · Inconsistent pluralization in response type naming. Most response types use the singular form of the entity name (e.g., UserResponse, MusicResponse, ReceiptResponse), but 'ClotheResponse' uses the singular form of a noun that is typically pluralized in this context (Clothes), or is grammatically awkward as a singular count noun without an article. Additionally, the entity type is 'Clothe' (singular) while the query is 'GetClothesQuery' (plural) and the service is 'ClotheService' (singular). The inconsistency lies in 'Clothe' vs the standard pattern of singular entity names mapping to singular response names, but 'Clothe' itself is non-standard compared to 'Music', 'User', etc. However, the most glaring inconsistency is between the entity name 'Clothe' and the query/service naming 'Clothes'/'Clothe'. Let's look closer. The entity is `BlazorShop.Domain.Entities.TodoItem` (Singular). The response is `TodoItemResponse` (Singular). The entity for clothing is not explicitly listed as a Type, but `ClotheResponse` exists. The query is `GetClothesQuery`. The service is `ClotheService`. The handler is `ClotheHandler`. The command is `CreateClotheCommand`. The entity name seems to be `Clothe` (singular, non-standard) or `Clothes` (plural, standard). Given `GetClothesQuery` uses plural, but `CreateClotheCommand` uses singular, there is an inconsistency in the entity name usage itself. But looking at the list, `ClotheResponse` is the outlier in terms of standard English noun usage if we assume the entity is 'Clothes'. If the entity is 'Clothe', it's consistent with 'Music' (singular). But 'Clothe' is a verb or a rare singular noun. 'Clothes' is the standard noun. The query `GetClothesQuery` suggests the domain concept is 'Clothes'. The command `CreateClotheCommand` suggests the domain concept is 'Clothe'. This is a naming inconsistency within the domain model itself. · ×1
  • Inconsistent pluralization in response type naming. Most response types use the singular form of the entity name (e.g., UserResponse, MusicResponse, ReceiptResponse), but 'ClotheResponse' uses the singular form of a noun that is typically pluralized in this context (Clothes), or is grammatically awkward as a singular count noun without an article. Additionally, the entity type is 'Clothe' (singular) while the query is 'GetClothesQuery' (plural) and the service is 'ClotheService' (singular). The inconsistency lies in 'Clothe' vs the standard pattern of singular entity names mapping to singular response names, but 'Clothe' itself is non-standard compared to 'Music', 'User', etc. However, the most glaring inconsistency is between the entity name 'Clothe' and the query/service naming 'Clothes'/'Clothe'. Let's look closer. The entity is `BlazorShop.Domain.Entities.TodoItem` (Singular). The response is `TodoItemResponse` (Singular). The entity for clothing is not explicitly listed as a Type, but `ClotheResponse` exists. The query is `GetClothesQuery`. The service is `ClotheService`. The handler is `ClotheHandler`. The command is `CreateClotheCommand`. The entity name seems to be `Clothe` (singular, non-standard) or `Clothes` (plural, standard). Given `GetClothesQuery` uses plural, but `CreateClotheCommand` uses singular, there is an inconsistency in the entity name usage itself. But looking at the list, `ClotheResponse` is the outlier in terms of standard English noun usage if we assume the entity is 'Clothes'. If the entity is 'Clothe', it's consistent with 'Music' (singular). But 'Clothe' is a verb or a rare singular noun. 'Clothes' is the standard noun. The query `GetClothesQuery` suggests the domain concept is 'Clothes'. The command `CreateClotheCommand` suggests the domain concept is 'Clothe'. This is a naming inconsistency within the domain model itself. — Standardize the entity name to 'Clothes' (plural noun) or 'Clothing' (mass noun). If 'Clothes', then `CreateClothesCommand`, `ClothesService`, `ClothesResponse`, `GetClothesQuery`. If 'Clothing', then `CreateClothingCommand`, `ClothingService`, `ClothingResponse`, `GetClothingQuery`. Currently, `GetClothesQuery` (plural) conflicts with `CreateClotheCommand` (singular/non-standard). (symbols: BlazorShop.Application.Responses.ClotheResponse, BlazorShop.Application.Responses.MusicResponse, BlazorShop.Application.Responses.ReceiptResponse, BlazorShop.Application.Responses.SubscriberResponse, BlazorShop.Application.Responses.SubscriptionResponse, BlazorShop.Application.Responses.TodoItemResponse, BlazorShop.Application.Responses.TodoListResponse, BlazorShop.Application.Responses.UserResponse, BlazorShop.Application.Responses.CartResponse, BlazorShop.Application.Responses.InvoiceResponse, BlazorShop.Application.Responses.RoleResponse)
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 7 project(s) overshoot their size bounds, lowering Project Cohesion to 7.1/10. The most over is `BlazorShop.Application` (10765 LoC, 256 public types across 72 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 151 of 151 significant files have no living knowledge — the codebase as a whole is dormant, not 151 separate risks. Counted over 151 of the 383 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D34 · Knowledge Freshness · Most significant orphaned file · ×1
  • Most significant orphaned file BlazorShop.Infrastructure/Persistence/ApplicationDbContextSeed.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 2 authored method(s) exceed the IL budget BlazorShop.Application/Responses/SubscriberResponse.cs:93 — 2 of 1014 first-party methods compile to oversized IL bodies (> 250 instructions); worst: BlazorShop.Application.Responses.SubscriberResponse.Mapping @ BlazorShop.Application/Responses/SubscriberResponse.cs:93, 409 IL instructions; that pulled this dimension to 10.0/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.
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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'.
S1 · Web-Security Posture · Security headers incomplete · ×1
  • Security headers incomplete BlazorShop.WebApi/Program.cs:158 — Set: Permissions-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.0 on this card.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 66/224 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.
Minor — 26 finding(s)
D12 · Dependency Hygiene · Outdated · ×19
  • Outdated: FluentValidation — FluentValidation 11.5.0 → 12.2.0 available (referenced by BlazorShop.WebClient).
  • Outdated: MatBlazor — MatBlazor 2.8.0 → 2.10.0 available (referenced by BlazorShop.WebClient).
  • Outdated: Microsoft.IdentityModel.Tokens — Microsoft.IdentityModel.Tokens 6.27.0 → 8.23.0 available (referenced by BlazorShop.WebClient).
  • Outdated: Polly — Polly 7.2.4 → 8.8.0 available (referenced by BlazorShop.WebClient).
  • Outdated: Serilog — Serilog 2.12.0 → 4.4.0 available (referenced by BlazorShop.WebClient).
  • Outdated: System.IdentityModel.Tokens.Jwt — REDACTED → 8.23.0 available (referenced by BlazorShop.WebClient).
  • Outdated: Toolbelt.Blazor.LoadingBar — Toolbelt.Blazor.LoadingBar 13.1.2 → 14.0.0 available (referenced by BlazorShop.WebClient).
  • Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection — AutoMapper.Extensions.Microsoft.DependencyInjection 12.0.0 → 12.0.1 available (referenced by BlazorShop.Application).
  • Outdated: FluentValidation.DependencyInjectionExtensions — FluentValidation.DependencyInjectionExtensions 11.5.0 → 12.2.0 available (referenced by BlazorShop.Application).
  • Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.2 → 13.0.4 available (referenced by BlazorShop.Application).
  • Outdated: MediatR — MediatR 12.0.1 → 14.2.0 available (referenced by BlazorShop.Domain).
  • Outdated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 11.2.2 → 11.3.1 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.AspNetCore.ApiAuthorization.IdentityServer — Microsoft.AspNetCore.ApiAuthorization.IdentityServer 7.0.3 → 7.0.20 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.AspNetCore.Mvc.Abstractions — Microsoft.AspNetCore.Mvc.Abstractions 2.2.0 → 2.3.13 available (referenced by BlazorShop.WebApi).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.5.0 → 18.11.0 available (referenced by BlazorShop.UnitTests).
  • Outdated: Moq — Moq 4.18.4 → 4.21.0 available (referenced by BlazorShop.UnitTests).
  • Outdated: System.Linq.Async — System.Linq.Async 6.0.1 → 7.0.1 available (referenced by BlazorShop.UnitTests).
  • Outdated: xunit — xunit 2.4.2 → 2.9.3 available (referenced by BlazorShop.UnitTests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.4.5 → 4.0.1 available (referenced by BlazorShop.UnitTests).
D19 · Documentation Quality · XML-doc coverage · ×6
  • XML-doc coverage: BlazorShop.WebClient REDACTED — BlazorShop.WebClient: 100 % XML-doc coverage (166/166).
  • XML-doc coverage: BlazorShop.Application REDACTED — BlazorShop.Application: 100 % XML-doc coverage (923/923).
  • XML-doc coverage: BlazorShop.Domain BlazorShop.Domain/BlazorShop.Domain.csproj — BlazorShop.Domain: 100 % XML-doc coverage (100/100).
  • XML-doc coverage: BlazorShop.Infrastructure REDACTED — BlazorShop.Infrastructure: 90 % XML-doc coverage (121/134).
  • XML-doc coverage: BlazorShop.WebApi REDACTED — BlazorShop.WebApi: 100 % XML-doc coverage (123/123).
  • XML-doc coverage: BlazorShop.WorkerService BlazorShop.WorkerService/BlazorShop.WorkerService.csproj — BlazorShop.WorkerService: 100 % XML-doc coverage (2/2).
D10 · Test Quality · Mock framework · ×1
  • Mock framework: Moq — BlazorShop.UnitTests 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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bffdd299067a43bfa78717492a8ebec0/history.json --exit-code 0 --source .0artifacts/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-bffdd299067a43bfa78717492a8ebec0/tree.json --exit-code 0 --source .0artifacts/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 .12artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list BlazorShop.sln package --vulnerable --include-transitive --format json16artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .1artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a161ad-7506-7f1a-a8fe-9d24dc06d647 · 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 — 39 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, 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 — 27 field(s)
  • LoginCommand.Email BlazorShop.Application/Commands/AccountCommand/LoginCommand.cs:15
  • RegisterCommand.Email BlazorShop.Application/Commands/AccountCommand/RegisterCommand.cs:15
  • ResetPasswordCommand.Email BlazorShop.Application/Commands/AccountCommand/ResetPasswordCommand.cs:15
  • CreateInvoiceCommand.UserEmail BlazorShop.Application/Commands/InvoiceCommand/CreateInvoiceCommand.cs:15
  • UpdateInvoiceCommand.UserEmail BlazorShop.Application/Commands/InvoiceCommand/UpdateInvoiceCommand.cs:20
  • CreateOrderCommand.UserEmail BlazorShop.Application/Commands/OrderCommand/CreateOrderCommand.cs:15
  • UpdateOrderCommand.UserEmail BlazorShop.Application/Commands/OrderCommand/UpdateOrderCommand.cs:20
  • CreateReceiptCommand.UserEmail BlazorShop.Application/Commands/ReceiptCommand/CreateReceiptCommand.cs:15
  • UpdateReceiptCommand.UserEmail BlazorShop.Application/Commands/ReceiptCommand/UpdateReceiptCommand.cs:20
  • UpdateCreatedSubscriberCommand.CustomerEmail BlazorShop.Application/Commands/SubscriberCommand/UpdateCreatedSubscriberCommand.cs:25
  • CreateUserCommand.Email BlazorShop.Application/Commands/UserCommand/CreateUserCommand.cs:15
  • UpdateUserEmailCommand.Email BlazorShop.Application/Commands/UserCommand/UpdateUserEmailCommand.cs:20
  • UpdateUserEmailCommand.NewEmail BlazorShop.Application/Commands/UserCommand/UpdateUserEmailCommand.cs:25
  • GetOrderByIdQuery.UserEmail BlazorShop.Application/Queries/OrderQuery/GetOrderByIdQuery.cs:20
  • GetOrdersQuery.UserEmail BlazorShop.Application/Queries/OrderQuery/GetOrdersQuery.cs:15
  • GetReceiptByIdQuery.UserEmail BlazorShop.Application/Queries/ReceiptQuery/GetReceiptByIdQuery.cs:20
  • GetReceiptsQuery.UserEmail BlazorShop.Application/Queries/ReceiptQuery/GetReceiptsQuery.cs:15
  • GetUserByEmailQuery.Email BlazorShop.Application/Queries/UserQuery/GetUserByEmailQuery.cs:15
  • InvoiceResponse.UserEmail BlazorShop.Application/Responses/InvoiceResponse.cs:20
  • OrderResponse.UserEmail BlazorShop.Application/Responses/OrderResponse.cs:20
  • ReceiptResponse.UserEmail BlazorShop.Application/Responses/ReceiptResponse.cs:20
  • SubscriberResponse.CustomerEmail BlazorShop.Application/Responses/SubscriberResponse.cs:65
  • UserResponse.Email BlazorShop.Application/Responses/UserResponse.cs:25
  • Invoice.UserEmail BlazorShop.Domain/Entities/Invoice.cs:15
  • Order.UserEmail BlazorShop.Domain/Entities/Order.cs:15
  • Receipt.UserEmail BlazorShop.Domain/Entities/Receipt.cs:15
  • AdminSeedModel.Email BlazorShop.Infrastructure/Utils/AdminSeedModel.cs:30
Name — 12 field(s)
  • RegisterCommand.FirstName BlazorShop.Application/Commands/AccountCommand/RegisterCommand.cs:20
  • RegisterCommand.LastName BlazorShop.Application/Commands/AccountCommand/RegisterCommand.cs:25
  • CreateUserCommand.FirstName BlazorShop.Application/Commands/UserCommand/CreateUserCommand.cs:20
  • CreateUserCommand.LastName BlazorShop.Application/Commands/UserCommand/CreateUserCommand.cs:25
  • UpdateUserCommand.FirstName BlazorShop.Application/Commands/UserCommand/UpdateUserCommand.cs:20
  • UpdateUserCommand.LastName BlazorShop.Application/Commands/UserCommand/UpdateUserCommand.cs:25
  • UserResponse.FirstName BlazorShop.Application/Responses/UserResponse.cs:30
  • UserResponse.LastName BlazorShop.Application/Responses/UserResponse.cs:35
  • User.FirstName BlazorShop.Domain/Entities/Identity/User.cs:15
  • User.LastName BlazorShop.Domain/Entities/Identity/User.cs:20
  • AdminSeedModel.FirstName BlazorShop.Infrastructure/Utils/AdminSeedModel.cs:20
  • AdminSeedModel.LastName BlazorShop.Infrastructure/Utils/AdminSeedModel.cs:25

Issues: 64 · Warnings: 399 · Recommendations: 531 · Info: 26 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 03:35 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md