Public report of evgenirusev/Distributed-eStore, published 21 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, 21 October 2026, 20:58 UTC · Survey ID cd_984755b191524d8584e13ce5b35aeab3

evgenirusev/Distributed-eStore

Measured 21 October 2026, 20:49 UTC, at code version 2d77f2b

Code coverage: not measured

Code coverage is not measured: No coverage collector is wired up.

CAI score 33out 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.

Performance 100 Exemplary Architecture 77 Adequate Security and Compliance 61 Adequate Domain Modelling 52 Adequate Code Health 49 Weak Maturity 42 Weak Accessibility 37 Weak Production Readiness 20 Critical

A small codebase: 6,757 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 20

Findings by how serious they are

150 critical 198 serious 165 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
21 October 2026, 20:49 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 ▸

104of 108 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
461of 513 findings point to an exact file and line, so you can open each one in the code. The other 52 concern the repository as a whole, such as missing documentation.
108dimensions across 8 lenses, read from 6,757 lines of product code in 6 projects.
Chapters

Executive summary

evgenirusev/Distributed-eStore scores 33 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 20 and is rated Critical. Its Dependency Hygiene 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 8 Leaked secret finding(s) in Secret Scanning and to resolve the 3 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 33 to about 44.

150 findings are critical: 85 in Dependency Vulnerabilities, 17 in IaC & Container Security, ten in Forms & labels, eight in Explicit Debt, eight in Secret Scanning, five in Domain ↔ infrastructure boundary, four in Secrets (history), four in Text alternatives, three in Circular Imports, three in Dependency Hygiene, two in Keyboard semantics and one in Test Quality.

Watchdog couldn't measure Test Reliability, Naming Consistency and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 6,757 lines, which would take an estimated 0.1 person-years, around €6,700, to rebuild.

Code Health 49 Weak, capped by Structured logging and Nullable reference types Architecture 77 Adequate, capped by Circular Imports Maturity 42 Weak, capped by Knowledge Freshness and Documentation accuracy Production Readiness 20 ⚠ Critical, capped by Dependency Hygiene, Secret Scanning, CI/CD gates, Security & performance tooling and Outbound HTTP resilience Security and Compliance 61 Adequate, capped by Dependency Vulnerabilities and IaC & Container Security Domain Modelling 52 Adequate, capped by Strongly-typed ids, Encapsulated state and Domain ↔ infrastructure boundary Accessibility 37 Weak, capped by Text alternatives and Keyboard semantics 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 20 · counts for 45%Accessibility 37 · counts for 25%Maturity 42 · counts for 14%Code Health 49 · counts for 8%Domain Modelling 52 · counts for 4%Security and Compliance 61 · counts for 2%Architecture 77 · counts for 1%Performance 100 · counts for 1%

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

Code composition: what the lines of code are
Business logic 16%Supporting code 84%Tests 0%
New since the last survey: 69 findings

These 69 critical or serious findings weren't in the previous survey, on 6 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: 8 findings

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

  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Authentication.OpenIdConnect
  • Dependency Hygiene · Deprecated: OpenTracing.Contrib.NetCore
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs
Rebuild cost: about €6,700 · Estimate
Cost to rebuild€2,300 to €11,000, for 38 to 118 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemHigh, 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 33. 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: 6,757 lines of product code
Comment linesThe estimate prices 6,714 lines. Comment lines count towards the size of 6,757 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 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (8).
Raises the score by about 11 points · Low effort · Secret Scanning
2
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.
Raises the score by about 8 points · Low effort · Dependency Hygiene
3
Resolve the 30 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (19), REDACTED (3), Distributed-eStore.Services.Order.csproj (3).
Raises the score by about 11 points · Medium 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 €6,700 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 20 (Critical). 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 16 Domain Modelling findings · Common cause
16 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. 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 (3 findings) · Strongly-typed ids (13 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 8 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 11 points for low effort, because it clears the 8 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 Distributed-eStore.Api.Gateway Gateway Distributed-eStore.Common Common Distributed-eStore.Api.Gateway->Distributed-eStore.Common Distributed-eStore.Services.Identity Identity Distributed-eStore.Services.Identity->Distributed-eStore.Common Distributed-eStore.Services.Order Order Distributed-eStore.Services.Order->Distributed-eStore.Common Distributed-eStore.Services.Product Product Distributed-eStore.Services.Product->Distributed-eStore.Common Distributed-eStore.UI UI Distributed-eStore.UI->Distributed-eStore.Common

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.

82 modules, with 109 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; 42 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 Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes2 Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes3 Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes4 DistributedEStore.Common5 DistributedEStore.Common.Authentication6 DistributedEStore.Common.Commands.Identity7 DistributedEStore.Common.Messages8 DistributedEStore.Common.Models9 DistributedEStore.Common.Models.Products10 DistributedEStore.Common.Queries11 DistributedEStore.Common.Types12 Distributed-eStore_UI.src.ClientApp.src.state13 DistributedEStore.Api.Services14 DistributedEStore.Common.Dispatchers15 DistributedEStore.Common.Messages.Orders16 DistributedEStore.Common.Messages.Products17 DistributedEStore.Common.Mongo18 DistributedEStore.Common.RabbitMq19 DistributedEStore.Services.Identity.Domain20 DistributedEStore.Services.Identity.Messages.Commands21 DistributedEStore.Services.Orders.DomainEntities22 DistributedEStore.Services.Orders.Queries23 DistributedEStore.Services.Product.Queries24 DistributedEStore.Services.Products.DomainEntities25 DistributedEStore.Services.Products.Queries26 Distributed-eStore_UI.src.ClientApp.src.containers.Cart27 Distributed-eStore_UI.src.ClientApp.src.state.Products28 DistributedEStore.Api.Gateway29 DistributedEStore.Common.Handlers30 DistributedEStore.Common.Mvc31 DistributedEStore.Services.Identity.Repositories32 DistributedEStore.Services.Orders.Repositories33 DistributedEStore.Services.Products.Repositories34 DistributedEStore.UI.Controllers35 DistributedEStore.Api.Gateway.Controllers36 DistributedEStore.Services.Identity.Services37 DistributedEStore.Services.Orders.Handlers38 DistributedEStore.Services.Product.Controllers39 DistributedEStore.Services.Products.Handlers40 DistributedEStore.Services.Identity.Controllers
1 Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes
2 Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes
3 Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes
4 DistributedEStore.Common
5 DistributedEStore.Common.Authentication
6 DistributedEStore.Common.Commands.Identity
7 DistributedEStore.Common.Messages
8 DistributedEStore.Common.Models
9 DistributedEStore.Common.Models.Products
10 DistributedEStore.Common.Queries
11 DistributedEStore.Common.Types
12 Distributed-eStore_UI.src.ClientApp.src.state111
13 DistributedEStore.Api.Services243222
14 DistributedEStore.Common.Dispatchers4
15 DistributedEStore.Common.Messages.Orders1
16 DistributedEStore.Common.Messages.Products1
17 DistributedEStore.Common.Mongo14
18 DistributedEStore.Common.RabbitMq22
19 DistributedEStore.Services.Identity.Domain2
20 DistributedEStore.Services.Identity.Messages.Commands4
21 DistributedEStore.Services.Orders.DomainEntities2
22 DistributedEStore.Services.Orders.Queries2
23 DistributedEStore.Services.Product.Queries2
24 DistributedEStore.Services.Products.DomainEntities1
25 DistributedEStore.Services.Products.Queries1
26 Distributed-eStore_UI.src.ClientApp.src.containers.Cart21
27 Distributed-eStore_UI.src.ClientApp.src.state.Products21
28 DistributedEStore.Api.Gateway122
29 DistributedEStore.Common.Handlers22
30 DistributedEStore.Common.Mvc21
31 DistributedEStore.Services.Identity.Repositories24
32 DistributedEStore.Services.Orders.Repositories12
33 DistributedEStore.Services.Products.Repositories2122
34 DistributedEStore.UI.Controllers122123
35 DistributedEStore.Api.Gateway.Controllers12111131144
36 DistributedEStore.Services.Identity.Services62224
37 DistributedEStore.Services.Orders.Handlers1211122
38 DistributedEStore.Services.Product.Controllers12112
39 DistributedEStore.Services.Products.Handlers1111133
40 DistributedEStore.Services.Identity.Controllers22142
Uses a module listed above itPart of a loopThe module itself
1 Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes2 Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes3 Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes4 DistributedEStore.Common5 DistributedEStore.Common.Authentication6 DistributedEStore.Common.Commands.Identity7 DistributedEStore.Common.Messages8 DistributedEStore.Common.Models9 DistributedEStore.Common.Models.Products10 DistributedEStore.Common.Queries11 DistributedEStore.Common.Types12 Distributed-eStore_UI.src.ClientApp.src.state13 DistributedEStore.Api.Services14 DistributedEStore.Common.Dispatchers15 DistributedEStore.Common.Messages.Orders16 DistributedEStore.Common.Messages.Products17 DistributedEStore.Common.Mongo18 DistributedEStore.Common.RabbitMq19 DistributedEStore.Services.Identity.Domain20 DistributedEStore.Services.Identity.Messages.Commands21 DistributedEStore.Services.Orders.DomainEntities22 DistributedEStore.Services.Orders.Queries23 DistributedEStore.Services.Product.Queries24 DistributedEStore.Services.Products.DomainEntities25 DistributedEStore.Services.Products.Queries26 Distributed-eStore_UI.src.ClientApp.src.containers.Cart27 Distributed-eStore_UI.src.ClientApp.src.state.Products28 DistributedEStore.Api.Gateway29 DistributedEStore.Common.Handlers30 DistributedEStore.Common.Mvc31 DistributedEStore.Services.Identity.Repositories32 DistributedEStore.Services.Orders.Repositories33 DistributedEStore.Services.Products.Repositories34 DistributedEStore.UI.Controllers35 DistributedEStore.Api.Gateway.Controllers36 DistributedEStore.Services.Identity.Services37 DistributedEStore.Services.Orders.Handlers38 DistributedEStore.Services.Product.Controllers39 DistributedEStore.Services.Products.Handlers40 DistributedEStore.Services.Identity.ControllersDistributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes1Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes2Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes3DistributedEStore.Common4DistributedEStore.Common.Authentication5DistributedEStore.Common.Commands.Identity6DistributedEStore.Common.Messages7DistributedEStore.Common.Models8DistributedEStore.Common.Models.Products9DistributedEStore.Common.Queries10DistributedEStore.Common.Types11Distributed-eStore_UI.src.ClientApp.src.state12DistributedEStore.Api.Services13DistributedEStore.Common.Dispatchers14DistributedEStore.Common.Messages.Orders15DistributedEStore.Common.Messages.Products16DistributedEStore.Common.Mongo17DistributedEStore.Common.RabbitMq18DistributedEStore.Services.Identity.Domain19DistributedEStore.Services.Identity.Messages.Commands20DistributedEStore.Services.Orders.DomainEntities21DistributedEStore.Services.Orders.Queries22DistributedEStore.Services.Product.Queries23DistributedEStore.Services.Products.DomainEntities24DistributedEStore.Services.Products.Queries25Distributed-eStore_UI.src.ClientApp.src.containers.Cart26Distributed-eStore_UI.src.ClientApp.src.state.Products27DistributedEStore.Api.Gateway28DistributedEStore.Common.Handlers29DistributedEStore.Common.Mvc30DistributedEStore.Services.Identity.Repositories31DistributedEStore.Services.Orders.Repositories32DistributedEStore.Services.Products.Repositories33DistributedEStore.UI.Controllers34DistributedEStore.Api.Gateway.Controllers35DistributedEStore.Services.Identity.Services36DistributedEStore.Services.Orders.Handlers37DistributedEStore.Services.Product.Controllers38DistributedEStore.Services.Products.Handlers39DistributedEStore.Services.Identity.Controllers401112432224111422242221121211222221241221221221231211113114462224121112212112111113322142+42 more modules (most-connected shown)

At a glance — Code Health · 49% · Weak · gated by X4, X5 ·

The Good
D1 · .NET / C# Cyclomatic Complexity 9.7 D2 · .NET / C# Cognitive Complexity 10.0 D3 · .NET / C# God Classes 9.3 D4 · .NET / C# Code Duplication 9.4 D17 · .NET / C# Explicit Debt 7.7 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 8.8 R1 · React / TS Type Safety 9.8 R10 · React / TS Code Duplication 8.1 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 7.5 X1 · Repo Async correctness 7.2 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0
The Ugly
X2 · Repo Cancellation propagation 4.3 X4 · Repo Structured logging 2.5 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 77% · Adequate · gated by R9 ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D23 · .NET / C# Boundary Type-Coupling 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 8.9 D35 · .NET / C# Change Coupling 9.9 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 7.7 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX9 · Repo CQS / query purity 10.0
The Ugly
R9 · React / TS Circular Imports 3.7

At a glance — Maturity · 42% · Weak · gated by D34, M4 ·

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

At a glance — Readiness · 20% · Critical · gated by D12, D13, P1, P3, P7 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 R4 · React / TS Test Coverage 8.8 R8 · React / TS Dependency Hygiene 7.5
The Bad
D10 · .NET / C# Test Quality 6.2 P2 · Repo Observability 5.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0 R5 · React / TS Dependency Freshness 6.4 R6 · React / TS Tooling 6.7
The Ugly
D12 · .NET / C# Dependency Hygiene 0.0 D13 · .NET / C# Secret Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 61% · Adequate · gated by D30, D31 ·

The Good
D32 · .NET / C# Data Compliance (PII/GDPR) 9.0 D43 · .NET / C# Malicious Dependencies 10.0 C2 · Repo Access Controls 10.0 S1 · Repo Web-Security Posture 8.0 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
D28 · .NET / C# Secrets (history) 6.0 D29 · .NET / C# Static Analysis (SAST) 6.6 D44 · .NET / C# Platform End-of-Life 6.0 C4 · Repo Data Retention 6.5
The Ugly
D30 · .NET / C# Dependency Vulnerabilities 0.0 D31 · .NET / C# IaC & Container Security 2.6 C1 · Repo Data Protection 4.0

At a glance — Domain Modelling · 52% · Adequate · gated by DM2, DM5, 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 8.8 DM4 · Repo Rich vs anemic model 10.0 DM7 · Repo Repository granularity 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0
The Ugly
DM2 · Repo Strongly-typed ids 3.0 DM5 · Repo Encapsulated state 3.0 DM6 · Repo Domain ↔ infrastructure boundary 1.8

At a glance — Accessibility · 37% · Weak · gated by AC1, AC4 ·

The Good
AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0
The Bad
AC3 · Repo Page structure 5.2 AC7 · Repo A11y enforcement 6.0
The Ugly
AC1 · Repo Text alternatives 1.0 AC2 · Repo Forms & labels 4.9 AC4 · Repo Keyboard semantics 1.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 Failures130High / Critical
A02:2025 — Security Misconfiguration48High / Critical
A07:2025 — Authentication Failures13High / Critical
A05:2025 — Injection8Medium
A01:2025 — Broken Access Control1Medium

Roadmap

Begin by addressing the 30 deprecated dependencies, prioritizing the Distributed-eStore.Common project, followed by resolving the 8 leaked secrets found in REDACTED. Next, remediate the 3 vulnerable dependencies and update the 10 prerelease dependencies to ensure stability and security. Finally, fix the empty test in App.test.tsx to improve overall test quality and coverage.

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

Do thisHelpsEffortDimension
Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (8).+10.7 ptsLowSecret Scanning
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.+8.4 ptsLowDependency Hygiene
Resolve the 30 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (19), REDACTED (3), Distributed-eStore.Services.Order.csproj (3).+10.7 ptsMediumDependency Hygiene
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with App.test.tsx.+4.5 ptsLowTest Quality
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with App.test.tsx.+4.3 ptsLowTest Quality
Resolve the 10 Prerelease dependency finding(s) in Dependency Hygiene.+7.7 ptsMediumDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.9 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR.+3.4 ptsMediumCI/CD gates

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED3.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED3.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED3.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED4.0MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED4.3MixedDependency Vulnerabilities: High CVE: REDACTED
Distributed-eStore.UI/src/Distributed-eStore.UI.csproj4.9MixedPlatform End-of-Life: End-of-life runtime: .NET net5.0
Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs4.9MixedExplicit Debt: WriteOnlyPrivateField
REDACTED5.0MixedExplicit Debt: WriteOnlyPrivateField
Distributed-eStore.UI/src/Controllers/BaseController.cs5.5MixedExplicit Debt: WriteOnlyPrivateField
REDACTED5.5MixedExplicit Debt: WriteOnlyPrivateField

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

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

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

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. 104 of 108 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 108 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D17D18D19D20D23D24D26D27D28D29D30D31D32D34D35D39D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX5AX6AX9C1C2C4DM1DM10DM11DM12DM2DM4DM5DM6DM7DM8DM9ED5GD1IC1M1M2M3M4P1P2P3P4P6P7PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 461 of 513 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16039-fd26-7a1a-9bf7-9d1dd39008ae.

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.

  • D11 Test Reliability — 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. Test source is present (.tsx) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but the runner its test command uses is one the re-runner has no executor for (`react-scripts`). Read from the manifests: `Distributed-eStore.UI/src/ClientApp` has a `scripts.test` of `cross-env CI=true react-scripts test --env=jsdom` and declares `react-scripts`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's runner coverage, not a missing .tsx runner and not a finding about this repository.
  • D12 Dependency Hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones — manifest: REDACTED — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read it, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 310 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 'Distributed-eStore.UI/src/Distributed-eStore.UI.csproj' with message: The target framework 'net5.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
  • D21 Naming Consistency — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
  • 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. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — identity-service Error context canceled rabbitmq Error context canceled order-service Error context canceled consul Error context canceled fabio Error context canceled ui Error context canceled mongo Error context canceled api-gateway Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: ui Error Get "https://registry-1.docker.io/v2/": Forbidden order-service Error context canceled fabio Error context canceled consul Error context canceled product-service Error Get "https://registry-1.docker.io/v2/": Forbidden mongo Error context canceled api-gateway Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
  • 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. 44 further occurrence(s) are not listed individually; the score already reflects all 84.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • 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.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • 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.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D24, 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 Complexity9.7 / 10Stronggated by 1 serious finding✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RegisterPage.render at 18.

RegisterPage.render (cyclomatic 18)Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:58

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with RegisterPage.render (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

D3 · God Classes9.3 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 over-large unit(s) detected — types, modules or files that carry too much.

MethodTooLong: ProductsSeeder.GetProductsDistributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:28

What to do

  1. Resolve the 1 MethodTooLong finding(s) in God Classes — start with ProductsSeeder.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.4 / 10Stronggated by 8 serious findings✓ Tool-verified

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

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

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

8 duplicated block group(s) detected.

Duplicated block (11 lines × 2) · ×2REDACTED:18
Duplicated block (18 lines × 2)Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:46
Duplicated block (16 lines × 2)Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:112
Duplicated block (13 lines × 2)Distributed-eStore.Services.Order/src/Startup.cs:29
Duplicated block (7 lines × 3)Distributed-eStore.Common/Messages/Products/CreateProduct.cs:9

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

What to do

  1. Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with REDACTED, BaseController.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with BaseController.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with BaseController.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: 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

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

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality6.2 / 10Adequate✓ 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 6.2 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests.

No assertions (empty test): renders without crashingDistributed-eStore.UI/src/ClientApp/src/App.test.tsx:7
Test project verifies nothing: Distributed-eStore.UI/src/ClientAppDistributed-eStore.UI/src/ClientApp/src/App.test.tsx:7

What to do

  1. Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with App.test.tsx. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with App.test.tsx. — One of this dimension's main actionable groups (1 warning-level).
  3. Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene0.0 / 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 0.0 / 10 · rule-coverage 100% · ceiling Verified

32 outdated, 3 vulnerable, 22 deprecated, 10 prerelease packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.

Vulnerable: Microsoft.AspNetCore.Authentication.JwtBearer · ×3
Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer · ×30REDACTED:11
Prerelease dependency: RawRabbit · ×10
Outdated: Microsoft.AspNetCore.Authentication.JwtBearer · ×15REDACTED:79
Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets · ×17

What to do

  1. Resolve the 30 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (19), REDACTED (3), Distributed-eStore.Services.Order.csproj (3). — One of this dimension's main actionable groups (30 warning-level).
  2. Resolve the 3 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 10 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (10 warning-level).
  4. Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

8 secret(s) detected.

REDACTED

What to do

  1. Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
  2. Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward 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 260 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 43 direct `PackageReference`(s), and 207 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 Debt7.7 / 10Adequategated by 8 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 7.7 / 10 · rule-coverage 100% · ceiling Prevented

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

WriteOnlyPrivateField · ×8REDACTED:13
TodoCommentDistributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:21
CommentedOutCodeDistributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22

What to do

  1. Resolve the 8 WriteOnlyPrivateField finding(s) in Explicit Debt — start with BaseController.cs (4), REDACTED, MongoDbInitializer.cs. — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with BrowseOrdersHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with BrowseOrdersHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward 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

6 projects, 183 source files, 5145 hand-written lines of code (5145 production / 0 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), 5 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

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

The repository's root README gives an overview of the containerized .NET Core online store with microservices and React frontend, lists technologies used, and shows a local-run steps guide plus architecture-diagram placeholders. The UI/ClientApp README is a proper project README documenting that directory (the ClientApp directory), but it is a wall-of-text documentation for a client-side CRA app rather than the main repository; its content is not flagged as missing because it is internal-facing and does not fall under any of the named categories. There are no architecture/design docs, XML-doc coverage gaps, or licence statements in the visible text.

Documentation: hard to navigateDistributed-eStore.UI/src/ClientApp/README.md
XML-doc coverage: Distributed-eStore.Services.Identity · ×6REDACTED

What to do

  1. Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types leak across context boundaries (6 contexts).

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

12 valuable / 0 redundant across 15 sampled comments; 1 shown with locations.

misleading commentREDACTED:21

✓ On the Gold path — maintain.

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

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

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

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

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

0 of 6 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability8.9 / 10Strong✓ 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 8.9 / 10 · rule-coverage 100% · ceiling Documented

90 % of calls cross a namespace and 19 % go through an interface, but 96 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

Pass-through layerDistributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs:8

What to do

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

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

D28 · Secrets (history)6.0 / 10Adequate✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D30 · Dependency Vulnerabilities0.0 / 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

130 finding(s): 21 critical, 64 high, 37 medium, 8 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 63 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (56), REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (63 issue-level).
  2. Resolve the 20 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
  3. Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security2.6 / 10Weak✓ Tool-verified

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

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

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

48 finding(s): 0 critical, 17 high, 13 medium, 18 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 18 Low IaC finding(s) in IaC & Container Security — start with REDACTED (18). — One of this dimension's main actionable groups (18 recommendation-level).
  2. Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (17 issue-level).
  3. Resolve the 13 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED. — One of this dimension's main actionable groups (13 warning-level).

Detailed fixes: d31_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

21 of 21 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs. Counted over 21 of the 183 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×21Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:1
Dormant codebase

What to do

  1. Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with Startup.cs (5), Extensions.cs (4), BaseController.cs (2). — One of this dimension's main actionable groups (21 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Stronggated by 2 serious findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: CartProduct.tsx↔Cart.tsx 73%; productsActions.ts↔productsReducers.ts 54%

Change coupling: CartProduct.tsx ↔ Cart.tsx · ×2Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:1

What to do

  1. Resolve the 2 Change coupling finding(s) in Change Coupling — start with CartProduct.tsx, productsActions.ts. — One of this dimension's main actionable groups (2 warning-level).

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

1 of 408 first-party methods have an oversized IL body.

IL efficiency: 1 authored method(s) exceed the IL budgetDistributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:30

✓ On the Gold path — maintain.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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 6 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 net5.0Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Distributed-eStore.UI.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 alternatives1.0 / 10Critical✓ 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. (×4) — Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:25, Distributed-eStore.UI/src/ClientApp/src/components/products/Product/Product.tsx:26, Distributed-eStore.UI/src/ClientApp/src/containers/NavMenu/NavMenu.tsx:29, …

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 & labels4.9 / 10Weak✓ 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 link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×2) — Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:13, Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:45
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:37, Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:60, Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:67, …
  • This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16

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

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — Distributed-eStore.UI/src/ClientApp/public/index.html:2
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — Distributed-eStore.UI/src/ClientApp/src/components/OrderCreatedPage/OrderCreatedPage.tsx:7, Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:24

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 semantics1.0 / 10Critical✓ Tool-verified

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

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

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

  • The repo's own CSS styles .cart-products__button__text with `cursor: pointer`, so this <span> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProducts/CartProducts.tsx:39
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

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.

AC7 · A11y enforcement6.0 / 10Adequate✓ 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.

  • An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 27 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

  • Accessibility linting is already configured — assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition7.7 / 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, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.

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.

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

What to do

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

C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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 domain8.8 / 10Strong✓ Tool-verified

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.

  • `RefreshToken` reads `DateTime.UtcNow` inside `Revoke`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:28

What to do

  • Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
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.

  • `RefreshToken.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:10
  • `AccessTokenRefreshed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRefreshed.cs:9
  • `AccessTokenRevoked.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRevoked.cs:9
  • `PasswordChanged.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/PasswordChanged.cs:9
  • `RefreshAccessTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RefreshAccessTokenRejected.cs:9
  • `RefreshTokenRevoked.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RefreshTokenRevoked.cs:9
  • `RevokeAccessTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RevokeAccessTokenRejected.cs:9
  • `RevokeRefreshTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RevokeRefreshTokenRejected.cs:9
  • `SignedIn.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/SignedIn.cs:9
  • `SignedUp.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/SignedUp.cs:9
  • `SignUpRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/SignUpRejected.cs:9
  • `Order.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:8
  • `OrderItem.ProductId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:8

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 model10.0 / 10Exemplary✓ Tool-verified

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

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

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

DM5 · Encapsulated state3.0 / 10Weak✓ 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.

  • `Product` exposes publicly writable state (Name, Description, Price, Category, ImageURLs, Colors). — Distributed-eStore.Services.Product/src/DomainEntities/Product.cs:6
  • `Order` exposes publicly writable state (CustomerId, OrderItems). — Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:6
  • `OrderItem` exposes publicly writable state (ProductId, Quantity, Size). — Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:6

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 boundary1.8 / 10Critical✓ 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.

  • `RefreshToken` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:20, Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:38
  • `User` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Distributed-eStore.Services.Identity/src/Domain/User.cs:49, Distributed-eStore.Services.Identity/src/Domain/User.cs:59
  • `User` (domain layer) names `PasswordVerificationResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — Distributed-eStore.Services.Identity/src/Domain/User.cs:60

What to do

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

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

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

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

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.

ED5 · Idempotency10.0 / 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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs8.8 / 10Strong✓ Tool-verified

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

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

  • `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — Distributed-eStore.Common/RestEase/QueryParamSerializer.cs:68, Distributed-eStore.Services.Identity/src/Startup.cs:66, Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22

What to do

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

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

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

What to do

  • 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 a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

  • Distributed-eStore.UI/src/ClientApp/README.md names `src/index.js`, but no file or folder `src/index.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:143
  • Distributed-eStore.UI/src/ClientApp/README.md installs `husky` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:296
  • Distributed-eStore.UI/src/ClientApp/README.md installs `lint-staged` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:296
  • Distributed-eStore.UI/src/ClientApp/README.md installs `prettier` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:296
  • Distributed-eStore.UI/src/ClientApp/README.md installs `node-sass-chokidar` (`npm install --save node-sass-chokidar`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:539
  • Distributed-eStore.UI/src/ClientApp/README.md installs `npm-run-all` (`yarn add npm-run-all`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:590
  • Distributed-eStore.UI/src/ClientApp/README.md installs `flow-bin` (`npm install --save flow-bin`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:794
  • Distributed-eStore.UI/src/ClientApp/README.md runs `npm run flow init`, but no REDACTED declares a `flow` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:796
  • Distributed-eStore.UI/src/ClientApp/README.md documents the environment variable `REACT_APP_SECRET_CODE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:854
  • Distributed-eStore.UI/src/ClientApp/README.md names `.env.development`, but no file or folder `.env.development` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:920
  • Distributed-eStore.UI/src/ClientApp/README.md names `.env.test`, but no file or folder `.env.test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:920
  • Distributed-eStore.UI/src/ClientApp/README.md names `.env.production`, but no file or folder `.env.production` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:920
  • Distributed-eStore.UI/src/ClientApp/README.md documents the environment variable `DANGEROUSLY_DISABLE_HOST_CHECK`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1025
  • Distributed-eStore.UI/src/ClientApp/README.md names `.test.js`, but no file or folder `.test.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1201
  • Distributed-eStore.UI/src/ClientApp/README.md names `.spec.js`, but no file or folder `.spec.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1202
  • Distributed-eStore.UI/src/ClientApp/README.md names `src/App.test.js`, but no file or folder `src/App.test.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1259
  • Distributed-eStore.UI/src/ClientApp/README.md installs `enzyme` (`npm install --save enzyme enzyme-adapter-react-16 react-test-renderer`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1266
  • Distributed-eStore.UI/src/ClientApp/README.md installs `enzyme-adapter-react-16` (`npm install --save enzyme enzyme-adapter-react-16 react-test-renderer`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1266
  • Distributed-eStore.UI/src/ClientApp/README.md installs `react-test-renderer` (`npm install --save enzyme enzyme-adapter-react-16 react-test-renderer`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1266
  • Distributed-eStore.UI/src/ClientApp/README.md installs `jest-enzyme` (`npm install --save jest-enzyme`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1330
  • Distributed-eStore.UI/src/ClientApp/README.md names `src/setupTests.js`, but no file or folder `src/setupTests.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1339
  • Distributed-eStore.UI/src/ClientApp/README.md installs `react-styleguidist` (`npm install --save react-styleguidist`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1579
  • Distributed-eStore.UI/src/ClientApp/README.md runs `npm run styleguide`, but no REDACTED declares a `styleguide` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1600
  • Distributed-eStore.UI/src/ClientApp/README.md links to `src/index.js`, but `Distributed-eStore.UI/src/ClientApp/src/index.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1633
  • Distributed-eStore.UI/src/ClientApp/README.md links to `src/registerServiceWorker.js`, but `Distributed-eStore.UI/src/ClientApp/src/registerServiceWorker.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Distributed-eStore.UI/src/ClientApp/README.md:1656

What to do

  • Reconcile the README with reality: Distributed-eStore.UI/src/ClientApp/README.md names `src/index.js`, but no file or folder `src/index.js` exists; Distributed-eStore.UI/src/ClientApp/README.md installs `husky` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it; Distributed-eStore.UI/src/ClientApp/README.md installs `lint-staged` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it; Distributed-eStore.UI/src/ClientApp/README.md installs `prettier` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it; Distributed-eStore.UI/src/ClientApp/README.md installs `node-sass-chokidar` (`npm install --save node-sass-chokidar`), but no REDACTED declares it.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.

  • `services.AddHttpClient<IConsulHttpClient, ConsulHttpClient>()` 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). — Distributed-eStore.Common/Consul/Extensions.cs:29
  • `services.AddHttpClient<IFabioHttpClient, FabioHttpClient>()` 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). — Distributed-eStore.Common/Fabio/Extensions.cs:17
  • `services.AddHttpClient(clientName)` 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). (×2) — Distributed-eStore.Common/RestEase/Extensions.cs:52, Distributed-eStore.Common/RestEase/Extensions.cs:61
  • `services.AddHttpClient(clientName, client => { var service = options.Services...` 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). — Distributed-eStore.Common/RestEase/Extensions.cs:69

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

R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.1 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:29 — the two spans are one implementation copied and then locally edited — 410 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25
  • Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16 · Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:29 — 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. — Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16
  • Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24 · Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24
  • Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24 · Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24
  • Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 · Distributed-eStore.UI/src/ClientApp/src/containers/MaleProductsPage/MaleProductsPage.tsx:24 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31
  • Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58 · Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:65 — 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. — Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58
  • Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:74 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:81 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:88 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

R4 · Test Coverage8.8 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×5) — Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts:1, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts:1, Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness6.4 / 10Adequate✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

  • 36 outdated package(s); JS/npm CVEs scored in D30

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling6.7 / 10Adequate✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add `tsc --noEmit` as REDACTED scripts and run them in CI.
R7 · Dead Code7.5 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 1 application, 1 tooling and 1 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts
  • no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts
  • no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — Distributed-eStore.UI/src/ClientApp/src/state/Products/productsTypes.ts
  • no import path from any entry point (1 application, 1 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — Distributed-eStore.UI/src/ClientApp/src/components/routing/PrivateRoute.jsx, Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts, Distributed-eStore.UI/src/ClientApp/src/containers/index.tsx
  • no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts
  • Nothing imports this binding — it is safe to review for removal. — Distributed-eStore.UI/src/ClientApp/src/registerServiceWorker.ts:99

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene7.5 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports3.7 / 10Weak✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

  • Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts → Distributed-eStore.UI/src/ClientApp/src/components/products/ColorSwitcher/ColorSwitcher.tsx → Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts (one verified cycle inside a mutually-dependent group of 11 files) — Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts:2
  • Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts → Distributed-eStore.UI/src/ClientApp/src/state/cart/index.ts → Distributed-eStore.UI/src/ClientApp/src/state/cart/cartActions.ts → Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts — Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts:3
  • Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts → Distributed-eStore.UI/src/ClientApp/src/state/user/index.ts → REDACTED → Distributed-eStore.UI/src/ClientApp/src/services/auth/index.ts → Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts — Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts:3

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture8.0 / 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.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×9) — Distributed-eStore.Api.Gateway/src/Program.cs:12, Distributed-eStore.Api.Gateway/src/Program.cs:25, Distributed-eStore.Services.Identity/src/Program.cs:12, …

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness7.2 / 10Strong✓ Tool-verified

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

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

  • `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:11
  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:19

What to do

  • async void method: SeedProductsAsync
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 correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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 propagation4.3 / 10Weak✓ 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 4/87 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) — Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:29, Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:37, Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:42, …

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 handling10.0 / 10Exemplary○ Nothing flagged

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

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

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 logging2.5 / 10Weak✓ Tool-verified

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

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

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×9) — REDACTED:31, Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:116, Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:117, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 0/5 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

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

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 Health49%Weak — gated by X4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture77%Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity42%Weak — gated by D34, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness20%Critical — gated by D12, D13, P1, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security61%Adequate — gated by D30, D31Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling52%Adequate — gated by DM2, DM5, DM6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility37%Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • 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 — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • 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.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 29 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.

  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — identity-service Error context canceled rabbitmq Error context canceled order-service Error context canceled consul Error context canceled fabio Error context canceled ui Error context canceled mongo Error context canceled api-gateway Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: ui Error Get "https://registry-1.docker.io/v2/": Forbidden order-service Error context canceled fabio Error context canceled consul Error context canceled product-service Error Get "https://registry-1.docker.io/v2/": Forbidden mongo Error context canceled api-gateway Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D11 Test Reliability — Test reliability not included — no executor for the `react-scripts` test runner
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D21 Naming Consistency — LLM evaluation failed
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D25 ADR Conformance — no ADRs to check
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 CQRS handler(s))
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • 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.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • 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 — 150 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×63
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 38 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×20
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×8
  • WriteOnlyPrivateField REDACTED:13 — private IOrdersService _ordersService — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Distributed-eStore.Common/Mongo/MongoDbInitializer.cs:15 — private IMongoDatabase _database — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:14 — private IOrdersRepository _ordersRepository — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:12 — private string AcceptLanguageHeader — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:13 — private string OperationHeader — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:14 — private string ResourceHeader — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:15 — private string DefaultCulture — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField REDACTED:15 — private ILogger<ErrorModel> logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
AC2 · Forms & labels · <input> without a programmatic label · ×7
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:37 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:60 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:67 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:69 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:76 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:83 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:90 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×5
  • Domain depends on infrastructure: RefreshToken Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:20 — `RefreshToken` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RefreshToken Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:38 — `RefreshToken` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs:49 — `User` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs:59 — `User` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs:60 — `User` (domain layer) names `PasswordVerificationResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
AC1 · Text alternatives · <img> without a text alternative · ×4
  • <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:25 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/components/products/Product/Product.tsx:26 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/containers/NavMenu/NavMenu.tsx:29 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/containers/ProductView/ProductView.tsx:57 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D28 · Secrets (history) · High secret · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Vulnerable · ×3
  • Vulnerable: Microsoft.AspNetCore.Authentication.JwtBearer — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: MongoDB.Driver — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: System.IdentityModel.Tokens.Jwt — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
AC2 · Forms & labels · Link with no accessible name · ×2
  • Link with no accessible name Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:13 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:45 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels · Custom control with no accessible name on <span> · ×1
  • Custom control with no accessible name on <span> Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16 — This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×1
  • Clickable element isn't keyboard-operable Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProducts/CartProducts.tsx:39 — The repo's own CSS styles .cart-products__button__text with `cursor: pointer`, so this <span> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×1
  • Click handler on a non-interactive <span> Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D10 · Test Quality · No assertions (empty test) · ×1
  • No assertions (empty test): renders without crashing Distributed-eStore.UI/src/ClientApp/src/App.test.tsx:7 — Test method has an empty body — it asserts nothing and exercises no code.
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×1
  • Import cycle (2 files) Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts:2 — Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts → Distributed-eStore.UI/src/ClientApp/src/components/products/ColorSwitcher/ColorSwitcher.tsx → Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts (one verified cycle inside a mutually-dependent group of 11 files)
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts:3 — Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts → Distributed-eStore.UI/src/ClientApp/src/state/cart/index.ts → Distributed-eStore.UI/src/ClientApp/src/state/cart/cartActions.ts → Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts
R9 · Circular Imports · Import cycle (4 files) · ×1
  • Import cycle (4 files) Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts:3 — Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts → Distributed-eStore.UI/src/ClientApp/src/state/user/index.ts → REDACTED → Distributed-eStore.UI/src/ClientApp/src/services/auth/index.ts → Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts
Serious — 198 finding(s)
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: SignUp Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SignIn Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:37 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ChangePassword Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefreshAccessToken REDACTED:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RevokeAccessToken REDACTED:32 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RevokeRefreshToken REDACTED:41 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync Distributed-eStore.Services.Identity/src/Repositories/RefreshTokenRepository.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAsync Distributed-eStore.Services.Identity/src/Repositories/RefreshTokenRepository.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync Distributed-eStore.Services.Identity/src/Repositories/RefreshTokenRepository.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SignUpAsync Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:38 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SignInAsync Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:68 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ChangePasswordAsync Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:85 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAsync Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:37 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateAccessTokenAsync Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:48 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RevokeAsync Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:75 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: IsCurrentActiveToken Distributed-eStore.Common/Authentication/AccessTokenService.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeactivateCurrentAsync Distributed-eStore.Common/Authentication/AccessTokenService.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: IsActiveAsync Distributed-eStore.Common/Authentication/AccessTokenService.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeactivateAsync Distributed-eStore.Common/Authentication/AccessTokenService.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync REDACTED:16 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetRequestUriAsync Distributed-eStore.Common/Consul/ConsulServiceDiscoveryMessageHandler.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×37
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 12 more in this group — see findings.md.
D12 · Dependency Hygiene · Deprecated · ×30
  • Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:11 — REDACTED — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:79 — Microsoft.AspNetCore.Authentication.JwtBearer 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:11 — REDACTED — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authentication.OpenIdConnect REDACTED:12 — Microsoft.AspNetCore.Authentication.OpenIdConnect 5.0.1 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authentication.OpenIdConnect Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:12 — Microsoft.AspNetCore.Authentication.OpenIdConnect 5.0.1 — Other,Legacy
  • Deprecated: OpenTracing.Contrib.NetCore REDACTED:25 — OpenTracing.Contrib.NetCore 0.5.0 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
  • Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj:19 — OpenTracing.Contrib.NetCore 0.5.0 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
  • Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.Services.Product/src/Distributed-eStore.Services.Product.csproj:18 — OpenTracing.Contrib.NetCore 0.5.0 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
  • Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:105 — OpenTracing.Contrib.NetCore 0.5.0 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
  • Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:15 — OpenTracing.Contrib.NetCore 0.5.0 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
  • Deprecated: Microsoft.AspNetCore REDACTED:17 — Microsoft.AspNetCore 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authentication REDACTED:78 — Microsoft.AspNetCore.Authentication 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authorization REDACTED:80 — Microsoft.AspNetCore.Authorization 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Hosting REDACTED:20 — Microsoft.AspNetCore.Hosting 2.2.7 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Identity REDACTED:77 — Microsoft.AspNetCore.Identity 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc REDACTED:23 — Microsoft.AspNetCore.Mvc 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc.Core REDACTED:26 — Microsoft.AspNetCore.Mvc.Core 2.2.5 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc.DataAnnotations REDACTED:29 — Microsoft.AspNetCore.Mvc.DataAnnotations 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Server.Kestrel REDACTED:32 — Microsoft.AspNetCore.Server.Kestrel 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.StaticFiles REDACTED:35 — Microsoft.AspNetCore.StaticFiles 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.Binder REDACTED:38 — Microsoft.Extensions.Configuration.Binder 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.EnvironmentVariables REDACTED:41 — Microsoft.Extensions.Configuration.EnvironmentVariables 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:44 — Microsoft.Extensions.Configuration.FileExtensions 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.Json REDACTED:47 — Microsoft.Extensions.Configuration.Json 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.DependencyInjection REDACTED:50 — Microsoft.Extensions.DependencyInjection 5.0.1 — Other,Legacy
  • + 5 more in this group — see findings.md.
D31 · IaC & Container Security · Medium IaC · ×13
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Prerelease dependency · ×10
  • Prerelease dependency: RawRabbit — RawRabbit resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.DependencyInjection.Autofac — RawRabbit.DependencyInjection.Autofac resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.DependencyInjection.ServiceCollection — RawRabbit.DependencyInjection.ServiceCollection resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Enrichers.Attributes — RawRabbit.Enrichers.Attributes resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Enrichers.MessageContext — RawRabbit.Enrichers.MessageContext resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Enrichers.MessageContext.Subscribe — RawRabbit.Enrichers.MessageContext.Subscribe resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Enrichers.Polly — RawRabbit.Enrichers.Polly resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Enrichers.RetryLater — RawRabbit.Enrichers.RetryLater resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Operations.Publish — RawRabbit.Operations.Publish resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: RawRabbit.Operations.Subscribe — RawRabbit.Operations.Subscribe resolves to 2.0.0-rc5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×5
  • Outbound HTTP without resilience Distributed-eStore.Common/Consul/Extensions.cs:29 — `services.AddHttpClient<IConsulHttpClient, ConsulHttpClient>()` 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).
  • Outbound HTTP without resilience Distributed-eStore.Common/Fabio/Extensions.cs:17 — `services.AddHttpClient<IFabioHttpClient, FabioHttpClient>()` 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).
  • Outbound HTTP without resilience Distributed-eStore.Common/RestEase/Extensions.cs:52 — `services.AddHttpClient(clientName)` 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).
  • Outbound HTTP without resilience Distributed-eStore.Common/RestEase/Extensions.cs:61 — `services.AddHttpClient(clientName)` 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).
  • Outbound HTTP without resilience Distributed-eStore.Common/RestEase/Extensions.cs:69 — `services.AddHttpClient(clientName, client => { var service = options.Services...` 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).
R4 · Test Coverage · No test reaches this file · ×5
  • No test reaches this file Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file Distributed-eStore.UI/src/ClientApp/src/state/Products/productsTypes.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file Distributed-eStore.UI/src/ClientApp/src/components/routing/PrivateRoute.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
DM5 · Encapsulated state · Mutable entity · ×3
  • Mutable entity: Product Distributed-eStore.Services.Product/src/DomainEntities/Product.cs:6 — `Product` exposes publicly writable state (Name, Description, Price, Category, ImageURLs, Colors).
  • Mutable entity: Order Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:6 — `Order` exposes publicly writable state (CustomerId, OrderItems).
  • Mutable entity: OrderItem Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:6 — `OrderItem` exposes publicly writable state (ProductId, Quantity, Size).
R10 · Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (7 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24 — Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24 · Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (7 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24 — Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24 · Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (7 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 · Distributed-eStore.UI/src/ClientApp/src/containers/MaleProductsPage/MaleProductsPage.tsx:24 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: CartProduct.tsx ↔ Cart.tsx Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:1 — `Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx` and `Distributed-eStore.UI/src/ClientApp/src/containers/Cart/Cart.tsx` change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `7daafced` refactor cart product css; `144ed02e` implement item from cart removal; `a35256de` make shopping cart responsive, redesign image — run `git show` on any of them.
  • Change coupling: productsActions.ts ↔ productsReducers.ts Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts:1 — `Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts` and `Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts` change together 54% of the time (15 of the 28 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `3dedb22a` implement logic for filtering; `8b6952d2` implement ProductFilter; `e3e19e8f` refactor reducers — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) REDACTED:18 — REDACTED:18-28 | REDACTED:18-28 — 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 (11 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:131 — Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:131-141 | Distributed-eStore.UI/src/Controllers/BaseController.cs:83-93 — before extracting anything, compare `Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs` and `Distributed-eStore.UI/src/Controllers/BaseController.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark Distributed-eStore.UI/src/ClientApp/public/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×1
  • Heading level jumps from h2 to h4 Distributed-eStore.UI/src/ClientApp/src/components/OrderCreatedPage/OrderCreatedPage.tsx:7 — 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 h3 · ×1
  • Heading level jumps from h1 to h3 Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:24 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D1 · Cyclomatic Complexity · RegisterPage.render (cyclomatic 18) · ×1
  • RegisterPage.render (cyclomatic 18) Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:58 — RegisterPage.render has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D10 · Test Quality · Test project verifies nothing · ×1
  • Test project verifies nothing: Distributed-eStore.UI/src/ClientApp Distributed-eStore.UI/src/ClientApp/src/App.test.tsx:7 — No conventional assertion call was detected in 1 of 1 tests in `Distributed-eStore.UI/src/ClientApp` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:21 — // todo: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22 — 7 consecutive commented-code lines
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: ProductsSeeder.GetProducts Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:28 — MethodTooLong — GetProducts runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:46 — Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:46-63 | Distributed-eStore.UI/src/Controllers/BaseController.cs:35-52 — before extracting anything, compare `Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs` and `Distributed-eStore.UI/src/Controllers/BaseController.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:112 — Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:112-127 | Distributed-eStore.UI/src/Controllers/BaseController.cs:64-79 — before extracting anything, compare `Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs` and `Distributed-eStore.UI/src/Controllers/BaseController.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) Distributed-eStore.Services.Order/src/Startup.cs:29 — Distributed-eStore.Services.Order/src/Startup.cs:29-41 | Distributed-eStore.Services.Product/src/Startup.cs:30-42 — before extracting anything, compare `Distributed-eStore.Services.Order/src/Startup.cs` and `Distributed-eStore.Services.Product/src/Startup.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 3) · ×1
  • Duplicated block (7 lines × 3) Distributed-eStore.Common/Messages/Products/CreateProduct.cs:9 — Distributed-eStore.Common/Messages/Products/CreateProduct.cs:9-15 | Distributed-eStore.Common/Models/Product.cs:7-13 | Distributed-eStore.Services.Product/src/Dto/ProductDto.cs:7-13 — 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 × 2) · ×1
  • Duplicated block (7 lines × 2) Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:118 — Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:118-125 | Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:163-169 — 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 `Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:127` calls `SetTag` and `Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:171` 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 (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:31 — Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:31-42 | Distributed-eStore.UI/src/Controllers/BaseController.cs:20-31 — before extracting anything, compare `Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs` and `Distributed-eStore.UI/src/Controllers/BaseController.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 net5.0 Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:4 — Distributed-eStore.UI/src/Distributed-eStore.UI.csproj declares .NET net5.0 as this project's target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 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 · Coverage not measured · ×1
  • Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×1
  • Domain type reads the wall clock: RefreshToken Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:28 — `RefreshToken` reads `DateTime.UtcNow` inside `Revoke`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — throws NotImplementedException Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×1
  • Unfinished stub — throws NotImplementedException Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19 — `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
R10 · Code Duplication · Duplicated block with local edits (53 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (53 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25 — Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:29 — the two spans are one implementation copied and then locally edited — 410 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16 — Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16 · Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:29 — 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.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×1
  • Duplicated block (7 lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58 — Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58 · Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:65 — 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.
R10 · Code Duplication · Duplicated block (7 lines × 4 locations) · ×1
  • Duplicated block (7 lines × 4 locations) Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67 — Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:74 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:81 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:88 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 36 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~76 LoC) · ×1
  • Dead file (~76 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~74 LoC) · ×1
  • Dead file (~74 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~31 LoC) · ×1
  • Dead file (~31 LoC) Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~25 LoC) · ×1
  • Dead file (~25 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/productsTypes.ts — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~13 LoC) · ×1
  • Dead file (~13 LoC) Distributed-eStore.UI/src/ClientApp/src/components/routing/PrivateRoute.jsx — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~3 LoC) · ×1
  • Dead file (~3 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~2 LoC) · ×1
  • Dead file (~2 LoC) Distributed-eStore.UI/src/ClientApp/src/containers/index.tsx — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~1 LoC) · ×1
  • Dead file (~1 LoC) Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts — no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency '@fortawesome/fontawesome-free' · ×1
  • Unused dependency '@fortawesome/fontawesome-free' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@reduxjs/toolkit' · ×1
  • Unused dependency '@reduxjs/toolkit' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'merge' · ×1
  • Unused dependency 'merge' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X1 · Async correctness · async void method · ×1
  • async void method: SeedProductsAsync Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:11 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:19 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Minor — 142 finding(s)
M4 · Documentation accuracy · README/code drift · ×25
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:143 — Distributed-eStore.UI/src/ClientApp/README.md names `src/index.js`, but no file or folder `src/index.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:296 — Distributed-eStore.UI/src/ClientApp/README.md installs `husky` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:296 — Distributed-eStore.UI/src/ClientApp/README.md installs `lint-staged` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:296 — Distributed-eStore.UI/src/ClientApp/README.md installs `prettier` (`npm install --save husky lint-staged prettier`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:539 — Distributed-eStore.UI/src/ClientApp/README.md installs `node-sass-chokidar` (`npm install --save node-sass-chokidar`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:590 — Distributed-eStore.UI/src/ClientApp/README.md installs `npm-run-all` (`yarn add npm-run-all`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:794 — Distributed-eStore.UI/src/ClientApp/README.md installs `flow-bin` (`npm install --save flow-bin`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:796 — Distributed-eStore.UI/src/ClientApp/README.md runs `npm run flow init`, but no REDACTED declares a `flow` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:854 — Distributed-eStore.UI/src/ClientApp/README.md documents the environment variable `REACT_APP_SECRET_CODE`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:920 — Distributed-eStore.UI/src/ClientApp/README.md names `.env.development`, but no file or folder `.env.development` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:920 — Distributed-eStore.UI/src/ClientApp/README.md names `.env.test`, but no file or folder `.env.test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:920 — Distributed-eStore.UI/src/ClientApp/README.md names `.env.production`, but no file or folder `.env.production` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1025 — Distributed-eStore.UI/src/ClientApp/README.md documents the environment variable `DANGEROUSLY_DISABLE_HOST_CHECK`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1201 — Distributed-eStore.UI/src/ClientApp/README.md names `.test.js`, but no file or folder `.test.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1202 — Distributed-eStore.UI/src/ClientApp/README.md names `.spec.js`, but no file or folder `.spec.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1259 — Distributed-eStore.UI/src/ClientApp/README.md names `src/App.test.js`, but no file or folder `src/App.test.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1266 — Distributed-eStore.UI/src/ClientApp/README.md installs `enzyme` (`npm install --save enzyme enzyme-adapter-react-16 react-test-renderer`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1266 — Distributed-eStore.UI/src/ClientApp/README.md installs `enzyme-adapter-react-16` (`npm install --save enzyme enzyme-adapter-react-16 react-test-renderer`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1266 — Distributed-eStore.UI/src/ClientApp/README.md installs `react-test-renderer` (`npm install --save enzyme enzyme-adapter-react-16 react-test-renderer`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1330 — Distributed-eStore.UI/src/ClientApp/README.md installs `jest-enzyme` (`npm install --save jest-enzyme`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1339 — Distributed-eStore.UI/src/ClientApp/README.md names `src/setupTests.js`, but no file or folder `src/setupTests.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1579 — Distributed-eStore.UI/src/ClientApp/README.md installs `react-styleguidist` (`npm install --save react-styleguidist`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1600 — Distributed-eStore.UI/src/ClientApp/README.md runs `npm run styleguide`, but no REDACTED declares a `styleguide` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1633 — Distributed-eStore.UI/src/ClientApp/README.md links to `src/index.js`, but `Distributed-eStore.UI/src/ClientApp/src/index.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Distributed-eStore.UI/src/ClientApp/README.md:1656 — Distributed-eStore.UI/src/ClientApp/README.md links to `src/registerServiceWorker.js`, but `Distributed-eStore.UI/src/ClientApp/src/registerServiceWorker.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D34 · Knowledge Freshness · Orphaned file · ×21
  • Orphaned file Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.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 Distributed-eStore.Common/RabbitMq/BusSubscriber.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 Distributed-eStore.Common/RabbitMq/Extensions.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 Distributed-eStore.Api.Gateway/src/Controllers/BaseController.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 Distributed-eStore.Common/Consul/Extensions.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 Distributed-eStore.Common/Mvc/Extensions.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 Distributed-eStore.Services.Identity/src/Services/IdentityService.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 Distributed-eStore.Common/Authentication/JwtHandler.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 Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.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 Distributed-eStore.Common/RestEase/Extensions.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 Distributed-eStore.UI/src/Controllers/BaseController.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 Distributed-eStore.Common/Consul/ConsulServiceDiscoveryMessageHandler.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 Distributed-eStore.Common/Mvc/JsonParser.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 Distributed-eStore.UI/src/Startup.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 Distributed-eStore.Common/RestEase/QueryParamSerializer.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 Distributed-eStore.Services.Identity/src/Startup.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 Distributed-eStore.Api.Gateway/src/Startup.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 Distributed-eStore.Services.Product/src/Startup.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 Distributed-eStore.Services.Order/src/Startup.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 Distributed-eStore.Services.Identity/src/Domain/User.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 Distributed-eStore.Common/RabbitMq/CorrelationContext.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.
D31 · IaC & Container Security · Low IaC · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Outdated · ×15
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:79 — REDACTED → 10.0.13 available (referenced by Distributed-eStore.Services.Identity).
  • Outdated: Microsoft.AspNetCore.Authentication.OpenIdConnect REDACTED:12 — Microsoft.AspNetCore.Authentication.OpenIdConnect 5.0.1 → 10.0.13 available (referenced by Distributed-eStore.Services.Identity).
  • Outdated: Swashbuckle.AspNetCore REDACTED:14 — Swashbuckle.AspNetCore 5.6.3 → 10.3.1 available (referenced by Distributed-eStore.Services.Identity).
  • Outdated: Autofac REDACTED:8 — Autofac 6.0.0 → 9.3.4 available (referenced by Distributed-eStore.Common).
  • Outdated: Autofac.Extensions.DependencyInjection REDACTED:11 — Autofac.Extensions.DependencyInjection 7.1.0 → 11.0.2 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Authorization REDACTED:80 — Microsoft.AspNetCore.Authorization 2.2.0 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.Extensions.Configuration.Binder REDACTED:38 — Microsoft.Extensions.Configuration.Binder 5.0.0 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables REDACTED:41 — Microsoft.Extensions.Configuration.EnvironmentVariables 5.0.0 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:44 — Microsoft.Extensions.Configuration.FileExtensions 5.0.0 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.Extensions.Configuration.Json REDACTED:47 — Microsoft.Extensions.Configuration.Json 5.0.0 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.Extensions.DependencyInjection REDACTED:50 — Microsoft.Extensions.DependencyInjection 5.0.1 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.Extensions.Http REDACTED:53 — Microsoft.Extensions.Http 5.0.0 → 10.0.13 available (referenced by Distributed-eStore.Common).
  • Outdated: System.IdentityModel.Tokens.Jwt REDACTED:76 — REDACTED → 8.23.0 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.SpaServices.Extensions Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:14 — Microsoft.AspNetCore.SpaServices.Extensions 5.0.1 → 10.0.13 available (referenced by Distributed-eStore.UI).
  • Outdated: Microsoft.TypeScript.MSBuild Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:15 — Microsoft.TypeScript.MSBuild 4.1.2 → 7.0.1 available (referenced by Distributed-eStore.UI).
DM2 · Strongly-typed ids · Primitive id on a domain type · ×13
  • Primitive id on a domain type: RefreshToken.UserId Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:10 — `RefreshToken.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: AccessTokenRefreshed.UserId Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRefreshed.cs:9 — `AccessTokenRefreshed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: AccessTokenRevoked.UserId Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRevoked.cs:9 — `AccessTokenRevoked.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: PasswordChanged.UserId Distributed-eStore.Services.Identity/src/Messages/Events/PasswordChanged.cs:9 — `PasswordChanged.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RefreshAccessTokenRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RefreshAccessTokenRejected.cs:9 — `RefreshAccessTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RefreshTokenRevoked.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RefreshTokenRevoked.cs:9 — `RefreshTokenRevoked.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RevokeAccessTokenRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RevokeAccessTokenRejected.cs:9 — `RevokeAccessTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RevokeRefreshTokenRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RevokeRefreshTokenRejected.cs:9 — `RevokeRefreshTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: SignedIn.UserId Distributed-eStore.Services.Identity/src/Messages/Events/SignedIn.cs:9 — `SignedIn.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: SignedUp.UserId Distributed-eStore.Services.Identity/src/Messages/Events/SignedUp.cs:9 — `SignedUp.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: SignUpRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/SignUpRejected.cs:9 — `SignUpRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Order.CustomerId Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:8 — `Order.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: OrderItem.ProductId Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:8 — `OrderItem.ProductId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
S1 · Web-Security Posture · No security response headers detected · ×10
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected Distributed-eStore.Api.Gateway/src/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Api.Gateway/src/Program.cs:25 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Services.Identity/src/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Services.Identity/src/Program.cs:25 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Services.Order/src/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Services.Order/src/Program.cs:25 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Services.Product/src/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.Services.Product/src/Program.cs:25 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Distributed-eStore.UI/src/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
X4 · Structured logging · Interpolated log message defeats structured logging · ×9
  • Interpolated log message defeats structured logging REDACTED:31 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:116 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:117 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:124 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:150 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:156 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:163 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:168 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:184 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
D30 · Dependency Vulnerabilities · Low CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Commented-out code · ×3
  • Commented-out code Distributed-eStore.Common/RestEase/QueryParamSerializer.cs:68 — 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 Distributed-eStore.Services.Identity/src/Startup.cs:66 — 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 Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:50 — `criteria == null || criteria(pagedResult)` appears character-identically in 2 files — Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs, Distributed-eStore.UI/src/Controllers/BaseController.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 Distributed-eStore.UI/src/ClientApp/src/state/cart/cartActions.ts:42 — `(error.response && error.response.data && error.response.data.message) || error.message || error.toString()` appears character-identically in 2 files — Distributed-eStore.UI/src/ClientApp/src/state/cart/cartActions.ts, REDACTED. 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 Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:116 — `result.CurrentPage > 1 && result.CurrentPage <= result.TotalPages` appears character-identically in 2 files — Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs, Distributed-eStore.UI/src/Controllers/BaseController.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.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 27 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.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: hard to navigate Distributed-eStore.UI/src/ClientApp/README.md — The UI README is a wall of CRA-specific content (updating releases, sending feedback, folder structure) with no headings ordering it under the ClientApp directory's scope. Reorganize into sections relevant to the client app and add navigation links.
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/`.
D24 · Comment Value · misleading comment · ×1
  • misleading comment REDACTED:21 — "technical debt - shouldn't be anonymous, todo - send JWT from UI." — Fix theAllowAnonymous call to allow anonymous access and remove the 'todo' comment; the real debt is that this endpoint exposes auth credentials.
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs:8 — OrdersRepository: all 5 public methods forward their arguments unchanged to _repository and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _repository directly, or give the layer a job.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 21 of 21 significant files have no living knowledge — the codebase as a whole is dormant, not 21 separate risks. Counted over 21 of the 183 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.
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 1 authored method(s) exceed the IL budget Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:30 — 1 of 408 first-party methods compile to oversized IL bodies (> 250 instructions); worst: DistributedEStore.Services.Product.Seed.ProductsSeeder.GetProducts @ Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:30, 708 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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/6 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 6, 5 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused export 'unregister' · ×1
  • Unused export 'unregister' Distributed-eStore.UI/src/ClientApp/src/registerServiceWorker.ts:99 — Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 4/87 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/5 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 23 finding(s)
D12 · Dependency Hygiene · Outdated · ×17
  • Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets — Microsoft.VisualStudio.Azure.Containers.Tools.Targets 1.10.9 → 1.23.0 available (referenced by Distributed-eStore.Services.Identity).
  • Outdated: OpenTracing.Contrib.NetCore — OpenTracing.Contrib.NetCore 0.5.0 → 0.9.0 available (referenced by Distributed-eStore.Services.Identity).
  • Outdated: Consul — Consul 1.6.1.1 → 1.8.0 available (referenced by Distributed-eStore.Common).
  • Outdated: Jaeger — Jaeger 0.3.2 → 1.0.3 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore — Microsoft.AspNetCore 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Authentication — Microsoft.AspNetCore.Authentication 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Hosting — Microsoft.AspNetCore.Hosting 2.2.7 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Identity — Microsoft.AspNetCore.Identity 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Mvc — Microsoft.AspNetCore.Mvc 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Mvc.Core — Microsoft.AspNetCore.Mvc.Core 2.2.5 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Mvc.DataAnnotations — Microsoft.AspNetCore.Mvc.DataAnnotations 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.Server.Kestrel — Microsoft.AspNetCore.Server.Kestrel 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.AspNetCore.StaticFiles — Microsoft.AspNetCore.StaticFiles 2.2.0 → 2.3.13 available (referenced by Distributed-eStore.Common).
  • Outdated: Microsoft.NETCore.UniversalWindowsPlatform — Microsoft.NETCore.UniversalWindowsPlatform 6.2.11 → 6.2.14 available (referenced by Distributed-eStore.Common).
  • Outdated: MongoDB.Driver — REDACTED → 3.12.0 available (referenced by Distributed-eStore.Common).
  • Outdated: Polly — Polly 7.2.1 → 8.8.0 available (referenced by Distributed-eStore.Common).
  • Outdated: RestEase — RestEase 1.4.9 → 1.6.4 available (referenced by Distributed-eStore.Common).
D19 · Documentation Quality · XML-doc coverage · ×6
  • XML-doc coverage: Distributed-eStore.Services.Identity REDACTED — Distributed-eStore.Services.Identity: 0 % XML-doc coverage (0/148).
  • XML-doc coverage: Distributed-eStore.Common REDACTED — Distributed-eStore.Common: 0 % XML-doc coverage (0/357).
  • XML-doc coverage: Distributed-eStore.Api.Gateway Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj — Distributed-eStore.Api.Gateway: 0 % XML-doc coverage (0/30).
  • XML-doc coverage: Distributed-eStore.Services.Product Distributed-eStore.Services.Product/src/Distributed-eStore.Services.Product.csproj — Distributed-eStore.Services.Product: 0 % XML-doc coverage (0/65).
  • XML-doc coverage: Distributed-eStore.UI Distributed-eStore.UI/src/Distributed-eStore.UI.csproj — Distributed-eStore.UI: 0 % XML-doc coverage (0/31).
  • XML-doc coverage: Distributed-eStore.Services.Order Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj — Distributed-eStore.Services.Order: 0 % XML-doc coverage (0/48).

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-511998b5ee4a42139721ff61e50e2913/history.json --exit-code 0 --source .4artifacts/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-511998b5ee4a42139721ff61e50e2913/tree.json --exit-code 0 --source .4artifacts/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 .8artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Distributed-eStore.sln package --vulnerable --include-transitive --format json130artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .48artifacts/raw/trivy-config.json
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
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a16039-fd26-7a1a-9bf7-9d1dd39008ae · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 9 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, 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 — 5 field(s)
  • SignInCommand.Email Distributed-eStore.Common/Commands/Identity/SignInCommand.cs:5
  • SignUpCommand.Email Distributed-eStore.Common/Commands/Identity/SignUpCommand.cs:8
  • User.Email Distributed-eStore.Services.Identity/src/Domain/User.cs:16
  • SignInRejected.Email Distributed-eStore.Services.Identity/src/Messages/Events/SignInRejected.cs:9
  • SignedUp.Email Distributed-eStore.Services.Identity/src/Messages/Events/SignedUp.cs:10
Name — 4 field(s)
  • SignUpCommand.FirstName Distributed-eStore.Common/Commands/Identity/SignUpCommand.cs:9
  • SignUpCommand.LastName Distributed-eStore.Common/Commands/Identity/SignUpCommand.cs:10
  • User.FirstName Distributed-eStore.Services.Identity/src/Domain/User.cs:17
  • User.LastName Distributed-eStore.Services.Identity/src/Domain/User.cs:18

Issues: 150 · Warnings: 198 · Recommendations: 142 · Info: 23 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 20:49 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