Executive summary
mohamedelareeg/CleanArchitecture is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because the project has no automated tests and we found no automated security scanning of the code, its secrets or its dependencies. It scores 52 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 14 points. Adding automated security scanning comes next, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 64.
Nine known security holes in the packages the code depends on can be used by attackers. Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one password or key is open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing the exposed password or key would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The four data fields that are written but never read need removing.
The product code is 2,917 lines, about €4,600 to rebuild.
If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 52 to about 64.
Fixed since the last survey: 8 findings
- Static Analysis (SAST) · Medium: REDACTED CleanArchitecture.Api/Controllers/AuthController.cs
- Static Analysis (SAST) · Medium: REDACTED CleanArchitecture.Api/Controllers/AuthController.cs
- Static Analysis (SAST) · Medium: REDACTED CleanArchitecture.Api/Controllers/AuthController.cs
- Static Analysis (SAST) · Medium: REDACTED CleanArchitecture.Api/Controllers/AuthController.cs
- Cancellation propagation · Async method without CancellationToken: Login CleanArchitecture.Identity/Services/AuthService.cs
- Cancellation propagation · Async method drops its ambient CancellationToken: Invoke CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs
- Slice cohesion · Cross-slice coupling: Auth → Authentication CleanArchitecture.Application/Features/Auth/Handlers/Commands/AuthCommandHandler.cs
- Slice cohesion · Cross-slice coupling: Auth → Authentication CleanArchitecture.Application/Features/Auth/Handlers/Commands/AuthCommandHandler.cs
Rebuild cost: about €4,600 · Estimate
| Cost to rebuild | €1,500 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 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,917 lines of product code, of which 41% is declarations and boilerplate, 40% straight logic and 19% 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 CleanArchitecture.Api.Base | 3 CleanArchitecture.Api.Configuration.Extensions.Swagger | 4 CleanArchitecture.Application | 5 CleanArchitecture.Application.Bases | 6 CleanArchitecture.Application.Features.Auth.Mapping | 7 CleanArchitecture.Application.Features.Auth.Requests.Commands | 8 CleanArchitecture.Application.Features.Auth.Results | 9 CleanArchitecture.Application.Features.Auth.Validators.Commands | 10 CleanArchitecture.Application.Features.Emails.Requests.Commands | 11 CleanArchitecture.Application.Features.Roles.Requests.Commands | 12 CleanArchitecture.Application.Features.Roles.Requests.Queries | 13 CleanArchitecture.Application.Models | 14 CleanArchitecture.Application.Models.Identity | 15 CleanArchitecture.Application.Security | 16 CleanArchitecture.Application.Wrappers | 17 CleanArchitecture.Domain.AppMetaData | 18 CleanArchitecture.Domain.Entities | 19 CleanArchitecture.Identity | 20 CleanArchitecture.Identity.Entities | 21 CleanArchitecture.Identity.Helpers.Filters | 22 CleanArchitecture.Infrustructure | 23 CleanArchitecture.Mvc.Controllers | 24 CleanArchitecture.Persistence | 25 SchoolProject.Core.Features.Authentication.Commands.Models | 26 CleanArchitecture.Api.Controllers | 27 CleanArchitecture.Application.Contracts.Identity | 28 CleanArchitecture.Application.Contracts.Persistence.Repositories | 29 CleanArchitecture.Application.Extensions | 30 CleanArchitecture.Application.Middleware | 31 CleanArchitecture.Identity.Configurations | 32 CleanArchitecture.Identity.Helpers | 33 CleanArchitecture.Application.Behaviors | 34 CleanArchitecture.Application.Features.Auth.Handlers.Commands | 35 CleanArchitecture.Application.Features.Auth.Handlers.Queries | 36 CleanArchitecture.Application.Features.Emails.Handlers.Commands | 37 CleanArchitecture.Application.Features.Roles.Handlers | 38 CleanArchitecture.Application.Features.Roles.Handlers.Queries | 39 CleanArchitecture.Identity.Services | 40 CleanArchitecture.Persistence.Repositories |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanArchitecture.Api.Base | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanArchitecture.Api.Configuration.Extensions.Swagger | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanArchitecture.Application | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanArchitecture.Application.Bases | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanArchitecture.Application.Features.Auth.Mapping | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanArchitecture.Application.Features.Auth.Requests.Commands | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanArchitecture.Application.Features.Auth.Results | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanArchitecture.Application.Features.Auth.Validators.Commands | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanArchitecture.Application.Features.Emails.Requests.Commands | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanArchitecture.Application.Features.Roles.Requests.Commands | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanArchitecture.Application.Features.Roles.Requests.Queries | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanArchitecture.Application.Models | ||||||||||||||||||||||||||||||||||||||||
| 14 CleanArchitecture.Application.Models.Identity | ||||||||||||||||||||||||||||||||||||||||
| 15 CleanArchitecture.Application.Security | ||||||||||||||||||||||||||||||||||||||||
| 16 CleanArchitecture.Application.Wrappers | ||||||||||||||||||||||||||||||||||||||||
| 17 CleanArchitecture.Domain.AppMetaData | ||||||||||||||||||||||||||||||||||||||||
| 18 CleanArchitecture.Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 19 CleanArchitecture.Identity | ||||||||||||||||||||||||||||||||||||||||
| 20 CleanArchitecture.Identity.Entities | ||||||||||||||||||||||||||||||||||||||||
| 21 CleanArchitecture.Identity.Helpers.Filters | ||||||||||||||||||||||||||||||||||||||||
| 22 CleanArchitecture.Infrustructure | ||||||||||||||||||||||||||||||||||||||||
| 23 CleanArchitecture.Mvc.Controllers | ||||||||||||||||||||||||||||||||||||||||
| 24 CleanArchitecture.Persistence | ||||||||||||||||||||||||||||||||||||||||
| 25 SchoolProject.Core.Features.Authentication.Commands.Models | ||||||||||||||||||||||||||||||||||||||||
| 26 CleanArchitecture.Api.Controllers | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 CleanArchitecture.Application.Contracts.Identity | 3 | 2 | 2 | 6 | 1 | |||||||||||||||||||||||||||||||||||
| 28 CleanArchitecture.Application.Contracts.Persistence.Repositories | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 CleanArchitecture.Application.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 CleanArchitecture.Application.Middleware | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 CleanArchitecture.Identity.Configurations | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 CleanArchitecture.Identity.Helpers | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 CleanArchitecture.Application.Behaviors | 4 | |||||||||||||||||||||||||||||||||||||||
| 34 CleanArchitecture.Application.Features.Auth.Handlers.Commands | 1 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 35 CleanArchitecture.Application.Features.Auth.Handlers.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 CleanArchitecture.Application.Features.Emails.Handlers.Commands | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 CleanArchitecture.Application.Features.Roles.Handlers | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 CleanArchitecture.Application.Features.Roles.Handlers.Queries | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 CleanArchitecture.Identity.Services | 6 | 2 | 2 | 6 | 2 | 1 | 5 | 8 | 1 | |||||||||||||||||||||||||||||||
| 40 CleanArchitecture.Persistence.Repositories | 1 | 1 | 1 |
26→2 CleanArchitecture.Api.Controllers uses CleanArchitecture.Api.Base✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Api.Base.
- The types involved
CleanArchitecture.Api.Controllers.AuthController→CleanArchitecture.Api.Base.AppControllerBaseCleanArchitecture.Api.Controllers.EmailsController→CleanArchitecture.Api.Base.AppControllerBaseCleanArchitecture.Api.Controllers.RoleController→CleanArchitecture.Api.Base.AppControllerBase
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Api.Base, so a change to CleanArchitecture.Api.Base can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Api.Base.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
27→5 CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Bases✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Contracts.Identity uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Contracts.Identity.IAuthService→CleanArchitecture.Application.Bases.BaseResponseCleanArchitecture.Application.Contracts.Identity.IEmailsService→CleanArchitecture.Application.Bases.BaseResponseCleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Bases.BaseResponse
- Direction
- CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Contracts.Identity, while a change to CleanArchitecture.Application.Contracts.Identity can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
27→7 CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Features.Auth.Requests.Commands✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Contracts.Identity uses a type in CleanArchitecture.Application.Features.Auth.Requests.Commands.
- The types involved
CleanArchitecture.Application.Contracts.Identity.IAuthService→CleanArchitecture.Application.Features.Auth.Requests.Commands.LoginCommandCleanArchitecture.Application.Contracts.Identity.IAuthService→CleanArchitecture.Application.Features.Auth.Requests.Commands.RegisterCommand
- Direction
- CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Features.Auth.Requests.Commands, so a change to CleanArchitecture.Application.Features.Auth.Requests.Commands can break CleanArchitecture.Application.Contracts.Identity, while a change to CleanArchitecture.Application.Contracts.Identity can't break CleanArchitecture.Application.Features.Auth.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
27→8 CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Features.Auth.Results✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Contracts.Identity uses a type in CleanArchitecture.Application.Features.Auth.Results.
- The types involved
CleanArchitecture.Application.Contracts.Identity.IAuthService→CleanArchitecture.Application.Features.Auth.Results.LoginResultCleanArchitecture.Application.Contracts.Identity.IAuthService→CleanArchitecture.Application.Features.Auth.Results.RegisterResult
- Direction
- CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Features.Auth.Results, so a change to CleanArchitecture.Application.Features.Auth.Results can break CleanArchitecture.Application.Contracts.Identity, while a change to CleanArchitecture.Application.Contracts.Identity can't break CleanArchitecture.Application.Features.Auth.Results.
- Position
- Below the diagonal: CleanArchitecture.Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
27→11 CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Features.Roles.Requests.Commands✕
- Connections
- 6 pairs of types, where a type in CleanArchitecture.Application.Contracts.Identity uses a type in CleanArchitecture.Application.Features.Roles.Requests.Commands.
- The types involved
CleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.AddClaimToRoleCommandCleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.AssignClaimToUserCommandCleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.AssignRoleToUserCommandCleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.CreateRoleCommandCleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.DeleteRoleCommandCleanArchitecture.Application.Contracts.Identity.IRoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.EditRoleCommand
- Direction
- CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Features.Roles.Requests.Commands, so a change to CleanArchitecture.Application.Features.Roles.Requests.Commands can break CleanArchitecture.Application.Contracts.Identity, while a change to CleanArchitecture.Application.Contracts.Identity can't break CleanArchitecture.Application.Features.Roles.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
27→14 CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Models.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Contracts.Identity uses a type in CleanArchitecture.Application.Models.Identity.
- The types involved
CleanArchitecture.Application.Contracts.Identity.IUserService→CleanArchitecture.Application.Models.Identity.Employee
- Direction
- CleanArchitecture.Application.Contracts.Identity uses CleanArchitecture.Application.Models.Identity, so a change to CleanArchitecture.Application.Models.Identity can break CleanArchitecture.Application.Contracts.Identity, while a change to CleanArchitecture.Application.Contracts.Identity can't break CleanArchitecture.Application.Models.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
28→5 CleanArchitecture.Application.Contracts.Persistence.Repositories uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Contracts.Persistence.Repositories uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Contracts.Persistence.Repositories.IBaseRepo→CleanArchitecture.Application.Bases.BaseFilteration
- Direction
- CleanArchitecture.Application.Contracts.Persistence.Repositories uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Contracts.Persistence.Repositories, while a change to CleanArchitecture.Application.Contracts.Persistence.Repositories can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Contracts.Persistence.Repositories uses a module listed above it, which is the healthy direction.
29→16 CleanArchitecture.Application.Extensions uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Extensions uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Extensions.QueryableExtensions→CleanArchitecture.Application.Wrappers.PaginatedResult
- Direction
- CleanArchitecture.Application.Extensions uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Extensions, while a change to CleanArchitecture.Application.Extensions can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Extensions uses a module listed above it, which is the healthy direction.
30→5 CleanArchitecture.Application.Middleware uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Middleware uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Middleware.ErrorHandlerMiddleware→CleanArchitecture.Application.Bases.BaseResponse
- Direction
- CleanArchitecture.Application.Middleware uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Middleware, while a change to CleanArchitecture.Application.Middleware can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Middleware uses a module listed above it, which is the healthy direction.
31→20 CleanArchitecture.Identity.Configurations uses CleanArchitecture.Identity.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Identity.Configurations uses a type in CleanArchitecture.Identity.Entities.
- The types involved
CleanArchitecture.Identity.Configurations.UserConfiguration→CleanArchitecture.Identity.Entities.ApplicationUser
- Direction
- CleanArchitecture.Identity.Configurations uses CleanArchitecture.Identity.Entities, so a change to CleanArchitecture.Identity.Entities can break CleanArchitecture.Identity.Configurations, while a change to CleanArchitecture.Identity.Configurations can't break CleanArchitecture.Identity.Entities.
- Position
- Below the diagonal: CleanArchitecture.Identity.Configurations uses a module listed above it, which is the healthy direction.
32→13 CleanArchitecture.Identity.Helpers uses CleanArchitecture.Application.Models✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Identity.Helpers uses a type in CleanArchitecture.Application.Models.
- The types involved
CleanArchitecture.Identity.Helpers.AddIdentityOptions→CleanArchitecture.Application.Models.DefaultIdentityOptions
- Direction
- CleanArchitecture.Identity.Helpers uses CleanArchitecture.Application.Models, so a change to CleanArchitecture.Application.Models can break CleanArchitecture.Identity.Helpers, while a change to CleanArchitecture.Identity.Helpers can't break CleanArchitecture.Application.Models.
- Position
- Below the diagonal: CleanArchitecture.Identity.Helpers uses a module listed above it, which is the healthy direction.
33→27 CleanArchitecture.Application.Behaviors uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Application.Behaviors uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Application.Behaviors.AuthorizationBehaviour→CleanArchitecture.Application.Contracts.Identity.IIdentityServiceCleanArchitecture.Application.Behaviors.AuthorizationBehaviour→CleanArchitecture.Application.Contracts.Identity.IUserCleanArchitecture.Application.Behaviors.AuthorizationJWTBehaviour→CleanArchitecture.Application.Contracts.Identity.IIdentityServiceCleanArchitecture.Application.Behaviors.AuthorizationJWTBehaviour→CleanArchitecture.Application.Contracts.Identity.IUser
- Direction
- CleanArchitecture.Application.Behaviors uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Application.Behaviors, while a change to CleanArchitecture.Application.Behaviors can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Behaviors uses a module listed above it, which is the healthy direction.
34→5 CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→CleanArchitecture.Application.Bases.BaseResponse
- Direction
- CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Features.Auth.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Auth.Handlers.Commands can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a module listed above it, which is the healthy direction.
34→7 CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Features.Auth.Requests.Commands✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a type in CleanArchitecture.Application.Features.Auth.Requests.Commands.
- The types involved
CleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→CleanArchitecture.Application.Features.Auth.Requests.Commands.LoginCommandCleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→CleanArchitecture.Application.Features.Auth.Requests.Commands.RegisterCommand
- Direction
- CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Features.Auth.Requests.Commands, so a change to CleanArchitecture.Application.Features.Auth.Requests.Commands can break CleanArchitecture.Application.Features.Auth.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Auth.Handlers.Commands can't break CleanArchitecture.Application.Features.Auth.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a module listed above it, which is the healthy direction.
34→8 CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Features.Auth.Results✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a type in CleanArchitecture.Application.Features.Auth.Results.
- The types involved
CleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→CleanArchitecture.Application.Features.Auth.Results.LoginResultCleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→CleanArchitecture.Application.Features.Auth.Results.RegisterResult
- Direction
- CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Features.Auth.Results, so a change to CleanArchitecture.Application.Features.Auth.Results can break CleanArchitecture.Application.Features.Auth.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Auth.Handlers.Commands can't break CleanArchitecture.Application.Features.Auth.Results.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a module listed above it, which is the healthy direction.
34→25 CleanArchitecture.Application.Features.Auth.Handlers.Commands uses SchoolProject.Core.Features.Authentication.Commands.Models✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a type in SchoolProject.Core.Features.Authentication.Commands.Models.
- The types involved
CleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→SchoolProject.Core.Features.Authentication.Commands.Models.ResetPasswordCommandCleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→SchoolProject.Core.Features.Authentication.Commands.Models.SendResetPasswordCommand
- Direction
- CleanArchitecture.Application.Features.Auth.Handlers.Commands uses SchoolProject.Core.Features.Authentication.Commands.Models, so a change to SchoolProject.Core.Features.Authentication.Commands.Models can break CleanArchitecture.Application.Features.Auth.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Auth.Handlers.Commands can't break SchoolProject.Core.Features.Authentication.Commands.Models.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a module listed above it, which is the healthy direction.
34→27 CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Application.Features.Auth.Handlers.Commands.AuthCommandHandler→CleanArchitecture.Application.Contracts.Identity.IAuthService
- Direction
- CleanArchitecture.Application.Features.Auth.Handlers.Commands uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Application.Features.Auth.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Auth.Handlers.Commands can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Auth.Handlers.Commands uses a module listed above it, which is the healthy direction.
35→27 CleanArchitecture.Application.Features.Auth.Handlers.Queries uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Auth.Handlers.Queries uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Application.Features.Auth.Handlers.Queries.AuthQueryHandler→CleanArchitecture.Application.Contracts.Identity.IAuthService
- Direction
- CleanArchitecture.Application.Features.Auth.Handlers.Queries uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Application.Features.Auth.Handlers.Queries, while a change to CleanArchitecture.Application.Features.Auth.Handlers.Queries can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Auth.Handlers.Queries uses a module listed above it, which is the healthy direction.
36→5 CleanArchitecture.Application.Features.Emails.Handlers.Commands uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Emails.Handlers.Commands uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Features.Emails.Handlers.Commands.EmailCommandHandler→CleanArchitecture.Application.Bases.BaseResponse
- Direction
- CleanArchitecture.Application.Features.Emails.Handlers.Commands uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Features.Emails.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Emails.Handlers.Commands can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Emails.Handlers.Commands uses a module listed above it, which is the healthy direction.
36→10 CleanArchitecture.Application.Features.Emails.Handlers.Commands uses CleanArchitecture.Application.Features.Emails.Requests.Commands✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Emails.Handlers.Commands uses a type in CleanArchitecture.Application.Features.Emails.Requests.Commands.
- The types involved
CleanArchitecture.Application.Features.Emails.Handlers.Commands.EmailCommandHandler→CleanArchitecture.Application.Features.Emails.Requests.Commands.SendEmailCommand
- Direction
- CleanArchitecture.Application.Features.Emails.Handlers.Commands uses CleanArchitecture.Application.Features.Emails.Requests.Commands, so a change to CleanArchitecture.Application.Features.Emails.Requests.Commands can break CleanArchitecture.Application.Features.Emails.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Emails.Handlers.Commands can't break CleanArchitecture.Application.Features.Emails.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Emails.Handlers.Commands uses a module listed above it, which is the healthy direction.
36→27 CleanArchitecture.Application.Features.Emails.Handlers.Commands uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Emails.Handlers.Commands uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Application.Features.Emails.Handlers.Commands.EmailCommandHandler→CleanArchitecture.Application.Contracts.Identity.IEmailsService
- Direction
- CleanArchitecture.Application.Features.Emails.Handlers.Commands uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Application.Features.Emails.Handlers.Commands, while a change to CleanArchitecture.Application.Features.Emails.Handlers.Commands can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Emails.Handlers.Commands uses a module listed above it, which is the healthy direction.
37→5 CleanArchitecture.Application.Features.Roles.Handlers uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Roles.Handlers uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Bases.BaseResponse
- Direction
- CleanArchitecture.Application.Features.Roles.Handlers uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Features.Roles.Handlers, while a change to CleanArchitecture.Application.Features.Roles.Handlers can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Roles.Handlers uses a module listed above it, which is the healthy direction.
37→11 CleanArchitecture.Application.Features.Roles.Handlers uses CleanArchitecture.Application.Features.Roles.Requests.Commands✕
- Connections
- 6 pairs of types, where a type in CleanArchitecture.Application.Features.Roles.Handlers uses a type in CleanArchitecture.Application.Features.Roles.Requests.Commands.
- The types involved
CleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Features.Roles.Requests.Commands.AddClaimToRoleCommandCleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Features.Roles.Requests.Commands.AssignClaimToUserCommandCleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Features.Roles.Requests.Commands.AssignRoleToUserCommandCleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Features.Roles.Requests.Commands.CreateRoleCommandCleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Features.Roles.Requests.Commands.DeleteRoleCommandCleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Features.Roles.Requests.Commands.EditRoleCommand
- Direction
- CleanArchitecture.Application.Features.Roles.Handlers uses CleanArchitecture.Application.Features.Roles.Requests.Commands, so a change to CleanArchitecture.Application.Features.Roles.Requests.Commands can break CleanArchitecture.Application.Features.Roles.Handlers, while a change to CleanArchitecture.Application.Features.Roles.Handlers can't break CleanArchitecture.Application.Features.Roles.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Roles.Handlers uses a module listed above it, which is the healthy direction.
37→27 CleanArchitecture.Application.Features.Roles.Handlers uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Roles.Handlers uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Application.Features.Roles.Handlers.RolesCommandHandler→CleanArchitecture.Application.Contracts.Identity.IRoleService
- Direction
- CleanArchitecture.Application.Features.Roles.Handlers uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Application.Features.Roles.Handlers, while a change to CleanArchitecture.Application.Features.Roles.Handlers can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Roles.Handlers uses a module listed above it, which is the healthy direction.
38→5 CleanArchitecture.Application.Features.Roles.Handlers.Queries uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Roles.Handlers.Queries uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Bases.BaseResponse
- Direction
- CleanArchitecture.Application.Features.Roles.Handlers.Queries uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Application.Features.Roles.Handlers.Queries, while a change to CleanArchitecture.Application.Features.Roles.Handlers.Queries can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Roles.Handlers.Queries uses a module listed above it, which is the healthy direction.
38→12 CleanArchitecture.Application.Features.Roles.Handlers.Queries uses CleanArchitecture.Application.Features.Roles.Requests.Queries✕
- Connections
- 5 pairs of types, where a type in CleanArchitecture.Application.Features.Roles.Handlers.Queries uses a type in CleanArchitecture.Application.Features.Roles.Requests.Queries.
- The types involved
CleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Features.Roles.Requests.Queries.GetAllClaimsQueryCleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Features.Roles.Requests.Queries.GetAllRolesQueryCleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Features.Roles.Requests.Queries.GetRoleClaimsQueryCleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Features.Roles.Requests.Queries.GetUserClaimsQueryCleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Features.Roles.Requests.Queries.GetUserRolesQuery
- Direction
- CleanArchitecture.Application.Features.Roles.Handlers.Queries uses CleanArchitecture.Application.Features.Roles.Requests.Queries, so a change to CleanArchitecture.Application.Features.Roles.Requests.Queries can break CleanArchitecture.Application.Features.Roles.Handlers.Queries, while a change to CleanArchitecture.Application.Features.Roles.Handlers.Queries can't break CleanArchitecture.Application.Features.Roles.Requests.Queries.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Roles.Handlers.Queries uses a module listed above it, which is the healthy direction.
38→27 CleanArchitecture.Application.Features.Roles.Handlers.Queries uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Roles.Handlers.Queries uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Application.Features.Roles.Handlers.Queries.RolesQueryHandler→CleanArchitecture.Application.Contracts.Identity.IRoleService
- Direction
- CleanArchitecture.Application.Features.Roles.Handlers.Queries uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Application.Features.Roles.Handlers.Queries, while a change to CleanArchitecture.Application.Features.Roles.Handlers.Queries can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Roles.Handlers.Queries uses a module listed above it, which is the healthy direction.
39→5 CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Bases✕
- Connections
- 6 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Bases.BaseResponseCleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Bases.BaseResponseHandlerCleanArchitecture.Identity.Services.EmailsService→CleanArchitecture.Application.Bases.BaseResponseCleanArchitecture.Identity.Services.EmailsService→CleanArchitecture.Application.Bases.BaseResponseHandlerCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Bases.BaseResponseCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Bases.BaseResponseHandler
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→7 CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Features.Auth.Requests.Commands✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Application.Features.Auth.Requests.Commands.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Features.Auth.Requests.Commands.LoginCommandCleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Features.Auth.Requests.Commands.RegisterCommand
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Features.Auth.Requests.Commands, so a change to CleanArchitecture.Application.Features.Auth.Requests.Commands can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Application.Features.Auth.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→8 CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Features.Auth.Results✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Application.Features.Auth.Results.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Features.Auth.Results.LoginResultCleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Features.Auth.Results.RegisterResult
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Features.Auth.Results, so a change to CleanArchitecture.Application.Features.Auth.Results can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Application.Features.Auth.Results.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→11 CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Features.Roles.Requests.Commands✕
- Connections
- 6 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Application.Features.Roles.Requests.Commands.
- The types involved
CleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.AddClaimToRoleCommandCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.AssignClaimToUserCommandCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.AssignRoleToUserCommandCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.CreateRoleCommandCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.DeleteRoleCommandCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Features.Roles.Requests.Commands.EditRoleCommand
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Features.Roles.Requests.Commands, so a change to CleanArchitecture.Application.Features.Roles.Requests.Commands can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Application.Features.Roles.Requests.Commands.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→14 CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Models.Identity✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Application.Models.Identity.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Models.Identity.JwtSettingsCleanArchitecture.Identity.Services.UserService→CleanArchitecture.Application.Models.Identity.Employee
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Models.Identity, so a change to CleanArchitecture.Application.Models.Identity can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Application.Models.Identity.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→19 CleanArchitecture.Identity.Services uses CleanArchitecture.Identity✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Identity.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Identity.IdentityDbContext
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Identity, so a change to CleanArchitecture.Identity can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Identity.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→20 CleanArchitecture.Identity.Services uses CleanArchitecture.Identity.Entities✕
- Connections
- 5 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Identity.Entities.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Identity.Entities.ApplicationUserCleanArchitecture.Identity.Services.CurrentUser→CleanArchitecture.Identity.Entities.ApplicationUserCleanArchitecture.Identity.Services.IdentityService→CleanArchitecture.Identity.Entities.ApplicationUserCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Identity.Entities.ApplicationUserCleanArchitecture.Identity.Services.UserService→CleanArchitecture.Identity.Entities.ApplicationUser
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Identity.Entities, so a change to CleanArchitecture.Identity.Entities can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Identity.Entities.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→27 CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Contracts.Identity✕
- Connections
- 8 pairs of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Application.Contracts.Identity.
- The types involved
CleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Contracts.Identity.IAuthServiceCleanArchitecture.Identity.Services.AuthService→CleanArchitecture.Application.Contracts.Identity.IEmailsServiceCleanArchitecture.Identity.Services.CurrentUser→CleanArchitecture.Application.Contracts.Identity.IUserCleanArchitecture.Identity.Services.EmailsService→CleanArchitecture.Application.Contracts.Identity.IEmailsServiceCleanArchitecture.Identity.Services.IdentityService→CleanArchitecture.Application.Contracts.Identity.IIdentityServiceCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Contracts.Identity.IRoleServiceCleanArchitecture.Identity.Services.RoleService→CleanArchitecture.Application.Contracts.Identity.IUserCleanArchitecture.Identity.Services.UserService→CleanArchitecture.Application.Contracts.Identity.IUserService
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Application.Contracts.Identity, so a change to CleanArchitecture.Application.Contracts.Identity can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Application.Contracts.Identity.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
39→32 CleanArchitecture.Identity.Services uses CleanArchitecture.Identity.Helpers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Identity.Services uses a type in CleanArchitecture.Identity.Helpers.
- The types involved
CleanArchitecture.Identity.Services.EmailsService→CleanArchitecture.Identity.Helpers.EmailSettings
- Direction
- CleanArchitecture.Identity.Services uses CleanArchitecture.Identity.Helpers, so a change to CleanArchitecture.Identity.Helpers can break CleanArchitecture.Identity.Services, while a change to CleanArchitecture.Identity.Services can't break CleanArchitecture.Identity.Helpers.
- Position
- Below the diagonal: CleanArchitecture.Identity.Services uses a module listed above it, which is the healthy direction.
40→5 CleanArchitecture.Persistence.Repositories uses CleanArchitecture.Application.Bases✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Persistence.Repositories uses a type in CleanArchitecture.Application.Bases.
- The types involved
CleanArchitecture.Persistence.Repositories.BaseRepo→CleanArchitecture.Application.Bases.BaseFilteration
- Direction
- CleanArchitecture.Persistence.Repositories uses CleanArchitecture.Application.Bases, so a change to CleanArchitecture.Application.Bases can break CleanArchitecture.Persistence.Repositories, while a change to CleanArchitecture.Persistence.Repositories can't break CleanArchitecture.Application.Bases.
- Position
- Below the diagonal: CleanArchitecture.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→24 CleanArchitecture.Persistence.Repositories uses CleanArchitecture.Persistence✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Persistence.Repositories uses a type in CleanArchitecture.Persistence.
- The types involved
CleanArchitecture.Persistence.Repositories.BaseRepo→CleanArchitecture.Persistence.ApplicationDbContext
- Direction
- CleanArchitecture.Persistence.Repositories uses CleanArchitecture.Persistence, so a change to CleanArchitecture.Persistence can break CleanArchitecture.Persistence.Repositories, while a change to CleanArchitecture.Persistence.Repositories can't break CleanArchitecture.Persistence.
- Position
- Below the diagonal: CleanArchitecture.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→28 CleanArchitecture.Persistence.Repositories uses CleanArchitecture.Application.Contracts.Persistence.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Persistence.Repositories uses a type in CleanArchitecture.Application.Contracts.Persistence.Repositories.
- The types involved
CleanArchitecture.Persistence.Repositories.BaseRepo→CleanArchitecture.Application.Contracts.Persistence.Repositories.IBaseRepo
- Direction
- CleanArchitecture.Persistence.Repositories uses CleanArchitecture.Application.Contracts.Persistence.Repositories, so a change to CleanArchitecture.Application.Contracts.Persistence.Repositories can break CleanArchitecture.Persistence.Repositories, while a change to CleanArchitecture.Persistence.Repositories can't break CleanArchitecture.Application.Contracts.Persistence.Repositories.
- Position
- Below the diagonal: CleanArchitecture.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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
| A05:2025 — Injection | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No tests found finding(s) in Test Distribution; Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +13.6 pts | Low | Test Distribution |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +7.8 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.1 pts | Low | ADR Quality |
| Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AuthorizationBehaviour.cs, AuthorizationJWTBehaviour.cs, AuthQueryHandler.cs. | +2.2 pts | Low | Explicit Debt |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +2.9 pts | Medium | Deployment & Rollback |
| Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability. | +2.5 pts | Medium | Observability |
| 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. | +2.4 pts | Medium | Architecture documentation |
| Resolve the 3 CommentedOutCode finding(s) in Explicit Debt — start with AuthorizationBehaviour.cs, IdentityDependencies.cs, BaseRepo.cs. | +1.0 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.cs | 4.3 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| CleanArchitecture.Persistence/Repo/BaseRepo.cs | 6.7 | Mixed | Explicit Debt: CommentedOutCode |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| CleanArchitecture.Application/Behaviors/AuthorizationJWTBehaviour.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| CleanArchitecture.Application/Features/Auth/Handlers/Queries/AuthQueryHandler.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| CleanArchitecture.Identity/Services/CurrentUser.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| CleanArchitecture.Identity/IdentityDependencies.cs | 8.2 | Near-clean | Explicit Debt: CommentedOutCode |
| CleanArchitecture.Api/Base/AppControllerBase.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
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 79 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 79 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, 115 of 128 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
- 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 scored — the test tier(s) built and ran but no tests were discovered, so reliability couldn't be exercised.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 27 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 27 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
- D18 Solution Shape — 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. `dotnet build` reported 1 error(s), and the diagnostics it printed were: NETSDK1004: Assets file 'CleanArchitecture.Api/obj/project.assets.json' not found. Run a NuGet package restore to generate this file.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
- 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 — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — 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. 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.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `CleanArchitecture.Api/Resources/ar-EG.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (27 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 27 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D39 IL Efficiency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AXR1 Runtime accessibility — not measured this run — 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 DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — cleanarchitecture.mvc Warning pull access denied for cleanarchitecture-mvc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied cleanarchitecture.api Built cleanarchitecture.mvc Built container .-docker-login-1 exited (0); runtime evidence skipped.
- X2 Cancellation propagation — 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. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was AuthorizationBehaviour.Handle at 44.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with AuthorizationBehaviour.Handle (cognitive 44). — Refactoring it lifts Cognitive Complexity from 8.8 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
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with BaseRepo.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with AppControllerBase.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with QueryableExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
8 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 10 classes have LCOM4 above 3.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 258 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 32 direct `PackageReference`(s), and 218 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
8 deducted debt markers + unmeasured dead symbols across 2917 LoC in the .NET projects (1.0/KLoC) → score 8.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AuthorizationBehaviour.cs, AuthorizationJWTBehaviour.cs, AuthQueryHandler.cs. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 CommentedOutCode finding(s) in Explicit Debt — start with AuthorizationBehaviour.cs, IdentityDependencies.cs, BaseRepo.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with ErrorHandlerMiddleware.cs. — One of this dimension's main actionable groups (1 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
8 projects, 84 source files, 2921 hand-written lines of code (2917 production / 4 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 1496 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 7 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 8 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 projects flagged as possibly oversized/incoherent.
D27 · Navigability
100 % of calls cross a namespace and 3 % go through an interface, but 97 % 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)
1 finding(s): 0 critical, 1 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 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 4 high, 4 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `CleanArchitecture.Api/Resources/de-DE.json` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
15 finding(s): 1 critical, 8 high, 6 medium, 0 low.
What to do
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 1 high, 4 medium, 2 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 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 8 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
AC2 · Forms & labels
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 5 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
- `IBaseRepo<T>` declares 47 members: `GetById`, `GetByIdAsync`, `GetAll`, `GetAllAsync`, `Find`, `FindInclude`, `FindAsync`, `FindNoTraking`, `FindNoTraking`, `FindNoTraking`, `FindNoTraking`, `FindNoTraking`, `FindAll`, `FindAlike`, `FindAll`, `FindAll`, `FindAllAsync`, `FindAllAsync`, `FindAllAsync`, `FindAllInclude`, `FindAllInclude`, `FindAllInclude`, `GetAllNolist`, `Add`, `AddAsync`, `AddRange`, `AddRangeAsync`, `Update`, `UpdateRange`, `Delete`, `DeleteRange`, `Attach`, `AttachRange`, `Count`, `Count`, `CountAsync`, `CountAsync`, `GetChildsAsync`, `isExist`, `Commit`, and 7 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 47 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — CleanArchitecture.Application/Contracts/Persistence/Repo/IBaseRepo.cs:6
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `HandleRequirementAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — CleanArchitecture.Identity/Helpers/Filters/PermissionAuthorizationHandler.cs:12
- `AddInfrustructureDependencies` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — CleanArchitecture.Infrustructure/InfrustructureDependencies.cs:8
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×14) — CleanArchitecture.Application/ApplicationDependencies.cs:22, CleanArchitecture.Application/ApplicationDependencies.cs:30, CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.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
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1224 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:13
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `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. — CleanArchitecture.Identity/IdentityDependencies.cs:46
- `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. — REDACTED:89
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×2) — CleanArchitecture.Api/Program.cs:9, CleanArchitecture.Mvc/Program.cs:1
What to do
- Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
- Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
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 19/59 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×39) — CleanArchitecture.Persistence/AuditableDbContext.cs:12, CleanArchitecture.Persistence/Repo/BaseRepo.cs:23, CleanArchitecture.Persistence/Repo/BaseRepo.cs:30, …
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
- `_localizer["DearUser"]` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — CleanArchitecture.Identity/Services/EmailsService.cs:39
- `message` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — CleanArchitecture.Identity/Services/EmailsService.cs:40
- `_localizer["BestRegards"]` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — CleanArchitecture.Identity/Services/EmailsService.cs:41
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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
- `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. — CleanArchitecture.Identity/Helpers/AddIdentityOptions.cs:36
What to do
- Rethrow loses stack trace (`throw ex;`)
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×2) — CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs:95, CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs:99
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 59% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36% | Weak — gated by D9, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Strong | Solid. |
| Accessibility | 80% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 33 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — cleanarchitecture.mvc Warning pull access denied for cleanarchitecture-mvc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied cleanarchitecture.api Built cleanarchitecture.mvc Built container .-docker-login-1 exited (0); 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.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No tests discovered
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,917 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 (25 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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.
- D39 IL Efficiency — IL not measured — the target did not build
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 4 CQRS handler(s)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.cs:13
- WriteOnlyPrivateField CleanArchitecture.Application/Behaviors/AuthorizationJWTBehaviour.cs:11
- WriteOnlyPrivateField CleanArchitecture.Application/Features/Auth/Handlers/Queries/AuthQueryHandler.cs:7
- WriteOnlyPrivateField CleanArchitecture.Identity/Services/CurrentUser.cs:12
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 73 finding(s)
- Async method without CancellationToken: SaveChangesAsync CleanArchitecture.Persistence/AuditableDbContext.cs:12
- Async method without CancellationToken: GetAllAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:23
- Async method without CancellationToken: GetByIdAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:30
- Async method without CancellationToken: FindAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:73
- Async method without CancellationToken: FindAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:74
- Async method without CancellationToken: FindAllAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:128
- Async method without CancellationToken: FindAllAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:129
- Async method without CancellationToken: FindAllAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:140
- Async method without CancellationToken: FindAllAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:145
- Async method without CancellationToken: AddAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:208
- Async method without CancellationToken: AddRangeAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:222
- Async method without CancellationToken: CountAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:269
- Async method without CancellationToken: CountAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:274
- Async method without CancellationToken: GetChildsAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:279
- Async method without CancellationToken: IsExistAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:339
- Async method without CancellationToken: SaveChangesAsync CleanArchitecture.Persistence/Repo/BaseRepo.cs:344
- Async method without CancellationToken: ToPaginatedListAsync CleanArchitecture.Application/Extenstions/QueryableExtensions.cs:9
- Async method without CancellationToken: ToPaginatedTableListAsync CleanArchitecture.Application/Extenstions/QueryableExtensions.cs:28
- Async method without CancellationToken: SendResetPasswordCode CleanArchitecture.Identity/Services/AuthService.cs:113
- Async method without CancellationToken: ConfirmAndResetPassword CleanArchitecture.Identity/Services/AuthService.cs:150
- Async method without CancellationToken: SendEmail CleanArchitecture.Identity/Services/EmailsService.cs:26
- Async method without CancellationToken: GetUserNameAsync REDACTED:32
- Async method without CancellationToken: HasClaim REDACTED:61
- Async method without CancellationToken: Login CleanArchitecture.Api/Controllers/AuthController.cs:16
- Async method without CancellationToken: Register CleanArchitecture.Api/Controllers/AuthController.cs:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CommentedOutCode CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.cs:33
- CommentedOutCode CleanArchitecture.Identity/IdentityDependencies.cs:77
- CommentedOutCode CleanArchitecture.Persistence/Repo/BaseRepo.cs:332
- Untrusted text written into markup unescaped CleanArchitecture.Identity/Services/EmailsService.cs:39
- Untrusted text written into markup unescaped CleanArchitecture.Identity/Services/EmailsService.cs:40
- Untrusted text written into markup unescaped CleanArchitecture.Identity/Services/EmailsService.cs:41
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Accessibility enforcement below the top rung
- TodoComment CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs:35
- AuthorizationBehaviour.Handle (cognitive 44) CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.cs:25
- REDACTED
- REDACTED
- TooManyMethods: BaseRepo CleanArchitecture.Persistence/Repo/BaseRepo.cs
- Duplicated block (14 lines × 2) CleanArchitecture.Api/Base/AppControllerBase.cs:43
- Duplicated block (8 lines × 2) CleanArchitecture.Application/Extenstions/QueryableExtensions.cs:13
- Coverage not measured — test suite did not build
- Fake-async — async method never awaits CleanArchitecture.Identity/Helpers/Filters/PermissionAuthorizationHandler.cs:12
- Hollow method — returns a constant without doing the work CleanArchitecture.Infrustructure/InfrustructureDependencies.cs:8
- Token validation disabled REDACTED:89
- NuGet dependencies are not locked
- Rethrow loses stack trace (`throw ex;`) CleanArchitecture.Identity/Helpers/AddIdentityOptions.cs:36
Minor — 36 finding(s)
- Commented-out code CleanArchitecture.Application/ApplicationDependencies.cs:22
- Commented-out code CleanArchitecture.Application/ApplicationDependencies.cs:30
- Commented-out code CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.cs:36
- Commented-out code CleanArchitecture.Application/Behaviors/AuthorizationBehaviour.cs:108
- Commented-out code CleanArchitecture.Application/Contracts/Persistence/Repo/IBaseRepo.cs:43
- Commented-out code CleanArchitecture.Application/Contracts/Persistence/Repo/IBaseRepo.cs:45
- Commented-out code CleanArchitecture.Application/Contracts/Persistence/Repo/IBaseRepo.cs:59
- Commented-out code CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs:30
- Commented-out code CleanArchitecture.Identity/IdentityDbContext.cs:18
- Commented-out code CleanArchitecture.Identity/IdentityDependencies.cs:24
- Commented-out code CleanArchitecture.Identity/IdentityDependencies.cs:79
- Commented-out code CleanArchitecture.Identity/IdentityDependencies.cs:80
- Commented-out code CleanArchitecture.Persistence/Repo/BaseRepo.cs:212
- Commented-out code CleanArchitecture.Persistence/Repo/BaseRepo.cs:230
- No security response headers detected
- No security response headers detected CleanArchitecture.Api/Program.cs:9
- No security response headers detected CleanArchitecture.Mvc/Program.cs:1
- REDACTED
- REDACTED
- Interpolated log message defeats structured logging CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs:95
- Interpolated log message defeats structured logging CleanArchitecture.Application/Middleware/ErrorHandlerMiddleware.cs:99
- Fat interface: IBaseRepo<T> (47 members) CleanArchitecture.Application/Contracts/Persistence/Repo/IBaseRepo.cs:6
- No ADRs found
- Pass-through layer CleanArchitecture.Application/Features/Roles/Handlers/Commands/RolesCommandHandler.cs:9
- REDACTED
- REDACTED
- No tests found
- No ADRs
- No src/ separation
- No tests/ separation
- No SAST REDACTED:6
- No dependency-update automation REDACTED:13
- No rollback/health safety
- OIDC metadata fetched over HTTP CleanArchitecture.Identity/IdentityDependencies.cs:46
- Not all async methods take a CancellationToken
- Silent fallback default in catch CleanArchitecture.Application/Middleware/Localization/JsonStringLocalizer.cs:102
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-02065e371c844d019bfff1c59632bd7a/history.json --exit-code 0 --source . | 0 | 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-02065e371c844d019bfff1c59632bd7a/tree.json --exit-code 0 --source . | 0 | 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 CleanArchitecture.Identity/Migrations --exclude CleanArchitecture.Persistence/Migrations . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list CleanArchitecture.sln package --vulnerable --include-transitive --format json | 15 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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-3cc6400962b34163b125d221e1883f8e | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 9 field(s)
- LoginCommand.Email CleanArchitecture.Application/Features/Auth/Requests/Commands/LoginCommand.cs:9
- RegisterCommand.Email CleanArchitecture.Application/Features/Auth/Requests/Commands/RegisterCommand.cs:11
- ResetPasswordCommand.Email CleanArchitecture.Application/Features/Auth/Requests/Commands/ResetPasswordCommand.cs:8
- SendResetPasswordCommand.Email CleanArchitecture.Application/Features/Auth/Requests/Commands/SendResetPasswordCommand.cs:8
- LoginResult.Email CleanArchitecture.Application/Features/Auth/Results/LoginResult.cs:7
- SendEmailCommand.Email CleanArchitecture.Application/Features/Emails/Requests/Commands/SendEmailCommand.cs:8
- Employee.Email CleanArchitecture.Application/Models/Identity/Employee.cs:6
- EmailSettings.FromEmail CleanArchitecture.Identity/Helpers/EmailSettings.cs:7
- EmailsService._emailSettings CleanArchitecture.Identity/Services/EmailsService.cs:13
Name — 6 field(s)
- RegisterCommand.FirstName CleanArchitecture.Application/Features/Auth/Requests/Commands/RegisterCommand.cs:9
- RegisterCommand.LastName CleanArchitecture.Application/Features/Auth/Requests/Commands/RegisterCommand.cs:10
- Employee.Firstname CleanArchitecture.Application/Models/Identity/Employee.cs:7
- Employee.Lastname CleanArchitecture.Application/Models/Identity/Employee.cs:8
- ApplicationUser.FirstName CleanArchitecture.Identity/Entities/ApplicationUser.cs:7
- ApplicationUser.LastName CleanArchitecture.Identity/Entities/ApplicationUser.cs:8