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

kodlamaio-projects/nArchitecture

Measured 21 October 2026, 20:07 UTC, at code version a0cc8d5

Bus factor: not measured

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

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

Performance 100 Exemplary Architecture 93 Exemplary Code Health 82 Strong Maturity 47 Weak Production Readiness 40 Weak Security and Compliance 20 Critical

A small codebase: 3,677 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Security and Compliance, 20

Findings by how serious they are

12 critical 161 serious 94 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 20:07 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 ▸

75of 80 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
207of 267 findings point to an exact file and line, so you can open each one in the code. The other 60 concern the repository as a whole, such as missing documentation.
80dimensions across 6 lenses, read from 3,677 lines of product code in 6 projects.
Chapters

Executive summary

kodlamaio-projects/nArchitecture scores 39 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 Security and Compliance, which scores 20 and is rated Critical. Its Supply-chain Provenance & Signing dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 4 Outdated finding(s) in Dependency Hygiene and to encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault, and if Security and Compliance rose to 70, the score would rise from 39 to about 53.

12 findings are critical: eight in Dependency Vulnerabilities, three in Static Analysis (SAST) and one in Dependency Hygiene.

Watchdog couldn't measure Schema migrations in this code, so that dimension is left out of the score. The product code is 3,677 lines, which would take an estimated 0.1 person-years, around €3,200, to rebuild.

Code Health 82 Strong Architecture 93 ★ Exemplary Maturity 47 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 40 Weak, capped by Security & performance tooling Security and Compliance 20 ⚠ Critical, capped by Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing, Data Protection and Access Controls Performance 100 ★ Exemplary

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

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

If Security and Compliance rose from 20 to 70, the lowest score rated Strong, the score would rise from 39 to about 53.

Code composition: what the lines of code are
Business logic 4%Supporting code 82%Tests 14%
New since the last survey: 67 findings

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

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

Fixed since the last survey: 2 findings

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

  • Coupling · Off the main sequence: Domain
  • Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €3,200 · Estimate
Cost to rebuild€1,100 to €5,300, for 18 to 56 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemStandard, 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 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 3,677 lines of product code, of which 54% is declarations and boilerplate, 41% straight logic and 4% logic with branches
Comment linesThe estimate prices 3,676 lines. Comment lines count towards the size of 3,677 lines but aren't priced as work.

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

Top priorities

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

1
Resolve the 4 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, WebAPI.csproj.
Raises the score by about 6 points · Low effort · Dependency Hygiene
2
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 10 points · Medium effort · Data Protection
3
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 10 points · Medium effort · Access Controls

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 €3,200 to build again, about 0.1 person-years of work. Its weakest lens is Security and Compliance, at 20 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 4 Outdated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 4 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 Application Application Domain Domain Application->Domain Infrastructure Infrastructure Infrastructure->Application Persistence Persistence Persistence->Application WebAPI WebAPI WebAPI->Application WebAPI->Infrastructure WebAPI->Persistence

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.

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

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Application.Services.ImageService2 Domain.Entities3 Application.Services.Repositories4 Infrastructure.Adapters.ImageService5 Persistence.Contexts6 Application.Features.Auth.Rules7 Application.Features.OperationClaims.Queries.GetList8 Application.Features.OperationClaims.Rules9 Application.Features.UserOperationClaims.Queries.GetList10 Application.Features.UserOperationClaims.Rules11 Application.Features.Users.Queries.GetList12 Application.Features.Users.Rules13 Application.Services.AuthService14 Application.Services.AuthenticatorService15 Persistence.Repositories16 Application.Features.Auth.Commands.Register17 Application.Features.Auth.Commands.RevokeToken18 Application.Features.Auth.Commands.VerifyEmailAuthenticator19 Application.Features.OperationClaims.Commands.Create20 Application.Features.OperationClaims.Commands.Delete21 Application.Features.OperationClaims.Commands.Update22 Application.Features.OperationClaims.Queries.GetById23 Application.Features.UserOperationClaims.Commands.Create24 Application.Features.UserOperationClaims.Commands.Delete25 Application.Features.UserOperationClaims.Commands.Update26 Application.Features.UserOperationClaims.Queries.GetById27 Application.Features.Users.Commands.Create28 Application.Features.Users.Commands.Delete29 Application.Features.Users.Commands.Update30 Application.Features.Users.Commands.UpdateFromAuth31 Application.Features.Users.Queries.GetById32 Application.Services.OperationClaims33 Application.Services.UserOperationClaims34 Application.Services.UsersService35 Application.Features.Auth.Commands.EnableEmailAuthenticator36 Application.Features.Auth.Commands.EnableOtpAuthenticator37 Application.Features.Auth.Commands.Login38 Application.Features.Auth.Commands.RefreshToken39 Application.Features.Auth.Commands.VerifyOtpAuthenticator40 WebAPI.Controllers
1 Application.Services.ImageService
2 Domain.Entities
3 Application.Services.Repositories2
4 Infrastructure.Adapters.ImageService1
5 Persistence.Contexts6
6 Application.Features.Auth.Rules41
7 Application.Features.OperationClaims.Queries.GetList1
8 Application.Features.OperationClaims.Rules11
9 Application.Features.UserOperationClaims.Queries.GetList1
10 Application.Features.UserOperationClaims.Rules11
11 Application.Features.Users.Queries.GetList1
12 Application.Features.Users.Rules11
13 Application.Services.AuthService42
14 Application.Services.AuthenticatorService62
15 Persistence.Repositories266
16 Application.Features.Auth.Commands.Register1111
17 Application.Features.Auth.Commands.RevokeToken11
18 Application.Features.Auth.Commands.VerifyEmailAuthenticator11
19 Application.Features.OperationClaims.Commands.Create11
20 Application.Features.OperationClaims.Commands.Delete11
21 Application.Features.OperationClaims.Commands.Update11
22 Application.Features.OperationClaims.Queries.GetById11
23 Application.Features.UserOperationClaims.Commands.Create11
24 Application.Features.UserOperationClaims.Commands.Delete11
25 Application.Features.UserOperationClaims.Commands.Update11
26 Application.Features.UserOperationClaims.Queries.GetById11
27 Application.Features.Users.Commands.Create11
28 Application.Features.Users.Commands.Delete11
29 Application.Features.Users.Commands.Update11
30 Application.Features.Users.Commands.UpdateFromAuth111
31 Application.Features.Users.Queries.GetById11
32 Application.Services.OperationClaims211
33 Application.Services.UserOperationClaims211
34 Application.Services.UsersService211
35 Application.Features.Auth.Commands.EnableEmailAuthenticator1111
36 Application.Features.Auth.Commands.EnableOtpAuthenticator1111
37 Application.Features.Auth.Commands.Login11111
38 Application.Features.Auth.Commands.RefreshToken1111
39 Application.Features.Auth.Commands.VerifyOtpAuthenticator1111
40 WebAPI.Controllers111111111111111
Uses a module listed above itPart of a loopThe module itself
1 Application.Services.ImageService2 Domain.Entities3 Application.Services.Repositories4 Infrastructure.Adapters.ImageService5 Persistence.Contexts6 Application.Features.Auth.Rules7 Application.Features.OperationClaims.Queries.GetList8 Application.Features.OperationClaims.Rules9 Application.Features.UserOperationClaims.Queries.GetList10 Application.Features.UserOperationClaims.Rules11 Application.Features.Users.Queries.GetList12 Application.Features.Users.Rules13 Application.Services.AuthService14 Application.Services.AuthenticatorService15 Persistence.Repositories16 Application.Features.Auth.Commands.Register17 Application.Features.Auth.Commands.RevokeToken18 Application.Features.Auth.Commands.VerifyEmailAuthenticator19 Application.Features.OperationClaims.Commands.Create20 Application.Features.OperationClaims.Commands.Delete21 Application.Features.OperationClaims.Commands.Update22 Application.Features.OperationClaims.Queries.GetById23 Application.Features.UserOperationClaims.Commands.Create24 Application.Features.UserOperationClaims.Commands.Delete25 Application.Features.UserOperationClaims.Commands.Update26 Application.Features.UserOperationClaims.Queries.GetById27 Application.Features.Users.Commands.Create28 Application.Features.Users.Commands.Delete29 Application.Features.Users.Commands.Update30 Application.Features.Users.Commands.UpdateFromAuth31 Application.Features.Users.Queries.GetById32 Application.Services.OperationClaims33 Application.Services.UserOperationClaims34 Application.Services.UsersService35 Application.Features.Auth.Commands.EnableEmailAuthenticator36 Application.Features.Auth.Commands.EnableOtpAuthenticator37 Application.Features.Auth.Commands.Login38 Application.Features.Auth.Commands.RefreshToken39 Application.Features.Auth.Commands.VerifyOtpAuthenticator40 WebAPI.ControllersApplication.Services.ImageService1Domain.Entities2Application.Services.Repositories3Infrastructure.Adapters.ImageService4Persistence.Contexts5Application.Features.Auth.Rules6Application.Features.OperationClaims.Queries.GetList7Application.Features.OperationClaims.Rules8Application.Features.UserOperationClaims.Queries.GetList9Application.Features.UserOperationClaims.Rules10Application.Features.Users.Queries.GetList11Application.Features.Users.Rules12Application.Services.AuthService13Application.Services.AuthenticatorService14Persistence.Repositories15Application.Features.Auth.Commands.Register16Application.Features.Auth.Commands.RevokeToken17Application.Features.Auth.Commands.VerifyEmailAuthenticator18Application.Features.OperationClaims.Commands.Create19Application.Features.OperationClaims.Commands.Delete20Application.Features.OperationClaims.Commands.Update21Application.Features.OperationClaims.Queries.GetById22Application.Features.UserOperationClaims.Commands.Create23Application.Features.UserOperationClaims.Commands.Delete24Application.Features.UserOperationClaims.Commands.Update25Application.Features.UserOperationClaims.Queries.GetById26Application.Features.Users.Commands.Create27Application.Features.Users.Commands.Delete28Application.Features.Users.Commands.Update29Application.Features.Users.Commands.UpdateFromAuth30Application.Features.Users.Queries.GetById31Application.Services.OperationClaims32Application.Services.UserOperationClaims33Application.Services.UsersService34Application.Features.Auth.Commands.EnableEmailAuthenticator35Application.Features.Auth.Commands.EnableOtpAuthenticator36Application.Features.Auth.Commands.Login37Application.Features.Auth.Commands.RefreshToken38Application.Features.Auth.Commands.VerifyOtpAuthenticator39WebAPI.Controllers4021641111111111426226611111111111111111111111111111111111211211211111111111111111111111111111111111111+16 more modules (most-connected shown)

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

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

At a glance — Architecture · 93% · Exemplary ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 8.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX7 · Repo Slice cohesion 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0
The Bad
D27 · .NET / C# Navigability 6.6

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

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

At a glance — Readiness · 40% · Weak · gated by P3 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P1 · Repo CI/CD gates 10.0
The Bad
D8 · .NET / C# Code Coverage 5.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0 P9 · Repo Domain vs controller coverage 6.0
The Ugly
D12 · .NET / C# Dependency Hygiene 4.2 P2 · Repo Observability 4.8 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 20% · Critical · gated by D29, D30, D36, C1, C2 ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D44 · .NET / C# Platform End-of-Life 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
S1 · Repo Web-Security Posture 6.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 2.3 D30 · .NET / C# Dependency Vulnerabilities 3.6 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 0.0 C2 · Repo Access Controls 0.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection31High / Critical
A03:2025 — Software Supply Chain Failures19High / Critical

Roadmap

Immediately secure sensitive data by implementing encryption at rest and managing keys in a vault, while enforcing strict default-deny access controls on all endpoints. Concurrently, resolve the critical authorization gaps identified in static analysis and eliminate orphaned files to ensure codebase integrity. Finally, update outdated dependencies to maintain system stability and security hygiene.

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

Do thisHelpsEffortDimension
Resolve the 4 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, WebAPI.csproj.+5.5 ptsLowDependency Hygiene
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).+9.8 ptsMediumData Protection
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.+9.8 ptsMediumAccess Controls
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.+3.6 ptsLowDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.+3.5 ptsLowADR Quality
Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (3).+3.4 ptsLowDependency Vulnerabilities
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with WebAPI.csproj, REDACTED.+3.2 ptsLowDependency Hygiene
Resolve the 25 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (7), REDACTED (5).+6.3 ptsMediumStatic Analysis (SAST)

File quality

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

FileScoreBandWorst signal
REDACTED0.9SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.9SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.9SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.4MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
src/starterProject/WebAPI/WebAPI.csproj6.5MixedCode Coverage: No test project references WebAPI
src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs6.7MixedExplicit Debt: Dead code: UserUserOperationClaimManager
src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs6.7MixedExplicit Debt: Dead code: OperationClaimManager
src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs7.4MixedCode Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens)
src/starterProject/WebAPI/Controllers/BaseController.cs8.2Near-cleanExplicit Debt: TodoComment
src/starterProject/Application/Services/TranslateService/ITranslateService.cs8.2Near-cleanExplicit Debt: Dead code: ITranslateService
src/starterProject/WebAPI/Controllers/Dtos/UpdateByAuthFromServiceRequestDto.cs8.2Near-cleanExplicit Debt: Dead code: UpdateByAuthFromServiceRequestDto
src/starterProject/Application/Features/OperationClaims/Constants/OperationClaimsOperationClaims.cs8.5Near-cleanCode Duplication: Duplicated block (8 lines × 3)
src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommandValidator.cs8.5Near-cleanCode Duplication: Duplicated block (5 lines × 2)
src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs8.5Near-cleanCode Duplication: Duplicated block (6 lines × 4)
src/starterProject/Application/ApplicationServiceRegistration.cs8.5Near-cleanCode Coverage: Low coverage: src/starterProject/Application/ApplicationServiceRegistration.cs

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

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

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

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

Could not be resolved — 5

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

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

What we checked — 80 dimensions across the health lenses
D1D2D3D4D5D6D8D9D10D11D12D13D14D15D17D18D19D20D21D24D26D27D28D29D30D34D35D36D39D44AX1AX10AX3AX5AX6AX7AX8AX9C1C2ED5GD1IC1M1M2M3M4P1P2P3P4P6P9PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a16013-9312-7109-92dd-76ddea344a1c.

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 24 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 24 of the 119 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
  • 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.
  • P8 Schema migrations — 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. Every other migration runner — DbUp, FluentMigrator, Evolve, Flyway, Liquibase, RoundhousE, a hand-rolled versioned-SQL runner — is invisible to the detector, so an absence here is our blind spot rather than a missing migration strategy in the repository. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool other than EF Core migrations, naming it lets us teach the detector to read it.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 41 further occurrence(s) are not listed individually; the score already reflects all 81.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

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

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

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

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

Members sharing a duplicated core (6 members, 50+ identical tokens)src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:10
Duplicated block (8 lines × 3)src/starterProject/Application/Features/OperationClaims/Constants/OperationClaimsOperationClaims.cs:7
Duplicated block (9 lines × 3)src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:18
Duplicated block (8 lines × 6)src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:16
Duplicated block (5 lines × 2)src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommandValidator.cs:9

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

What to do

  1. Resolve the 1 Members sharing a duplicated core (6 members, 50+ identical tokens) finding(s) in Code Duplication — start with EmailAuthenticatorConfiguration.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with OperationClaimsOperationClaims.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (9 lines × 3) finding(s) in Code Duplication — start with EmailAuthenticatorConfiguration.cs. — One of this dimension's main actionable groups (1 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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

0 of 9 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage5.0 / 10Adequate✓ Tool-verified

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

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

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

Line coverage 21.8% — 43 file(s) below 50%.

Low coverage: src/starterProject/Application/ApplicationServiceRegistration.cs · ×43src/starterProject/Application/ApplicationServiceRegistration.cs:1
No test project references PersistenceREDACTED
No test project references WebAPIsrc/starterProject/WebAPI/WebAPI.csproj
No test project references Infrastructuresrc/starterProject/Infrastructure/Infrastructure.csproj

What to do

  1. Resolve the 43 Low coverage finding(s) in Code Coverage — start with MappingProfiles.cs (2), ApplicationServiceRegistration.cs, UserManager.cs. — One of this dimension's main actionable groups (43 warning-level).
  2. Resolve the 1 No test project references Persistence finding(s) in Code Coverage — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 No test project references WebAPI finding(s) in Code Coverage — start with WebAPI.csproj. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

19 test methods: 19 unit, 0 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

0 skipped, 0 zero-assertion, 1 mock references across 19 tests.

Mock framework: Moq

✓ 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 1 measured tier(s). unit: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene4.2 / 10Weak✓ 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 4.2 / 10 · rule-coverage 100% · ceiling Verified

37 outdated, 1 vulnerable, 2 deprecated packages.

Vulnerable: AutoMapper
Deprecated: System.IdentityModel.Tokens.Jwt · ×2src/starterProject/WebAPI/WebAPI.csproj:9
Outdated: AutoMapper · ×4REDACTED:11
Outdated: MediatR · ×33

What to do

  1. Resolve the 4 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, WebAPI.csproj. — One of this dimension's main actionable groups (4 recommendation-level).
  2. Resolve the 1 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with WebAPI.csproj, REDACTED. — 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 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 251 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 37 direct `PackageReference`(s), and 213 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 / 10Stronggated by 5 serious 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

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

Dead code: OperationClaimManager · ×4src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:10
TodoCommentsrc/starterProject/WebAPI/Controllers/BaseController.cs:25

What to do

  1. Resolve the 4 Dead code finding(s) in Explicit Debt — start with OperationClaimManager.cs, ITranslateService.cs, UserOperationClaimManager.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with BaseController.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. 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

6 projects, 139 source files, 4290 hand-written lines of code (3677 production / 613 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), 7 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityAdequate◐ Sampled · advisory

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

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

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

The repository's root README is a single cohesive document that states what the project is (nArchitecture; Kodlama.io examples of completed projects), its purpose (Clean Architecture, CQRS, JWT, OTP, dynamic querying), and links to GitHub contributors, forks, stars, issues, and the license. It also begins with an overview section ('## 💻 About The Project') that promises a Built With/Getting Started/Usage/Analysis/Format/Roadmap/Contribution/License section but is cut by the scanner before those appear. A companion Semantic Commit Messages doc exists (docs/Semantic Commit Messages.md) covering commit-message conventions, types, and references; it is not a README and does not fall under any of the four project-level missing-*/categories. The visible content is clear and complete for an overview document but lacks the full outline promised by its own opening paragraph.

XML-doc coverage: Application · ×5REDACTED

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The repository's root README is a single cohesive document that states what the project is (nArchitecture; Kodlama.io examples of completed projects), its purpose (Clean Architecture, CQRS, JWT, OTP, dynamic querying), and links to GitHub contributors, forks, stars, issues, and the license. It also begins with an overview section ('## 💻 About The Project') that promises a Built With/Getting Started/Usage/Analysis/Format/Roadmap/Contribution/License section but is cut by the scanner before those appear. A companion Semantic Commit Messages doc exists (docs/Semantic Commit Messages.md) covering commit-message conventions, types, and references; it is not a README and does not fall under any of the four project-level missing-*/categories. The visible content is clear and complete for an overview document but lacks the full outline promised by its own opening paragraph.

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 ConsistencyStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Verified

4 naming inconsistencies across 200 sampled symbols.

Inconsistent predicate naming for the same business rule concept (checking if a user email is unique/available). One method uses 'ShouldNotExists' (grammatically incorrect pluralization of the adjective/existential state) while the other uses 'ShouldBeNotExists'.
Inconsistent naming for the 'OTP authenticator already verified' concept. The rule method uses 'ThatVerifiedShouldNotBeExists' (verbose, awkward grammar) while the constant message uses 'AlreadyVerified...IsExists'. The rule name implies a check for non-existence of a verified state, but the phrasing is inconsistent with standard predicate conventions and the message constant.
Inconsistent predicate naming style. 'UserShouldNotHasOperationClaimAlreadyWhenInsert' is a verbose, imperative-style clause with grammatical errors ('ShouldNotHas'). 'UserOperationClaimShouldNotExistWhenSelected' is a more standard predicate but uses 'WhenSelected' which is vague compared to 'WhenInsert'.
Inconsistent naming convention for helper methods within the same business rules class. 'throwBusinessException' is a verb phrase (command), while other methods in the same class are predicates (noun phrases describing a state/check).

What to do

  1. Resolve the 1 Inconsistent predicate naming for the same business rule concept… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Inconsistent naming for the 'OTP authenticator already verified'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Inconsistent predicate naming style.… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

redundant commentsrc/starterProject/WebAPI/Program.cs:88

What to do

  1. Resolve the 1 redundant comment finding(s) in Comment Value — start with Program.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

0 of 6 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability6.6 / 10Adequate✓ Tool-verified

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

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

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

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

92 % of calls cross a namespace and 28 % go through an interface, but 56 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

Scattered collaborators

What to do

  1. Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

31 finding(s): 0 critical, 3 high, 28 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D30 · Dependency Vulnerabilities3.6 / 10Weak✓ 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 3.6 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

Orphaned file · ×24src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:1
Dormant codebase

What to do

  1. Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with AuthenticatorManager.cs, REDACTED, AuthManager.cs. — One of this dimension's main actionable groups (24 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 Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

3 of 308 first-party methods have an oversized IL body.

IL efficiency: 3 authored method(s) exceed the IL budgetsrc/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:11

✓ On the Gold path — maintain.

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

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

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

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

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

What to do

  • The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls0.0 / 10Critical✓ Tool-verified

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.

  • No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • `AuthController.Login` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:31
  • `AuthController.Register` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:43
  • `AuthController.RefreshToken` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:52
  • `AuthController.RevokeToken` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:62
  • `AuthController.EnableEmailAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:71
  • `AuthController.EnableOtpAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:85
  • `AuthController.VerifyEmailAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:94
  • `AuthController.VerifyOtpAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:103
  • `OperationClaimsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:17
  • `OperationClaimsController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:24
  • `OperationClaimsController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:32
  • `OperationClaimsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:39
  • `OperationClaimsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:46
  • `UserOperationClaimsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:17
  • `UserOperationClaimsController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:24
  • `UserOperationClaimsController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:32
  • `UserOperationClaimsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:39
  • `UserOperationClaimsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:46
  • `UsersController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:18
  • `UsersController.GetFromAuth` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:25
  • `UsersController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:33
  • `UsersController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:41
  • `UsersController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:48
  • `UsersController.UpdateFromAuth` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:55
  • `UsersController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:63

What to do

  • Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
ED5 · Idempotency10.0 / 10Exemplary◐ Sampled · advisory

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

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

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

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

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

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

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

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

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

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 6 of 6 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 structure8.0 / 10Strong✓ Tool-verified

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

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

  • Only 1/6 projects share a common root namespace — the code's module identity is inconsistent.

What to do

  • Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
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.

  • README.md names .NET 7, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:41
  • README.md names `src/corePackages`, but no file or folder `src/corePackages` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:90

What to do

  • Reconcile the README with reality: README.md names .NET 7, but the projects target .NET 8; README.md names `src/corePackages`, but no file or folder `src/corePackages` exists.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability4.8 / 10Weak✓ 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 1/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 4, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

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

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 853 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 automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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.
P9 · Domain vs controller coverage6.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
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 Posture6.0 / 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.

  • 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. — src/starterProject/WebAPI/Program.cs:19
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/starterProject/WebAPI/Program.cs:19

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X18 · Disposal-pattern 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 propagation5.4 / 10Adequate✓ Tool-verified

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

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

  • Only 30/104 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:29, src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:35, src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:41, …

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 types7.8 / 10Strong✓ 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.

  • ~2.7 `!` suppressions per 1k syntax nodes — 53 suppression(s) across the 19514 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 Health82%StrongSolid.
Architecture93%ExemplarySolid.
Maturity47%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness40%Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security20%Critical — gated by D29, D30, D36, C1, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 37 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.
  • AX2 Stateful singletons — no singleton implementations detected
  • AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXO1 Runtime API surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (3,677 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 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.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 repository port(s) loading or saving an aggregate/entity)
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 24 CQRS handler(s)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • P8 Schema migrations — EF Core is used, but the schema-migration mechanism could not be identified — this check only recognises EF migrations, so any other migration runner reads as an absence. Our limit, not a verdict on this repository.
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 12 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Vulnerable · ×1
  • Vulnerable: AutoMapper — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
Serious — 161 finding(s)
D8 · Code Coverage · Low coverage · ×43
  • Low coverage: src/starterProject/Application/ApplicationServiceRegistration.cs src/starterProject/Application/ApplicationServiceRegistration.cs:1 — 0.0% line coverage (0/32).
  • Low coverage: src/starterProject/Application/Services/UsersService/UserManager.cs src/starterProject/Application/Services/UsersService/UserManager.cs:1 — 25.0% line coverage (9/36).
  • Low coverage: src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs:1 — 0.0% line coverage (0/56).
  • Low coverage: src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:1 — 0.0% line coverage (0/45).
  • Low coverage: src/starterProject/Application/Services/ImageService/ImageServiceBase.cs src/starterProject/Application/Services/ImageService/ImageServiceBase.cs:1 — 0.0% line coverage (0/12).
  • Low coverage: src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:1 — 15.9% line coverage (14/88).
  • Low coverage: src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:1 — 0.0% line coverage (0/20).
  • Low coverage: src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:1 — 0.0% line coverage (0/54).
  • Low coverage: src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommandValidator.cs src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommandValidator.cs:1 — 0.0% line coverage (0/17).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:1 — 0.0% line coverage (0/38).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Queries/GetList/GetListUserOperationClaimQuery.cs src/starterProject/Application/Features/UserOperationClaims/Queries/GetList/GetListUserOperationClaimQuery.cs:1 — 0.0% line coverage (0/26).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Queries/GetById/GetByIdUserOperationClaimQuery.cs src/starterProject/Application/Features/UserOperationClaims/Queries/GetById/GetByIdUserOperationClaimQuery.cs:1 — 0.0% line coverage (0/24).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Profiles/MappingProfiles.cs src/starterProject/Application/Features/UserOperationClaims/Profiles/MappingProfiles.cs:1 — 0.0% line coverage (0/12).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommand.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommand.cs:1 — 0.0% line coverage (0/35).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommandValidator.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommandValidator.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Delete/DeleteUserOperationClaimCommand.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Delete/DeleteUserOperationClaimCommand.cs:1 — 0.0% line coverage (0/22).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.cs:1 — 0.0% line coverage (0/25).
  • Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommandValidator.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommandValidator.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:1 — 0.0% line coverage (0/30).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimListItemDto.cs src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimListItemDto.cs:1 — 0.0% line coverage (0/11).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimQuery.cs src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimQuery.cs:1 — 0.0% line coverage (0/27).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimQuery.cs src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimQuery.cs:1 — 0.0% line coverage (0/22).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimResponse.cs src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimResponse.cs:1 — 0.0% line coverage (0/11).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Profiles/MappingProfiles.cs src/starterProject/Application/Features/OperationClaims/Profiles/MappingProfiles.cs:1 — 0.0% line coverage (0/12).
  • Low coverage: src/starterProject/Application/Features/OperationClaims/Commands/Update/UpdatedOperationClaimResponse.cs src/starterProject/Application/Features/OperationClaims/Commands/Update/UpdatedOperationClaimResponse.cs:1 — 0.0% line coverage (0/11).
  • + 18 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: EmailAuthenticatorShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OtpAuthenticatorShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OtpAuthenticatorThatVerifiedShouldNotBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:41 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: EmailAuthenticatorActivationKeyShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserShouldBeExistsWhenSelected src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:53 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserShouldNotBeHaveAuthenticator src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefreshTokenShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:65 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefreshTokenShouldBeActive src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserEmailShouldBeNotExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:77 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserPasswordShouldBeMatch src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:84 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OperationClaimShouldExistWhenSelected src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OperationClaimIdShouldExistWhenSelected src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OperationClaimNameShouldNotExistWhenCreating src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OperationClaimNameShouldNotExistWhenUpdating src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserOperationClaimShouldExistWhenSelected src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserOperationClaimIdShouldExistWhenSelected src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserOperationClaimShouldNotExistWhenSelected src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserShouldNotHasOperationClaimAlreadyWhenInsert src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserShouldNotHasOperationClaimAlreadyWhenUpdated src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:58 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserShouldBeExistsWhenSelected src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserIdShouldBeExistsWhenSelected src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserPasswordShouldBeMatched src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:41 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserEmailShouldNotExistsWhenInsert src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserEmailShouldNotExistsWhenUpdate src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendAuthenticatorCode src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:65 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
C2 · Access Controls · No authorization · ×26
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization REDACTED:31 — `AuthController.Login` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:43 — `AuthController.Register` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:52 — `AuthController.RefreshToken` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:62 — `AuthController.RevokeToken` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:71 — `AuthController.EnableEmailAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:85 — `AuthController.EnableOtpAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:94 — `AuthController.VerifyEmailAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:103 — `AuthController.VerifyOtpAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:17 — `OperationClaimsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:24 — `OperationClaimsController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:32 — `OperationClaimsController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:39 — `OperationClaimsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:46 — `OperationClaimsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:17 — `UserOperationClaimsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:24 — `UserOperationClaimsController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:32 — `UserOperationClaimsController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:39 — `UserOperationClaimsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:46 — `UserOperationClaimsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:18 — `UsersController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:25 — `UsersController.GetFromAuth` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:33 — `UsersController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:41 — `UsersController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:48 — `UsersController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:55 — `UsersController.UpdateFromAuth` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • + 1 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · Dead code · ×4
  • Dead code: OperationClaimManager src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:10 — NamedType OperationClaimManager — Roslyn's SymbolFinder walked every project the solution loads, including Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ITranslateService src/starterProject/Application/Services/TranslateService/ITranslateService.cs:3 — NamedType ITranslateService — Roslyn's SymbolFinder walked every project the solution loads, including Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: UserUserOperationClaimManager src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs:10 — NamedType UserUserOperationClaimManager — Roslyn's SymbolFinder walked every project the solution loads, including Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: UpdateByAuthFromServiceRequestDto src/starterProject/WebAPI/Controllers/Dtos/UpdateByAuthFromServiceRequestDto.cs:3 — NamedType UpdateByAuthFromServiceRequestDto — Roslyn's SymbolFinder walked every project the solution loads, including WebAPI, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: System.IdentityModel.Tokens.Jwt src/starterProject/WebAPI/WebAPI.csproj:9 — System.IdentityModel.Tokens.Jwt 7.5.0 — Legacy
  • Deprecated: xunit REDACTED:10 — xunit 2.7.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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×2
  • REDACTED
  • REDACTED
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment src/starterProject/WebAPI/Controllers/BaseController.cs:25 — //todo authentication behavior? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
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/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:10 — src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:10-26 | src/starterProject/Persistence/EntityConfigurations/OperationClaimConfiguration.cs:15-29 | src/starterProject/Persistence/EntityConfigurations/OtpAuthenticatorConfiguration.cs:10-26 | src/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:10-31 | src/starterProject/Persistence/EntityConfigurations/UserConfiguration.cs:11-33 | src/starterProject/Persistence/EntityConfigurations/UserOperationClaimConfiguration.cs:10-28 — 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 (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) src/starterProject/Application/Features/OperationClaims/Constants/OperationClaimsOperationClaims.cs:7 — src/starterProject/Application/Features/OperationClaims/Constants/OperationClaimsOperationClaims.cs:7-14 | src/starterProject/Application/Features/UserOperationClaims/Constants/UserOperationClaimsOperationClaims.cs:7-14 | src/starterProject/Application/Features/Users/Constants/UsersOperationClaims.cs:7-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:18 — src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:18-26 | src/starterProject/Persistence/EntityConfigurations/OtpAuthenticatorConfiguration.cs:18-26 | src/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:23-31 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<EmailAuthenticator>` in one and `EntityTypeBuilder<OtpAuthenticator>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:15` calls `Property`, `HasColumnName` and `src/starterProject/Persistence/EntityConfigurations/OtpAuthenticatorConfiguration.cs:15` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:16 — src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:16-23 | src/starterProject/Persistence/EntityConfigurations/OperationClaimConfiguration.cs:19-26 | src/starterProject/Persistence/EntityConfigurations/OtpAuthenticatorConfiguration.cs:16-23 | src/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:21-28 | src/starterProject/Persistence/EntityConfigurations/UserConfiguration.cs:18-25 | src/starterProject/Persistence/EntityConfigurations/UserOperationClaimConfiguration.cs:15-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<EmailAuthenticator>` in one and `EntityTypeBuilder<OperationClaim>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:14` calls `Property`, `HasColumnName`, `IsRequired` and `src/starterProject/Persistence/EntityConfigurations/OperationClaimConfiguration.cs:18` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommandValidator.cs:9 — src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommandValidator.cs:9-13 | src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommandValidator.cs:9-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:22 — src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:22-27 | src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:22-27 | src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:22-27 | src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:22-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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.
D8 · Code Coverage · No test project references Persistence · ×1
  • No test project references Persistence REDACTED — No test project in this repository references Persistence (14 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 21.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references WebAPI · ×1
  • No test project references WebAPI src/starterProject/WebAPI/WebAPI.csproj — No test project in this repository references WebAPI (8 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 21.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references Infrastructure · ×1
  • No test project references Infrastructure src/starterProject/Infrastructure/Infrastructure.csproj — No test project in this repository references Infrastructure (2 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 21.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
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.
Minor — 55 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×24
  • Orphaned file src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.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/starterProject/Application/Services/AuthService/AuthManager.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/starterProject/WebAPI/Program.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/starterProject/Persistence/EntityConfigurations/OperationClaimConfiguration.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/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.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/starterProject/Application/ApplicationServiceRegistration.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/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.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/starterProject/Application/Features/Auth/Commands/EnableEmailAuthenticator/EnableEmailAuthenticatorCommand.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/starterProject/Application/Services/OperationClaims/OperationClaimManager.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/starterProject/Application/Features/Auth/Commands/Login/LoginCommand.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/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.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/starterProject/Application/Features/Auth/Commands/EnableOtpAuthenticator/EnableOtpAuthenticatorCommand.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/starterProject/Application/Features/Auth/Commands/RefreshToken/RefreshTokenCommand.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/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommand.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/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.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/starterProject/Application/Features/Auth/Commands/Register/RegisterCommand.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/starterProject/Application/Features/Auth/Commands/VerifyOtpAuthenticator/VerifyOtpAuthenticatorCommand.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/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.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/starterProject/Application/Features/OperationClaims/Commands/Update/UpdateOperationClaimCommand.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/starterProject/Application/Services/UsersService/UserManager.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/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.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/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.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.
D12 · Dependency Hygiene · Outdated · ×4
  • Outdated: AutoMapper REDACTED:11 — REDACTED → 16.2.0 available (referenced by Application).
  • Outdated: Swashbuckle.AspNetCore src/starterProject/WebAPI/WebAPI.csproj:8 — Swashbuckle.AspNetCore 6.5.0 → 10.3.1 available (referenced by WebAPI).
  • Outdated: coverlet.collector REDACTED:18 — coverlet.collector 6.0.2 → 10.1.0 available (referenced by StarterProject.Application.Tests).
  • Outdated: Xunit.DependencyInjection REDACTED:13 — Xunit.DependencyInjection 9.0.1 → 12.0.1 available (referenced by StarterProject.Application.Tests).
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift README.md:41 — README.md names .NET 7, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:90 — README.md names `src/corePackages`, but no file or folder `src/corePackages` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
S1 · Web-Security Posture · No security response headers detected · ×2
  • 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 src/starterProject/WebAPI/Program.cs:19 — 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.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected src/starterProject/WebAPI/Program.cs:19 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D21 · Naming Consistency · Inconsistent predicate naming for the same business rule concept (checking if a user email is unique/available). One method uses 'ShouldNotExists' (grammatically incorrect pluralization of the adjective/existential state) while the other uses 'ShouldBeNotExists'. · ×1
  • Inconsistent predicate naming for the same business rule concept (checking if a user email is unique/available). One method uses 'ShouldNotExists' (grammatically incorrect pluralization of the adjective/existential state) while the other uses 'ShouldBeNotExists'. — Standardize to 'UserEmailShouldNotExist' (singular, standard predicate form). (symbols: Application.Features.Users.Rules.UserBusinessRules.UserEmailShouldNotExistsWhenInsert, Application.Features.Auth.Rules.AuthBusinessRules.UserEmailShouldBeNotExists)
D21 · Naming Consistency · Inconsistent naming for the 'OTP authenticator already verified' concept. The rule method uses 'ThatVerifiedShouldNotBeExists' (verbose, awkward grammar) while the constant message uses 'AlreadyVerified...IsExists'. The rule name implies a check for non-existence of a verified state, but the phrasing is inconsistent with standard predicate conventions and the message constant. · ×1
  • Inconsistent naming for the 'OTP authenticator already verified' concept. The rule method uses 'ThatVerifiedShouldNotBeExists' (verbose, awkward grammar) while the constant message uses 'AlreadyVerified...IsExists'. The rule name implies a check for non-existence of a verified state, but the phrasing is inconsistent with standard predicate conventions and the message constant. — Standardize to 'OtpAuthenticatorShouldNotBeAlreadyVerified' for the rule and 'AlreadyVerifiedOtpAuthenticator' for the message/key. (symbols: Application.Features.Auth.Rules.AuthBusinessRules.OtpAuthenticatorThatVerifiedShouldNotBeExists, Application.Features.Auth.Constants.AuthMessages.AlreadyVerifiedOtpAuthenticatorIsExists)
D21 · Naming Consistency · Inconsistent predicate naming style. 'UserShouldNotHasOperationClaimAlreadyWhenInsert' is a verbose, imperative-style clause with grammatical errors ('ShouldNotHas'). 'UserOperationClaimShouldNotExistWhenSelected' is a more standard predicate but uses 'WhenSelected' which is vague compared to 'WhenInsert'. · ×1
  • Inconsistent predicate naming style. 'UserShouldNotHasOperationClaimAlreadyWhenInsert' is a verbose, imperative-style clause with grammatical errors ('ShouldNotHas'). 'UserOperationClaimShouldNotExistWhenSelected' is a more standard predicate but uses 'WhenSelected' which is vague compared to 'WhenInsert'. — Standardize to clear, grammatically correct predicates like 'UserShouldNotHaveOperationClaim' and 'UserOperationClaimShouldExist' (or 'NotExist'). (symbols: Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules.UserShouldNotHasOperationClaimAlreadyWhenInsert, Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules.UserOperationClaimShouldNotExistWhenSelected)
D21 · Naming Consistency · Inconsistent naming convention for helper methods within the same business rules class. 'throwBusinessException' is a verb phrase (command), while other methods in the same class are predicates (noun phrases describing a state/check). · ×1
  • Inconsistent naming convention for helper methods within the same business rules class. 'throwBusinessException' is a verb phrase (command), while other methods in the same class are predicates (noun phrases describing a state/check). — Rename 'throwBusinessException' to a noun phrase describing the exception type or behavior, e.g., 'ThrowBusinessException' (if it's a command) or ensure it aligns with the class's primary role. Given it's a void method, 'ThrowBusinessException' is acceptable as a command, but the inconsistency lies in mixing commands and predicates without clear role separation in naming style. However, since one is void (command) and others are void (predicates/checks), the main issue is the grammatical form. 'throwBusinessException' is a command. 'UserEmailShouldNotExists...' is a predicate (void). This is a role-based inconsistency. Suggestion: Ensure all void methods that check conditions are named as predicates (e.g., 'CheckUserEmailExists') or all are commands. The current mix is confusing. (symbols: Application.Features.Users.Rules.UserBusinessRules.throwBusinessException, Application.Features.Users.Rules.UserBusinessRules.UserEmailShouldNotExistsWhenInsert)
D24 · Comment Value · redundant comment · ×1
  • redundant comment src/starterProject/WebAPI/Program.cs:88 — "Configure the HTTP request pipeline." — delete - IsDevelopment() is already stating this; the comment repeats Configure(...) and says nothing a reader cannot infer from context.
D27 · Navigability · Scattered collaborators · ×1
  • Scattered collaborators — 92 % of calls cross a namespace and only 56 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 24 of 24 significant files have no living knowledge — the codebase as a whole is dormant, not 24 separate risks. Counted over 24 of the 119 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
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 3 authored method(s) exceed the IL budget src/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:11 — 3 of 308 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Persistence.EntityConfigurations.RefreshTokenConfiguration.Configure @ src/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:11, 366 IL instructions; that pulled this dimension to 9.8/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M3 · Folder & project structure · Inconsistent root namespaces · ×1
  • Inconsistent root namespaces — Only 1/6 projects share a common root namespace — the code's module identity is inconsistent.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 4, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 853 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 30/104 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~2.7 `!` suppressions per 1k syntax nodes — 53 suppression(s) across the 19514 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 — 39 finding(s)
D12 · Dependency Hygiene · Outdated · ×33
  • Outdated: MediatR — MediatR 12.2.0 → 14.2.0 available (referenced by Application).
  • Outdated: NArchitecture.Core.Application — NArchitecture.Core.Application 1.0.1 → 1.0.7 available (referenced by Application).
  • Outdated: NArchitecture.Core.CrossCuttingConcerns.Exception — NArchitecture.Core.CrossCuttingConcerns.Exception 1.0.0 → 1.0.2 available (referenced by Application).
  • Outdated: NArchitecture.Core.CrossCuttingConcerns.Logging.Serilog.File — NArchitecture.Core.CrossCuttingConcerns.Logging.Serilog.File 1.0.0 → 1.0.3 available (referenced by Application).
  • Outdated: NArchitecture.Core.ElasticSearch — NArchitecture.Core.ElasticSearch 1.0.0 → 1.0.1 available (referenced by Application).
  • Outdated: NArchitecture.Core.Localization.Abstraction — NArchitecture.Core.Localization.Abstraction 1.0.0 → 1.0.1 available (referenced by Application).
  • Outdated: NArchitecture.Core.Localization.Resource.Yaml.DependencyInjection — NArchitecture.Core.Localization.Resource.Yaml.DependencyInjection 1.0.1 → 1.0.2 available (referenced by Application).
  • Outdated: NArchitecture.Core.Mailing — NArchitecture.Core.Mailing 1.0.1 → 1.0.3 available (referenced by Application).
  • Outdated: NArchitecture.Core.Mailing.Mailkit — NArchitecture.Core.Mailing.Mailkit 1.0.1 → 1.0.3 available (referenced by Application).
  • Outdated: NArchitecture.Core.Security.DependencyInjection — NArchitecture.Core.Security.DependencyInjection 1.2.0 → 1.2.1 available (referenced by Application).
  • Outdated: NArchitecture.Core.Persistence — NArchitecture.Core.Persistence 1.1.1 → 1.1.5 available (referenced by Domain).
  • Outdated: NArchitecture.Core.Security — NArchitecture.Core.Security 1.3.1 → 1.3.3 available (referenced by Domain).
  • Outdated: Microsoft.EntityFrameworkCore.InMemory — Microsoft.EntityFrameworkCore.InMemory 8.0.3 → 10.0.13 available (referenced by Persistence).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 8.0.3 → 10.0.13 available (referenced by Persistence).
  • Outdated: Microsoft.Extensions.Configuration.Abstractions — Microsoft.Extensions.Configuration.Abstractions 8.0.0 → 10.0.13 available (referenced by Persistence).
  • Outdated: NArchitecture.Core.Persistence.DependencyInjection — NArchitecture.Core.Persistence.DependencyInjection 1.0.1 → 1.0.2 available (referenced by Persistence).
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer — Microsoft.AspNetCore.Authentication.JwtBearer 8.0.3 → 10.0.13 available (referenced by WebAPI).
  • Outdated: Microsoft.EntityFrameworkCore.Tools — Microsoft.EntityFrameworkCore.Tools 8.0.3 → 10.0.13 available (referenced by WebAPI).
  • Outdated: Microsoft.Extensions.Caching.StackExchangeRedis — Microsoft.Extensions.Caching.StackExchangeRedis 8.0.3 → 10.0.13 available (referenced by WebAPI).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 8.0.0 → 10.0.13 available (referenced by WebAPI).
  • Outdated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 8.0.0 → 10.0.13 available (referenced by WebAPI).
  • Outdated: NArchitecture.Core.CrossCuttingConcerns.Exception.WebApi — NArchitecture.Core.CrossCuttingConcerns.Exception.WebApi 1.1.0 → 1.1.3 available (referenced by WebAPI).
  • Outdated: NArchitecture.Core.Localization.WebApi — NArchitecture.Core.Localization.WebApi 1.0.0 → 1.0.1 available (referenced by WebAPI).
  • Outdated: NArchitecture.Core.Persistence.WebApi — NArchitecture.Core.Persistence.WebApi 1.0.0 → 1.0.2 available (referenced by WebAPI).
  • Outdated: NArchitecture.Core.Security.WebApi.Swagger — NArchitecture.Core.Security.WebApi.Swagger 1.0.0 → 1.0.2 available (referenced by WebAPI).
  • + 8 more in this group — see findings.md.
D19 · Documentation Quality · XML-doc coverage · ×5
  • XML-doc coverage: Application REDACTED — Application: 0 % XML-doc coverage (0/479).
  • XML-doc coverage: Domain src/starterProject/Domain/Domain.csproj — Domain: 0 % XML-doc coverage (0/15).
  • XML-doc coverage: Persistence REDACTED — Persistence: 0 % XML-doc coverage (0/38).
  • XML-doc coverage: WebAPI src/starterProject/WebAPI/WebAPI.csproj — WebAPI: 0 % XML-doc coverage (0/40).
  • XML-doc coverage: Infrastructure src/starterProject/Infrastructure/Infrastructure.csproj — Infrastructure: 0 % XML-doc coverage (0/6).
D10 · Test Quality · Mock framework · ×1
  • Mock framework: Moq — StarterProject.Application.Tests references Moq.

Appendix B — Reproduction & audit trail

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

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-5761f4da78ab4b61933d822b0270e85d/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5761f4da78ab4b61933d822b0270e85d/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .31artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list NArchitecture.sln package --vulnerable --include-transitive --format json12artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: 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.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious 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 01a16013-9312-7109-92dd-76ddea344a1c · 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 — 26 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 16 field(s)
  • CreateUserCommand.FirstName src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:15
  • CreateUserCommand.LastName src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:16
  • CreatedUserResponse.FirstName src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:8
  • CreatedUserResponse.LastName src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:9
  • UpdateUserCommand.FirstName src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:16
  • UpdateUserCommand.LastName src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:17
  • UpdatedUserResponse.FirstName src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:8
  • UpdatedUserResponse.LastName src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:9
  • UpdateUserFromAuthCommand.FirstName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:14
  • UpdateUserFromAuthCommand.LastName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:15
  • UpdatedUserFromAuthResponse.FirstName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:9
  • UpdatedUserFromAuthResponse.LastName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:10
  • GetByIdUserResponse.FirstName src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:8
  • GetByIdUserResponse.LastName src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:9
  • GetListUserListItemDto.FirstName src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:8
  • GetListUserListItemDto.LastName src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:9
Email — 10 field(s)
  • EnableEmailAuthenticatorCommand.VerifyEmailUrlPrefix src/starterProject/Application/Features/Auth/Commands/EnableEmailAuthenticator/EnableEmailAuthenticatorCommand.cs:18
  • CreateUserCommand.Email src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:17
  • CreatedUserResponse.Email src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:10
  • UpdateUserCommand.Email src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:18
  • UpdatedUserResponse.Email src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:10
  • UpdatedUserFromAuthResponse.Email src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:11
  • GetByIdUserResponse.Email src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:10
  • GetListUserListItemDto.Email src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:10
  • User.EmailAuthenticators src/starterProject/Domain/Entities/User.cs:8
  • BaseDbContext.EmailAuthenticators src/starterProject/Persistence/Contexts/BaseDbContext.cs:11

Issues: 12 · Warnings: 161 · Recommendations: 55 · Info: 39 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 20:07 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