Executive summary
omid-ahmadpour/CleanArchitecture-Template falls short of our standard for a template or a sample because it has pieces of business logic tied to the database or web code. It scores 38 out of 100 and is rated Adequate, and 19 of its 32 critical findings are security problems.
Domain Modelling, at 18, is the weakest lens and counts most in the score. The best first step is moving database and web code out of the business core, worth about 18 points. Hashing passwords properly comes next, worth about 7 points. Raising Domain Modelling to 58 would lift the score to about 52.
Six passwords or keys in the code and six in the code's history are open to anyone who can read the repository. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one setting leaves the servers or containers unsafe. Replacing each exposed password or key, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the place where passwords are scrambled with a fast general-purpose hash. The two data fields that are written but never read need removing.
The product code is 2,954 lines, about €4,600 to rebuild.
If Domain Modelling rose from 18 to 58, the lowest score rated Strong, the score would rise from 38 to about 52.
New since the last survey: 11 findings
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: RefreshToken src/Core/Domain/Entities/Users/RefreshToken.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Role src/Core/Domain/Entities/Users/Role.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: User src/Core/Domain/Entities/Users/User.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IReanOnlyRepository src/Core/Domain/IRepositories/IReanOnlyRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IRepository src/Core/Domain/IRepositories/IRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: CleanTemplate.Domain src/Core/Domain/CleanTemplate.Domain.csproj
Fixed since the last survey: 2 findings
- Dependency Hygiene · Vulnerable: System.Security.Cryptography.Xml
- Cancellation propagation · Async method without CancellationToken: GenerateAsync src/Infrastructure/Persistance/Jwt/JwtService.cs
Rebuild cost: about €4,600 · Estimate
| Cost to rebuild | €1,600 to €7,700, for 26 to 81 hours of work, under 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 38. 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: 2,954 lines of product code, of which 46% is declarations and boilerplate, 42% straight logic and 12% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 CleanTemplate.Api.Controllers.v1.Products.Requests | 3 CleanTemplate.Api.Controllers.v1.Products.Validators | 4 CleanTemplate.Api.Controllers.v1.Users.Validators | 5 CleanTemplate.Api.Filters | 6 CleanTemplate.ApiFramework.Attributes | 7 CleanTemplate.ApiFramework.Configuration | 8 CleanTemplate.ApiFramework.Swagger | 9 CleanTemplate.ApiFramework.Tools | 10 CleanTemplate.Application | 11 CleanTemplate.Common | 12 CleanTemplate.Common.General | 13 CleanTemplate.Common.Utilities | 14 CleanTemplate.Dispatching | 15 CleanTemplate.Domain.Entities | 16 CleanTemplate.Persistence.Db | 17 CleanTemplate.Api | 18 CleanTemplate.Api.Controllers.v1 | 19 CleanTemplate.Application.Products.Command.AddProduct | 20 CleanTemplate.Application.Products.Query.GetProductById | 21 CleanTemplate.Application.Products.Query.GetProducts | 22 CleanTemplate.Application.Products.Query.ReadProductFromRedis | 23 CleanTemplate.Application.Users.Command.Login | 24 CleanTemplate.Application.Users.Command.RefreshToken | 25 CleanTemplate.Common.Behaviours | 26 CleanTemplate.Domain.Entities.Products | 27 CleanTemplate.Domain.Entities.Users | 28 CleanTemplate.Persistence | 29 CleanTemplate.Api.Controllers.v1.Products | 30 CleanTemplate.Api.Controllers.v1.Users.Requests | 31 CleanTemplate.Application.Users.Command.CreateUser | 32 CleanTemplate.Domain.IRepositories | 33 CleanTemplate.Persistence.CommandHandlers.Products | 34 CleanTemplate.Persistence.Configuration.Products | 35 CleanTemplate.Persistence.Configuration.Users | 36 CleanTemplate.Persistence.Jwt | 37 CleanTemplate.Persistence.QueryHandlers.Products | 38 CleanTemplate.Api.Controllers.v1.Users | 39 CleanTemplate.Persistence.CommandHandlers.Users | 40 CleanTemplate.Persistence.Repositories |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanTemplate.Api.Controllers.v1.Products.Requests | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanTemplate.Api.Controllers.v1.Products.Validators | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanTemplate.Api.Controllers.v1.Users.Validators | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanTemplate.Api.Filters | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanTemplate.ApiFramework.Attributes | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanTemplate.ApiFramework.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanTemplate.ApiFramework.Swagger | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanTemplate.ApiFramework.Tools | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanTemplate.Application | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanTemplate.Common | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanTemplate.Common.General | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanTemplate.Common.Utilities | ||||||||||||||||||||||||||||||||||||||||
| 14 CleanTemplate.Dispatching | ||||||||||||||||||||||||||||||||||||||||
| 15 CleanTemplate.Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 16 CleanTemplate.Persistence.Db | ||||||||||||||||||||||||||||||||||||||||
| 17 CleanTemplate.Api | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 CleanTemplate.Api.Controllers.v1 | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 CleanTemplate.Application.Products.Command.AddProduct | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 CleanTemplate.Application.Products.Query.GetProductById | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 CleanTemplate.Application.Products.Query.GetProducts | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 CleanTemplate.Application.Products.Query.ReadProductFromRedis | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 CleanTemplate.Application.Users.Command.Login | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 CleanTemplate.Application.Users.Command.RefreshToken | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 CleanTemplate.Common.Behaviours | 6 | |||||||||||||||||||||||||||||||||||||||
| 26 CleanTemplate.Domain.Entities.Products | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 CleanTemplate.Domain.Entities.Users | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 CleanTemplate.Persistence | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 CleanTemplate.Api.Controllers.v1.Products | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 CleanTemplate.Api.Controllers.v1.Users.Requests | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 CleanTemplate.Application.Users.Command.CreateUser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 CleanTemplate.Domain.IRepositories | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 CleanTemplate.Persistence.CommandHandlers.Products | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 CleanTemplate.Persistence.Configuration.Products | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 CleanTemplate.Persistence.Configuration.Users | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 CleanTemplate.Persistence.Jwt | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 CleanTemplate.Persistence.QueryHandlers.Products | 1 | 3 | 3 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 38 CleanTemplate.Api.Controllers.v1.Users | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 39 CleanTemplate.Persistence.CommandHandlers.Users | 3 | 2 | 2 | 4 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 40 CleanTemplate.Persistence.Repositories | 2 | 4 | 2 | 4 |
17→12 CleanTemplate.Api uses CleanTemplate.Common.General✕
- Connections
- 3 pairs of types, where a type in CleanTemplate.Api uses a type in CleanTemplate.Common.General.
- The types involved
CleanTemplate.Api.DependencyInjection→CleanTemplate.Common.General.IdentitySettingsCleanTemplate.Api.DependencyInjection→CleanTemplate.Common.General.JwtSettingsCleanTemplate.Api.DependencyInjection→CleanTemplate.Common.General.SiteSettings
- Direction
- CleanTemplate.Api uses CleanTemplate.Common.General, so a change to CleanTemplate.Common.General can break CleanTemplate.Api, while a change to CleanTemplate.Api can't break CleanTemplate.Common.General.
- Position
- Below the diagonal: CleanTemplate.Api uses a module listed above it, which is the healthy direction.
18→14 CleanTemplate.Api.Controllers.v1 uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1 uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Api.Controllers.v1.BaseControllerV1→CleanTemplate.Dispatching.IDispatcher
- Direction
- CleanTemplate.Api.Controllers.v1 uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Api.Controllers.v1, while a change to CleanTemplate.Api.Controllers.v1 can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1 uses a module listed above it, which is the healthy direction.
19→14 CleanTemplate.Application.Products.Command.AddProduct uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Products.Command.AddProduct uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Products.Command.AddProduct.AddProductCommand→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Products.Command.AddProduct uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Products.Command.AddProduct, while a change to CleanTemplate.Application.Products.Command.AddProduct can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Products.Command.AddProduct uses a module listed above it, which is the healthy direction.
20→14 CleanTemplate.Application.Products.Query.GetProductById uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Products.Query.GetProductById uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Products.Query.GetProductById.GetProductByIdQuery→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Products.Query.GetProductById uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Products.Query.GetProductById, while a change to CleanTemplate.Application.Products.Query.GetProductById can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Products.Query.GetProductById uses a module listed above it, which is the healthy direction.
21→14 CleanTemplate.Application.Products.Query.GetProducts uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Products.Query.GetProducts uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Products.Query.GetProducts.GetProductsQuery→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Products.Query.GetProducts uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Products.Query.GetProducts, while a change to CleanTemplate.Application.Products.Query.GetProducts can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Products.Query.GetProducts uses a module listed above it, which is the healthy direction.
22→14 CleanTemplate.Application.Products.Query.ReadProductFromRedis uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Products.Query.ReadProductFromRedis uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Products.Query.ReadProductFromRedis.ReadProductFromRedisQuery→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Products.Query.ReadProductFromRedis uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Products.Query.ReadProductFromRedis, while a change to CleanTemplate.Application.Products.Query.ReadProductFromRedis can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Products.Query.ReadProductFromRedis uses a module listed above it, which is the healthy direction.
23→14 CleanTemplate.Application.Users.Command.Login uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Users.Command.Login uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Users.Command.Login.LoginCommand→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Users.Command.Login uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Users.Command.Login, while a change to CleanTemplate.Application.Users.Command.Login can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Users.Command.Login uses a module listed above it, which is the healthy direction.
24→14 CleanTemplate.Application.Users.Command.RefreshToken uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Users.Command.RefreshToken uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Users.Command.RefreshToken.RefreshTokenCommand→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Users.Command.RefreshToken uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Users.Command.RefreshToken, while a change to CleanTemplate.Application.Users.Command.RefreshToken can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Users.Command.RefreshToken uses a module listed above it, which is the healthy direction.
25→14 CleanTemplate.Common.Behaviours uses CleanTemplate.Dispatching✕
- Connections
- 6 pairs of types, where a type in CleanTemplate.Common.Behaviours uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Common.Behaviours.PerformanceBehaviour→CleanTemplate.Dispatching.IRequestPipelineBehaviorCleanTemplate.Common.Behaviours.PerformanceBehaviour→CleanTemplate.Dispatching.RequestHandlerDelegateCleanTemplate.Common.Behaviours.UnhandledExceptionBehaviour→CleanTemplate.Dispatching.IRequestPipelineBehaviorCleanTemplate.Common.Behaviours.UnhandledExceptionBehaviour→CleanTemplate.Dispatching.RequestHandlerDelegateCleanTemplate.Common.Behaviours.ValidationBehavior→CleanTemplate.Dispatching.IRequestPipelineBehaviorCleanTemplate.Common.Behaviours.ValidationBehavior→CleanTemplate.Dispatching.RequestHandlerDelegate
- Direction
- CleanTemplate.Common.Behaviours uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Common.Behaviours, while a change to CleanTemplate.Common.Behaviours can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Common.Behaviours uses a module listed above it, which is the healthy direction.
26→15 CleanTemplate.Domain.Entities.Products uses CleanTemplate.Domain.Entities✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Domain.Entities.Products uses a type in CleanTemplate.Domain.Entities.
- The types involved
CleanTemplate.Domain.Entities.Products.Product→CleanTemplate.Domain.Entities.IEntity
- Direction
- CleanTemplate.Domain.Entities.Products uses CleanTemplate.Domain.Entities, so a change to CleanTemplate.Domain.Entities can break CleanTemplate.Domain.Entities.Products, while a change to CleanTemplate.Domain.Entities.Products can't break CleanTemplate.Domain.Entities.
- Position
- Below the diagonal: CleanTemplate.Domain.Entities.Products uses a module listed above it, which is the healthy direction.
27→15 CleanTemplate.Domain.Entities.Users uses CleanTemplate.Domain.Entities✕
- Connections
- 3 pairs of types, where a type in CleanTemplate.Domain.Entities.Users uses a type in CleanTemplate.Domain.Entities.
- The types involved
CleanTemplate.Domain.Entities.Users.RefreshToken→CleanTemplate.Domain.Entities.IEntityCleanTemplate.Domain.Entities.Users.Role→CleanTemplate.Domain.Entities.IEntityCleanTemplate.Domain.Entities.Users.User→CleanTemplate.Domain.Entities.IEntity
- Direction
- CleanTemplate.Domain.Entities.Users uses CleanTemplate.Domain.Entities, so a change to CleanTemplate.Domain.Entities can break CleanTemplate.Domain.Entities.Users, while a change to CleanTemplate.Domain.Entities.Users can't break CleanTemplate.Domain.Entities.
- Position
- Below the diagonal: CleanTemplate.Domain.Entities.Users uses a module listed above it, which is the healthy direction.
28→16 CleanTemplate.Persistence uses CleanTemplate.Persistence.Db✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence uses a type in CleanTemplate.Persistence.Db.
- The types involved
CleanTemplate.Persistence.AppDbContextFactory→CleanTemplate.Persistence.Db.AppDbContext
- Direction
- CleanTemplate.Persistence uses CleanTemplate.Persistence.Db, so a change to CleanTemplate.Persistence.Db can break CleanTemplate.Persistence, while a change to CleanTemplate.Persistence can't break CleanTemplate.Persistence.Db.
- Position
- Below the diagonal: CleanTemplate.Persistence uses a module listed above it, which is the healthy direction.
29→2 CleanTemplate.Api.Controllers.v1.Products uses CleanTemplate.Api.Controllers.v1.Products.Requests✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Api.Controllers.v1.Products uses a type in CleanTemplate.Api.Controllers.v1.Products.Requests.
- The types involved
CleanTemplate.Api.Controllers.v1.Products.ProductController→CleanTemplate.Api.Controllers.v1.Products.Requests.AddProductRequestCleanTemplate.Api.Controllers.v1.Products.ProductController→CleanTemplate.Api.Controllers.v1.Products.Requests.GetProductsRequest
- Direction
- CleanTemplate.Api.Controllers.v1.Products uses CleanTemplate.Api.Controllers.v1.Products.Requests, so a change to CleanTemplate.Api.Controllers.v1.Products.Requests can break CleanTemplate.Api.Controllers.v1.Products, while a change to CleanTemplate.Api.Controllers.v1.Products can't break CleanTemplate.Api.Controllers.v1.Products.Requests.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Products uses a module listed above it, which is the healthy direction.
29→18 CleanTemplate.Api.Controllers.v1.Products uses CleanTemplate.Api.Controllers.v1✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1.Products uses a type in CleanTemplate.Api.Controllers.v1.
- The types involved
CleanTemplate.Api.Controllers.v1.Products.ProductController→CleanTemplate.Api.Controllers.v1.BaseControllerV1
- Direction
- CleanTemplate.Api.Controllers.v1.Products uses CleanTemplate.Api.Controllers.v1, so a change to CleanTemplate.Api.Controllers.v1 can break CleanTemplate.Api.Controllers.v1.Products, while a change to CleanTemplate.Api.Controllers.v1.Products can't break CleanTemplate.Api.Controllers.v1.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Products uses a module listed above it, which is the healthy direction.
30→27 CleanTemplate.Api.Controllers.v1.Users.Requests uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1.Users.Requests uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Api.Controllers.v1.Users.Requests.SingUpRequest→CleanTemplate.Domain.Entities.Users.GenderType
- Direction
- CleanTemplate.Api.Controllers.v1.Users.Requests uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Api.Controllers.v1.Users.Requests, while a change to CleanTemplate.Api.Controllers.v1.Users.Requests can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Users.Requests uses a module listed above it, which is the healthy direction.
31→14 CleanTemplate.Application.Users.Command.CreateUser uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Users.Command.CreateUser uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Application.Users.Command.CreateUser.CreateUserCommand→CleanTemplate.Dispatching.IRequest
- Direction
- CleanTemplate.Application.Users.Command.CreateUser uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Application.Users.Command.CreateUser, while a change to CleanTemplate.Application.Users.Command.CreateUser can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Application.Users.Command.CreateUser uses a module listed above it, which is the healthy direction.
31→27 CleanTemplate.Application.Users.Command.CreateUser uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Application.Users.Command.CreateUser uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Application.Users.Command.CreateUser.CreateUserCommand→CleanTemplate.Domain.Entities.Users.GenderType
- Direction
- CleanTemplate.Application.Users.Command.CreateUser uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Application.Users.Command.CreateUser, while a change to CleanTemplate.Application.Users.Command.CreateUser can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Application.Users.Command.CreateUser uses a module listed above it, which is the healthy direction.
32→27 CleanTemplate.Domain.IRepositories uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Domain.IRepositories uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Domain.IRepositories.IRefreshTokenRepository→CleanTemplate.Domain.Entities.Users.RefreshTokenCleanTemplate.Domain.IRepositories.IUserRepository→CleanTemplate.Domain.Entities.Users.User
- Direction
- CleanTemplate.Domain.IRepositories uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Domain.IRepositories, while a change to CleanTemplate.Domain.IRepositories can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Domain.IRepositories uses a module listed above it, which is the healthy direction.
33→14 CleanTemplate.Persistence.CommandHandlers.Products uses CleanTemplate.Dispatching✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.CommandHandlers.Products uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Products.AddProductCommandHandler→CleanTemplate.Dispatching.IRequestHandler
- Direction
- CleanTemplate.Persistence.CommandHandlers.Products uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Persistence.CommandHandlers.Products, while a change to CleanTemplate.Persistence.CommandHandlers.Products can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Products uses a module listed above it, which is the healthy direction.
33→16 CleanTemplate.Persistence.CommandHandlers.Products uses CleanTemplate.Persistence.Db✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.CommandHandlers.Products uses a type in CleanTemplate.Persistence.Db.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Products.AddProductCommandHandler→CleanTemplate.Persistence.Db.CleanArchWriteDbContext
- Direction
- CleanTemplate.Persistence.CommandHandlers.Products uses CleanTemplate.Persistence.Db, so a change to CleanTemplate.Persistence.Db can break CleanTemplate.Persistence.CommandHandlers.Products, while a change to CleanTemplate.Persistence.CommandHandlers.Products can't break CleanTemplate.Persistence.Db.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Products uses a module listed above it, which is the healthy direction.
33→19 CleanTemplate.Persistence.CommandHandlers.Products uses CleanTemplate.Application.Products.Command.AddProduct✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.CommandHandlers.Products uses a type in CleanTemplate.Application.Products.Command.AddProduct.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Products.AddProductCommandHandler→CleanTemplate.Application.Products.Command.AddProduct.AddProductCommand
- Direction
- CleanTemplate.Persistence.CommandHandlers.Products uses CleanTemplate.Application.Products.Command.AddProduct, so a change to CleanTemplate.Application.Products.Command.AddProduct can break CleanTemplate.Persistence.CommandHandlers.Products, while a change to CleanTemplate.Persistence.CommandHandlers.Products can't break CleanTemplate.Application.Products.Command.AddProduct.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Products uses a module listed above it, which is the healthy direction.
34→26 CleanTemplate.Persistence.Configuration.Products uses CleanTemplate.Domain.Entities.Products✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.Configuration.Products uses a type in CleanTemplate.Domain.Entities.Products.
- The types involved
CleanTemplate.Persistence.Configuration.Products.ProductConfiguration→CleanTemplate.Domain.Entities.Products.Product
- Direction
- CleanTemplate.Persistence.Configuration.Products uses CleanTemplate.Domain.Entities.Products, so a change to CleanTemplate.Domain.Entities.Products can break CleanTemplate.Persistence.Configuration.Products, while a change to CleanTemplate.Persistence.Configuration.Products can't break CleanTemplate.Domain.Entities.Products.
- Position
- Below the diagonal: CleanTemplate.Persistence.Configuration.Products uses a module listed above it, which is the healthy direction.
35→27 CleanTemplate.Persistence.Configuration.Users uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.Configuration.Users uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Persistence.Configuration.Users.RoleConfiguration→CleanTemplate.Domain.Entities.Users.RoleCleanTemplate.Persistence.Configuration.Users.UserConfiguration→CleanTemplate.Domain.Entities.Users.User
- Direction
- CleanTemplate.Persistence.Configuration.Users uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Persistence.Configuration.Users, while a change to CleanTemplate.Persistence.Configuration.Users can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Persistence.Configuration.Users uses a module listed above it, which is the healthy direction.
36→11 CleanTemplate.Persistence.Jwt uses CleanTemplate.Common✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.Jwt uses a type in CleanTemplate.Common.
- The types involved
CleanTemplate.Persistence.Jwt.JwtService→CleanTemplate.Common.IScopedDependency
- Direction
- CleanTemplate.Persistence.Jwt uses CleanTemplate.Common, so a change to CleanTemplate.Common can break CleanTemplate.Persistence.Jwt, while a change to CleanTemplate.Persistence.Jwt can't break CleanTemplate.Common.
- Position
- Below the diagonal: CleanTemplate.Persistence.Jwt uses a module listed above it, which is the healthy direction.
36→12 CleanTemplate.Persistence.Jwt uses CleanTemplate.Common.General✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.Jwt uses a type in CleanTemplate.Common.General.
- The types involved
CleanTemplate.Persistence.Jwt.JwtService→CleanTemplate.Common.General.SiteSettings
- Direction
- CleanTemplate.Persistence.Jwt uses CleanTemplate.Common.General, so a change to CleanTemplate.Common.General can break CleanTemplate.Persistence.Jwt, while a change to CleanTemplate.Persistence.Jwt can't break CleanTemplate.Common.General.
- Position
- Below the diagonal: CleanTemplate.Persistence.Jwt uses a module listed above it, which is the healthy direction.
36→27 CleanTemplate.Persistence.Jwt uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.Jwt uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Persistence.Jwt.IJwtService→CleanTemplate.Domain.Entities.Users.UserCleanTemplate.Persistence.Jwt.JwtService→CleanTemplate.Domain.Entities.Users.User
- Direction
- CleanTemplate.Persistence.Jwt uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Persistence.Jwt, while a change to CleanTemplate.Persistence.Jwt can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Persistence.Jwt uses a module listed above it, which is the healthy direction.
37→13 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Common.Utilities✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Common.Utilities.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.GetProductsQueryHandler→CleanTemplate.Common.Utilities.PagedResult
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Common.Utilities, so a change to CleanTemplate.Common.Utilities can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Common.Utilities.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
37→14 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Dispatching✕
- Connections
- 3 pairs of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.GetProductByIdQueryHandler→CleanTemplate.Dispatching.IRequestHandlerCleanTemplate.Persistence.QueryHandlers.Products.GetProductsQueryHandler→CleanTemplate.Dispatching.IRequestHandlerCleanTemplate.Persistence.QueryHandlers.Products.ReadProductFromRedisQueryHandler→CleanTemplate.Dispatching.IRequestHandler
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
37→16 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Persistence.Db✕
- Connections
- 3 pairs of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Persistence.Db.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.GetProductByIdQueryHandler→CleanTemplate.Persistence.Db.CleanArchReadOnlyDbContextCleanTemplate.Persistence.QueryHandlers.Products.GetProductsQueryHandler→CleanTemplate.Persistence.Db.CleanArchReadOnlyDbContextCleanTemplate.Persistence.QueryHandlers.Products.ReadProductFromRedisQueryHandler→CleanTemplate.Persistence.Db.CleanArchReadOnlyDbContext
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Persistence.Db, so a change to CleanTemplate.Persistence.Db can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Persistence.Db.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
37→20 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Application.Products.Query.GetProductById✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Application.Products.Query.GetProductById.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.GetProductByIdQueryHandler→CleanTemplate.Application.Products.Query.GetProductById.GetProductByIdQueryCleanTemplate.Persistence.QueryHandlers.Products.GetProductByIdQueryHandler→CleanTemplate.Application.Products.Query.GetProductById.ProductQueryModel
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Application.Products.Query.GetProductById, so a change to CleanTemplate.Application.Products.Query.GetProductById can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Application.Products.Query.GetProductById.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
37→21 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Application.Products.Query.GetProducts✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Application.Products.Query.GetProducts.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.GetProductsQueryHandler→CleanTemplate.Application.Products.Query.GetProducts.GetProductsQuery
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Application.Products.Query.GetProducts, so a change to CleanTemplate.Application.Products.Query.GetProducts can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Application.Products.Query.GetProducts.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
37→22 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Application.Products.Query.ReadProductFromRedis✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Application.Products.Query.ReadProductFromRedis.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.ReadProductFromRedisQueryHandler→CleanTemplate.Application.Products.Query.ReadProductFromRedis.ReadProductFromRedisQueryCleanTemplate.Persistence.QueryHandlers.Products.ReadProductFromRedisQueryHandler→CleanTemplate.Application.Products.Query.ReadProductFromRedis.ReadProductFromRedisResponse
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Application.Products.Query.ReadProductFromRedis, so a change to CleanTemplate.Application.Products.Query.ReadProductFromRedis can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Application.Products.Query.ReadProductFromRedis.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
37→26 CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Domain.Entities.Products✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.QueryHandlers.Products uses a type in CleanTemplate.Domain.Entities.Products.
- The types involved
CleanTemplate.Persistence.QueryHandlers.Products.GetProductsQueryHandler→CleanTemplate.Domain.Entities.Products.Product
- Direction
- CleanTemplate.Persistence.QueryHandlers.Products uses CleanTemplate.Domain.Entities.Products, so a change to CleanTemplate.Domain.Entities.Products can break CleanTemplate.Persistence.QueryHandlers.Products, while a change to CleanTemplate.Persistence.QueryHandlers.Products can't break CleanTemplate.Domain.Entities.Products.
- Position
- Below the diagonal: CleanTemplate.Persistence.QueryHandlers.Products uses a module listed above it, which is the healthy direction.
38→9 CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.ApiFramework.Tools✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1.Users uses a type in CleanTemplate.ApiFramework.Tools.
- The types involved
CleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.ApiFramework.Tools.ApiResult
- Direction
- CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.ApiFramework.Tools, so a change to CleanTemplate.ApiFramework.Tools can break CleanTemplate.Api.Controllers.v1.Users, while a change to CleanTemplate.Api.Controllers.v1.Users can't break CleanTemplate.ApiFramework.Tools.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Users uses a module listed above it, which is the healthy direction.
38→18 CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Api.Controllers.v1✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1.Users uses a type in CleanTemplate.Api.Controllers.v1.
- The types involved
CleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.Api.Controllers.v1.BaseControllerV1
- Direction
- CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Api.Controllers.v1, so a change to CleanTemplate.Api.Controllers.v1 can break CleanTemplate.Api.Controllers.v1.Users, while a change to CleanTemplate.Api.Controllers.v1.Users can't break CleanTemplate.Api.Controllers.v1.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Users uses a module listed above it, which is the healthy direction.
38→23 CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Application.Users.Command.Login✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1.Users uses a type in CleanTemplate.Application.Users.Command.Login.
- The types involved
CleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.Application.Users.Command.Login.LoginResponse
- Direction
- CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Application.Users.Command.Login, so a change to CleanTemplate.Application.Users.Command.Login can break CleanTemplate.Api.Controllers.v1.Users, while a change to CleanTemplate.Api.Controllers.v1.Users can't break CleanTemplate.Application.Users.Command.Login.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Users uses a module listed above it, which is the healthy direction.
38→24 CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Application.Users.Command.RefreshToken✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Api.Controllers.v1.Users uses a type in CleanTemplate.Application.Users.Command.RefreshToken.
- The types involved
CleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.Application.Users.Command.RefreshToken.RefreshTokenResponse
- Direction
- CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Application.Users.Command.RefreshToken, so a change to CleanTemplate.Application.Users.Command.RefreshToken can break CleanTemplate.Api.Controllers.v1.Users, while a change to CleanTemplate.Api.Controllers.v1.Users can't break CleanTemplate.Application.Users.Command.RefreshToken.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Users uses a module listed above it, which is the healthy direction.
38→30 CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Api.Controllers.v1.Users.Requests✕
- Connections
- 3 pairs of types, where a type in CleanTemplate.Api.Controllers.v1.Users uses a type in CleanTemplate.Api.Controllers.v1.Users.Requests.
- The types involved
CleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.Api.Controllers.v1.Users.Requests.LoginRequestCleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.Api.Controllers.v1.Users.Requests.RefreshTokenRequestCleanTemplate.Api.Controllers.v1.Users.UserController→CleanTemplate.Api.Controllers.v1.Users.Requests.SingUpRequest
- Direction
- CleanTemplate.Api.Controllers.v1.Users uses CleanTemplate.Api.Controllers.v1.Users.Requests, so a change to CleanTemplate.Api.Controllers.v1.Users.Requests can break CleanTemplate.Api.Controllers.v1.Users, while a change to CleanTemplate.Api.Controllers.v1.Users can't break CleanTemplate.Api.Controllers.v1.Users.Requests.
- Position
- Below the diagonal: CleanTemplate.Api.Controllers.v1.Users uses a module listed above it, which is the healthy direction.
39→14 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Dispatching✕
- Connections
- 3 pairs of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Dispatching.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.CreateUserCommandHandler→CleanTemplate.Dispatching.IRequestHandlerCleanTemplate.Persistence.CommandHandlers.Users.LoginCommandHandler→CleanTemplate.Dispatching.IRequestHandlerCleanTemplate.Persistence.CommandHandlers.Users.RefreshTokenCommandHandler→CleanTemplate.Dispatching.IRequestHandler
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Dispatching, so a change to CleanTemplate.Dispatching can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Dispatching.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
39→23 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Application.Users.Command.Login✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Application.Users.Command.Login.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.LoginCommandHandler→CleanTemplate.Application.Users.Command.Login.LoginCommandCleanTemplate.Persistence.CommandHandlers.Users.LoginCommandHandler→CleanTemplate.Application.Users.Command.Login.LoginResponse
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Application.Users.Command.Login, so a change to CleanTemplate.Application.Users.Command.Login can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Application.Users.Command.Login.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
39→24 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Application.Users.Command.RefreshToken✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Application.Users.Command.RefreshToken.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.RefreshTokenCommandHandler→CleanTemplate.Application.Users.Command.RefreshToken.RefreshTokenCommandCleanTemplate.Persistence.CommandHandlers.Users.RefreshTokenCommandHandler→CleanTemplate.Application.Users.Command.RefreshToken.RefreshTokenResponse
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Application.Users.Command.RefreshToken, so a change to CleanTemplate.Application.Users.Command.RefreshToken can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Application.Users.Command.RefreshToken.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
39→27 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 4 pairs of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.CreateUserCommandHandler→CleanTemplate.Domain.Entities.Users.RoleCleanTemplate.Persistence.CommandHandlers.Users.CreateUserCommandHandler→CleanTemplate.Domain.Entities.Users.UserCleanTemplate.Persistence.CommandHandlers.Users.LoginCommandHandler→CleanTemplate.Domain.Entities.Users.UserCleanTemplate.Persistence.CommandHandlers.Users.RefreshTokenCommandHandler→CleanTemplate.Domain.Entities.Users.User
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
39→31 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Application.Users.Command.CreateUser✕
- Connections
- 1 pair of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Application.Users.Command.CreateUser.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.CreateUserCommandHandler→CleanTemplate.Application.Users.Command.CreateUser.CreateUserCommand
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Application.Users.Command.CreateUser, so a change to CleanTemplate.Application.Users.Command.CreateUser can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Application.Users.Command.CreateUser.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
39→32 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Domain.IRepositories✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Domain.IRepositories.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.LoginCommandHandler→CleanTemplate.Domain.IRepositories.IRefreshTokenRepositoryCleanTemplate.Persistence.CommandHandlers.Users.RefreshTokenCommandHandler→CleanTemplate.Domain.IRepositories.IRefreshTokenRepository
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Domain.IRepositories, so a change to CleanTemplate.Domain.IRepositories can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Domain.IRepositories.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
39→36 CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Persistence.Jwt✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.CommandHandlers.Users uses a type in CleanTemplate.Persistence.Jwt.
- The types involved
CleanTemplate.Persistence.CommandHandlers.Users.LoginCommandHandler→CleanTemplate.Persistence.Jwt.IJwtServiceCleanTemplate.Persistence.CommandHandlers.Users.RefreshTokenCommandHandler→CleanTemplate.Persistence.Jwt.IJwtService
- Direction
- CleanTemplate.Persistence.CommandHandlers.Users uses CleanTemplate.Persistence.Jwt, so a change to CleanTemplate.Persistence.Jwt can break CleanTemplate.Persistence.CommandHandlers.Users, while a change to CleanTemplate.Persistence.CommandHandlers.Users can't break CleanTemplate.Persistence.Jwt.
- Position
- Below the diagonal: CleanTemplate.Persistence.CommandHandlers.Users uses a module listed above it, which is the healthy direction.
40→11 CleanTemplate.Persistence.Repositories uses CleanTemplate.Common✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.Repositories uses a type in CleanTemplate.Common.
- The types involved
CleanTemplate.Persistence.Repositories.RefreshTokenRepository→CleanTemplate.Common.IScopedDependencyCleanTemplate.Persistence.Repositories.UserRepository→CleanTemplate.Common.IScopedDependency
- Direction
- CleanTemplate.Persistence.Repositories uses CleanTemplate.Common, so a change to CleanTemplate.Common can break CleanTemplate.Persistence.Repositories, while a change to CleanTemplate.Persistence.Repositories can't break CleanTemplate.Common.
- Position
- Below the diagonal: CleanTemplate.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→16 CleanTemplate.Persistence.Repositories uses CleanTemplate.Persistence.Db✕
- Connections
- 4 pairs of types, where a type in CleanTemplate.Persistence.Repositories uses a type in CleanTemplate.Persistence.Db.
- The types involved
CleanTemplate.Persistence.Repositories.EfReadOnlyRepository→CleanTemplate.Persistence.Db.CleanArchReadOnlyDbContextCleanTemplate.Persistence.Repositories.RefreshTokenRepository→CleanTemplate.Persistence.Db.CleanArchWriteDbContextCleanTemplate.Persistence.Repositories.Repository→CleanTemplate.Persistence.Db.CleanArchWriteDbContextCleanTemplate.Persistence.Repositories.UserRepository→CleanTemplate.Persistence.Db.CleanArchWriteDbContext
- Direction
- CleanTemplate.Persistence.Repositories uses CleanTemplate.Persistence.Db, so a change to CleanTemplate.Persistence.Db can break CleanTemplate.Persistence.Repositories, while a change to CleanTemplate.Persistence.Repositories can't break CleanTemplate.Persistence.Db.
- Position
- Below the diagonal: CleanTemplate.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→27 CleanTemplate.Persistence.Repositories uses CleanTemplate.Domain.Entities.Users✕
- Connections
- 2 pairs of types, where a type in CleanTemplate.Persistence.Repositories uses a type in CleanTemplate.Domain.Entities.Users.
- The types involved
CleanTemplate.Persistence.Repositories.RefreshTokenRepository→CleanTemplate.Domain.Entities.Users.RefreshTokenCleanTemplate.Persistence.Repositories.UserRepository→CleanTemplate.Domain.Entities.Users.User
- Direction
- CleanTemplate.Persistence.Repositories uses CleanTemplate.Domain.Entities.Users, so a change to CleanTemplate.Domain.Entities.Users can break CleanTemplate.Persistence.Repositories, while a change to CleanTemplate.Persistence.Repositories can't break CleanTemplate.Domain.Entities.Users.
- Position
- Below the diagonal: CleanTemplate.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→32 CleanTemplate.Persistence.Repositories uses CleanTemplate.Domain.IRepositories✕
- Connections
- 4 pairs of types, where a type in CleanTemplate.Persistence.Repositories uses a type in CleanTemplate.Domain.IRepositories.
- The types involved
CleanTemplate.Persistence.Repositories.EfReadOnlyRepository→CleanTemplate.Domain.IRepositories.IReanOnlyRepositoryCleanTemplate.Persistence.Repositories.RefreshTokenRepository→CleanTemplate.Domain.IRepositories.IRefreshTokenRepositoryCleanTemplate.Persistence.Repositories.Repository→CleanTemplate.Domain.IRepositories.IRepositoryCleanTemplate.Persistence.Repositories.UserRepository→CleanTemplate.Domain.IRepositories.IUserRepository
- Direction
- CleanTemplate.Persistence.Repositories uses CleanTemplate.Domain.IRepositories, so a change to CleanTemplate.Domain.IRepositories can break CleanTemplate.Persistence.Repositories, while a change to CleanTemplate.Persistence.Repositories can't break CleanTemplate.Domain.IRepositories.
- Position
- Below the diagonal: CleanTemplate.Persistence.Repositories uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 13 | High / Critical |
| A05:2025 — Injection | 10 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
| A01:2025 — Broken Access Control | 2 | Medium |
Roadmap
Top priorities: Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion); Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Infrastructure/Persistance/Repositories/UserRepository.cs:23`; Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion). | +17.6 pts | Medium | Domain ↔ infrastructure boundary |
| Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Infrastructure/Persistance/Repositories/UserRepository.cs:23`. | +6.9 pts | Medium | Web-Security Posture |
| Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2). | +1.6 pts | Low | REDACTED Scanning |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). | +1.4 pts | Low | Static Analysis (SAST) |
| Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CreateUserCommandHandler.cs, UnauthorizedResponsesOperationFilter.cs. | +1.2 pts | Low | Explicit Debt |
| Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization. | +2.5 pts | Medium | Access Controls |
| Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Secrets (history) |
| Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/Infrastructure/Persistance/CommandHandlers/Users/CreateUserCommandHandler.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.3 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/Core/Domain/IRepositories/IRepository.cs | 6.4 | Near-clean | Explicit Debt: Dead code: Delete |
| src/Common/Utilities/StringExtensions.cs | 6.5 | Near-clean | Explicit Debt: Dead code: ToInt |
| src/Core/Domain/IRepositories/IUserRepository.cs | 6.8 | Near-clean | Explicit Debt: Dead code: GetByUserAndPass |
| src/Web/Api/DependencyInjection.cs | 6.9 | Near-clean | Explicit Debt: CommentedOutCode |
| src/Common/Utilities/ModelBuilderExtensions.cs | 7.3 | Near-clean | Explicit Debt: Dead code: AddRestrictDeleteBehaviorConvention |
| src/Web/ApiFramework/Swagger/UnauthorizedResponsesOperationFilter.cs | 7.6 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| src/Web/ApiFramework/Swagger/ApplySummariesOperationFilter.cs | 7.8 | Near-clean | Cyclomatic Complexity: ApplySummariesOperationFilter.Apply (cyclomatic 29) |
| REDACTED | 7.9 | Near-clean | Data Compliance (PII/GDPR): REDACTED |
| REDACTED | 7.9 | Near-clean | Data Compliance (PII/GDPR): REDACTED |
| test/CleanTemplate.Api.EndToEndTests/CleanTemplate.Api.EndToEndTests.csproj | 8.0 | Near-clean | Dependency Hygiene: Deprecated: xunit |
| src/Core/Application/Products/Query/GetProducts/ProductsQueryModel.cs | 8.2 | Near-clean | Explicit Debt: Dead code: ProductsQueryModel |
| src/Core/Domain/Entities/IEntity.cs | 8.2 | Near-clean | Explicit Debt: Dead code: BaseEntity |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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
This survey 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. All 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 77 dimensions across the health lenses
- 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, 128 of 174 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, 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.
Tools & methods
| 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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We 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. The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. Your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, or make the suite runnable in-image, and real coverage will be measured.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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 (5 contributor(s) across 281 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 4 hold 1.2% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- AXR1 Runtime accessibility — not measured this run — We 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 REDACTED (REDACTED). docker build failed (exit 1) — 15 | >>> COPY ["src/Common/CleanTemplate.Common.csproj", "src/Common/"] 16 | RUN dotnet restore "src/Web/Api/CleanTemplate.Api.csproj" 17 | COPY . . -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e6108187-1d90-4d8b-95d6-012e8b695cce::usjg9p8j2n9ec98sntba8a3r0: "/src/Common/CleanTemplate.Common.csproj": not found; runtime evidence skipped.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ApplySummariesOperationFilter.Apply at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ApplySummariesOperationFilter.Apply (cyclomatic 29). — Refactoring it lifts Cyclomatic Complexity from 9.2 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.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ApplySummariesOperationFilter.Apply at 34.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ApplySummariesOperationFilter.Apply (cognitive 34). — Refactoring it lifts Cognitive Complexity from 9.1 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.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with LoginCommandHandler.cs, ApiResult.cs. — One of this dimension's main actionable groups (2 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.
D5 · Coupling
9 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D9 · Test Distribution
12 test methods: 12 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 12 tests.
D12 · Dependency Hygiene
33 outdated, 1 vulnerable, 1 deprecated packages.
What to do
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with CleanTemplate.CommandHandler.Tests.csproj, CleanTemplate.Api.EndToEndTests.csproj. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with CleanTemplate.ApiFramework.csproj, CleanTemplate.Api.EndToEndTests.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
6 secret(s) detected.
What to do
- Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (6 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.
D14 · License Compliance
0 of 262 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 43 direct `PackageReference`(s), and 207 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
6 deducted debt markers + 25 dead symbols across 2954 LoC in the .NET projects (1.9/KLoC) → score 6.3.
What to do
- Resolve the 25 Dead code finding(s) in Explicit Debt — start with IRepository.cs (11), StringExtensions.cs (6), IUserRepository.cs (2). — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CreateUserCommandHandler.cs, UnauthorizedResponsesOperationFilter.cs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 CommentedOutCode finding(s) in Explicit Debt — start with DependencyInjection.cs (3), CreateUserCommandHandler.cs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
9 projects, 105 source files, 3373 hand-written lines of code (2954 production / 419 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 1864 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 17 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 2 document(s) read across 8 unit(s).
D21 · Naming Consistency
1 naming inconsistencies among 15 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `GetByUserAndPass` returns an awaitable but lacks the `Async` suffix its… finding(s) in Naming Consistency — start with IUserRepository.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 9 projects flagged as possibly oversized/incoherent.
D27 · Navigability
98 % of calls cross a namespace and 3 % 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.
D28 · Secrets (history)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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).
D29 · Static Analysis (SAST)
10 finding(s): 0 critical, 5 high, 4 medium, 1 low. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 1 high, 2 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
D32 · Data Compliance (PII/GDPR)
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
1 of 10 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Infrastructure/Persistance/CommandHandlers/Users/RefreshTokenCommandHandler.cs. Counted over 10 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 231 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 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.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
- `IRepository<TEntity>` declares 23 members: `Entities`, `Table`, `TableNoTracking`, `Add`, `AddAsync`, `AddRange`, `AddRangeAsync`, `Attach`, `Delete`, `DeleteAsync`, `DeleteRange`, `DeleteRangeAsync`, `Detach`, `GetById`, `GetByIdAsync`, `LoadCollection`, `LoadCollectionAsync`, `LoadReference`, `LoadReferenceAsync`, `Update`, `UpdateAsync`, `UpdateRange`, `UpdateRangeAsync`. 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. 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/Domain/IRepositories/IRepository.cs:12
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
AX9 · CQS / query purity
C2 · Access Controls
- Authorization IS enforced here (via [Authorize]/guards) — this is NOT a claim that endpoints are unprotected. What's missing is NAMED policies (AddAuthorization/AddPolicy, RequireRole/RequireClaim, RequireAuthorization): the access rules are implicit rather than named and testable. Recommendation, not a defect — name the rules so they're reviewable.
- This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable. — src/Web/Api/Controllers/v1/BaseControllerV1.cs:13
- [AllowAnonymous] (3) outweighs [Authorize] (1) — review whether the open surface is intended.
What to do
- Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization.
- Review the [AllowAnonymous] surface — keep anonymous endpoints deliberate and documented so the open surface stays intentional.
C4 · Data Retention
- 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.
DM6 · Domain ↔ infrastructure boundary
- `RefreshToken` (domain layer) names `ForeignKeyAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Core/Domain/Entities/Users/RefreshToken.cs:14
- `Role` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/Domain/Entities/Users/Role.cs:5
- `User` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/Domain/Entities/Users/User.cs:8
- `IReanOnlyRepository` (domain layer) names `DbSet` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Core/Domain/IRepositories/IReanOnlyRepository.cs:11
- `IRepository` (domain layer) names `DbSet` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Core/Domain/IRepositories/IRepository.cs:14
- `IUserRepository` (domain layer) names `User` from `CleanTemplate.Domain.Entities.Users` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/Domain/IRepositories/IUserRepository.cs:7
- `IUserRepository` (domain layer) names `User` from `CleanTemplate.Domain.Entities.Users` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×4) — src/Core/Domain/IRepositories/IUserRepository.cs:9, src/Core/Domain/IRepositories/IUserRepository.cs:11, src/Core/Domain/IRepositories/IUserRepository.cs:13, …
- The domain project `CleanTemplate.Domain` references `Microsoft.EntityFrameworkCore.Relational` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/Core/Domain/CleanTemplate.Domain.csproj:9
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `AddCommon` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Common/DependencyInjection.cs:8
- `AddApplication` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Core/Application/DependencyInjection.cs:8
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×28) — src/Common/Utilities/SecurityHelper.cs:16, src/Infrastructure/Persistance/CommandHandlers/Users/CreateUserCommandHandler.cs:48, src/Infrastructure/Persistance/Repositories/Repository.cs:36, …
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 7 of 7 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
P6 · Release Hygiene
- 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.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- Identifier 'passwordHash' looks like a password-hash field/property, but no KDF (PBKDF2 / Argon2 / BCrypt / PasswordHasher) was found anywhere in the source — so passwords aren't protected by a salted key-derivation function (whether a fast/plain hash, or a client-hashed value stored and compared verbatim). Password storage needs a salted KDF and a constant-time compare. — src/Infrastructure/Persistance/Repositories/UserRepository.cs:23
- Password-hash field compared with `==` — use a constant-time compare to avoid timing oracles (CryptographicOperations.FixedTimeEquals). — src/Infrastructure/Persistance/Repositories/UserRepository.cs:24
- `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/Web/Api/DependencyInjection.cs:294
- `ValidateAudience`, `ValidateIssuer` 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. — src/Infrastructure/Persistance/Jwt/JwtService.cs:75
- 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. — REDACTED:15
- 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. — REDACTED:15
What to do
- Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Infrastructure/Persistance/Repositories/UserRepository.cs:23`.
- 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.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 26/31 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. (×5) — src/Common/Utilities/PagingHelper.cs:11, src/Web/Api/Controllers/v1/Products/ProductController.cs:22, src/Web/Api/Controllers/v1/Products/ProductController.cs:33, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- This method contradicts itself about `exception`: line 54 assigns it with `as ValidationException`, which hands back null rather than throwing when the value is not a `ValidationException`, but line 56 then dereferences it directly as `exception.Errors` 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 `exception` once before the first use and handle the null case, or cast with `(ValidationException)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Web/Api/Filters/ApiExceptionFilter.cs:56
- This method contradicts itself about `exception`: line 68 assigns it with `as NotFoundException`, which hands back null rather than throwing when the value is not a `NotFoundException`, but line 70 then dereferences it directly as `exception.Message` 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 `exception` once before the first use and handle the null case, or cast with `(NotFoundException)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Web/Api/Filters/ApiExceptionFilter.cs:70
- This method contradicts itself about `exception`: line 76 assigns it with `as ExistingRecordException`, which hands back null rather than throwing when the value is not a `ExistingRecordException`, but line 78 then dereferences it directly as `exception.Message` 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 `exception` once before the first use and handle the null case, or cast with `(ExistingRecordException)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Web/Api/Filters/ApiExceptionFilter.cs:78
- 0/7 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- 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 `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 83% | Strong | Solid. |
| Maturity | 78% | Exemplary | Solid. |
| Readiness | 65% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 38% | Weak — gated by D29, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 18% | Weak — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 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
- 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 — 38 check(s) not relevant to this codebase
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 15 | >>> COPY ["src/Common/CleanTemplate.Common.csproj", "src/Common/"] 16 | RUN dotnet restore "src/Web/Api/CleanTemplate.Api.csproj" 17 | COPY . . -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e6108187-1d90-4d8b-95d6-012e8b695cce::usjg9p8j2n9ec98sntba8a3r0: "Common/CleanTemplate.Common.csproj": not found; 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.
- C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- 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.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,954 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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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"]`.
- D24 Comment Value — Too few judgeable comments (16 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- 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.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 CQRS handler(s))
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X6 Hand-rolled structured-format parsing — 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)
Critical — 32 finding(s)
- Domain depends on infrastructure: RefreshToken src/Core/Domain/Entities/Users/RefreshToken.cs:14
- Domain depends on infrastructure: Role src/Core/Domain/Entities/Users/Role.cs:5
- Domain depends on infrastructure: User src/Core/Domain/Entities/Users/User.cs:8
- Domain depends on infrastructure: IReanOnlyRepository src/Core/Domain/IRepositories/IReanOnlyRepository.cs:11
- Domain depends on infrastructure: IRepository src/Core/Domain/IRepositories/IRepository.cs:14
- Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs:7
- Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs:9
- Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs:11
- Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs:13
- Domain depends on infrastructure: IUserRepository src/Core/Domain/IRepositories/IUserRepository.cs:15
- Domain depends on infrastructure: CleanTemplate.Domain src/Core/Domain/CleanTemplate.Domain.csproj:9
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/Infrastructure/Persistance/CommandHandlers/Users/CreateUserCommandHandler.cs:15
- WriteOnlyPrivateField src/Web/ApiFramework/Swagger/UnauthorizedResponsesOperationFilter.cs:12
- REDACTED
- Password hashing without a KDF src/Infrastructure/Persistance/Repositories/UserRepository.cs:23
Serious — 56 finding(s)
- Dead code: ProductsQueryModel src/Core/Application/Products/Query/GetProducts/ProductsQueryModel.cs:3
- Dead code: BaseEntity src/Core/Domain/Entities/IEntity.cs:16
- Dead code: GetById src/Core/Domain/IRepositories/IReanOnlyRepository.cs:17
- Dead code: Delete src/Core/Domain/IRepositories/IRepository.cs:30
- Dead code: DeleteAsync src/Core/Domain/IRepositories/IRepository.cs:32
- Dead code: DeleteRange src/Core/Domain/IRepositories/IRepository.cs:34
- Dead code: DeleteRangeAsync src/Core/Domain/IRepositories/IRepository.cs:36
- Dead code: Detach src/Core/Domain/IRepositories/IRepository.cs:38
- Dead code: GetById src/Core/Domain/IRepositories/IRepository.cs:40
- Dead code: LoadCollection src/Core/Domain/IRepositories/IRepository.cs:44
- Dead code: LoadCollectionAsync src/Core/Domain/IRepositories/IRepository.cs:46
- Dead code: LoadReference src/Core/Domain/IRepositories/IRepository.cs:48
- Dead code: LoadReferenceAsync src/Core/Domain/IRepositories/IRepository.cs:50
- Dead code: UpdateRangeAsync src/Core/Domain/IRepositories/IRepository.cs:58
- Dead code: GetByUserAndPass src/Core/Domain/IRepositories/IUserRepository.cs:9
- Dead code: UpdateSecurityStampAsync src/Core/Domain/IRepositories/IUserRepository.cs:13
- Dead code: GetUserName src/Common/Utilities/IdentityExtensions.cs:34
- Dead code: AddRestrictDeleteBehaviorConvention src/Common/Utilities/ModelBuilderExtensions.cs:17
- Dead code: RegisterEntityTypeConfiguration src/Common/Utilities/ModelBuilderExtensions.cs:31
- Dead code: ToInt src/Common/Utilities/StringExtensions.cs:12
- Dead code: ToNumeric src/Common/Utilities/StringExtensions.cs:22
- Dead code: ToNumeric src/Common/Utilities/StringExtensions.cs:27
- Dead code: ToCurrency src/Common/Utilities/StringExtensions.cs:32
- Dead code: ToCurrency src/Common/Utilities/StringExtensions.cs:39
- Dead code: NullIfEmpty src/Common/Utilities/StringExtensions.cs:44
- Async method without CancellationToken: GetPaged src/Common/Utilities/PagingHelper.cs:11
- Async method without CancellationToken: AddAsync src/Web/Api/Controllers/v1/Products/ProductController.cs:22
- Async method without CancellationToken: GetByIdAsync src/Web/Api/Controllers/v1/Products/ProductController.cs:33
- Async method without CancellationToken: GetAllAsync src/Web/Api/Controllers/v1/Products/ProductController.cs:41
- Async method without CancellationToken: ReadFromCacheAsync src/Web/Api/Controllers/v1/Products/ProductController.cs:51
- CommentedOutCode src/Infrastructure/Persistance/CommandHandlers/Users/CreateUserCommandHandler.cs:43
- CommentedOutCode src/Web/Api/DependencyInjection.cs:177
- CommentedOutCode src/Web/Api/DependencyInjection.cs:316
- CommentedOutCode src/Web/Api/DependencyInjection.cs:327
- REDACTED
- REDACTED
- REDACTED
- Symbol treated as nullable, then dereferenced unguarded src/Web/Api/Filters/ApiExceptionFilter.cs:56
- Symbol treated as nullable, then dereferenced unguarded src/Web/Api/Filters/ApiExceptionFilter.cs:70
- Symbol treated as nullable, then dereferenced unguarded src/Web/Api/Filters/ApiExceptionFilter.cs:78
- Deprecated: xunit test/CleanTemplate.CommandHandler.Tests/CleanTemplate.CommandHandler.Tests.csproj:13
- Deprecated: xunit test/CleanTemplate.Api.EndToEndTests/CleanTemplate.Api.EndToEndTests.csproj:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) src/Infrastructure/Persistance/CommandHandlers/Users/LoginCommandHandler.cs:24
- Duplicated block (5 lines × 2) src/Web/ApiFramework/Tools/ApiResult.cs:42
- Hollow method — returns a constant without doing the work src/Common/DependencyInjection.cs:8
- Hollow method — returns a constant without doing the work src/Core/Application/DependencyInjection.cs:8
- ApplySummariesOperationFilter.Apply (cyclomatic 29) src/Web/ApiFramework/Swagger/ApplySummariesOperationFilter.cs:13
- ApplySummariesOperationFilter.Apply (cognitive 34) src/Web/ApiFramework/Swagger/ApplySummariesOperationFilter.cs:13
- REDACTED
- Password hash compared with `==` src/Infrastructure/Persistance/Repositories/UserRepository.cs:24
- Token validation disabled src/Infrastructure/Persistance/Jwt/JwtService.cs:75
- NuGet dependencies are not locked
Minor — 53 finding(s)
- Commented-out code src/Common/Utilities/SecurityHelper.cs:16
- Commented-out code src/Infrastructure/Persistance/CommandHandlers/Users/CreateUserCommandHandler.cs:48
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:36
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:44
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:52
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:60
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:68
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:76
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:91
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:99
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:107
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:115
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:123
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:131
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:141
- Commented-out code src/Infrastructure/Persistance/Repositories/Repository.cs:149
- Commented-out code src/Infrastructure/Persistance/Repositories/UserRepository.cs:29
- Commented-out code src/Web/Api/DependencyInjection.cs:160
- Commented-out code src/Web/Api/DependencyInjection.cs:211
- Commented-out code src/Web/Api/DependencyInjection.cs:235
- Commented-out code src/Web/Api/DependencyInjection.cs:239
- Commented-out code src/Web/Api/DependencyInjection.cs:240
- Commented-out code src/Web/Api/DependencyInjection.cs:316
- Commented-out code src/Web/Api/DependencyInjection.cs:318
- Commented-out code src/Web/Api/DependencyInjection.cs:325
- No named authorization policies
- No named authorization policies src/Web/Api/Controllers/v1/BaseControllerV1.cs:13
- Outdated: Mapster src/Web/ApiFramework/CleanTemplate.ApiFramework.csproj:14
- Outdated: coverlet.collector test/CleanTemplate.Api.EndToEndTests/CleanTemplate.Api.EndToEndTests.csproj:18
- No security response headers detected
- No security response headers detected REDACTED:15
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected REDACTED:15
- Fat interface: IRepository<TEntity> (23 members) src/Core/Domain/IRepositories/IRepository.cs:12
- Anonymous-heavy surface
- Partial data-retention evidence
- `GetByUserAndPass` returns an awaitable but lacks the `Async` suffix its 14 peers carry src/Core/Domain/IRepositories/IUserRepository.cs:9
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file src/Infrastructure/Persistance/CommandHandlers/Users/RefreshTokenCommandHandler.cs:1
- No ADRs
- No rollback/health safety
- No changelog
- OIDC metadata fetched over HTTP src/Web/Api/DependencyInjection.cs:294
- Duplicated predicate src/Web/ApiFramework/Tools/ApiResult.cs:42
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
- Silent fallback default in catch src/Infrastructure/Persistance/Jwt/JwtService.cs:84
Minor — 33 finding(s)
- Outdated: Microsoft.AspNetCore.Mvc.Abstractions
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: Microsoft.EntityFrameworkCore.Relational
- Outdated: Microsoft.Extensions.Identity.Stores
- Outdated: FluentValidation
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.Extensions.Configuration
- Outdated: Microsoft.Extensions.Configuration.Binder
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables
- Outdated: Microsoft.Extensions.Configuration.FileExtensions
- Outdated: Microsoft.Extensions.Configuration.Json
- Outdated: System.Security.Cryptography.Xml
- Outdated: Asp.Versioning.Mvc
- Outdated: Asp.Versioning.Mvc.ApiExplorer
- Outdated: Autofac.Extensions.DependencyInjection
- Outdated: Microsoft.AspNetCore.Mvc.Core
- Outdated: Swashbuckle.AspNetCore
- Outdated: Swashbuckle.AspNetCore.Annotations
- Outdated: Swashbuckle.AspNetCore.ReDoc
- Outdated: Swashbuckle.AspNetCore.Swagger
- Mock framework: Moq
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e3968912991143c895c083ee64ab2b9e/history.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e3968912991143c895c083ee64ab2b9e/tree.json --exit-code 0 --source . | 3 | 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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Infrastructure/Persistance/Migrations . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Infrastructure/Persistance/Migrations . | 2 | artifacts/raw/semgrep-gdpr.json |
| 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-f7664a0aedae48e5bcbbfac23f35d792 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 3 field(s)
- CreateUserCommand.FullName src/Core/Application/Users/Command/CreateUser/CreateUserCommand.cs:14
- User.FullName src/Core/Domain/Entities/Users/User.cs:15
- SingUpRequest.FullName src/Web/Api/Controllers/v1/Users/Requests/SingUpRequest.cs:13
Email — 2 field(s)
- CreateUserCommand.Email src/Core/Application/Users/Command/CreateUser/CreateUserCommand.cs:10
- SingUpRequest.Email src/Web/Api/Controllers/v1/Users/Requests/SingUpRequest.cs:9