babaktaremi/Clean-Architecture-Template

Executive summary

babaktaremi/Clean-Architecture-Template scores 52 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 47 and is rated Adequate. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 5 Leaked secret finding(s) in REDACTED Scanning and to resolve the 1 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 52 to about 55.

26 findings are critical: six in Dependency Vulnerabilities, five in REDACTED Scanning, five in Static Analysis (SAST), three in IaC & Container Security, three in Secrets (history), two in Explicit Debt, one in Dependency Hygiene and one in Project dependency cycles.

Watchdog couldn't measure Runtime accessibility in this code, so that dimension is left out of the score. The product code is 4,657 lines, which would take an estimated 0.1 person-years, around €7,700, to rebuild.

Code Health 53 Adequate, capped by Structured logging and Nullable reference types Architecture 83 ★ Exemplary Maturity 55 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 47 Adequate, capped by Code Coverage, REDACTED Scanning and Domain vs controller coverage Security and Compliance 53 Adequate, capped by Static Analysis (SAST) and Data Protection Performance 64 Strong

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 47 · counts for 46%Code Health 53 · counts for 25%Security and Compliance 53 · counts for 14%Maturity 55 · counts for 8%Performance 64 · counts for 4%Architecture 83 · counts for 2%

If Production Readiness rose from 47 to 70, the lowest score rated Strong, the score would rise from 52 to about 55.

Code composition: what the lines of code are

Business logic 16%Supporting code 59%Tests 2%Generated by tools 22%

New since the last survey: 110 findings

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

REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
Explicit Debt · Dead code: GetDependentAssemblies src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs
Explicit Debt · Dead code: ToGroupedDictionary src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs
Explicit Debt · Dead code: GetEnumValues src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs
Explicit Debt · Dead code: GetEnumFlags src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs
Explicit Debt · Dead code: GetUserName src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs
Explicit Debt · Dead code: AddSingularizingTableNameConvention src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs
Explicit Debt · Dead code: AddSequentialGuidForIdConvention src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs
Explicit Debt · Dead code: RegisterEntityTypeConfiguration src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs
Explicit Debt · Dead code: BaseTypeIsGeneric src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs
Explicit Debt · Dead code: IsEnumerable src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs
Explicit Debt · Dead code: IsEnumerable src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs
Explicit Debt · Dead code: GetBaseTypesAndInterfaces src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs
Explicit Debt · Dead code: IsCustomType src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs
Explicit Debt · Dead code: IsAssignableFromBaseTypeGeneric src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs
Explicit Debt · Dead code: ToInt src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: ToNumeric src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: ToNumeric src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: ToCurrency src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: ToCurrency src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: En2Fa src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: CleanString src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs
Explicit Debt · Dead code: PasswordlessLoginTokenProviderOptions src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs
Explicit Debt · Dead code: IncrementAccessFailedCountAsync src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs
Explicit Debt · Dead code: ResetUserLockoutAsync src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs
Explicit Debt · Dead code: DeleteRoleAsync src/Core/CleanArc.Application/Contracts/Identity/IRoleManagerService.cs
Explicit Debt · Dead code: GetRolePermissionsAsync src/Core/CleanArc.Application/Contracts/Identity/IRoleManagerService.cs
Explicit Debt · Dead code: GetPrincipalFromExpiredToken src/Core/CleanArc.Application/Contracts/IJwtService.cs
Explicit Debt · Dead code: GenerateByPhoneNumberAsync src/Core/CleanArc.Application/Contracts/IJwtService.cs
Explicit Debt · Dead code: RollBackAsync src/Core/CleanArc.Application/Contracts/Persistence/IUnitOfWork.cs
Explicit Debt · Dead code: RemoveUserOldTokens src/Core/CleanArc.Application/Contracts/Persistence/IUserRefreshTokenRepository.cs
Explicit Debt · Dead code: AddError src/Core/CleanArc.Application/Models/Common/OperationResult.cs
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Cancellation propagation · Async method without CancellationToken: GetRolesAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Cancellation propagation · Async method without CancellationToken: DeleteRoleAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Cancellation propagation · Async method without CancellationToken: GetRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Cancellation propagation · Async method without CancellationToken: ChangeRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Cancellation propagation · Async method without CancellationToken: GenerateAsync REDACTED
Cancellation propagation · Async method without CancellationToken: GenerateByPhoneNumberAsync REDACTED
Cancellation propagation · Async method without CancellationToken: RefreshToken REDACTED
Cancellation propagation · Async method without CancellationToken: IsExistUser src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
Cancellation propagation · Async method without CancellationToken: IsExistUserName src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
Cancellation propagation · Async method without CancellationToken: GetUserByCode src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
Cancellation propagation · Async method without CancellationToken: GetUserByPhoneNumber src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
Cancellation propagation · Async method without CancellationToken: GetAllUsersAsync src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
Cancellation propagation · Async method without CancellationToken: CommitAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/UnitOfWork.cs
Cancellation propagation · Async method without CancellationToken: AddOrderAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
Cancellation propagation · Async method without CancellationToken: GetAllUserOrdersAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
Cancellation propagation · Async method without CancellationToken: GetAllOrdersWithRelatedUserAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
Cancellation propagation · Async method without CancellationToken: GetUserOrderByIdAndUserIdAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
Cancellation propagation · Async method without CancellationToken: DeleteUserOrdersAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
Cancellation propagation · Async method without CancellationToken: CreateToken src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs
Cancellation propagation · Async method without CancellationToken: GetTokenWithInvalidation src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs
Cancellation propagation · Async method without CancellationToken: GetUserByRefreshToken src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs
Cancellation propagation · Async method without CancellationToken: GetUserOrders src/API/Plugins/CleanArc.Web.Plugins.Grpc/Services/OrderGrpcServices.cs
Cancellation propagation · Async method without CancellationToken: TokenRequest REDACTED
Cancellation propagation · Async method without CancellationToken: GetUserToken REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED

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: 1 finding

This critical or serious finding was in the previous survey, on 7 October 2026, and is gone from this one.

Coupling · Off the main sequence: CleanArc.Infrastructure.Monitoring

Rebuild cost: about €7,700 · Estimate

Cost to rebuild	€2,600 to €13,000, for 43 to 135 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem	High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Small: 4,657 lines of product code, of which 40% is declarations and boilerplate, 39% straight logic and 21% logic with branches

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

Top priorities

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

Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2).

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

Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.

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

Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2).

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

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €7,700 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 47 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

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

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

If you do one thing first · First action

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

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

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

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.

63 modules, with 109 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 23 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.Models.Common	2 Application.Models.Jwt	3 Domain.Common	4 Infrastructure.Identity.Identity.Dtos	5 Infrastructure.Persistence	6 SharedKernel.ValidationBase	7 Domain.Entities.Order	8 SharedKernel.ValidationBase.Contracts	9 WebFramework.BaseController	10 Domain.Entities.User	11 Application.Contracts	12 Application.Contracts.Persistence	13 Application.Models.Identity	14 Infrastructure.Identity.Identity.Manager	15 Application.Contracts.Identity	18 Application.Features.Users.Commands.RefreshUserTokenCommand	22 Infrastructure.Persistence.Repositories.Common	23 Application.Features.Admin.Commands.AddAdminCommand	24 Application.Features.Admin.Queries.GetToken	25 Application.Features.Order.Commands	26 Application.Features.Role.Commands.AddRoleCommand	27 Application.Features.Role.Commands.UpdateRoleClaimsCommand	30 Application.Features.Users.Commands.Create	32 Application.Features.Users.Queries.GenerateUserToken	34 Application.Features.Users.Queries.TokenRequest
1 Application.Models.Common
2 Application.Models.Jwt
3 Domain.Common
4 Infrastructure.Identity.Identity.Dtos
5 Infrastructure.Persistence
6 SharedKernel.ValidationBase
7 Domain.Entities.Order			1							1
8 SharedKernel.ValidationBase.Contracts						1
9 WebFramework.BaseController	1
10 Domain.Entities.User			8				1
11 Application.Contracts		1								1
12 Application.Contracts.Persistence							1			2
13 Application.Models.Identity										1
14 Infrastructure.Identity.Identity.Manager										3
15 Application.Contracts.Identity										3			5
16 Application.Features.Order.Queries.GetAllOrders	1											1
17 Application.Features.Order.Queries.GetUserOrders	1											1
18 Application.Features.Users.Commands.RefreshUserTokenCommand	1	1				1		1			1
19 Infrastructure.Identity.Identity										1				2
20 Infrastructure.Identity.Identity.SeedDatabaseService														2
21 Infrastructure.Identity.Jwt		1		1						1	1	1		1
22 Infrastructure.Persistence.Repositories.Common					2							3
23 Application.Features.Admin.Commands.AddAdminCommand	1					1		1							2
24 Application.Features.Admin.Queries.GetToken	1	1				1		1			1				1
25 Application.Features.Order.Commands	3					2		2				3			1
26 Application.Features.Role.Commands.AddRoleCommand	1					1		1							1
27 Application.Features.Role.Commands.UpdateRoleClaimsCommand	1														1
28 Application.Features.Role.Queries.GetAllRolesQuery	1														1
29 Application.Features.Role.Queries.GetAuthorizableRoutesQuery	1														1
30 Application.Features.Users.Commands.Create	1					1		1							1
31 Application.Features.Users.Commands.RequestLogout	1														1
32 Application.Features.Users.Queries.GenerateUserToken	1	1				1		1			1				1
33 Application.Features.Users.Queries.GetUsers	1														1
34 Application.Features.Users.Queries.TokenRequest	2	1				2		2			1				2
35 Infrastructure.Identity.Identity.PermissionManager					1					1			5	2	1
36 Infrastructure.Identity.UserManager										2				1	1
37 Infrastructure.Persistence.Repositories					2		1			2		2					2
38 Web.Api.Controllers.V1.Admin									4									1	1		1	1
39 Web.Api.Controllers.V1.Order									1											2
40 Web.Api.Controllers.V1.UserManagement									1							1							1	1	2

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 53% · Adequate · gated by X4, X5 ·

The Good

D1 · .NET / C# Cyclomatic Complexity 9.6 D2 · .NET / C# Cognitive Complexity 9.2 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.4 D17 · .NET / C# Explicit Debt 6.6 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.8 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

The Bad

X2 · Repo Cancellation propagation 5.8

The Ugly

X4 · Repo Structured logging 2.7 X5 · Repo Nullable reference types 2.8

At a glance — Architecture · 83% · Exemplary ·

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.9 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.7 AX7 · Repo Slice cohesion 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

The Ugly

D22 · .NET / C# Internal API Consistency 3.0 AX10 · Repo Code composition 4.0

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

The Good

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

The Ugly

D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 47% · Adequate · gated by D8, D13, P9 ·

The Good

D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D12 · .NET / C# Dependency Hygiene 6.1 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 6.0 P2 · Repo Observability 8.7 P8 · Repo Schema migrations 10.0

The Bad

D8 · .NET / C# Code Coverage 3.8 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0

The Ugly

D13 · .NET / C# REDACTED Scanning 0.0 P9 · Repo Domain vs controller coverage 1.3

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

The Good

D28 · .NET / C# Secrets (history) 7.0 D31 · .NET / C# IaC & Container Security 8.7 D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D30 · .NET / C# Dependency Vulnerabilities 5.4 C4 · Repo Data Retention 6.5

The Ugly

D29 · .NET / C# Static Analysis (SAST) 2.0 C1 · Repo Data Protection 3.5 S1 · Repo Web-Security Posture 4.0

At a glance — Performance · 64% · Strong ·

The Good

PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 7.7 PF3 · Repo Async & latency hygiene 6.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 category	Findings	Severity
A05:2025 — Injection	19	High / Critical
A07:2025 — Authentication Failures	9	High / Critical
A03:2025 — Software Supply Chain Failures	8	High / Critical
A02:2025 — Security Misconfiguration	7	High / Critical

Roadmap

Immediately address security risks by resolving five leaked secrets in configuration files and fixing one vulnerable dependency. Strengthen code quality by eliminating thirty-two low-coverage areas, particularly in extension classes, and removing two deprecated package references. Finally, improve reliability by raising unit-test coverage for domain logic, where correctness is most critical.

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

Do this	Helps	Effort	Dimension
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2).	+4.8 pts	Low	REDACTED Scanning
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.	+3.8 pts	Low	Dependency Hygiene
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2).	+3.2 pts	Low	Dependency Hygiene
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene.	+2.6 pts	Low	Dependency Hygiene
Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.	+3.3 pts	Medium	Domain vs controller coverage
Resolve the 32 Low coverage finding(s) in Code Coverage — start with AssemblyExtensions.cs, CollectionExtensions.cs, EnumExtentions.cs.	+3.2 pts	Medium	Code Coverage
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED.	+1.4 pts	Low	Explicit Debt
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RoleManagerService.cs.	+1.4 pts	Low	Explicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 67 files carrying findings, judged against the Template bar: 7% slop · 5% mixed · 88% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	0.9	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	1.4	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	1.9	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	2.0	Slop	IaC & Container Security: High IaC: REDACTED
src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs	4.8	Mixed	Code Duplication: Duplicated block (41 lines × 2)
src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs	5.0	Mixed	Explicit Debt: WriteOnlyPrivateField
REDACTED	5.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs	6.0	Near-clean	Explicit Debt: Dead code: GetEnumValues
src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs	6.0	Near-clean	Explicit Debt: Dead code: AddSingularizingTableNameConvention
src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs	6.0	Near-clean	Explicit Debt: Dead code: BaseTypeIsGeneric
REDACTED	6.1	Near-clean	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.2	Near-clean	Dependency Hygiene: Deprecated: Serilog.Sinks.Elasticsearch
REDACTED	6.4	Near-clean	Dependency Vulnerabilities: Medium CVE: REDACTED
src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs	6.4	Near-clean	Explicit Debt: Dead code: ToInt
src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs	6.7	Near-clean	Cyclomatic Complexity: ApplySummariesOperationFilter.Process (cyclomatic 21)
src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs	6.7	Near-clean	Explicit Debt: Dead code: GetDependentAssemblies
src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs	6.7	Near-clean	Explicit Debt: Dead code: ToGroupedDictionary
src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs	6.7	Near-clean	Explicit Debt: Dead code: GetUserName
src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs	6.7	Near-clean	Explicit Debt: Dead code: PasswordlessLoginTokenProviderOptions

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

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

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

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

Could not be resolved — 4

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

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

What we checked — 85 dimensions across the health lenses

D1D2D3D4D5D6D8D9D10D11D12D13D14D15D17D18D19D21D22D24D26D27D28D29D30D31D34D35D39D44AX1AX10AX3AX4AX5AX6AX7AX8AX9C1C2C4ED5GD1IC1M1M2M3M4P1P10P2P4P6P8P9PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 287 of 342 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a161b1-30b3-7da1-b677-5a32eddf3f7f.

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

Run transparency — what happened this run

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

D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 142 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `REDACTED`, `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs`, `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs`, `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs`, `src/Core/CleanArc.Application/Common/LoggingBehavior.cs`, … (+19 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — web_api Pulling sql Pulling web_api Error Get "https://registry-1.docker.io/v2/": Forbidden sql Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: web_api Pulling sql Pulling web_api Error Get "https://registry-1.docker.io/v2/": Forbidden sql Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 114 further occurrence(s) are not listed individually; the score already reflects all 154.
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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.

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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
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.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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 (6): D19, D21, D22, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.6 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ApplySummariesOperationFilter.Process at 21.

ApplySummariesOperationFilter.Process (cyclomatic 21)src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:12

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

ApplySummariesOperationFilter.Process (cognitive 29)src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:12

What to do

Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ApplySummariesOperationFilter.Process (cognitive 29). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God 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.

Do you agree with this assessment?

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

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

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

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

8 duplicated block group(s) detected.

Duplicated block (6 lines × 2) · ×3src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:43

Duplicated block (41 lines × 2)src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:121

Duplicated block (32–35 lines × 2)src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:46

Duplicated block (17 lines × 2)src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:218

Duplicated block (7 lines × 2)src/API/CleanArc.WebFramework/Filters/BadRequestResultFilterAttribute.cs:19

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

What to do

Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ApplySummariesOperationFilter.cs (2), LookupProtector.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Duplicated block (41 lines × 2) finding(s) in Code Duplication — start with LookupProtector.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (32–35 lines × 2) finding(s) in Code Duplication — start with LookupProtector.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

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

Off the main sequence: CleanArc.SharedKernelsrc/Shared/CleanArc.SharedKernel/CleanArc.SharedKernel.csproj:1

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

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

0 of 6 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs · ×32src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs:1

CRAP 42: LookupProtector.ByteArraysEqual · ×3src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:215

CRAP 30: RoleManagerService.GetPermissionActionsAsync · ×2src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:83

No test project references CleanArc.WebFrameworksrc/API/CleanArc.WebFramework/CleanArc.WebFramework.csproj

No test project references CleanArc.Web.ApiREDACTED

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

What to do

Resolve the 32 Low coverage finding(s) in Code Coverage — start with AssemblyExtensions.cs, CollectionExtensions.cs, EnumExtentions.cs. — One of this dimension's main actionable groups (32 warning-level).
Resolve the 3 CRAP 42 finding(s) in Code Coverage — start with LookupProtector.cs, PersonalDataProtector.cs, ServiceCollectionExtension.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 CRAP 30 finding(s) in Code Coverage — start with RoleManagerService.cs, ReflectionExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
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.

Do you agree with this assessment?

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

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

Mock framework: NSubstitute

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene6.1 / 10Adequate✓ 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 6.1 / 10 · rule-coverage 100% · ceiling Verified

35 outdated, 1 vulnerable, 2 deprecated, 1 prerelease packages.

Vulnerable: NuGet.Packaging

Deprecated: Serilog.Sinks.Elasticsearch · ×2REDACTED:50

Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore

Outdated: Mapster · ×3REDACTED:17

Outdated: FluentValidation · ×32

What to do

Resolve the 1 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
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.

Do you agree with this assessment?

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

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

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

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

3 secret(s) detected.

REDACTED

What to do

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

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

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 49 direct `PackageReference`(s), and 201 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity 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.

Do you agree with this assessment?

D17 · Explicit Debt6.6 / 10Adequate✓ 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 6.6 / 10 · rule-coverage 100% · ceiling Prevented

8 deducted debt markers + 33 dead symbols across 4657 LoC in the .NET projects (1.7/KLoC) → score 6.6.

WriteOnlyPrivateFieldsrc/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:25

NoWarnInCsprojREDACTED:8

Dead code: GetDependentAssemblies · ×33src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs:7

CommentedOutCode · ×2src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17

TodoComment · ×2src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:49

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

What to do

Resolve the 33 Dead code finding(s) in Explicit Debt — start with StringExtensions.cs (7), ReflectionExtensions.cs (6), ModelBuilderExtensions.cs (3). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RoleManagerService.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

12 projects, 164 source files, 4826 hand-written lines of code (4657 production / 169 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 1534 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 20 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

Do you agree with this assessment?

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 long document that claims to be the 'everything you need to start an enterprise project' boilerplate for ASP.NET Core and Clean Architecture. It gives a strong personal endorsement ('most of them are not usable in production...this framework was built upon actual real-world challenges'), links to a NuGet badge, a GitHub PRs welcome badge, and a LinkedIn/Email/Telegram presence. The body is an unbroken narrative with no visible headings or outline; the document's own opening paragraph under 'ASP NET Core 10 Clean architecture boiler plate' serves as its overview but it does not explain what the project is for or how to use the template beyond the one-line dotnet new install command, so the README lacks a clear overview and usage. The visible content is mostly installation with an unshown clip; no architecture/design docs are referenced.

XML-doc coverage: CleanArc.SharedKernel · ×10src/Shared/CleanArc.SharedKernel/CleanArc.SharedKernel.csproj

What to do

Improve Documentation Quality — currently 6.0/10. — The repository's root README is a single long document that claims to be the 'everything you need to start an enterprise project' boilerplate for ASP.NET Core and Clean Architecture. It gives a strong personal endorsement ('most of them are not usable in production...this framework was built upon actual real-world challenges'), links to a NuGet badge, a GitHub PRs welcome badge, and a LinkedIn/Email/Telegram presence. The body is an unbroken narrative with no visible headings or outline; the document's own opening paragraph under 'ASP NET Core 10 Clean architecture boiler plate' serves as its overview but it does not explain what the project is for or how to use the template beyond the one-line dotnet new install command, so the README lacks a clear overview and usage. The visible content is mostly installation with an unshown clip; no architecture/design docs are referenced.

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyWeak◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

3 API inconsistencies across 7 exposed types.

Fragmented Authentication/Token Logic: The API exposes multiple distinct endpoints for token generation and validation across different controllers (Admin vs User). 'AdminLogin' and 'TokenRequest' likely perform similar authentication flows but are separated by role. 'ValidateUser' and 'TokenRequest' have ambiguous naming regarding whether they generate new tokens or just verify existing ones. 'RefreshUserToken' is a specific state change, but the lack of a unified 'Auth' or 'Account' controller makes the authentication surface disjointed.

Inconsistent Naming Convention for Retrieval: 'GetAllUsers' uses a plural noun indicating a collection, while 'GetUserOrders' uses a possessive/relationship structure. While semantically distinct, the pattern for listing resources is inconsistent. More critically, 'GetOrders' in OrderManagementController lacks the 'All' or 'List' qualifier, whereas 'GetAllUsers' explicitly states it retrieves all. This creates ambiguity about whether 'GetOrders' returns all orders or requires parameters.

Inconsistent Verb Usage for Creation: 'CreateUser' uses the standard 'Create' verb, while 'AddNewAdmin' uses 'AddNew'. 'AddNew' is redundant ('Add' implies creation) and inconsistent with the 'Create' pattern used elsewhere. This suggests a lack of standardized command naming conventions for resource creation.

What to do

Resolve the 1 Fragmented Authentication/Token Logic finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent Naming Convention for Retrieval finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent Verb Usage for Creation finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

32 valuable / 0 redundant across 93 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

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 12 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

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

19 finding(s): 0 critical, 5 high, 14 medium, 0 low. semgrep hit a parse error in 24 file(s) — `REDACTED` (lines 16–17, line 37), `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs` (lines 22–23, line 67), `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs` (line 16), `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs` (line 11), `src/Core/CleanArc.Application/Common/LoggingBehavior.cs` (line 7), … (+19 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 23 of those file(s) — `REDACTED`, `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs`, `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs`, `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs`, `src/Core/CleanArc.Application/Common/LoggingBehavior.cs`, … (+18 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities5.4 / 10Adequate✓ 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 5.4 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security8.7 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge 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

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

Orphaned file · ×19src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:1

Orphaned files with no living knowledge

What to do

Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtension.cs, PersonalDataProtector.cs, LookupProtector.cs. — One of this dimension's main actionable groups (19 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge 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.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

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

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

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

IL efficiency: 1 authored method(s) exceed the IL budgetsrc/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:15

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

AX10 · Code composition4.0 / 10Weak✓ Tool-verified

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

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

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

What to do

The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

The namespaces CleanArc.Domain.Entities.Order ↔ CleanArc.Domain.Entities.User depend on each other. The lightest dependency in the cycle is CleanArc.Domain.Entities.Order → CleanArc.Domain.Entities.User (CleanArc.Domain.Entities.Order.Order → CleanArc.Domain.Entities.User.User, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/CleanArc.Domain/Entities/Order/Order.cs:5

What to do

Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX6 · Interface segregation9.7 / 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.

`IAppUserManager` declares 22 members: `CreateUser`, `CreateUser`, `IsExistUser`, `IsExistUserName`, `GeneratePhoneNumberConfirmationToken`, `GetUserByCode`, `ChangePhoneNumber`, `VerifyUserCode`, `GenerateOtpCode`, `GetUserByPhoneNumber`, `GetByUserName`, `GetUserByIdAsync`, `GetAllUsersAsync`, `CreateUserWithPasswordAsync`, `AddUserToRoleAsync`, `IncrementAccessFailedCountAsync`, `IsUserLockedOutAsync`, `ResetUserLockoutAsync`, `UpdateUserAsync`, `UpdateSecurityStampAsync`, `IsPasswordValidAsync`, `GetRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:6

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

What to do

Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

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

What to do

Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36

What to do

Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.8 / 10Exemplary✓ Tool-verified

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

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

`RemoveUserOldTokens` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×21) — src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17, src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:18, src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:19, …

What to do

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

Do you agree with this assessment?

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

M4 · Documentation accuracy8.0 / 10Exemplary◐ Sampled · advisory

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

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

README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:152

What to do

Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.

What to do

Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.

Do you agree with this assessment?

P2 · Observability8.7 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
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 a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

P9 · Domain vs controller coverage1.3 / 10Weak✓ Tool-verified

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

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

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

What to do

Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.

Do you agree with this assessment?

PF1 · Benchmark discipline6.0 / 10Strong✓ Tool-verified

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

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

No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).

Do you agree with this assessment?

PF2 · Allocation hygiene7.7 / 10Strong✓ Tool-verified

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

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

What to do

Raise allocation-aware density on the hot paths — currently 28 use(s) across 8,297 production line(s) (~3.4/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.0 / 10Strong✓ 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.

Only 0/153 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
`await UserManager.GetRolesAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:18
`await base.GenerateClaimsAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:20
`await manager.GetPhoneNumberAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:34
`await _roleManger.Roles.Where(c => !c.Name.Equals("admin")).Select(r => _mapper.Map...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:43
`await _roleManger.CreateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:54
`await _roleManger.Roles.Include(r => r.Claims) .Include(r => r.Users).FirstOrDefaul...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:61
`await _userManager.GetUsersInRoleAsync(role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:67, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:197
`await _userManager.RemoveFromRoleAsync(user, role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:71
`await _userManager.UpdateSecurityStampAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:72, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:201
`await _db.SaveChangesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:78, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:191
`await _roleManger.Roles .Include(x => x.Claims) .SingleOrDefaultAsync(x => x.Id == ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:130, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:147
`await this.GetPermissionActionsAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:137
`await _roleManger.UpdateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:193
`await _roleManger.FindByIdAsync(roleId.ToString())` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:212
`await _roleManager.CreateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:31
`await _userManager.CreateAsync(user, "qw123321")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:43
`await _userManager.AddToRoleAsync(user,"admin")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:44
`await base.ValidateAsync(manager, user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs:15
`await _getClaimsAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:42
`await _unitOfWork.UserRefreshTokenRepository.CreateToken(user.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:61
`await _unitOfWork.CommitAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — REDACTED:62, REDACTED:105
`await _userManager.Users.AsNoTracking().FirstOrDefaultAsync(u => u.PhoneNumber == p...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:91
`await this.GenerateAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — REDACTED:92, REDACTED:112
`await _unitOfWork.UserRefreshTokenRepository.GetTokenWithInvalidation(refreshTokenId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:98
`await _unitOfWork.UserRefreshTokenRepository.GetUserByRefreshToken(refreshTokenId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:107
`await _claimsPrincipal.CreateAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:119
`await signInManager.ValidateSecurityStampAsync(context.Principal)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:166
`await context.Response.WriteAsJsonAsync(response)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:182, src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:192
`await context.Response.WriteAsJsonAsync(new ApiResult(false, ApiResultStatusCode.Un...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:201
`await context.Response.WriteAsJsonAsync(new ApiResult(false, ApiResultStatusCode.Fo...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:208
`await using … = app.Services.CreateAsyncScope()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:219
`await seedService.Seed()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:222

What to do

In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.

Do you agree with this assessment?

S1 · Web-Security Posture4.0 / 10Weak✓ 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.

`RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:134
`ValidateAudience`, `ValidateIssuer`, `ValidateLifetime` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — REDACTED:71
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/API/CleanArc.Web.Api/Program.cs:24
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/API/CleanArc.Web.Api/Program.cs:24

What to do

Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X2 · Cancellation propagation5.8 / 10Adequate✓ Tool-verified

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

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

Only 22/72 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. (×34) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:41, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:59, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:128, …
No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:217, src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs:25
No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken. (×3) — src/API/Plugins/CleanArc.Web.Plugins.Grpc/Services/OrderGrpcServices.cs:23, REDACTED:18, REDACTED:53

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup 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.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception 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.

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging2.7 / 10Weak✓ Tool-verified

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

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

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×4) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:121, src/Core/CleanArc.Application/Common/LoggingBehavior.cs:22, src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:47, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types2.8 / 10Weak✓ 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.

This method contradicts itself about `claimsIdentity`: line 150 assigns it with `as ClaimsIdentity`, which hands back null rather than throwing when the value is not a `ClaimsIdentity`, but line 151 then dereferences it directly as `claimsIdentity.Claims` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `claimsIdentity` once before the first use and handle the null case, or cast with `(ClaimsIdentity)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:151
1/10 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.1 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 6761 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

Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Do you agree with this assessment?

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	53%	Adequate — gated by X4, X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	83%	Exemplary	Strongest area.
Maturity	55%	Adequate — gated by D34, M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	47%	Adequate — gated by D8, D13, P9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	53%	Adequate — gated by D29, C1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	64%	Strong	Solid.

Unscored — 2 check(s) recorded observations but carry no score

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

P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 3 control(s) we could not find positive evidence for

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

C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 31 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — web_api Pulling sql Pulling web_api Error Get "https://registry-1.docker.io/v2/": Forbidden sql Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: web_api Pulling sql Pulling web_api Error Get "https://registry-1.docker.io/v2/": Forbidden sql Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
D23 Boundary Type-Coupling — small single-context codebase (4,657 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
D32 Data Compliance (PII/GDPR) — 24 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a Domain/Aggregates/ValueObjects layer; 4 repository port(s) loading or saving an aggregate/entity
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (18 CQRS handler(s))
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
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
SC1 Supply-chain hygiene — 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 — 26 finding(s)

D13 · REDACTED Scanning · Leaked secret · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

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

REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×2

REDACTED
REDACTED

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

Namespace dependency cycle src/Core/CleanArc.Domain/Entities/Order/Order.cs:5 — The namespaces CleanArc.Domain.Entities.Order ↔ CleanArc.Domain.Entities.User depend on each other. The lightest dependency in the cycle is CleanArc.Domain.Entities.Order → CleanArc.Domain.Entities.User (CleanArc.Domain.Entities.Order.Order → CleanArc.Domain.Entities.User.User, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.

D12 · Dependency Hygiene · Vulnerable · ×1

Vulnerable: NuGet.Packaging — REDACTED — Low severity. https://github.com/advisories/[GHSA redacted]

D17 · Explicit Debt · WriteOnlyPrivateField · ×1

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

D17 · Explicit Debt · NoWarnInCsproj · ×1

NoWarnInCsproj REDACTED:8 — 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.

D28 · Secrets (history) · High secret · ×1

REDACTED

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

REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×1

REDACTED

Serious — 200 finding(s)

PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×40

Awaits without ConfigureAwait(false) — Only 0/153 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:18 — `await UserManager.GetRolesAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:20 — `await base.GenerateClaimsAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:34 — `await manager.GetPhoneNumberAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:43 — `await _roleManger.Roles.Where(c => !c.Name.Equals("admin")).Select(r => _mapper.Map...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:54 — `await _roleManger.CreateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:61 — `await _roleManger.Roles.Include(r => r.Claims) .Include(r => r.Users).FirstOrDefaul...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:67 — `await _userManager.GetUsersInRoleAsync(role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:71 — `await _userManager.RemoveFromRoleAsync(user, role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:72 — `await _userManager.UpdateSecurityStampAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:78 — `await _db.SaveChangesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:130 — `await _roleManger.Roles .Include(x => x.Claims) .SingleOrDefaultAsync(x => x.Id == ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:137 — `await this.GetPermissionActionsAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:147 — `await _roleManger.Roles .Include(x => x.Claims) .SingleOrDefaultAsync(x => x.Id == ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:191 — `await _db.SaveChangesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:193 — `await _roleManger.UpdateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:197 — `await _userManager.GetUsersInRoleAsync(role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:201 — `await _userManager.UpdateSecurityStampAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:212 — `await _roleManger.FindByIdAsync(roleId.ToString())` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:31 — `await _roleManager.CreateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:43 — `await _userManager.CreateAsync(user, "qw123321")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:44 — `await _userManager.AddToRoleAsync(user,"admin")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs:15 — `await base.ValidateAsync(manager, user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) REDACTED:42 — `await _getClaimsAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) REDACTED:61 — `await _unitOfWork.UserRefreshTokenRepository.CreateToken(user.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
+ 15 more in this group — see findings.md.

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

Async method without CancellationToken: GetRolesAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:41 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteRoleAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:128 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ChangeRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:145 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateAsync REDACTED:33 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateByPhoneNumberAsync REDACTED:89 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RefreshToken REDACTED:96 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SeedDefaultUsersAsync src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:217 — No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken.
Async method without CancellationToken: IsExistUser src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsExistUserName src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:33 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetUserByCode src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetUserByPhoneNumber src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllUsersAsync src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ListAllAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CommitAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/UnitOfWork.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddOrderAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:10 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllUserOrdersAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:15 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllOrdersWithRelatedUserAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetUserOrderByIdAndUserIdAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:27 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteUserOrdersAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:37 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateToken src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetTokenWithInvalidation src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.

D17 · Explicit Debt · Dead code · ×33

Dead code: GetDependentAssemblies src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs:7 — Method GetDependentAssemblies — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: ToGroupedDictionary src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs:5 — Method ToGroupedDictionary — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: GetEnumValues src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs:8 — Method GetEnumValues — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: GetEnumFlags src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs:16 — Method GetEnumFlags — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: GetUserName src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs:34 — Method GetUserName — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: AddSingularizingTableNameConvention src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:14 — Method AddSingularizingTableNameConvention — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: AddSequentialGuidForIdConvention src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:45 — Method AddSequentialGuidForIdConvention — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: RegisterEntityTypeConfiguration src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:85 — Method RegisterEntityTypeConfiguration — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: BaseTypeIsGeneric src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:31 — Method BaseTypeIsGeneric — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: IsEnumerable src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:56 — Method IsEnumerable — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: IsEnumerable src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:61 — Method IsEnumerable — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: GetBaseTypesAndInterfaces src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:66 — Method GetBaseTypesAndInterfaces — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: IsCustomType src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:82 — Method IsCustomType — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: IsAssignableFromBaseTypeGeneric src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:98 — Method IsAssignableFromBaseTypeGeneric — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: ToInt src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:10 — Method ToInt — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: ToNumeric src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:20 — Method ToNumeric — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: ToNumeric src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:25 — Method ToNumeric — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: ToCurrency src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:30 — Method ToCurrency — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: ToCurrency src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:37 — Method ToCurrency — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: En2Fa src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:42 — Method En2Fa — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: CleanString src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:94 — Method CleanString — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.SharedKernel, 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: PasswordlessLoginTokenProviderOptions src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:39 — NamedType PasswordlessLoginTokenProviderOptions — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.Infrastructure.Identity, 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: IncrementAccessFailedCountAsync src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:23 — Method IncrementAccessFailedCountAsync — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.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: ResetUserLockoutAsync src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:25 — Method ResetUserLockoutAsync — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.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: DeleteRoleAsync src/Core/CleanArc.Application/Contracts/Identity/IRoleManagerService.cs:11 — Method DeleteRoleAsync — Roslyn's SymbolFinder walked every project the solution loads, including CleanArc.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.
+ 8 more in this group — see findings.md.

D8 · Code Coverage · Low coverage · ×32

Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs:1 — 0.0% line coverage (0/9).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs:1 — 0.0% line coverage (0/8).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs:1 — 0.0% line coverage (0/24).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs:1 — 0.0% line coverage (0/22).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:1 — 36.8% line coverage (21/57).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:1 — 0.0% line coverage (0/57).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/RegExHelpers.cs src/Shared/CleanArc.SharedKernel/Extensions/RegExHelpers.cs:1 — 0.0% line coverage (0/5).
Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/ValidatorExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/ValidatorExtensions.cs:1 — 0.0% line coverage (0/25).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs:1 — 0.0% line coverage (0/16).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:1 — 5.0% line coverage (1/20).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:1 — 42.1% line coverage (8/19).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:1 — 45.0% line coverage (9/20).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:1 — 32.1% line coverage (26/81).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:1 — 0.0% line coverage (0/172).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppErrorDescriber.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppErrorDescriber.cs:1 — 0.0% line coverage (0/56).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:1 — 0.0% line coverage (0/13).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppRoleValidator.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppRoleValidator.cs:1 — 0.0% line coverage (0/6).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs:1 — 0.0% line coverage (0/7).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:1 — 0.0% line coverage (0/26).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionRequirement.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionRequirement.cs:1 — 0.0% line coverage (0/23).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionService.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionService.cs:1 — 0.0% line coverage (0/8).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:1 — 0.0% line coverage (0/135).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:1 — 40.9% line coverage (9/22).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/KeyRing.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/KeyRing.cs:1 — 0.0% line coverage (0/49).
Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:1 — 0.0% line coverage (0/150).
+ 7 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

REDACTED
REDACTED
REDACTED

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

Duplicated block (6 lines × 2) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:43 — src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:43-48 | src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:69-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:56 — src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:56-61 | src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:82-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:56` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:208 — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:208-213 | src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:213-218 — before extracting anything, compare `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs` and `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D8 · Code Coverage · CRAP 42 · ×3

CRAP 42: LookupProtector.ByteArraysEqual src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:215 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 42: PersonalDataProtector.ByteArraysEqual src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:220 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 42: ServiceCollectionExtension.RegisterIdentityServices src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:30 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

D12 · Dependency Hygiene · Deprecated · ×2

Deprecated: Serilog.Sinks.Elasticsearch REDACTED:50 — Serilog.Sinks.Elasticsearch 10.0.0 — Legacy — the publisher's replacement is `Elastic.Serilog.Sinks`; migrate the reference to it.
Deprecated: xunit REDACTED:54 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.

D17 · Explicit Debt · CommentedOutCode · ×2

CommentedOutCode src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17 — 3 consecutive commented-code lines
CommentedOutCode src/Infrastructure/CleanArc.Infrastructure.CrossCutting/Logging/LoggingConfiguration.cs:59 — 11 consecutive commented-code lines

D17 · Explicit Debt · TodoComment · ×2

TodoComment src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:49 — //TODO Send Code Via Sms Provider — 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.
TodoComment src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs:26 — //TODO Send Code Via Sms Provider — 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

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D8 · Code Coverage · CRAP 30 · ×2

CRAP 30: RoleManagerService.GetPermissionActionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:83 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 30: ReflectionHelper.GetBaseTypesAndInterfaces src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:66 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

D1 · Cyclomatic Complexity · ApplySummariesOperationFilter.Process (cyclomatic 21) · ×1

ApplySummariesOperationFilter.Process (cyclomatic 21) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:12 — ApplySummariesOperationFilter.Process has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D12 · Dependency Hygiene · Prerelease dependency · ×1

Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore — OpenTelemetry.Exporter.Prometheus.AspNetCore resolves to 1.9.0-beta.1, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.

D2 · Cognitive Complexity · ApplySummariesOperationFilter.Process (cognitive 29) · ×1

ApplySummariesOperationFilter.Process (cognitive 29) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:12 — ApplySummariesOperationFilter.Process has cognitive complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D22 · Internal API Consistency · Fragmented Authentication/Token Logic · ×1

Fragmented Authentication/Token Logic: The API exposes multiple distinct endpoints for token generation and validation across different controllers (Admin vs User). 'AdminLogin' and 'TokenRequest' likely perform similar authentication flows but are separated by role. 'ValidateUser' and 'TokenRequest' have ambiguous naming regarding whether they generate new tokens or just verify existing ones. 'RefreshUserToken' is a specific state change, but the lack of a unified 'Auth' or 'Account' controller makes the authentication surface disjointed. — Consolidate authentication endpoints into a single 'AuthController' or 'AccountController'. Use a unified 'Login' or 'Authenticate' command/query that handles role-based routing internally, or clearly separate 'Public Auth' (Login/Register) from 'Session Management' (Refresh/Validate) regardless of user role. (signatures: AdminManagerController.AdminLogin(AdminGetTokenQuery model) | UserController.TokenRequest(UserTokenRequestQuery model) | UserController.ValidateUser(GenerateUserTokenQuery model) | UserController.RefreshUserToken(RefreshUserTokenCommand model))

D22 · Internal API Consistency · Inconsistent Naming Convention for Retrieval · ×1

Inconsistent Naming Convention for Retrieval: 'GetAllUsers' uses a plural noun indicating a collection, while 'GetUserOrders' uses a possessive/relationship structure. While semantically distinct, the pattern for listing resources is inconsistent. More critically, 'GetOrders' in OrderManagementController lacks the 'All' or 'List' qualifier, whereas 'GetAllUsers' explicitly states it retrieves all. This creates ambiguity about whether 'GetOrders' returns all orders or requires parameters. — Standardize retrieval methods. Use 'GetAll[Entity]' for unfiltered list retrieval (e.g., 'GetAllOrders') or 'List[Entity]' consistently. If 'GetOrders' implies filtering, it should accept parameters or be named 'ListOrders'. Ensure 'GetAllUsers' and 'GetAllOrders' follow the same pattern. (signatures: UserManagementController.GetAllUsers() | OrderController.GetUserOrders())

D22 · Internal API Consistency · Inconsistent Verb Usage for Creation · ×1

Inconsistent Verb Usage for Creation: 'CreateUser' uses the standard 'Create' verb, while 'AddNewAdmin' uses 'AddNew'. 'AddNew' is redundant ('Add' implies creation) and inconsistent with the 'Create' pattern used elsewhere. This suggests a lack of standardized command naming conventions for resource creation. — Standardize creation commands to use the 'Create' verb (e.g., 'CreateAdmin' or 'CreateUser'). Remove 'AddNew' in favor of 'Create' or 'Add' consistently across the API. (signatures: UserController.CreateUser(UserCreateCommand model) | AdminManagerController.AddNewAdmin(AddAdminCommand model))

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

REDACTED

D30 · Dependency Vulnerabilities · Medium CVE · ×1

REDACTED

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

Duplicated block (41 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:121 — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:121-161 | src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:136-176 — before extracting anything, compare `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs` and `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.

D4 · Code Duplication · Duplicated block (32–35 lines × 2) · ×1

Duplicated block (32–35 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:46 — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:46-77 | src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:43-77 — before extracting anything, compare `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs` and `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:46` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:81` calls `CombineByteArrays`, `Parse`, `ToByteArray` and `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:80` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

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

Duplicated block (17 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:218 — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:218-234 | src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:223-239 — before extracting anything, compare `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs` and `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (7 lines × 2) src/API/CleanArc.WebFramework/Filters/BadRequestResultFilterAttribute.cs:19 — src/API/CleanArc.WebFramework/Filters/BadRequestResultFilterAttribute.cs:19-25 | src/API/CleanArc.WebFramework/Filters/ModelStateValidationAttribute.cs:43-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `ResultExecutingContext` in one and `ActionExecutingContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

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

Duplicated block (5 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:170 — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:170-174 | src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:185-189 — before extracting anything, compare `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs` and `src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D8 · Code Coverage · No test project references CleanArc.WebFramework · ×1

No test project references CleanArc.WebFramework src/API/CleanArc.WebFramework/CleanArc.WebFramework.csproj — No test project in this repository references CleanArc.WebFramework (20 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 15.4% 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 CleanArc.Web.Api · ×1

No test project references CleanArc.Web.Api REDACTED — No test project in this repository references CleanArc.Web.Api (7 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 15.4% 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 CleanArc.Infrastructure.Monitoring · ×1

No test project references CleanArc.Infrastructure.Monitoring REDACTED — No test project in this repository references CleanArc.Infrastructure.Monitoring (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 15.4% 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 CleanArc.Web.Plugins.Grpc · ×1

No test project references CleanArc.Web.Plugins.Grpc src/API/Plugins/CleanArc.Web.Plugins.Grpc/CleanArc.Web.Plugins.Grpc.csproj — No test project in this repository references CleanArc.Web.Plugins.Grpc (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 15.4% 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 CleanArc.Infrastructure.CrossCutting · ×1

No test project references CleanArc.Infrastructure.CrossCutting REDACTED — No test project in this repository references CleanArc.Infrastructure.CrossCutting (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 15.4% 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 · CRAP 72 · ×1

CRAP 72: RoleManagerService.ChangeRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:145 — Cyclomatic 8 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

D8 · Code Coverage · CRAP 56 · ×1

CRAP 56: ValidatorExtensions.RegisterValidatorsAsServices src/Shared/CleanArc.SharedKernel/Extensions/ValidatorExtensions.cs:10 — Cyclomatic 7 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

GD1 · Unfinished & placeholder code · Unfinished stub · ×1

Unfinished stub — throws NotImplementedException src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

IC1 · Incompleteness & stubs · Unfinished stub · ×1

Unfinished stub — throws NotImplementedException src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36 — `RemoveUserOldTokens` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.

P12 · CI test-gate honesty · Test suite runs only after the merge · ×1

Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.

P9 · Domain vs controller coverage · Low domain coverage · ×1

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

S1 · Web-Security Posture · Token validation disabled · ×1

Token validation disabled REDACTED:71 — `ValidateAudience`, `ValidateIssuer`, `ValidateLifetime` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.

X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×1

Symbol treated as nullable, then dereferenced unguarded src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:151 — This method contradicts itself about `claimsIdentity`: line 150 assigns it with `as ClaimsIdentity`, which hands back null rather than throwing when the value is not a `ClaimsIdentity`, but line 151 then dereferences it directly as `claimsIdentity.Claims` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `claimsIdentity` once before the first use and handle the null case, or cast with `(ClaimsIdentity)` so the failure is reported where it happens — rather than leaving the two readings side by side.

Minor — 72 finding(s)

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

Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:18 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:19 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:21 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:24 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:27 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:29 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.CrossCutting/Logging/LoggingConfiguration.cs:57 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:21 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:22 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:30 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:68 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:87 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:89 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:91 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:142 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:164 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:174 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:16 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:17 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:84 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).

D34 · Knowledge Freshness · Orphaned file · ×19

Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.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/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.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/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.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/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.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/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.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/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.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/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.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/API/CleanArc.Web.Api/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/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.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/API/CleanArc.WebFramework/Filters/ApiResultFilterAttribute.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/Infrastructure/CleanArc.Infrastructure.Persistence/ApplicationDbContext.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 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 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/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.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/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.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/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/KeyRing.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/Infrastructure/CleanArc.Infrastructure.CrossCutting/Logging/LoggingConfiguration.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/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.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.

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

Interpolated log message defeats structured logging src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:121 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Core/CleanArc.Application/Common/LoggingBehavior.cs:22 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:47 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs:24 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.

D12 · Dependency Hygiene · Outdated · ×3

Outdated: Mapster REDACTED:17 — Mapster 7.4.0 → 10.0.13 available (referenced by CleanArc.SharedKernel).
Outdated: Mapster.DependencyInjection REDACTED:18 — Mapster.DependencyInjection 1.0.1 → 10.0.13 available (referenced by CleanArc.SharedKernel).
Outdated: coverlet.collector REDACTED:13 — coverlet.collector 6.0.4 → 10.1.0 available (referenced by CleanArc.Tests.Setup).

D17 · Explicit Debt · ObsoleteWithoutCallers · ×2

ObsoleteWithoutCallers src/API/CleanArc.WebFramework/Filters/ApiResultFilterAttribute.cs:8 — [Obsolete] ApiResultFilterAttribute
ObsoleteWithoutCallers src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:85 — [Obsolete] RegisterEntityTypeConfiguration

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/API/CleanArc.Web.Api/Program.cs:24 — 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/API/CleanArc.Web.Api/Program.cs:24 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.

AX6 · Interface segregation · Fat interface · ×1

Fat interface: IAppUserManager (22 members) src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:6 — `IAppUserManager` declares 22 members: `CreateUser`, `CreateUser`, `IsExistUser`, `IsExistUserName`, `GeneratePhoneNumberConfirmationToken`, `GetUserByCode`, `ChangePhoneNumber`, `VerifyUserCode`, `GenerateOtpCode`, `GetUserByPhoneNumber`, `GetByUserName`, `GetUserByIdAsync`, `GetAllUsersAsync`, `CreateUserWithPasswordAsync`, `AddUserToRoleAsync`, `IncrementAccessFailedCountAsync`, `IsUserLockedOutAsync`, `ResetUserLockoutAsync`, `UpdateUserAsync`, `UpdateSecurityStampAsync`, `IsPasswordValidAsync`, `GetRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

C4 · Data Retention · Partial data-retention evidence · ×1

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

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D30 · Dependency Vulnerabilities · Low CVE · ×1

REDACTED

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

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 19 of 19 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 19 of the 159 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs, src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs, src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs, src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs, REDACTED (and 11 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D39 · IL Efficiency · IL efficiency · ×1

IL efficiency: 1 authored method(s) exceed the IL budget src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:15 — 1 of 457 first-party methods compile to oversized IL bodies (> 250 instructions); worst: CleanArc.WebFramework.Swagger.ApplySummariesOperationFilter.Process @ src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:15, 290 IL instructions; that pulled this dimension to 10.0/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.

M2 · Architecture documentation · No ADRs · ×1

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

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

README/code drift README.md:152 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.

P10 · Library API & versioning · No explicit versioning · ×1

No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.

P4 · Deployment & Rollback · No rollback/health safety · ×1

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

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

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

P6 · Release Hygiene · No changelog · ×1

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

PF1 · Benchmark discipline · No performance benchmarks · ×1

No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

S1 · Web-Security Posture · OIDC metadata fetched over HTTP · ×1

OIDC metadata fetched over HTTP src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:134 — `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path.

X10 · Duplicated predicate · Duplicated predicate · ×1

Duplicated predicate src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:223 — `a == null || b == null || a.Length != b.Length` appears character-identically in 2 files — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

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

Not all async methods take a CancellationToken — Only 22/72 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.

X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1

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

X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1

Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.1 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 6761 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 — 44 finding(s)

D12 · Dependency Hygiene · Outdated · ×32

Outdated: FluentValidation — FluentValidation 12.1.0 → 12.2.0 available (referenced by CleanArc.SharedKernel).
Outdated: Microsoft.AspNetCore.OpenApi — Microsoft.AspNetCore.OpenApi 10.0.0 → 10.0.13 available (referenced by CleanArc.SharedKernel).
Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 10.0.0 → 10.0.13 available (referenced by CleanArc.SharedKernel).
Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 10.0.0 → 10.0.13 available (referenced by CleanArc.SharedKernel).
Outdated: Microsoft.Extensions.Identity.Stores — Microsoft.Extensions.Identity.Stores 10.0.0 → 10.0.13 available (referenced by CleanArc.SharedKernel).
Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 10.0.0 → 10.0.13 available (referenced by CleanArc.Infrastructure.CrossCutting).
Outdated: Serilog.Sinks.MSSqlServer — Serilog.Sinks.MSSqlServer 9.0.2 → 10.0.0 available (referenced by CleanArc.Infrastructure.CrossCutting).
Outdated: Microsoft.AspNetCore.Authentication.JwtBearer — Microsoft.AspNetCore.Authentication.JwtBearer 10.0.0 → 10.0.13 available (referenced by CleanArc.Infrastructure.Identity).
Outdated: Microsoft.AspNetCore.Authorization — Microsoft.AspNetCore.Authorization 10.0.0 → 10.0.13 available (referenced by CleanArc.Infrastructure.Identity).
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 10.0.0 → 10.0.13 available (referenced by CleanArc.Infrastructure.Identity).
Outdated: Microsoft.Extensions.Identity.Core — Microsoft.Extensions.Identity.Core 10.0.0 → 10.0.13 available (referenced by CleanArc.Infrastructure.Identity).
Outdated: Microsoft.EntityFrameworkCore.Tools — Microsoft.EntityFrameworkCore.Tools 10.0.0 → 10.0.13 available (referenced by CleanArc.Infrastructure.Persistence).
Outdated: Mediator.Abstractions — Mediator.Abstractions 3.0.1 → 3.0.2 available (referenced by CleanArc.Application).
Outdated: Mediator.SourceGenerator — Mediator.SourceGenerator 3.0.1 → 3.0.2 available (referenced by CleanArc.Application).
Outdated: System.Linq.Async — System.Linq.Async 6.0.3 → 7.0.1 available (referenced by CleanArc.Application).
Outdated: Grpc.AspNetCore — Grpc.AspNetCore 2.71.0 → 2.84.0 available (referenced by CleanArc.Web.Plugins.Grpc).
Outdated: Grpc.AspNetCore.Server.Reflection — Grpc.AspNetCore.Server.Reflection 2.71.0 → 2.84.0 available (referenced by CleanArc.Web.Plugins.Grpc).
Outdated: Microsoft.EntityFrameworkCore.Design — Microsoft.EntityFrameworkCore.Design 10.0.0 → 10.0.13 available (referenced by CleanArc.Web.Api).
Outdated: Microsoft.Extensions.Logging.Debug — Microsoft.Extensions.Logging.Debug 10.0.0 → 10.0.13 available (referenced by CleanArc.Web.Api).
Outdated: Serilog.AspNetCore — Serilog.AspNetCore 9.0.0 → 10.0.0 available (referenced by CleanArc.Web.Api).
Outdated: Asp.Versioning.Http — Asp.Versioning.Http 8.1.0 → 10.2.3 available (referenced by CleanArc.WebFramework).
Outdated: Asp.Versioning.Mvc — Asp.Versioning.Mvc 8.1.0 → 10.2.1 available (referenced by CleanArc.WebFramework).
Outdated: Asp.Versioning.Mvc.ApiExplorer — Asp.Versioning.Mvc.ApiExplorer 8.1.0 → 10.2.1 available (referenced by CleanArc.WebFramework).
Outdated: NSwag.AspNetCore — NSwag.AspNetCore 14.6.2 → 14.7.1 available (referenced by CleanArc.WebFramework).
Outdated: NuGet.Packaging — REDACTED → 7.9.0 available (referenced by CleanArc.WebFramework).
+ 7 more in this group — see findings.md.

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

XML-doc coverage: CleanArc.SharedKernel src/Shared/CleanArc.SharedKernel/CleanArc.SharedKernel.csproj — CleanArc.SharedKernel: 11 % XML-doc coverage (7/62).
XML-doc coverage: CleanArc.Infrastructure.CrossCutting REDACTED — CleanArc.Infrastructure.CrossCutting: 0 % XML-doc coverage (0/2).
XML-doc coverage: CleanArc.Infrastructure.Identity src/Infrastructure/CleanArc.Infrastructure.Identity/CleanArc.Infrastructure.Identity.csproj — CleanArc.Infrastructure.Identity: 0 % XML-doc coverage (0/120).
XML-doc coverage: CleanArc.Infrastructure.Persistence REDACTED — CleanArc.Infrastructure.Persistence: 6 % XML-doc coverage (2/34).
XML-doc coverage: CleanArc.Application REDACTED — CleanArc.Application: 1 % XML-doc coverage (1/144).
XML-doc coverage: CleanArc.Domain src/Core/CleanArc.Domain/CleanArc.Domain.csproj — CleanArc.Domain: 0 % XML-doc coverage (0/57).
XML-doc coverage: CleanArc.Web.Plugins.Grpc src/API/Plugins/CleanArc.Web.Plugins.Grpc/CleanArc.Web.Plugins.Grpc.csproj — CleanArc.Web.Plugins.Grpc: 0 % XML-doc coverage (0/10).
XML-doc coverage: CleanArc.Web.Api REDACTED — CleanArc.Web.Api: 4 % XML-doc coverage (1/27).
XML-doc coverage: CleanArc.WebFramework src/API/CleanArc.WebFramework/CleanArc.WebFramework.csproj — CleanArc.WebFramework: 5 % XML-doc coverage (2/43).
XML-doc coverage: CleanArc.Infrastructure.Monitoring REDACTED — CleanArc.Infrastructure.Monitoring: 0 % XML-doc coverage (0/7).

D10 · Test Quality · Mock framework · ×1

Mock framework: NSubstitute — CleanArc.Tests.Setup references NSubstitute.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: CleanArc.SharedKernel src/Shared/CleanArc.SharedKernel/CleanArc.SharedKernel.csproj:1 — CleanArc.SharedKernel: abstractness 0.09, instability 0.00, distance 0.91 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8e6732aa132b41349646c1cfb1614272/history.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8e6732aa132b41349646c1cfb1614272/tree.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	19	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list CleanArcTemplate.sln package --vulnerable --include-transitive --format json	8	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	7	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 24 file(s) — `REDACTED`, `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs`, `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs`, `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs`, `src/Core/CleanArc.Application/Common/LoggingBehavior.cs`, … (+19 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	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 Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	none (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 01a161b1-30b3-7da1-b677-5a32eddf3f7f · 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 — 7 field(s) across 3 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Email — 3 field(s)

BaseController.UserEmail src/API/CleanArc.WebFramework/BaseController/BaseController.cs:13
AddAdminCommand.Email src/Core/CleanArc.Application/Features/Admin/Commands/AddAdminCommand/AddAdminCommand.cs:10
GetUsersQueryResponse.Email src/Core/CleanArc.Application/Features/Users/Queries/GetUsers/GetUsersQuery.Response.cs:9

Name — 2 field(s)

UserCreateCommand.FamilyName src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.cs:12
User.FamilyName src/Core/CleanArc.Domain/Entities/User/User.cs:14

Phone — 2 field(s)

UserCreateCommand.PhoneNumber src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.cs:12
UserTokenRequestQuery.UserPhoneNumber src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.cs:10

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — bounded-context dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 53% · Adequate · gated by X4, X5 ·

At a glance — Architecture · 83% · Exemplary ·

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

At a glance — Readiness · 47% · Adequate · gated by D8, D13, P9 ·

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

At a glance — Performance · 64% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts