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

dr-marek-jaskula/DomainDrivenDesignUniversity

Measured 22 October 2026, 00:26 UTC, at code version 53167e9

Code coverage: not measuredBus factor: not measuredSupply-chain provenance & signing: not measuredIL efficiency: not measured

Code coverage is not measured: The repo's test suite did not build.

Bus factor is not measured: No living knowledge left to concentrate.

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

IL efficiency is not measured: The target did not build.

CAI score 45out of 100 At risk Down 1 since the last survey

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

Event-Driven 100 Exemplary Domain Modelling 87 Strong Code Health 87 Strong Performance 82 Strong Architecture 62 Adequate Security and Compliance 54 Adequate Maturity 51 Adequate Production Readiness 30 Weak

A medium codebase: 23,653 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 30

Findings by how serious they are

74 critical 211 serious 223 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 00:26 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 ▸

97of 103 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
431of 508 findings point to an exact file and line, so you can open each one in the code. The other 77 concern the repository as a whole, such as missing documentation.
103dimensions across 8 lenses, read from 23,653 lines of product code in 18 projects.
Chapters

Executive summary

dr-marek-jaskula/DomainDrivenDesignUniversity scores 45 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 30 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 5 Deprecated finding(s) in Dependency Hygiene and to resolve the 3 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 45 to about 58.

74 findings are critical: 23 in Secrets (history), 13 in Dependency Vulnerabilities, ten in REDACTED Scanning, eight in IaC & Container Security, seven in Project dependency cycles, five in Explicit Debt, five in Static Analysis (SAST) and three in Dependency Hygiene.

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

Code Health 87 Strong Architecture 62 Adequate, capped by Slice cohesion Maturity 51 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 30 Weak, capped by Dependency Hygiene, REDACTED Scanning, Security & performance tooling and DR & Backup Security and Compliance 54 Adequate, capped by Secrets (history), Static Analysis (SAST) and Dependency Vulnerabilities Domain Modelling 87 Strong Event-Driven 100 ★ Exemplary Performance 82 Strong

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 30 · counts for 45%Maturity 51 · counts for 25%Security and Compliance 54 · counts for 14%Architecture 62 · counts for 8%Performance 82 · counts for 4%Code Health 87 · counts for 2%Domain Modelling 87 · counts for 1%Event-Driven 100 · counts for 1%

If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 45 to about 58.

Code composition: what the lines of code are
Business logic 7%Supporting code 41%Tests 11%Generated by tools 40%Code analyzers 1%
New since the last survey: 141 findings

These 141 critical or serious findings weren't in the previous survey, on 7 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

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: 12 findings

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

  • Coupling · Off the main sequence: Shopway.Domain
  • Dependency Hygiene · Deprecated: xunit
  • Supply-chain Provenance & Signing · REDACTED
  • Aggregate boundaries · Aggregate holds a reference to another aggregate: OrderHeader._orderLines src/Shopway.Domain/Orders/OrderHeader.cs
  • Aggregate boundaries · Aggregate holds a reference to another aggregate: OrderHeader._payments src/Shopway.Domain/Orders/OrderHeader.cs
  • Aggregate boundaries · Aggregate holds a reference to another aggregate: OrderHeader.OrderLines src/Shopway.Domain/Orders/OrderHeader.cs
  • Aggregate boundaries · Aggregate holds a reference to another aggregate: OrderHeader.Payments src/Shopway.Domain/Orders/OrderHeader.cs
  • Aggregate boundaries · Aggregate holds a reference to another aggregate: Product._reviews src/Shopway.Domain/Products/Product.cs
  • Aggregate boundaries · Aggregate holds a reference to another aggregate: Product.Reviews src/Shopway.Domain/Products/Product.cs
  • Repository granularity · Repository for a non-root entity: OrderHeaderRepository → OrderHeader src/Shopway.Persistence/Repositories/OrderHeaderRepository.cs
  • Repository granularity · Repository for a non-root entity: ProductRepository → Product src/Shopway.Persistence/Repositories/ProductRepository.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false)
Rebuild cost: about €45,000 · Estimate
Cost to rebuild€15,000 to €75,000, for 251 to 793 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemVery high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 45. 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.
SizeMedium: 23,653 lines of product code, of which 45% is declarations and boilerplate, 39% straight logic and 15% logic with branches

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 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, Shopway.Tests.Unit.csproj, Shopway.Tests.Integration.csproj.
Raises the score by about 10 points · Low effort · Dependency Hygiene
2
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.
Raises the score by about 9 points · Low effort · Dependency Hygiene
3
Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3), REDACTED (2).
Raises the score by about 13 points · Medium effort · REDACTED Scanning

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 €45,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 30 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 8 Domain Modelling findings · Common cause
8 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. 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 (7 findings) · Rich vs anemic model (1 finding)
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 5 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for low effort, because it clears the 5 Dependency Hygiene 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 PaymentGateway PaymentGateway Shopway.App App Shopway.Persistence Persistence Shopway.App->Shopway.Persistence Shopway.Presentation Presentation Shopway.App->Shopway.Presentation Shopway.Application Application Shopway.Domain Domain Shopway.Application->Shopway.Domain Shopway.Infrastructure Infrastructure Shopway.Infrastructure->Shopway.Application Shopway.Persistence->Shopway.Infrastructure Shopway.Presentation->Shopway.Application

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.

196 modules, with 668 dependencies between them. 7 loops run through 24 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 156 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 Domain.Common.BaseTypes.Abstractions2 Domain.Common.DataProcessing.Abstractions3 Domain.Common.Results4 Domain.EntityKeys5 Domain.Common.BaseTypes6 Domain.Common.DataProcessing7 Domain.Common.Errors8 Domain.Common.DataProcessing.Proxy9 Domain.Products.ValueObjects10 Domain.Users.Authorization11 Domain.Users.ValueObjects12 Domain.Orders.ValueObjects13 Domain.Products14 Domain.Users15 Application.Abstractions16 Domain.Orders17 Domain.Products.DataProcessing.Filtering18 Domain.Products.DataProcessing.Sorting19 Application.Features20 Application.Features.Products.Queries21 Persistence.Framework22 Application.Features.Orders.Queries23 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery24 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery25 Application.Features.Products.Commands.BatchUpsertProduct26 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery27 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery28 Persistence.Repositories29 Application.Features.Proxy30 Application.Abstractions.CQRS31 Application.Features.Orders.Commands.CreateHeaderOrder32 Application.Features.Products.Commands.AddReview33 Application.Features.Products.Commands.RemoveReview34 Application.Features.Products.Queries.DynamicOffsetProductQuery35 Application.Features.Products.Queries.GetProductsCursorDictionary36 Application.Features.Products.Queries.GetProductsOffsetDictionary37 Application.Features.Products.Queries.QueryOffsetPageProduct38 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping39 Application.Mappings40 Presentation.Controllers
1 Domain.Common.BaseTypes.Abstractions
2 Domain.Common.DataProcessing.Abstractions4
3 Domain.Common.Results2
4 Domain.EntityKeys21
5 Domain.Common.BaseTypes51
6 Domain.Common.DataProcessing8
7 Domain.Common.Errors23
8 Domain.Common.DataProcessing.Proxy1216
9 Domain.Products.ValueObjects777
10 Domain.Users.Authorization113
11 Domain.Users.ValueObjects1131213
12 Domain.Orders.ValueObjects24244
13 Domain.Products2612191
14 Domain.Users32113
15 Application.Abstractions4122
16 Domain.Orders5633162
17 Domain.Products.DataProcessing.Filtering814
18 Domain.Products.DataProcessing.Sorting423
19 Application.Features2113
20 Application.Features.Products.Queries12
21 Persistence.Framework1
22 Application.Features.Orders.Queries214112
23 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery111122
24 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery111122
25 Application.Features.Products.Commands.BatchUpsertProduct15424
26 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery11111122
27 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery11111122
28 Persistence.Repositories181121322527
29 Application.Features.Proxy21181214111114
30 Application.Abstractions.CQRS121
31 Application.Features.Orders.Commands.CreateHeaderOrder211122
32 Application.Features.Products.Commands.AddReview131232
33 Application.Features.Products.Commands.RemoveReview21113
34 Application.Features.Products.Queries.DynamicOffsetProductQuery111111112
35 Application.Features.Products.Queries.GetProductsCursorDictionary111111122
36 Application.Features.Products.Queries.GetProductsOffsetDictionary111111122
37 Application.Features.Products.Queries.QueryOffsetPageProduct111111112
38 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping11111122
39 Application.Mappings1222143242111
40 Presentation.Controllers11511211122211111
Uses a module listed above itPart of a loopThe module itself
1 Domain.Common.BaseTypes.Abstractions2 Domain.Common.DataProcessing.Abstractions3 Domain.Common.Results4 Domain.EntityKeys5 Domain.Common.BaseTypes6 Domain.Common.DataProcessing7 Domain.Common.Errors8 Domain.Common.DataProcessing.Proxy9 Domain.Products.ValueObjects10 Domain.Users.Authorization11 Domain.Users.ValueObjects12 Domain.Orders.ValueObjects13 Domain.Products14 Domain.Users15 Application.Abstractions16 Domain.Orders17 Domain.Products.DataProcessing.Filtering18 Domain.Products.DataProcessing.Sorting19 Application.Features20 Application.Features.Products.Queries21 Persistence.Framework22 Application.Features.Orders.Queries23 Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery24 Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery25 Application.Features.Products.Commands.BatchUpsertProduct26 Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery27 Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery28 Persistence.Repositories29 Application.Features.Proxy30 Application.Abstractions.CQRS31 Application.Features.Orders.Commands.CreateHeaderOrder32 Application.Features.Products.Commands.AddReview33 Application.Features.Products.Commands.RemoveReview34 Application.Features.Products.Queries.DynamicOffsetProductQuery35 Application.Features.Products.Queries.GetProductsCursorDictionary36 Application.Features.Products.Queries.GetProductsOffsetDictionary37 Application.Features.Products.Queries.QueryOffsetPageProduct38 Application.Features.Products.Queries.QueryOffsetPageProductWithMapping39 Application.Mappings40 Presentation.ControllersDomain.Common.BaseTypes.Abstractions1Domain.Common.DataProcessing.Abstractions2Domain.Common.Results3Domain.EntityKeys4Domain.Common.BaseTypes5Domain.Common.DataProcessing6Domain.Common.Errors7Domain.Common.DataProcessing.Proxy8Domain.Products.ValueObjects9Domain.Users.Authorization10Domain.Users.ValueObjects11Domain.Orders.ValueObjects12Domain.Products13Domain.Users14Application.Abstractions15Domain.Orders16Domain.Products.DataProcessing.Filtering17Domain.Products.DataProcessing.Sorting18Application.Features19Application.Features.Products.Queries20Persistence.Framework21Application.Features.Orders.Queries22Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery23Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery24Application.Features.Products.Commands.BatchUpsertProduct25Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery26Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery27Persistence.Repositories28Application.Features.Proxy29Application.Abstractions.CQRS30Application.Features.Orders.Commands.CreateHeaderOrder31Application.Features.Products.Commands.AddReview32Application.Features.Products.Commands.RemoveReview33Application.Features.Products.Queries.DynamicOffsetProductQuery34Application.Features.Products.Queries.GetProductsCursorDictionary35Application.Features.Products.Queries.GetProductsOffsetDictionary36Application.Features.Products.Queries.QueryOffsetPageProduct37Application.Features.Products.Queries.QueryOffsetPageProductWithMapping38Application.Mappings39Presentation.Controllers404221518231216777113113121324244261219132113412256331628144232113121214112111122111122154241111112211111122181121322527211812141111141212111221312322111311111111211111112211111112211111111211111122122214324211111511211122211111+156 more modules (most-connected shown)

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

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

At a glance — Architecture · 62% · Adequate · gated by AX7 ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.1 D26 · .NET / C# Project Cohesion 7.8 D27 · .NET / C# Navigability 8.2 D35 · .NET / C# Change Coupling 9.9 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 7.1 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0
The Bad
D23 · .NET / C# Boundary Type-Coupling 5.8 AX2 · Repo Stateful singletons 5.9
The Ugly
AX7 · Repo Slice cohesion 1.0

At a glance — Maturity · 51% · Adequate · gated by D34, M2 ·

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

At a glance — Readiness · 30% · Weak · gated by D12, D13, P3, P5 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 9.3 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.0 P7 · Repo Outbound HTTP resilience 10.0 P8 · Repo Schema migrations 10.0
The Bad
P10 · Repo Library API & versioning 6.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0
The Ugly
D12 · .NET / C# Dependency Hygiene 1.4 D13 · .NET / C# REDACTED Scanning 0.0 P3 · Repo Security & performance tooling 1.0 P5 · Repo DR & Backup 0.0

At a glance — Security · 54% · Adequate · gated by D28, D29, D30 ·

The Good
D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 10.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
D31 · .NET / C# IaC & Container Security 6.8 C1 · Repo Data Protection 6.5 C3 · Repo Audit Trail 5.0 C4 · Repo Data Retention 6.5 S1 · Repo Web-Security Posture 5.5
The Ugly
D28 · .NET / C# Secrets (history) 0.0 D29 · .NET / C# Static Analysis (SAST) 1.7 D30 · .NET / C# Dependency Vulnerabilities 0.0 D37 · .NET / C# Vulnerability-disclosure Policy 4.0

At a glance — Domain Modelling · 87% · Strong ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 9.2 DM11 · Repo Constructible invalid state 10.0 DM12 · Repo Ambient inputs in the domain 9.9 DM4 · Repo Rich vs anemic model 9.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM7 · Repo Repository granularity 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0
The Bad
DM5 · Repo Encapsulated state 6.5

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

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

At a glance — Performance · 82% · Strong ·

The Good
PF1 · Repo Benchmark discipline 9.5 PF3 · Repo Async & latency hygiene 10.0
The Bad
PF2 · Repo Allocation hygiene 6.1

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
A05:2025 — Injection39High / Critical
A07:2025 — Authentication Failures34High / Critical
A03:2025 — Software Supply Chain Failures19High / Critical
A02:2025 — Security Misconfiguration16High / Critical

Roadmap

Immediately resolve the ten leaked secrets in configuration and collection files to eliminate critical security exposure. Next, address the five deprecated and three vulnerable dependencies, followed by removing two prerelease packages, to ensure a stable and secure codebase. Finally, codify disaster recovery and backup procedures in infrastructure as code, documenting recovery time and point objectives to move beyond simple persistence guards.

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

Do thisHelpsEffortDimension
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, Shopway.Tests.Unit.csproj, Shopway.Tests.Integration.csproj.+10.4 ptsLowDependency Hygiene
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.+9.1 ptsLowDependency Hygiene
Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3), REDACTED (2).+13.0 ptsMediumREDACTED Scanning
Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene.+4.3 ptsLowDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.+2.8 ptsLowADR Quality
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.+5.0 ptsMediumDR & Backup
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+3.8 ptsMediumSecurity & performance tooling
Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy.+1.2 ptsLowVulnerability-disclosure Policy

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.6SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED1.5SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.6SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.3SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.3SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.8SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedSecrets (history): REDACTED: REDACTED
REDACTED4.8MixedSecrets (history): REDACTED: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
src/Shopway.Domain/Products/IProductRepository.cs5.5MixedCode Duplication: Duplicated block (7 lines × 2)
REDACTED5.5MixedExplicit Debt: WriteOnlyPrivateField
src/Shopway.Domain/Orders/IOrderHeaderRepository.cs5.5MixedCode Duplication: Duplicated block (7 lines × 2)
REDACTED5.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 74

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

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

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

Could not be resolved — 2

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

Methodology & how to trust this report

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

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, 431 of 508 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 01a16100-6be2-75a3-b8be-2fa8fc42f204.

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

Run transparency — what happened this run

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

  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 110 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 110 of the 720 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
  • 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: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
  • 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.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `PaymentGateway/Webhook/WebhookService.cs`, `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerToGenerateEntry.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs`, … (+156 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D39 IL Efficiency — not measured this run — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
  • 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) — ddduniversitydb Error context canceled aspiredashboard Error context canceled paymentgateway Warning context canceled jaeger Error context canceled prometheus Error context canceled opentelemetrycollector Error context canceled papercut Error context canceled shopway.app Warning context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: jaeger Error context canceled paymentgateway Warning context canceled shopway.app Warning context canceled aspiredashboard Error context canceled ddduniversitydb Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build paymentgateway shopway.app 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.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • 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.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity9.0 / 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.0 / 10 · rule-coverage 100% · ceiling Prevented

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StringUtilities.SqlLike at 35.

StringUtilities.SqlLike (cyclomatic 35)src/Shopway.Domain/Common/Utilities/StringUtilities.cs:166

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with StringUtilities.SqlLike (cyclomatic 35). — Refactoring it lifts Cyclomatic Complexity from 9.0 to about 10.0/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity7.8 / 10Strong✓ Tool-verified

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

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

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

5 method(s) exceeded the cognitive complexity threshold of 15; the worst was StringUtilities.SqlLike at 83.

StringUtilities.SqlLike (cognitive 83)src/Shopway.Domain/Common/Utilities/StringUtilities.cs:166
FilterByEntryJsonConverter.Read (cognitive 32)src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:12
MappingEntryJsonConverter.Read (cognitive 26)src/Shopway.Domain/Common/DataProcessing/MappingEntryJsonConverter.cs:10
ApplicationCache.CreateValidationResultCache (cognitive 19)src/Shopway.Application/Cache/ApplicationCache.ResultValidations.cs:21
MappingEntry.GetAllPropertyNamesWithHierarchy (cognitive 17)src/Shopway.Domain/Common/DataProcessing/MappingEntry.cs:21

What to do

  1. Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with StringUtilities.SqlLike (cognitive 83), FilterByEntryJsonConverter.Read (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.8 to about 8.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.8 / 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.8 / 10 · rule-coverage 100% · ceiling Prevented

1 god class(es) detected.

TooManyMethods: Errorsrc/Shopway.Domain/Common/Errors/Error.Common.cs

What to do

  1. Resolve the 1 TooManyMethods finding(s) in God Classes — start with Error.Common.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.3 / 10Stronggated by 35 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.3 / 10 · rule-coverage 100% · ceiling Verified

34 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.

Duplicated block (13 lines × 2) · ×4REDACTED:56
Duplicated block (10 lines × 2) · ×4src/Shopway.Application/Cache/ApplicationCache.AllowedFilterOperations.cs:15
Duplicated block (5 lines × 2) · ×4src/Shopway.Domain/Orders/OrderLineKeyJsonConverter.cs:48
Duplicated block (7 lines × 2) · ×3src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:29
Duplicated block (6 lines × 2) · ×3src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:10

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

What to do

  1. Resolve the 4 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), FluentValidationUtilities.cs, GenericFluentValidationUtilities.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ApplicationCache.AllowedFilterOperations.cs, AddPermissionToRoleCommandHandler.cs, HashUtilities.cs. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with OrderLineKeyJsonConverter.cs, ProductName.cs, AccessToken.cs. — One of this dimension's main actionable groups (4 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

4 of 51 classes have LCOM4 above 3.

Low cohesion: Specification (LCOM4 16) · ×4src/Shopway.Persistence/Specifications/Specification.cs:44

What to do

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

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

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

109 test methods: 97 unit, 12 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

1 skipped (1 with a documented reason), 0 zero-assertion, 3 mock references across 109 tests.

Mock framework: NSubstitute · ×3
Skipped (documented): CleanDatabaseFromTestDataAsynctest/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11

✓ On the Gold path — maintain.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

53 outdated, 3 vulnerable, 2 deprecated, 2 prerelease packages.

Vulnerable: MailKit · ×3
Deprecated: FluentValidation.AspNetCore · ×5REDACTED:10
Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore · ×2
Outdated: FastEndpoints · ×8src/Shopway.Presentation/Shopway.Presentation.csproj:21
Outdated: Asp.Versioning.Mvc.ApiExplorer · ×45

What to do

  1. Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, Shopway.Tests.Unit.csproj, Shopway.Tests.Integration.csproj. — One of this dimension's main actionable groups (5 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 2 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED 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

5 secret(s) detected.

REDACTED

What to do

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

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

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 295 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 65 direct `PackageReference`(s), and 185 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 Debt9.6 / 10Adequategated by 5 critical findings✓ Tool-verified

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

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

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

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

WriteOnlyPrivateField · ×4src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs:17
NoWarnInCsprojsrc/Shopway.Presentation/Shopway.Presentation.csproj:11
CommentedOutCodetest/Shopway.Tests.Benchmark/Benchmarks/ReflectionUtilitiesBenchmarks.cs:80
ObsoleteWithoutCallerssrc/Shopway.Persistence/Specifications/Specification.cs:222

What to do

  1. Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AddRoleToUserCommandHandler.cs, RemoveRoleFromUserCommandHandler.cs, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Shopway.Presentation.csproj. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with ReflectionUtilitiesBenchmarks.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

18 projects, 897 source files, 29259 hand-written lines of code (23653 production / 5606 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 20928 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 27 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 root README gives an overview (Domain Driven Design University) and a Clean Architecture solution structure diagram with .App/.Presentation/.Application/.Infrastructure/.Persistence layers plus a brief Contributor Covenant code of conduct. It is clear but thin on installation/usage examples, contribution guidance, and licence; the CODE_OF_CONDUCT.md and CONTRIBUTING.md files flesh out the latter while the root README only mentions giving a star as motivation for the project.

XML-doc coverage: Shopway.Presentation · ×9src/Shopway.Presentation/Shopway.Presentation.csproj

What to do

  1. Improve Documentation Quality — currently 5.0/10. — The root README gives an overview (Domain Driven Design University) and a Clean Architecture solution structure diagram with .App/.Presentation/.Application/.Infrastructure/.Persistence layers plus a brief Contributor Covenant code of conduct. It is clear but thin on installation/usage examples, contribution guidance, and licence; the CODE_OF_CONDUCT.md and CONTRIBUTING.md files flesh out the latter while the root README only mentions giving a star as motivation for the project.

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

1 naming inconsistencies across 200 sampled symbols.

The constant field `Username` in `TestUser` constants and the value object type `Username` in the domain share the exact same name but represent fundamentally different concepts: one is a static string constant for test data, the other is a complex value object type. This creates ambiguity when referencing 'Username' without full qualification, as it is unclear if the code refers to the test fixture value or the domain entity.

✓ On the Gold path — maintain.

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

D23 · Boundary Type-Coupling5.8 / 10Adequate✓ 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 5.8 / 10 · rule-coverage 100% · ceiling Verified

54 domain type(s) cross context boundaries across 7 contexts.

Cross-context type ProductId (Shopway → Products) · ×16src/Shopway.Domain/Products/IProductRepository.cs:17
Cross-context type OrderHeaderId (Shopway → Orders) · ×15src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:10
Cross-context type ReviewId (Shopway → Products) · ×6src/Shopway.Domain/Products/IProductRepository.cs:31
Cross-context type ProductId (Shopway → Orders) · ×5src/Shopway.Domain/Orders/OrderLineKey.cs:10
Cross-context type OrderLineId (Shopway → Orders) · ×4src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:12

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

What to do

  1. Resolve the 16 Cross-context type ProductId (Shopway → Products) finding(s) in Boundary Type-Coupling — start with IProductRepository.cs (8), ProductCreatedDomainEvent.cs (2), ReviewAddedDomainEvent.cs (2). — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 15 Cross-context type OrderHeaderId (Shopway → Orders) finding(s) in Boundary Type-Coupling — start with IOrderHeaderRepository.cs (5), OrderLine.cs (2), NewPaymentAddedDomainEvent.cs (2). — One of this dimension's main actionable groups (15 warning-level).
  3. Resolve the 6 Cross-context type ReviewId (Shopway → Products) finding(s) in Boundary Type-Coupling — start with ReviewAddedDomainEvent.cs (2), ReviewRemovedDomainEvent.cs (2), IProductRepository.cs. — One of this dimension's main actionable groups (6 warning-level).
  4. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

0 valuable / 0 redundant across 200 sampled comments.

What to do

  1. Improve Comment Value — currently 3.0/10. — 0 valuable / 0 redundant across 200 sampled comments.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion7.8 / 10Strong✓ Tool-verified

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

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

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

2 of 18 projects flagged as possibly oversized/incoherent.

Split Shopway.Application
Split Shopway.Domain

What to do

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

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

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

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

What to do

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

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 15 REDACTED finding(s) in Secrets (history) — start with REDACTED (9), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (15 issue-level).
  2. Resolve the 8 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
  3. 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)1.7 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

39 finding(s): 0 critical, 5 high, 34 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 165 file(s) — `PaymentGateway/Webhook/WebhookService.cs` (line 8), `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs` (lines 8–11, line 12, lines 13–15), `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs` (line 12, line 17, line 28), `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerToGenerateEntry.cs` (line 37, line 39), `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs` (line 12, line 17, line 28), … (+160 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 155 of those file(s) — `PaymentGateway/Webhook/WebhookService.cs`, `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdGenerator/EntityIdGenerator.cs`, … (+150 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 7 of those file(s) — `src/Shopway.Application/Exceptions/BadRequestException.cs`, `src/Shopway.Application/Exceptions/ForbidException.cs`, `src/Shopway.Application/Exceptions/NotFoundException.cs`, `src/Shopway.Application/Exceptions/UnavailableException.cs`, `src/Shopway.Domain/Common/Exceptions/DomainException.cs`, … (+2 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 31 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (13), REDACTED (9), REDACTED (5). — One of this dimension's main actionable groups (31 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. No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).

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

19 finding(s): 3 critical, 10 high, 6 medium, 0 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security6.8 / 10Adequate✓ 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 6.8 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

Orphaned file · ×110REDACTED:1
Dormant codebase

What to do

  1. Resolve the 110 Orphaned file finding(s) in Knowledge Freshness — start with QueryableUtilities.cs (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (110 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 5 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: ProductDictionaryCursorPageQueryHandler.cs↔ProductOffsetPageQueryHandler.cs 90%; ProductDictionaryCursorPageQueryHandler.cs↔ProductRepository.cs 70%; ProductOffsetPageQueryHandler.cs↔ProductRepository.cs 62%

Change coupling: ProductOffsetPageQueryHandler.cs ↔ ProductRepository.cs · ×4src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs:1
Change-coupling hub: ProductDictionaryCursorPageQueryHandler.cs → ProductOffsetPageQueryHandler.cs, CachedProductRepository.cs, ProductRepository.cssrc/Shopway.Application/Features/Products/Queries/ProductDictionaryCursorPageQuery/ProductDictionaryCursorPageQueryHandler.cs

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with ProductOffsetPageQueryHandler.cs (2), IProductRepository.cs, ProductRepository.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with ProductDictionaryCursorPageQueryHandler.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D37 · Vulnerability-disclosure Policy4.0 / 10Weak✓ Tool-verified

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

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

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

A vulnerability-disclosure policy (docs/SECURITY.md) is present but lists no reporting contact.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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

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

AX2 · Stateful singletons5.9 / 10Adequate✓ 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.

  • `WebhookService` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions; e.g. `_subscriptions` at line 14). — PaymentGateway/Webhook/WebhookService.cs:8

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

  • The namespaces Shopway.Domain.Common.Errors ↔ Shopway.Domain.Common.Results ↔ Shopway.Domain.Common.Results.Abstractions depend on each other. The lightest dependency in the cycle is Shopway.Domain.Common.Results → Shopway.Domain.Common.Results.Abstractions (Shopway.Domain.Common.Results.ValidationResult → Shopway.Domain.Common.Results.Abstractions.IValidationResult, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Domain/Common/Results/ValidationResult.cs:2
  • The namespaces Shopway.Domain.Users ↔ Shopway.Domain.Users.Authorization depend on each other. The lightest dependency in the cycle is Shopway.Domain.Users → Shopway.Domain.Users.Authorization (Shopway.Domain.Users.User → Shopway.Domain.Users.Authorization.Role, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Domain/Users/User.cs:3
  • The namespaces Shopway.Application.Abstractions ↔ Shopway.Application.Features.Users.Commands depend on each other. The lightest dependency in the cycle is Shopway.Application.Abstractions → Shopway.Application.Features.Users.Commands (Shopway.Application.Abstractions.ISecurityTokenService → Shopway.Application.Features.Users.Commands.AccessTokenResponse, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Application/Abstractions/ISecurityTokenService.cs:1
  • The namespaces Shopway.Persistence.Abstractions ↔ Shopway.Persistence.Framework depend on each other. The lightest dependency in the cycle is Shopway.Persistence.Framework → Shopway.Persistence.Abstractions (Shopway.Persistence.Framework.UnitOfWork → Shopway.Persistence.Abstractions.IUnitOfWork, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Persistence/Framework/UnitOfWork.cs:8
  • The namespaces Shopway.Domain.Common.DataProcessing ↔ Shopway.Domain.Common.DataProcessing.Abstractions depend on each other. The lightest dependency in the cycle is Shopway.Domain.Common.DataProcessing.Abstractions → Shopway.Domain.Common.DataProcessing (Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicFilter → Shopway.Domain.Common.DataProcessing.FilterByEntry, 4 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Domain/Common/DataProcessing/Abstractions/IDynamicFilter.cs:5
  • The namespaces Shopway.Domain.EntityKeys ↔ Shopway.Domain.Products depend on each other. The lightest dependency in the cycle is Shopway.Domain.EntityKeys → Shopway.Domain.Products (Shopway.Domain.EntityKeys.ProductKey → Shopway.Domain.Products.Product, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Domain/Products/ProductKey.cs:2
  • The namespaces Shopway.Application.Abstractions.CQRS ↔ Shopway.Application.Features.Orders.Queries ↔ Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery ↔ Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.DynamicProductWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery ↔ Shopway.Application.Features.Proxy ↔ Shopway.Application.Features.Proxy.GenericPageQuery ↔ Shopway.Application.Features.Proxy.GenericQuery.QueryById ↔ Shopway.Application.Features.Proxy.GenericQuery.QueryByKey depend on each other. The lightest dependency in the cycle is Shopway.Application.Abstractions.CQRS → Shopway.Application.Features.Proxy (Shopway.Application.Abstractions.CQRS.IMediatorProxyService → Shopway.Application.Features.Proxy.GenericProxyPageQuery, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Shopway.Application/Abstractions/CQRS/IMediatorProxyService.cs:2

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

  • `IProductRepository` declares 20 members under just 15 distinct name(s): `GetNamesAsync`, `GetByKeyOrDefaultAsync`, `AnyAsync`, `AnyAsync`, `VerifyIdsAsync`, `GetByIdAsync`, `GetByIdsAsync`, `GetByIdWithReviewAsync`, `GetByIdWithReviewAsync`, `GetByIdWithIncludesAsync`, `GetProductsDictionaryByNameAndRevision`, `Create`, `Update`, `Remove`, `PageAsync`, `PageAsync`, `QueryByIdAsync`, `QueryByIdAsync`, `QueryByKeyAsync`, `QueryByKeyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Shopway.Domain/Products/IProductRepository.cs:9

What to do

  • Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
AX7 · Slice cohesion1.0 / 10Critical✓ Tool-verified

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

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

  • `BatchUpsertOrderLineCommandHandler` (slice 'Orders') depends on `BatchUpsertOrderLineCommandUtilities` from slice 'Products'. — src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandHandler.cs:38
  • `BatchUpsertOrderLineCommandUtilities` (slice 'Products') depends on `BatchUpsertOrderLineCommand.BatchUpsertOrderLineRequest` from slice 'Orders'. — src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandUtilities.cs:18
  • `BatchUpsertOrderLineCommandValidator` (slice 'Orders') depends on `BatchUpsertOrderLineCommandUtilities` from slice 'Products'. — src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandValidator.cs:25
  • `RemoveOrderLineCommandHandler` (slice 'Products') depends on `RemoveOrderLineCommand` from slice 'Orders'. — src/Shopway.Application/Features/Orders/Commands/RemoveOrderLine/RemoveOrderLineCommandHandler.cs:11
  • `RemoveOrderLineCommandHandler` (slice 'Products') depends on `RemoveOrderLineResponse` from slice 'Orders'. — src/Shopway.Application/Features/Orders/Commands/RemoveOrderLine/RemoveOrderLineCommandHandler.cs:11
  • `UpdateOrderLineCommandHandler` (slice 'Products') depends on `UpdateOrderLineCommand` from slice 'Orders'. — src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandHandler.cs:12
  • `UpdateOrderLineCommandHandler` (slice 'Products') depends on `UpdateOrderLineResponse` from slice 'Orders'. — src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandHandler.cs:12
  • `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderOffsetPageDynamicWithMappingQuery` from slice 'Orders'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:16
  • `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderCursorPageDynamicWithMappingQuery` from slice 'Orders'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:32
  • `MediatorProxyService` (slice 'Proxy') depends on `ProductOffsetPageDynamicWithMappingQuery` from slice 'Products'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:16
  • `MediatorProxyService` (slice 'Proxy') depends on `ProductCursorPageDynamicWithMappingQuery` from slice 'Products'. — src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:32
  • `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderWithMappingQuery` from slice 'Orders'. — src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.OrderHeaders.cs:11
  • `MediatorProxyService` (slice 'Proxy') depends on `ProductWithMappingQuery` from slice 'Products'. — src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.Products.cs:11

What to do

  • Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

C1 · Data Protection6.5 / 10Adequate✓ Tool-verified

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

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

What to do

  • Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

C3 · Audit Trail5.0 / 10Adequate✓ Tool-verified

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

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

  • An audit marker (IAuditable / AddAuditing) was found, but no structural mechanism (an EF SaveChanges interceptor, an immutable audit-log type, or [Audited] usage) — the trail's completeness can't be confirmed from the source.

What to do

  • Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
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 aggregate9.2 / 10Exemplary✓ Tool-verified

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

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

  • `CachedOrderHeaderRepository.Update` saves `IOrderHeaderRepository`, `CacheUtilities` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Shopway.Persistence/Repositories/Decorators/CachedOrderHeaderRepository.cs:58
  • `CachedProductRepository.Update` saves `IProductRepository`, `CacheUtilities` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:56

What to do

  • Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
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 domain9.9 / 10Exemplary✓ 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.

  • `OrderHeader` reads `DateTimeOffset.UtcNow` inside `SoftDelete` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Shopway.Domain/Orders/OrderHeader.cs:127
  • `User` reads `DateTimeOffset.UtcNow` inside `SetTwoFactorToken` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Shopway.Domain/Users/User.cs:63

What to do

  • Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.
DM4 · Rich vs anemic model9.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.

  • `Customer` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Shopway.Domain/Users/Customer.cs:8

What to do

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

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

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

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

  • `OrderHeader` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, SoftDeletedOn, SoftDeleted). — src/Shopway.Domain/Orders/OrderHeader.cs:17
  • `OrderLine` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Orders/OrderLine.cs:7
  • `Payment` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Orders/Payment.cs:13
  • `Product` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Products/Product.cs:8
  • `Review` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Products/Review.cs:8
  • `Customer` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy). — src/Shopway.Domain/Users/Customer.cs:8
  • `User` exposes publicly writable state (Username, Email, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, and 5 more). — src/Shopway.Domain/Users/User.cs:9

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 boundary10.0 / 10Exemplary✓ 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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

ED5 · Idempotency9.3 / 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.

  • `Events.ClearCacheWhenReviewRemovedDomainEventHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Shopway.Application/Features/Products/Events/ClearCacheWhenReviewRemovedDomainEventHandler.cs:12

What to do

  • Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

IC1 · Incompleteness & stubs8.4 / 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.

  • `GetHashCode` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Shopway.Domain/Common/Utilities/IEnumerableUtilities.cs:123
  • `CreateAsync` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/Shopway.Infrastructure/Payments/DummyGatewayTypes/Refunds/RefundService.cs:5
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — src/Shopway.Application/Features/Proxy/GenericPageQuery/GenericPageQueryStrategyAttribute.cs:28, src/Shopway.Application/Features/Proxy/GenericQuery/QueryById/GenericStrategyByIdAttribute.cs:26, src/Shopway.Application/Features/Proxy/GenericQuery/QueryByKey/GenericStrategyByKeyAttribute.cs:26, …
  • A test is skipped ("Only for cleaning the database manually") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — test/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11

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)8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add a README to the 18 of 18 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 accuracy6.0 / 10Adequate◐ Sampled · advisory

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

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

  • docs/CONTRIBUTING.md links to `/fork`, but `fork` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CONTRIBUTING.md:3
  • docs/CONTRIBUTING.md links to `/compare`, but `compare` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CONTRIBUTING.md:4

What to do

  • Reconcile the README with reality: docs/CONTRIBUTING.md links to `/fork`, but `fork` does not exist; docs/CONTRIBUTING.md links to `/compare`, but `compare` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

What to do

  • Make types internal by default and expose only the deliberate public API — even for a small library, every public type is a stability contract.
P2 · Observability9.0 / 10Exemplary✓ Tool-verified

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

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

  • Only 4/6 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 6, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
  • `src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs` reports through `Console.Write…` at line 13 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs:13

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.
  • Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
P3 · Security & performance tooling1.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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 resilience10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

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

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

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

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

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

What to do

  • Raise allocation-aware density on the hot paths — currently 5 use(s) across 44,787 production line(s) (~0.1/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

S1 · Web-Security Posture5.5 / 10Adequate✓ 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.

  • `ValidateLifetime = false` means expired tokens keep working indefinitely, so a leaked or revoked token never stops being valid. — REDACTED:148
  • 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. (×2) — REDACTED:8, src/Shopway.App/Program.cs:7
  • No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — src/Shopway.Presentation/Controllers/UsersController.Google.cs:43

What to do

  • Re-enable token validation — `ValidateLifetime` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
  • 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.
  • Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness7.5 / 10Strong✓ Tool-verified

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

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

  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×3) — src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:45, src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:83, src/Shopway.Persistence/Pipelines/ReferenceValidationPipeline.cs:36

What to do

  • Sync-over-async (deadlock risk) through `.Result`
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 propagation9.4 / 10Exemplary✓ Tool-verified

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

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

  • Only 208/227 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. (×13) — src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:34, src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:40, src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:51, …
  • No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. (×2) — src/Shopway.Application/Middlewares/ErrorHandlingMiddleware.cs:46, src/Shopway.Persistence/Registration/HealthCheckRegistration.cs:109
  • No CancellationToken parameter, and the token `httpRequest.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpRequest.HttpContext.RequestAborted` on, or take a CancellationToken. — src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs:125
  • This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. (×2) — REDACTED:66, REDACTED:75
  • 4 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
  • Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). (×3) — src/Shopway.Application/Features/Orders/Events/DisplayMessageWhenOrderHeaderCreatedDomainEventHandler.cs:8, src/Shopway.Application/Features/Products/Events/DisplayMessageWhenProductCreatedDomainEventHandler.cs:8, src/Shopway.Application/Features/Products/Events/DisplayMessageWhenReviewAddedDomainEventHandler.cs:8
  • Its signature is fixed by the framework, and the token it carries (`context.CancellationToken`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.CancellationToken` to them. — src/Shopway.Persistence/BackgroundJobs/DeleteOutdatedSoftDeletableEntitiesJob.cs:24

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

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

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

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

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

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

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

What to do

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

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 Health87%StrongSolid.
Architecture62%Adequate — gated by AX7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity51%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness30%Weak — gated by D12, D13, P3, P5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security54%Adequate — gated by D28, D29, D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling87%StrongSolid.
Event-Driven100%ExemplaryStrongest area.
Performance82%StrongSolid.
Unscored — 4 check(s) recorded observations but carry no score

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

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 27 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • 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) — ddduniversitydb Error context canceled aspiredashboard Error context canceled paymentgateway Warning context canceled jaeger Error context canceled prometheus Error context canceled opentelemetrycollector Error context canceled papercut Error context canceled shopway.app Warning context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: jaeger Error context canceled paymentgateway Warning context canceled shopway.app Warning context canceled aspiredashboard Error context canceled ddduniversitydb Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build paymentgateway shopway.app 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.
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — 161 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — IL not measured — the target did not build
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 74 finding(s)
D28 · Secrets (history) · REDACTED · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×7
  • Namespace dependency cycle src/Shopway.Domain/Common/Results/ValidationResult.cs:2 — The namespaces Shopway.Domain.Common.Errors ↔ Shopway.Domain.Common.Results ↔ Shopway.Domain.Common.Results.Abstractions depend on each other. The lightest dependency in the cycle is Shopway.Domain.Common.Results → Shopway.Domain.Common.Results.Abstractions (Shopway.Domain.Common.Results.ValidationResult → Shopway.Domain.Common.Results.Abstractions.IValidationResult, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Shopway.Domain/Users/User.cs:3 — The namespaces Shopway.Domain.Users ↔ Shopway.Domain.Users.Authorization depend on each other. The lightest dependency in the cycle is Shopway.Domain.Users → Shopway.Domain.Users.Authorization (Shopway.Domain.Users.User → Shopway.Domain.Users.Authorization.Role, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Shopway.Application/Abstractions/ISecurityTokenService.cs:1 — The namespaces Shopway.Application.Abstractions ↔ Shopway.Application.Features.Users.Commands depend on each other. The lightest dependency in the cycle is Shopway.Application.Abstractions → Shopway.Application.Features.Users.Commands (Shopway.Application.Abstractions.ISecurityTokenService → Shopway.Application.Features.Users.Commands.AccessTokenResponse, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Shopway.Persistence/Framework/UnitOfWork.cs:8 — The namespaces Shopway.Persistence.Abstractions ↔ Shopway.Persistence.Framework depend on each other. The lightest dependency in the cycle is Shopway.Persistence.Framework → Shopway.Persistence.Abstractions (Shopway.Persistence.Framework.UnitOfWork → Shopway.Persistence.Abstractions.IUnitOfWork, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Shopway.Domain/Common/DataProcessing/Abstractions/IDynamicFilter.cs:5 — The namespaces Shopway.Domain.Common.DataProcessing ↔ Shopway.Domain.Common.DataProcessing.Abstractions depend on each other. The lightest dependency in the cycle is Shopway.Domain.Common.DataProcessing.Abstractions → Shopway.Domain.Common.DataProcessing (Shopway.Domain.Common.DataProcessing.Abstractions.IDynamicFilter → Shopway.Domain.Common.DataProcessing.FilterByEntry, 4 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Shopway.Domain/Products/ProductKey.cs:2 — The namespaces Shopway.Domain.EntityKeys ↔ Shopway.Domain.Products depend on each other. The lightest dependency in the cycle is Shopway.Domain.EntityKeys → Shopway.Domain.Products (Shopway.Domain.EntityKeys.ProductKey → Shopway.Domain.Products.Product, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Shopway.Application/Abstractions/CQRS/IMediatorProxyService.cs:2 — The namespaces Shopway.Application.Abstractions.CQRS ↔ Shopway.Application.Features.Orders.Queries ↔ Shopway.Application.Features.Orders.Queries.DynamicCursorOrderHeaderWithMappingQuery ↔ Shopway.Application.Features.Orders.Queries.DynamicOffsetOrderHeaderWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.DynamicOffsetProductWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.DynamicProductWithMappingQuery ↔ Shopway.Application.Features.Products.Queries.ProductCursorPageDynamicWithMappingQuery ↔ Shopway.Application.Features.Proxy ↔ Shopway.Application.Features.Proxy.GenericPageQuery ↔ Shopway.Application.Features.Proxy.GenericQuery.QueryById ↔ Shopway.Application.Features.Proxy.GenericQuery.QueryByKey depend on each other. The lightest dependency in the cycle is Shopway.Application.Abstractions.CQRS → Shopway.Application.Features.Proxy (Shopway.Application.Abstractions.CQRS.IMediatorProxyService → Shopway.Application.Features.Proxy.GenericProxyPageQuery, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×4
  • WriteOnlyPrivateField src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs:17 — private IUserContextService _userContextService — 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 src/Shopway.Application/Features/Users/Commands/RemoveRoleFromUser/RemoveRoleFromUserCommandHandler.cs:17 — private IUserContextService _userContextService — 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:32 — private GoogleOptions _googleOptions — 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 test/Shopway.Tests.Unit/UtilityTests/IEntityUtilityTests.cs:12 — private List<string> _orderLineAllPropertiesWithNestedProperties — 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.
D12 · Dependency Hygiene · Vulnerable · ×3
  • Vulnerable: MailKit — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: System.Linq.Dynamic.Core — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: OpenTelemetry.Exporter.OpenTelemetryProtocol — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · NoWarnInCsproj · ×1
  • NoWarnInCsproj src/Shopway.Presentation/Shopway.Presentation.csproj:11 — 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
Serious — 211 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 6 more in this group — see findings.md.
D23 · Boundary Type-Coupling · Cross-context type ProductId (Shopway → Products) · ×16
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:17 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.AnyAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:25 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.VerifyIdsAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:27 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.GetByIdAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:29 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.GetByIdsAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:31 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.GetByIdWithReviewAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:35 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.GetByIdWithIncludesAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:43 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.Remove — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:72 — ProductId (context Shopway) is exposed in Products's public surface via IProductRepository.QueryByIdAsync — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Product.cs:47 — ProductId (context Shopway) is exposed in Products's public surface via Product.Create — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Review.cs:36 — ProductId (context Shopway) is exposed in Products's public surface via Review.ProductId — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ProductCreatedDomainEvent.cs:5 — ProductId (context Shopway) is exposed in Products's public surface via ProductCreatedDomainEvent..ctor — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ProductCreatedDomainEvent.cs:7 — ProductId (context Shopway) is exposed in Products's public surface via ProductCreatedDomainEvent.New — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs:6 — ProductId (context Shopway) is exposed in Products's public surface via ReviewAddedDomainEvent..ctor — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs:8 — ProductId (context Shopway) is exposed in Products's public surface via ReviewAddedDomainEvent.New — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs:6 — ProductId (context Shopway) is exposed in Products's public surface via ReviewRemovedDomainEvent..ctor — couples the contexts.
  • Cross-context type ProductId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs:8 — ProductId (context Shopway) is exposed in Products's public surface via ReviewRemovedDomainEvent.New — couples the contexts.
X2 · Cancellation propagation · Async method without CancellationToken · ×16
  • Async method without CancellationToken: HasRolesAsync src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HasPermissionsAsync src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HasPermissionToReadAsync src/Shopway.Presentation/Authentication/RolePermissionAuthentication/UserAuthorizationService.cs:51 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HandleExceptionAsync src/Shopway.Application/Middlewares/ErrorHandlingMiddleware.cs:46 — No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
  • Async method without CancellationToken: StartSessionAsync src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Refund src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs:87 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPaymentGatewayEvent src/Shopway.Infrastructure/Payments/PaymentGatewayService.cs:125 — No CancellationToken parameter, and the token `httpRequest.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpRequest.HttpContext.RequestAborted` on, or take a CancellationToken.
  • Async method without CancellationToken: Refund src/Shopway.Domain/Orders/OrderHeader.cs:158 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Refund src/Shopway.Domain/Orders/Payment.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: WriteResponse src/Shopway.Persistence/Registration/HealthCheckRegistration.cs:109 — No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
  • Async method without CancellationToken: GetPermissionsAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:15 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HasPermissionsAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HasPermissionToReadAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HasRolesAsync src/Shopway.Persistence/Repositories/AuthorizationRepository.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddOutboxMessageConsumer src/Shopway.Persistence/Repositories/OutboxRepository.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PublishMessage PaymentGateway/Webhook/WebhookService.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
D23 · Boundary Type-Coupling · Cross-context type OrderHeaderId (Shopway → Orders) · ×15
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:10 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via IOrderHeaderRepository.GetByIdAsync — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:12 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via IOrderHeaderRepository.GetByIdWithOrderLineAsync — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:14 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via IOrderHeaderRepository.GetByIdWithIncludesAsync — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:16 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via IOrderHeaderRepository.IsOrderHeaderCreatedByUser — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:53 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via IOrderHeaderRepository.QueryByIdAsync — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/OrderHeader.cs:58 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderHeader.Create — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLine.cs:38 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderLine.OrderHeaderId — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLine.cs:44 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderLine.Create — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Payment.cs:33 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via Payment.OrderHeaderId — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs:6 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via NewPaymentAddedDomainEvent..ctor — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs:8 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via NewPaymentAddedDomainEvent.New — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderHeaderCreatedDomainEvent.cs:7 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderHeaderCreatedDomainEvent..ctor — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderHeaderCreatedDomainEvent.cs:9 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderHeaderCreatedDomainEvent.New — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs:7 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderLineAddedDomainEvent..ctor — couples the contexts.
  • Cross-context type OrderHeaderId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs:9 — OrderHeaderId (context Shopway) is exposed in Orders's public surface via OrderLineAddedDomainEvent.New — couples the contexts.
AX7 · Slice cohesion · Cross-slice coupling · ×13
  • Cross-slice coupling: Orders → Products src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandHandler.cs:38 — `BatchUpsertOrderLineCommandHandler` (slice 'Orders') depends on `BatchUpsertOrderLineCommandUtilities` from slice 'Products'.
  • Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandUtilities.cs:18 — `BatchUpsertOrderLineCommandUtilities` (slice 'Products') depends on `BatchUpsertOrderLineCommand.BatchUpsertOrderLineRequest` from slice 'Orders'.
  • Cross-slice coupling: Orders → Products src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandValidator.cs:25 — `BatchUpsertOrderLineCommandValidator` (slice 'Orders') depends on `BatchUpsertOrderLineCommandUtilities` from slice 'Products'.
  • Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/RemoveOrderLine/RemoveOrderLineCommandHandler.cs:11 — `RemoveOrderLineCommandHandler` (slice 'Products') depends on `RemoveOrderLineCommand` from slice 'Orders'.
  • Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/RemoveOrderLine/RemoveOrderLineCommandHandler.cs:11 — `RemoveOrderLineCommandHandler` (slice 'Products') depends on `RemoveOrderLineResponse` from slice 'Orders'.
  • Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandHandler.cs:12 — `UpdateOrderLineCommandHandler` (slice 'Products') depends on `UpdateOrderLineCommand` from slice 'Orders'.
  • Cross-slice coupling: Products → Orders src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandHandler.cs:12 — `UpdateOrderLineCommandHandler` (slice 'Products') depends on `UpdateOrderLineResponse` from slice 'Orders'.
  • Cross-slice coupling: Proxy → Orders src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:16 — `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderOffsetPageDynamicWithMappingQuery` from slice 'Orders'.
  • Cross-slice coupling: Proxy → Orders src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs:32 — `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderCursorPageDynamicWithMappingQuery` from slice 'Orders'.
  • Cross-slice coupling: Proxy → Products src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:16 — `MediatorProxyService` (slice 'Proxy') depends on `ProductOffsetPageDynamicWithMappingQuery` from slice 'Products'.
  • Cross-slice coupling: Proxy → Products src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs:32 — `MediatorProxyService` (slice 'Proxy') depends on `ProductCursorPageDynamicWithMappingQuery` from slice 'Products'.
  • Cross-slice coupling: Proxy → Orders src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.OrderHeaders.cs:11 — `MediatorProxyService` (slice 'Proxy') depends on `OrderHeaderWithMappingQuery` from slice 'Orders'.
  • Cross-slice coupling: Proxy → Products src/Shopway.Application/Features/Proxy/Query/MediatorProxyService.Products.cs:11 — `MediatorProxyService` (slice 'Proxy') depends on `ProductWithMappingQuery` from slice 'Products'.
D23 · Boundary Type-Coupling · Cross-context type ReviewId (Shopway → Products) · ×6
  • Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/IProductRepository.cs:31 — ReviewId (context Shopway) is exposed in Products's public surface via IProductRepository.GetByIdWithReviewAsync — couples the contexts.
  • Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Review.cs:44 — ReviewId (context Shopway) is exposed in Products's public surface via Review.Create — couples the contexts.
  • Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs:6 — ReviewId (context Shopway) is exposed in Products's public surface via ReviewAddedDomainEvent..ctor — couples the contexts.
  • Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewAddedDomainEvent.cs:8 — ReviewId (context Shopway) is exposed in Products's public surface via ReviewAddedDomainEvent.New — couples the contexts.
  • Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs:6 — ReviewId (context Shopway) is exposed in Products's public surface via ReviewRemovedDomainEvent..ctor — couples the contexts.
  • Cross-context type ReviewId (Shopway → Products) src/Shopway.Domain/Products/Events/ReviewRemovedDomainEvent.cs:8 — ReviewId (context Shopway) is exposed in Products's public surface via ReviewRemovedDomainEvent.New — couples the contexts.
D30 · Dependency Vulnerabilities · Medium CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Deprecated · ×5
  • Deprecated: FluentValidation.AspNetCore REDACTED:10 — FluentValidation.AspNetCore 11.3.0 — Legacy
  • Deprecated: xunit test/Shopway.Tests.Unit/Shopway.Tests.Unit.csproj:17 — xunit 2.9.0 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/Shopway.Tests.Integration/Shopway.Tests.Integration.csproj:19 — xunit 2.9.0 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit REDACTED:21 — xunit 2.9.0 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit REDACTED:17 — xunit 2.9.0 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
D23 · Boundary Type-Coupling · Cross-context type ProductId (Shopway → Orders) · ×5
  • Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLineKey.cs:10 — ProductId (context Shopway) is exposed in Orders's public surface via OrderLineKey.ProductId — couples the contexts.
  • Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLineKey.cs:12 — ProductId (context Shopway) is exposed in Orders's public surface via OrderLineKey..ctor — couples the contexts.
  • Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLineKey.cs:17 — ProductId (context Shopway) is exposed in Orders's public surface via OrderLineKey.Create — couples the contexts.
  • Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/ValueObjects/ProductSummary.cs:26 — ProductId (context Shopway) is exposed in Orders's public surface via ProductSummary.ProductId — couples the contexts.
  • Cross-context type ProductId (Shopway → Orders) src/Shopway.Domain/Orders/ValueObjects/ProductSummary.cs:32 — ProductId (context Shopway) is exposed in Orders's public surface via ProductSummary.Create — couples the contexts.
D31 · IaC & Container Security · Medium IaC · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D23 · Boundary Type-Coupling · Cross-context type OrderLineId (Shopway → Orders) · ×4
  • Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:12 — OrderLineId (context Shopway) is exposed in Orders's public surface via IOrderHeaderRepository.GetByIdWithOrderLineAsync — couples the contexts.
  • Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/OrderLine.cs:42 — OrderLineId (context Shopway) is exposed in Orders's public surface via OrderLine.Create — couples the contexts.
  • Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs:7 — OrderLineId (context Shopway) is exposed in Orders's public surface via OrderLineAddedDomainEvent..ctor — couples the contexts.
  • Cross-context type OrderLineId (Shopway → Orders) src/Shopway.Domain/Orders/Events/OrderLineAddedDomainEvent.cs:9 — OrderLineId (context Shopway) is exposed in Orders's public surface via OrderLineAddedDomainEvent.New — couples the contexts.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: ProductOffsetPageQueryHandler.cs ↔ ProductRepository.cs src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs:1 — `src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs` and `src/Shopway.Persistence/Repositories/ProductRepository.cs` change together 62% of the time (8 of the 13 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `68653550` simplify filtering and sorting (#32); `d92b0311` specification simplify (at that commit the files were still `src/Shopway.Application/CQRS/Products/Queries/QueryProduct/ProductPageQueryHandler.cs` and `src/Shopway.Persistance/Repositories/ProductRepository.cs`); `119c7f6d` correction (at that commit the files were still `src/Shopway.Application/CQRS/Products/Queries/QueryProduct/ProductPageQueryHandler.cs` and `src/Shopway.Persistance/Repositories/ProductRepository.cs`) — run `git show` on any of them.
  • Change coupling: IProductRepository.cs ↔ CachedOrderHeaderRepository.cs src/Shopway.Domain/Products/IProductRepository.cs:1 — `src/Shopway.Domain/Products/IProductRepository.cs` and `src/Shopway.Persistence/Repositories/Decorators/CachedOrderHeaderRepository.cs` change together 54% of the time (7 of the 13 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `021ab2b7` feat: use List instead of IList (#179); `9aa27a98` small fixes (#147); `f1a2bbb9` correction (at that commit the files were still `src/Shopway.Domain/Abstractions/Repositories/IProductRepository.cs` and `src/Shopway.Persistance/Repositories/Decorators/CachedOrderHeaderRepository.cs`) — run `git show` on any of them.
  • Change coupling: ProductOffsetPageQueryHandler.cs ↔ CachedProductRepository.cs src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs:1 — `src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs` and `src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs` change together 54% of the time (7 of the 13 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `68653550` simplify filtering and sorting (#32); `119c7f6d` correction (at that commit the files were still `src/Shopway.Application/CQRS/Products/Queries/QueryProduct/ProductPageQueryHandler.cs` and `src/Shopway.Persistance/Repositories/Decorators/CachedProductRepository.cs`); `a03a455b` add utility method to page results by queryable and specification (at that commit the files were still `src/Shopway.Application/CQRS/Products/Queries/QueryProduct/ProductPageQueryHandler.cs` and `src/Shopway.Persistance/Repositories/Decorators/CachedProductRepository.cs`) — run `git show` on any of them.
  • Change coupling: ProductRepository.cs ↔ SpecificationUtilities.cs src/Shopway.Persistence/Repositories/ProductRepository.cs:1 — `src/Shopway.Persistence/Repositories/ProductRepository.cs` and `src/Shopway.Persistence/Specifications/SpecificationUtilities.cs` change together 50% of the time (14 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `d5282ffc` feat: refactor specification (#77); `b8e93627` refator specification (#67) (at that commit the file was still `src/Shopway.Persistence/Abstractions/RepositoryBase.cs`); `68653550` simplify filtering and sorting (#32) (at that commit the file was still `src/Shopway.Persistence/Abstractions/RepositoryBase.cs`) — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×4
  • Duplicated block (13 lines × 2) REDACTED:56 — REDACTED:56-68 | REDACTED:127-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:56` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) REDACTED:79 — REDACTED:79-91 | REDACTED:102-114 — 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. 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 (13 lines × 2) src/Shopway.Application/Utilities/FluentValidationUtilities.cs:139 — src/Shopway.Application/Utilities/FluentValidationUtilities.cs:139-151 | src/Shopway.Application/Utilities/FluentValidationUtilities.cs:183-195 — 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. 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 (13 lines × 2) src/Shopway.Application/Features/Proxy/GenericValidators/GenericFluentValidationUtilities.cs:117 — src/Shopway.Application/Features/Proxy/GenericValidators/GenericFluentValidationUtilities.cs:117-129 | src/Shopway.Application/Utilities/FluentValidationUtilities.cs:111-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Application/Features/Proxy/GenericValidators/GenericFluentValidationUtilities.cs:117` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) src/Shopway.Application/Cache/ApplicationCache.AllowedFilterOperations.cs:15 — src/Shopway.Application/Cache/ApplicationCache.AllowedFilterOperations.cs:15-24 | src/Shopway.Application/Cache/ApplicationCache.AllowedFilterProperties.cs:15-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Application/Cache/ApplicationCache.AllowedFilterOperations.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Shopway.Application/Features/Users/Commands/AddPermissionToRole/AddPermissionToRoleCommandHandler.cs:43 — src/Shopway.Application/Features/Users/Commands/AddPermissionToRole/AddPermissionToRoleCommandHandler.cs:43-52 | src/Shopway.Application/Features/Users/Queries/GetPermissionDetails/GetPermissionDetailsQueryHandler.cs:29-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) PaymentGateway/Cryptography/HashUtilities.cs:10 — PaymentGateway/Cryptography/HashUtilities.cs:10-19 | src/Shopway.Domain/Common/Utilities/HashUtilities.cs:10-19 — 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 (10 lines × 2) src/Shopway.Presentation/FastEndpoints/Proxy/ProxyGroup.cs:13 — src/Shopway.Presentation/FastEndpoints/Proxy/ProxyGroup.cs:13-22 | src/Shopway.Presentation/FastEndpoints/Users/UsersGroup.cs:13-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) src/Shopway.Domain/Orders/OrderLineKeyJsonConverter.cs:48 — src/Shopway.Domain/Orders/OrderLineKeyJsonConverter.cs:48-52 | src/Shopway.Domain/Products/ReviewKeyJsonConverter.cs:42-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Domain/Orders/OrderLineKeyJsonConverter.cs:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Shopway.Domain/Products/ValueObjects/ProductName.cs:37 — src/Shopway.Domain/Products/ValueObjects/ProductName.cs:37-41 | src/Shopway.Domain/Users/ValueObjects/Username.cs:37-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 2) src/Shopway.Domain/Users/ValueObjects/AccessToken.cs:32 — src/Shopway.Domain/Users/ValueObjects/AccessToken.cs:32-36 | src/Shopway.Domain/Users/ValueObjects/RefreshToken.cs:36-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Shopway.Domain/Users/ValueObjects/PasswordHash.cs:33 — src/Shopway.Domain/Users/ValueObjects/PasswordHash.cs:33-37 | src/Shopway.Domain/Users/ValueObjects/TwoFactorTokenHash.cs:37-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D6 · Cohesion (LCOM4) · Low cohesion · ×4
  • Low cohesion: Specification (LCOM4 16) src/Shopway.Persistence/Specifications/Specification.cs:44 — Specification's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: OrderHeadersController (LCOM4 8) src/Shopway.Presentation/Controllers/OrderHeaderController.Payment.cs:13 — OrderHeadersController's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: User (LCOM4 5) src/Shopway.Domain/Users/User.cs:9 — User's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: OrderHeader (LCOM4 4) src/Shopway.Domain/Orders/OrderHeader.cs:17 — OrderHeader's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D23 · Boundary Type-Coupling · Cross-context type UserId (Users → Orders) · ×3
  • Cross-context type UserId (Users → Orders) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:16 — UserId (context Users) is exposed in Orders's public surface via IOrderHeaderRepository.IsOrderHeaderCreatedByUser — couples the contexts.
  • Cross-context type UserId (Users → Orders) src/Shopway.Domain/Orders/OrderHeader.cs:49 — UserId (context Users) is exposed in Orders's public surface via OrderHeader.UserId — couples the contexts.
  • Cross-context type UserId (Users → Orders) src/Shopway.Domain/Orders/OrderHeader.cs:59 — UserId (context Users) is exposed in Orders's public surface via OrderHeader.Create — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type PaymentId (Shopway → Orders) · ×3
  • Cross-context type PaymentId (Shopway → Orders) src/Shopway.Domain/Orders/OrderHeader.cs:158 — PaymentId (context Shopway) is exposed in Orders's public surface via OrderHeader.Refund — couples the contexts.
  • Cross-context type PaymentId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs:6 — PaymentId (context Shopway) is exposed in Orders's public surface via NewPaymentAddedDomainEvent..ctor — couples the contexts.
  • Cross-context type PaymentId (Shopway → Orders) src/Shopway.Domain/Orders/Events/NewPaymentAddedDomainEvent.cs:8 — PaymentId (context Shopway) is exposed in Orders's public surface via NewPaymentAddedDomainEvent.New — couples the contexts.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:29 — src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:29-35 | src/Shopway.Domain/Orders/IOrderHeaderRepository.cs:41-47 — 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.
  • Duplicated block (7 lines × 2) src/Shopway.Domain/Products/IProductRepository.cs:48 — src/Shopway.Domain/Products/IProductRepository.cs:48-54 | src/Shopway.Domain/Products/IProductRepository.cs:60-66 — 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.
  • Duplicated block (7 lines × 2) src/Shopway.Domain/Common/Discriminators/StrategyCacheFactory.cs:16 — src/Shopway.Domain/Common/Discriminators/StrategyCacheFactory.cs:16-22 | src/Shopway.Domain/Common/Discriminators/StrategyCacheFactory.cs:63-69 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:10 — src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:10-15 | src/Shopway.Application/Features/Proxy/GenericPageQuery/OffsetPage/GenericOffsetPageQuery.cs:10-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) PaymentGateway/DummyGatewayTypes/Session.cs:3 — PaymentGateway/DummyGatewayTypes/Session.cs:3-8 | src/Shopway.Infrastructure/Payments/DummyGatewayTypes/Sessions/Session.cs:3-8 — before extracting anything, compare `PaymentGateway/DummyGatewayTypes/Session.cs` and `src/Shopway.Infrastructure/Payments/DummyGatewayTypes/Sessions/Session.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `PaymentGateway/DummyGatewayTypes/Session.cs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/Shopway.Domain/Users/ValueObjects/FirstName.cs:41 — src/Shopway.Domain/Users/ValueObjects/FirstName.cs:41-46 | src/Shopway.Domain/Users/ValueObjects/LastName.cs:41-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×3
  • Sync-over-async (deadlock risk) through `.Result` src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:45 — 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.
  • Sync-over-async (deadlock risk) through `.Result` src/Shopway.Domain/Common/Utilities/TaskUtilities.cs:83 — 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.
  • Sync-over-async (deadlock risk) through `.Result` src/Shopway.Persistence/Pipelines/ReferenceValidationPipeline.cs:36 — 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.
X2 · Cancellation propagation · Async method drops its CancellationToken · ×3
  • Async method drops its CancellationToken: Handle src/Shopway.Application/Features/Orders/Events/DisplayMessageWhenOrderHeaderCreatedDomainEventHandler.cs:8 — Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async method drops its CancellationToken: Handle src/Shopway.Application/Features/Products/Events/DisplayMessageWhenProductCreatedDomainEventHandler.cs:8 — Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async method drops its CancellationToken: Handle src/Shopway.Application/Features/Products/Events/DisplayMessageWhenReviewAddedDomainEventHandler.cs:8 — Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
D12 · Dependency Hygiene · Prerelease dependency · ×2
  • Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore — OpenTelemetry.Exporter.Prometheus.AspNetCore resolves to 1.7.0-rc.1, 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: OpenTelemetry.Instrumentation.EntityFrameworkCore — OpenTelemetry.Instrumentation.EntityFrameworkCore resolves to 1.0.0-beta.11, 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.
D23 · Boundary Type-Coupling · Cross-context type CustomerId (Shopway → Users) · ×2
  • Cross-context type CustomerId (Shopway → Users) src/Shopway.Domain/Users/Customer.cs:58 — CustomerId (context Shopway) is exposed in Users's public surface via Customer.Create — couples the contexts.
  • Cross-context type CustomerId (Shopway → Users) src/Shopway.Domain/Users/User.cs:32 — CustomerId (context Shopway) is exposed in Users's public surface via User.CustomerId — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×2
  • Duplicated block (22 lines × 3) src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:42 — src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:42-63 | src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByKeyQueryFastEndpoint.cs:42-63 | src/Shopway.Presentation/FastEndpoints/Proxy/ProxyGenericPageQueryFastEndpoint.cs:43-64 — before extracting anything, compare `src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs` and `src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByKeyQueryFastEndpoint.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `GenericProxyByIdQuery` in one and `GenericProxyByKeyQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (22 lines × 3) src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByIdQueryMinimalEndpoint.cs:44 — src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByIdQueryMinimalEndpoint.cs:44-65 | src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByKeyQueryMinimalEndpoint.cs:44-65 | src/Shopway.Presentation/MinimalEndpoints/Proxy/ProxyGenericPageQueryMinimalEndpoint.cs:45-66 — before extracting anything, compare `src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByIdQueryMinimalEndpoint.cs` and `src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByKeyQueryMinimalEndpoint.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) src/Shopway.Application/Features/Users/Commands/AddPermissionToRole/AddPermissionToRoleCommandHandler.cs:18 — src/Shopway.Application/Features/Users/Commands/AddPermissionToRole/AddPermissionToRoleCommandHandler.cs:18-35 | src/Shopway.Application/Features/Users/Commands/RemovePermissionFromRole/RemovePermissionFromRoleCommandHandler.cs:17-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `AddPermissionToRoleCommand` in one and `RemovePermissionFromRoleCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (18 lines × 2) src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:28 — src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:28-45 | src/Shopway.Application/Features/Users/Commands/LoginTwoFactorTopt/LoginTwoFactorToptCommandHandler.cs:32-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `LogUserCommand` in one and `LoginTwoFactorToptCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) src/Shopway.Application/Features/Users/Commands/LoginByGoogle/LoginByGoogleCommandHandler.cs:61 — src/Shopway.Application/Features/Users/Commands/LoginByGoogle/LoginByGoogleCommandHandler.cs:61-76 | src/Shopway.Application/Features/Users/Commands/RefreshAccessToken/RefreshAccessTokenCommandHandler.cs:59-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Application/Features/Users/Commands/LoginByGoogle/LoginByGoogleCommandHandler.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) src/Shopway.Application/Features/Users/Commands/AddPropertyToReadPermission/AddPropertyToReadPermissionCommandHandler.cs:18 — src/Shopway.Application/Features/Users/Commands/AddPropertyToReadPermission/AddPropertyToReadPermissionCommandHandler.cs:18-33 | src/Shopway.Application/Features/Users/Commands/RemovePropertyFromReadPermission/RemovePropertyFromReadPermissionCommandHandler.cs:17-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `AddPropertyToReadPermissionCommand` in one and `RemovePropertyFromReadPermissionCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×2
  • One operation mutates 2 aggregates: CachedOrderHeaderRepository.Update src/Shopway.Persistence/Repositories/Decorators/CachedOrderHeaderRepository.cs:58 — `CachedOrderHeaderRepository.Update` saves `IOrderHeaderRepository`, `CacheUtilities` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: CachedProductRepository.Update src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:56 — `CachedProductRepository.Update` saves `IProductRepository`, `CacheUtilities` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×2
  • Domain type reads the wall clock: OrderHeader src/Shopway.Domain/Orders/OrderHeader.cs:127 — `OrderHeader` reads `DateTimeOffset.UtcNow` inside `SoftDelete` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.
  • Domain type reads the wall clock: User src/Shopway.Domain/Users/User.cs:63 — `User` reads `DateTimeOffset.UtcNow` inside `SetTwoFactorToken` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.
X2 · Cancellation propagation · Async endpoint handler without CancellationToken · ×2
  • Async endpoint handler without CancellationToken: /publish-payment-result/success REDACTED:66 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /publish-payment-result/failure REDACTED:75 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
AX2 · Stateful singletons · Stateful singleton · ×1
  • Stateful singleton: WebhookService PaymentGateway/Webhook/WebhookService.cs:8 — `WebhookService` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions; e.g. `_subscriptions` at line 14).
D1 · Cyclomatic Complexity · StringUtilities.SqlLike (cyclomatic 35) · ×1
  • StringUtilities.SqlLike (cyclomatic 35) src/Shopway.Domain/Common/Utilities/StringUtilities.cs:166 — StringUtilities.SqlLike has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode test/Shopway.Tests.Benchmark/Benchmarks/ReflectionUtilitiesBenchmarks.cs:80 — 4 consecutive commented-code lines
D2 · Cognitive Complexity · StringUtilities.SqlLike (cognitive 83) · ×1
  • StringUtilities.SqlLike (cognitive 83) src/Shopway.Domain/Common/Utilities/StringUtilities.cs:166 — StringUtilities.SqlLike has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FilterByEntryJsonConverter.Read (cognitive 32) · ×1
  • FilterByEntryJsonConverter.Read (cognitive 32) src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:12 — FilterByEntryJsonConverter.Read has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MappingEntryJsonConverter.Read (cognitive 26) · ×1
  • MappingEntryJsonConverter.Read (cognitive 26) src/Shopway.Domain/Common/DataProcessing/MappingEntryJsonConverter.cs:10 — MappingEntryJsonConverter.Read has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationCache.CreateValidationResultCache (cognitive 19) · ×1
  • ApplicationCache.CreateValidationResultCache (cognitive 19) src/Shopway.Application/Cache/ApplicationCache.ResultValidations.cs:21 — ApplicationCache.CreateValidationResultCache has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · MappingEntry.GetAllPropertyNamesWithHierarchy (cognitive 17) · ×1
  • MappingEntry.GetAllPropertyNamesWithHierarchy (cognitive 17) src/Shopway.Domain/Common/DataProcessing/MappingEntry.cs:21 — MappingEntry.GetAllPropertyNamesWithHierarchy has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: Error src/Shopway.Domain/Common/Errors/Error.Common.cs — TooManyMethods — 88 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods, declared across 2 files: Errors/Error.Common.cs (19), Errors/Error.cs (13). The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: ProductDictionaryCursorPageQueryHandler.cs → ProductOffsetPageQueryHandler.cs, CachedProductRepository.cs, ProductRepository.cs src/Shopway.Application/Features/Products/Queries/ProductDictionaryCursorPageQuery/ProductDictionaryCursorPageQueryHandler.cs — `src/Shopway.Application/Features/Products/Queries/ProductDictionaryCursorPageQuery/ProductDictionaryCursorPageQueryHandler.cs` changes together with 3 other files — `src/Shopway.Application/Features/Products/Queries/ProductOffsetPageStaticQuery/ProductOffsetPageQueryHandler.cs`, `src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs`, `src/Shopway.Persistence/Repositories/ProductRepository.cs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:41 — src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:41-70 | src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByKeyQueryFastEndpoint.cs:41-70 | src/Shopway.Presentation/FastEndpoints/Proxy/ProxyGenericPageQueryFastEndpoint.cs:42-73 | src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByIdQueryMinimalEndpoint.cs:43-72 | src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByKeyQueryMinimalEndpoint.cs:43-72 | src/Shopway.Presentation/MinimalEndpoints/Proxy/ProxyGenericPageQueryMinimalEndpoint.cs:44-75 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs:21 — src/Shopway.Application/Features/Users/Commands/AddRoleToUser/AddRoleToUserCommandHandler.cs:21-48 | src/Shopway.Application/Features/Users/Commands/RemoveRoleFromUser/RemoveRoleFromUserCommandHandler.cs:21-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `AddRoleToUserCommand` in one and `RemoveRoleFromUserCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:48 — src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:48-68 | src/Shopway.Application/Features/Users/Commands/LoginTwoFactorTopt/LoginTwoFactorToptCommandHandler.cs:61-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandHandler.cs:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/Shopway.Application/Features/Users/Commands/LoginTwoFactorSecondStep/LoginTwoFactorSecondStepCommandHandler.cs:53 — src/Shopway.Application/Features/Users/Commands/LoginTwoFactorSecondStep/LoginTwoFactorSecondStepCommandHandler.cs:53-67 | src/Shopway.Application/Features/Users/Commands/RefreshAccessToken/RefreshAccessTokenCommandHandler.cs:54-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:71 — src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:71-87 | src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:133-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×1
  • Duplicated block (12 lines × 6) src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:44 — src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs:44-55 | src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByKeyQueryFastEndpoint.cs:44-55 | src/Shopway.Presentation/FastEndpoints/Proxy/ProxyGenericPageQueryFastEndpoint.cs:45-56 | src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByIdQueryMinimalEndpoint.cs:46-57 | src/Shopway.Presentation/MinimalEndpoints/Proxy/GenericProxyByKeyQueryMinimalEndpoint.cs:46-57 | src/Shopway.Presentation/MinimalEndpoints/Proxy/ProxyGenericPageQueryMinimalEndpoint.cs:47-58 — before extracting anything, compare `src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByIdQueryFastEndpoint.cs` and `src/Shopway.Presentation/FastEndpoints/Proxy/GenericProxyByKeyQueryFastEndpoint.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `GenericProxyByIdQuery` in one and `GenericProxyByKeyQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/Shopway.Application/Features/Orders/Commands/AddOrderLine/AddOrderLineCommandValidator.Fluent.cs:11 — src/Shopway.Application/Features/Orders/Commands/AddOrderLine/AddOrderLineCommandValidator.Fluent.cs:11-22 | src/Shopway.Application/Features/Orders/Commands/UpdateOrderLine/UpdateOrderLineCommandValidator.Fluent.cs:11-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs:68 — SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs:68-76 | SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs:68-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) src/Shopway.Application/Abstractions/CursorPageQueryValidator.Fluent.cs:21 — src/Shopway.Application/Abstractions/CursorPageQueryValidator.Fluent.cs:21-42 | src/Shopway.Application/Abstractions/OffsetPageQueryValidator.Fluent.cs:16-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shopway.Application/Abstractions/CursorPageQueryValidator.Fluent.cs:21` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandValidator.Fluent.cs:11 — src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommandValidator.Fluent.cs:11-16 | src/Shopway.Application/Features/Users/Commands/LoginTwoFactorFirstStep/LoginTwoFactorFirstStepCommandValidator.Fluent.cs:11-16 | src/Shopway.Application/Features/Users/Commands/LoginTwoFactorTopt/LoginTwoFactorToptCommandValidate.Fluent.cs:11-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) src/Shopway.Domain/Products/ValueObjects/Description.cs:32 — src/Shopway.Domain/Products/ValueObjects/Description.cs:32-36 | src/Shopway.Domain/Products/ValueObjects/Revision.cs:33-37 | src/Shopway.Domain/Products/ValueObjects/Title.cs:32-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — test suite did not build — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
DM4 · Rich vs anemic model · Anemic entity · ×1
  • Anemic entity: Customer src/Shopway.Domain/Users/Customer.cs:8 — `Customer` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
ED5 · Idempotency · Non-idempotent mutation · ×1
  • Non-idempotent mutation: Events.ClearCacheWhenReviewRemovedDomainEventHandler.Handle src/Shopway.Application/Features/Products/Events/ClearCacheWhenReviewRemovedDomainEventHandler.cs:12 — `Events.ClearCacheWhenReviewRemovedDomainEventHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
IC1 · Incompleteness & stubs · Hollow method · ×1
  • Hollow method — returns a constant without doing the work src/Shopway.Domain/Common/Utilities/IEnumerableUtilities.cs:123 — `GetHashCode` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body — does nothing with its inputs src/Shopway.Infrastructure/Payments/DummyGatewayTypes/Refunds/RefundService.cs:5 — `CreateAsync` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
P12 · CI test-gate honesty · CI test gate excludes suites by filter · ×1
  • CI test gate excludes suites by filter REDACTED:29 — `dotnet test DomainDrivenDesignUniversity.sln --logger "trx;LogFileName=test-results.trx" --no-build --verbosity normal --filter "UnitTest…` filters with `UnitTest=Application|UnitTest=Architecture|UnitTest=Domain|UnitTest=Utility|UnitTest=Infrastructure` — 109 test(s) it drops — run by no other gate before merge (e.g. EntityIdComparerGeneratorTests.EntityIdComparerGenerator_ShouldGenerateEntityIdComparerAttribute, EntityIdComparerGeneratorTests.EntityIdComparerGenerator_ShouldGenerateEntityIdComparer). Run what it drops in another job before merge (a complementary filter), or remove the filter.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
S1 · Web-Security Posture · Token validation disabled · ×1
  • Token validation disabled REDACTED:148 — `ValidateLifetime = false` means expired tokens keep working indefinitely, so a leaked or revoked token never stops being valid.
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.
X2 · Cancellation propagation · Async method drops its ambient CancellationToken · ×1
  • Async method drops its ambient CancellationToken: Execute src/Shopway.Persistence/BackgroundJobs/DeleteOutdatedSoftDeletableEntitiesJob.cs:24 — Its signature is fixed by the framework, and the token it carries (`context.CancellationToken`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.CancellationToken` to them.
Minor — 165 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×110
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Shopway.Domain/Common/Utilities/QueryableUtilities.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Shopway.Persistence/Utilities/QueryableUtilities.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 src/Shopway.Domain/Common/Utilities/StringUtilities.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 src/Shopway.Persistence/Specifications/Specification.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 src/Shopway.Domain/Common/Utilities/ReflectionUtilities.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 src/Shopway.Domain/Common/Errors/Error.Common.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 src/Shopway.Domain/Common/DataProcessing/DataTransferObject.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 src/Shopway.Application/Utilities/FluentValidationUtilities.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 src/Shopway.Domain/Common/Utilities/ExpressionUtilities.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 src/Shopway.Persistence/Specifications/SpecificationUtilities.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 src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.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 src/Shopway.Application/Features/Proxy/MediatorProxyService.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 src/Shopway.Infrastructure/Builders/Batch/BatchResponseEntryBuilder.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 src/Shopway.Infrastructure/Builders/Batch/BatchResponseBuilder.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 src/Shopway.Domain/Common/DataProcessing/FilterByEntryJsonConverter.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdGenerator/EntityIdToGenerateEntry.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 src/Shopway.Persistence/Repositories/ProductRepository.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 src/Shopway.Application/Cache/ApplicationCache.ResultValidations.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 src/Shopway.Application/Features/Orders/Commands/BatchUpsertOrderLine/BatchUpsertOrderLineCommandHandler.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 src/Shopway.Domain/Common/DataProcessing/IncludeBuilder.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 src/Shopway.Domain/Users/ValueObjects/Address.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 src/Shopway.Application/Registration/MediatorRegistration.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.
  • + 85 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×8
  • Outdated: FastEndpoints src/Shopway.Presentation/Shopway.Presentation.csproj:21 — FastEndpoints 5.29.0 → 8.3.0 available (referenced by Shopway.Presentation).
  • Outdated: FastEndpoints.AspVersioning src/Shopway.Presentation/Shopway.Presentation.csproj:22 — FastEndpoints.AspVersioning 5.29.0 → 8.3.0 available (referenced by Shopway.Presentation).
  • Outdated: FastEndpoints.Security src/Shopway.Presentation/Shopway.Presentation.csproj:23 — FastEndpoints.Security 5.29.0 → 8.3.0 available (referenced by Shopway.Presentation).
  • Outdated: FastEndpoints.Swagger src/Shopway.Presentation/Shopway.Presentation.csproj:24 — FastEndpoints.Swagger 5.29.0 → 8.3.0 available (referenced by Shopway.Presentation).
  • Outdated: Scrutor REDACTED:19 — Scrutor 4.2.2 → 7.0.0 available (referenced by Shopway.Presentation).
  • Outdated: Swashbuckle.AspNetCore REDACTED:16 — Swashbuckle.AspNetCore 6.7.3 → 10.3.1 available (referenced by Shopway.Presentation).
  • Outdated: coverlet.collector SourceGenerators/Shopway.SourceGenerator.Base.Tests.Unit/Shopway.SourceGenerator.Base.Tests.Unit.csproj:14 — coverlet.collector 6.0.2 → 10.1.0 available (referenced by Shopway.Tests.Unit).
  • Outdated: Xunit.DependencyInjection REDACTED:18 — Xunit.DependencyInjection 9.4.0 → 12.0.1 available (referenced by Shopway.Tests.Performance).
DM5 · Encapsulated state · Mutable entity · ×7
  • Mutable entity: OrderHeader src/Shopway.Domain/Orders/OrderHeader.cs:17 — `OrderHeader` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, SoftDeletedOn, SoftDeleted).
  • Mutable entity: OrderLine src/Shopway.Domain/Orders/OrderLine.cs:7 — `OrderLine` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy).
  • Mutable entity: Payment src/Shopway.Domain/Orders/Payment.cs:13 — `Payment` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy).
  • Mutable entity: Product src/Shopway.Domain/Products/Product.cs:8 — `Product` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy).
  • Mutable entity: Review src/Shopway.Domain/Products/Review.cs:8 — `Review` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy).
  • Mutable entity: Customer src/Shopway.Domain/Users/Customer.cs:8 — `Customer` exposes publicly writable state (CreatedOn, UpdatedOn, CreatedBy, UpdatedBy).
  • Mutable entity: User src/Shopway.Domain/Users/User.cs:9 — `User` exposes publicly writable state (Username, Email, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, and 5 more).
IC1 · Incompleteness & stubs · Commented-out code · ×6
  • Commented-out code src/Shopway.Application/Features/Proxy/GenericPageQuery/GenericPageQueryStrategyAttribute.cs:28 — 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 src/Shopway.Application/Features/Proxy/GenericQuery/QueryById/GenericStrategyByIdAttribute.cs:26 — 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 src/Shopway.Application/Features/Proxy/GenericQuery/QueryByKey/GenericStrategyByKeyAttribute.cs:26 — 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 src/Shopway.Domain/Common/Utilities/ReflectionUtilities.cs:248 — 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 src/Shopway.Persistence/Registration/DatabaseContextRegistration.cs:30 — 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 src/Shopway.Persistence/Repositories/Decorators/CachedProductRepository.cs:46 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
S1 · Web-Security Posture · No security response headers detected · ×3
  • 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 REDACTED:8 — 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 src/Shopway.App/Program.cs:7 — 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.
D31 · IaC & Container Security · Low IaC · ×2
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift docs/CONTRIBUTING.md:3 — docs/CONTRIBUTING.md links to `/fork`, but `fork` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/CONTRIBUTING.md:4 — docs/CONTRIBUTING.md links to `/compare`, but `compare` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs:23 — `mapping is not null && mapping .MappingEntries .Any(x => x.PropertyName is nameof(IEntityId.Id)) is false` appears character-identically in 3 files — src/Shopway.Application/Features/Proxy/GenericPageQuery/CursorPage/GenericCursorPageQuery.cs, src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.OrderHeaders.cs, src/Shopway.Application/Features/Proxy/PageQuery/MediatorProxyService.Products.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Shopway.Infrastructure/Registration/ServiceRegistration.cs:72 — `x.ParameterType.IsGenericType && x.ParameterType.IsValueType is false` appears character-identically in 2 files — src/Shopway.Domain/Common/Utilities/ReflectionUtilities.cs, src/Shopway.Infrastructure/Registration/ServiceRegistration.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.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IProductRepository (20 members) src/Shopway.Domain/Products/IProductRepository.cs:9 — `IProductRepository` declares 20 members under just 15 distinct name(s): `GetNamesAsync`, `GetByKeyOrDefaultAsync`, `AnyAsync`, `AnyAsync`, `VerifyIdsAsync`, `GetByIdAsync`, `GetByIdsAsync`, `GetByIdWithReviewAsync`, `GetByIdWithReviewAsync`, `GetByIdWithIncludesAsync`, `GetProductsDictionaryByNameAndRevision`, `Create`, `Update`, `Remove`, `PageAsync`, `PageAsync`, `QueryByIdAsync`, `QueryByIdAsync`, `QueryByKeyAsync`, `QueryByKeyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
C3 · Audit Trail · Partial audit-trail evidence · ×1
  • Partial audit-trail evidence — An audit marker (IAuditable / AddAuditing) was found, but no structural mechanism (an EF SaveChanges interceptor, an immutable audit-log type, or [Audited] usage) — the trail's completeness can't be confirmed from the source.
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.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×1
  • ObsoleteWithoutCallers src/Shopway.Persistence/Specifications/Specification.cs:222 — [Obsolete] AddIncludeByQueryable
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D21 · Naming Consistency · The constant field `Username` in `TestUser` constants and the value object type `Username` in the domain share the exact same name but represent fundamentally different concepts · ×1
  • The constant field `Username` in `TestUser` constants and the value object type `Username` in the domain share the exact same name but represent fundamentally different concepts: one is a static string constant for test data, the other is a complex value object type. This creates ambiguity when referencing 'Username' without full qualification, as it is unclear if the code refers to the test fixture value or the domain entity. — Rename the constant to `TestUsername` or `DefaultTestUsername` to distinguish it from the domain value object type. (symbols: Shopway.Tests.Integration.Container.Constants.Constants.TestUser.Username, Shopway.Domain.Users.ValueObjects.Username)
D26 · Project Cohesion · Split Shopway.Application · ×1
  • Split Shopway.Application — `Shopway.Application` overshoots its size bounds (6932 LoC, 202 public types across 82 namespaces). Review it for cohesion. Suggested: split into cohesive application domains like Orders, Products, Users, with each domain's namespaces named only within the original project
D26 · Project Cohesion · Split Shopway.Domain · ×1
  • Split Shopway.Domain — A generic Domain name whose namespaces are all value objects, base types, discriminators, and utilities (Common.Utilities, DataProcessing.Proxy) across a single cohesive domain. Suggested: split into cohesive domain modules like Users, Products, Constants with each module's namespaces named only within the original project
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 110 of 110 significant files have no living knowledge — the codebase as a whole is dormant, not 110 separate risks. Counted over 110 of the 720 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D37 · Vulnerability-disclosure Policy · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Disabled test · ×1
  • Disabled test test/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11 — A test is skipped ("Only for cleaning the database manually") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
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.
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 5 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 4/6 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 6, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P2 · Observability · Console output used as the logging channel · ×1
  • Console output used as the logging channel src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs:13 — `src/Shopway.Persistence/Registration/PersistenceLayerRegistration.cs` reports through `Console.Write…` at line 13 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1806 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.)
S1 · Web-Security Posture · Secure cookie flags not detected · ×1
  • Secure cookie flags not detected src/Shopway.Presentation/Controllers/UsersController.Google.cs:43 — No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 208/227 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.
X2 · Cancellation propagation · Some async methods drop the CancellationToken they accept · ×1
  • Some async methods drop the CancellationToken they accept — 4 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.0 `!` suppressions per 1k syntax nodes — 256 suppression(s) across the 246658 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 58 finding(s)
D12 · Dependency Hygiene · Outdated · ×45
  • Outdated: Asp.Versioning.Mvc.ApiExplorer — Asp.Versioning.Mvc.ApiExplorer 8.1.0 → 10.2.1 available (referenced by Shopway.Presentation).
  • Outdated: Microsoft.AspNetCore.Authentication.Google — Microsoft.AspNetCore.Authentication.Google 8.0.8 → 10.0.13 available (referenced by Shopway.Presentation).
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer — Microsoft.AspNetCore.Authentication.JwtBearer 8.0.8 → 10.0.13 available (referenced by Shopway.Presentation).
  • Outdated: Microsoft.AspNetCore.OpenApi — Microsoft.AspNetCore.OpenApi 8.0.8 → 10.0.13 available (referenced by Shopway.Presentation).
  • Outdated: Swashbuckle.AspNetCore.Filters — Swashbuckle.AspNetCore.Filters 8.0.2 → 10.0.1 available (referenced by Shopway.Presentation).
  • Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets — Microsoft.VisualStudio.Azure.Containers.Tools.Targets 1.21.0 → 1.23.0 available (referenced by Shopway.App).
  • Outdated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 11.3.0 → 11.3.1 available (referenced by Shopway.Application).
  • Outdated: MediatR — MediatR 12.4.1 → 14.2.0 available (referenced by Shopway.Application).
  • Outdated: ZiggyCreatures.FusionCache — ZiggyCreatures.FusionCache 1.4.0 → 2.9.0 available (referenced by Shopway.Application).
  • Outdated: Google.Apis.Auth.AspNetCore3 — Google.Apis.Auth.AspNetCore3 1.68.0 → 1.77.0 available (referenced by Shopway.Infrastructure).
  • Outdated: MailKit — REDACTED → 4.18.1 available (referenced by Shopway.Infrastructure).
  • Outdated: Polly — Polly 8.4.1 → 8.8.0 available (referenced by Shopway.Infrastructure).
  • Outdated: SymSpell — SymSpell 6.7.2 → 6.7.3 available (referenced by Shopway.Infrastructure).
  • Outdated: System.Linq.Dynamic.Core — REDACTED → 1.7.4 available (referenced by Shopway.Domain).
  • Outdated: Ulid — Ulid 1.3.4 → 1.4.1 available (referenced by Shopway.Domain).
  • Outdated: FluentAssertions — FluentAssertions 6.12.1 → 8.11.0 available (referenced by Shopway.Tests.Unit).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.11.1 → 18.11.0 available (referenced by Shopway.Tests.Unit).
  • Outdated: NSubstitute — NSubstitute 5.1.0 → 6.2.0 available (referenced by Shopway.Tests.Unit).
  • Outdated: xunit — xunit 2.9.0 → 2.9.3 available (referenced by Shopway.Tests.Unit).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.8.2 → 4.0.1 available (referenced by Shopway.Tests.Unit).
  • Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 8.0.0 → 10.0.13 available (referenced by Shopway.Tests.Integration).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 8.0.0 → 10.0.13 available (referenced by Shopway.Tests.Integration).
  • Outdated: RestSharp — RestSharp 112.0.0 → 114.1.0 available (referenced by Shopway.Tests.Integration).
  • Outdated: Microsoft.AspNetCore.Mvc.Testing — Microsoft.AspNetCore.Mvc.Testing 8.0.8 → 10.0.13 available (referenced by Shopway.Tests.Integration.Container).
  • Outdated: Testcontainers — Testcontainers 3.10.0 → 4.16.0 available (referenced by Shopway.Tests.Integration.Container).
  • + 20 more in this group — see findings.md.
D19 · Documentation Quality · XML-doc coverage · ×9
  • XML-doc coverage: Shopway.Presentation src/Shopway.Presentation/Shopway.Presentation.csproj — Shopway.Presentation: 3 % XML-doc coverage (6/206).
  • XML-doc coverage: Shopway.App src/Shopway.App/Shopway.App.csproj — Shopway.App: 0 % XML-doc coverage (0/3).
  • XML-doc coverage: Shopway.Application REDACTED — Shopway.Application: 10 % XML-doc coverage (53/543).
  • XML-doc coverage: Shopway.Infrastructure REDACTED — Shopway.Infrastructure: 11 % XML-doc coverage (22/195).
  • XML-doc coverage: Shopway.Domain REDACTED — Shopway.Domain: 8 % XML-doc coverage (77/984).
  • XML-doc coverage: Shopway.Persistence REDACTED — Shopway.Persistence: 12 % XML-doc coverage (38/318).
  • XML-doc coverage: PaymentGateway REDACTED — PaymentGateway: 0 % XML-doc coverage (0/28).
  • XML-doc coverage: Shopway.SourceGenerator SourceGenerators/Shopway.SourceGenerator/Shopway.SourceGenerator.csproj — Shopway.SourceGenerator: 0 % XML-doc coverage (0/35).
  • XML-doc coverage: Shopway.SourceGenerator.Base SourceGenerators/Shopway.SourceGenerator.Base/Shopway.SourceGenerator.Base.csproj — Shopway.SourceGenerator.Base: 0 % XML-doc coverage (0/21).
D10 · Test Quality · Mock framework · ×3
  • Mock framework: NSubstitute — Shopway.Tests.Unit references NSubstitute.
  • Mock framework: NSubstitute — Shopway.Tests.Integration references NSubstitute.
  • Mock framework: NSubstitute — Shopway.Tests.Integration.Container references NSubstitute.
D10 · Test Quality · Skipped (documented) · ×1
  • Skipped (documented): CleanDatabaseFromTestDataAsync test/Shopway.Tests.Integration/Persistence/CleanTestData.cs:11 — Skipped with a documented reason — a deferral, not lazy debt: Only for cleaning the database manually

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-5601f1168e534622afcf36efc81bfe09/history.json --exit-code 0 --source .23artifacts/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-5601f1168e534622afcf36efc81bfe09/tree.json --exit-code 0 --source .8artifacts/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 .39artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list DomainDrivenDesignUniversity.sln package --vulnerable --include-transitive --format json19artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .15artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 161 file(s) — `PaymentGateway/Webhook/WebhookService.cs`, `SourceGenerators/Shopway.SourceGenerator.Base/IncrementalGeneratorBase.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerGenerator.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdComparerGenerator/EntityIdComparerToGenerateEntry.cs`, `SourceGenerators/Shopway.SourceGenerator/Generators/EntityIdConverterGenerator/EntityIdConverterGenerator.cs`, … (+156 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a16100-6be2-75a3-b8be-2fa8fc42f204 · 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 — 12 field(s) across 5 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 — 7 field(s)
  • LogUserCommand.Email src/Shopway.Application/Features/Users/Commands/LogUser/LogUserCommand.cs:7
  • LoginTwoFactorFirstStepCommand.Email src/Shopway.Application/Features/Users/Commands/LoginTwoFactorFirstStep/LoginTwoFactorFirstStepCommand.cs:7
  • LoginTwoFactorSecondStepCommand.Email src/Shopway.Application/Features/Users/Commands/LoginTwoFactorSecondStep/LoginTwoFactorSecondStepCommand.cs:7
  • LoginTwoFactorToptCommand.Email src/Shopway.Application/Features/Users/Commands/LoginTwoFactorTopt/LoginTwoFactorToptCommand.cs:7
  • RegisterUserCommand.Email src/Shopway.Application/Features/Users/Commands/RegisterUser/RegisterUserCommand.cs:8
  • UserResponse.Email src/Shopway.Application/Features/Users/Queries/GetUserByUsername/UserResponse.cs:10
  • User.Email src/Shopway.Domain/Users/User.cs:26
Name — 2 field(s)
  • Customer.FirstName src/Shopway.Domain/Users/Customer.cs:40
  • Customer.LastName src/Shopway.Domain/Users/Customer.cs:41
Address — 1 field(s)
  • Address.ZipCode src/Shopway.Domain/Users/ValueObjects/Address.cs:72
Date of birth — 1 field(s)
  • Customer.DateOfBirth src/Shopway.Domain/Users/Customer.cs:46
Phone — 1 field(s)
  • Customer.PhoneNumber src/Shopway.Domain/Users/Customer.cs:47

Issues: 74 · Warnings: 211 · Recommendations: 165 · Info: 58 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 00:26 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