Executive summary
jzwo/CleanAdmin falls short of our standard for a template or a sample, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 49 out of 100 and is rated Adequate, and 40 of its 46 critical findings are security problems.
Accessibility, at 39, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the five exposed passwords or keys and switching the old ones off, worth about 4 points. Fixing focus, motion and contrast would lift Accessibility itself, worth about 5 points. Raising Accessibility to 58 would lift the score to about 55.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nine passwords or keys in the code's history and five in the code are open to anyone who can read the repository, and five known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, replacing each exposed password or key and updating the vulnerable packages would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command. The three sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 13,313 lines, about €17,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Accessibility rose from 39 to 58, the lowest score rated Strong, the score would rise from 49 to about 55.
New since the last survey: 9 findings
- Cyclomatic Complexity · top-level statements (cyclomatic 20) REDACTED
- Cognitive Complexity · top-level statements (cognitive 29) REDACTED
- Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
- Rich vs anemic model · Anemic entity: UserRole src/CleanAdmin.Domain/AggregatesModel/UserAggregate/UserRole.cs
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Low contrast colour pair in CSS (4.4:1) src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Low contrast colour pair in CSS (3.2:1) src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Low contrast colour pair in CSS (3.2:1) src/CleanAdmin.Web/wwwroot/styles/light.css
Fixed since the last survey: 287 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Cancellation propagation · Async method without CancellationToken: NotifyLoginAsync src/CleanAdmin.Web.Client/Infrastructure/Auth/JwtAuthStateProvider.cs
- Cancellation propagation · Async method without CancellationToken: NotifyLogoutAsync src/CleanAdmin.Web.Client/Infrastructure/Auth/JwtAuthStateProvider.cs
- Cancellation propagation · Async method without CancellationToken: GetThemeAsync src/CleanAdmin.Web.Client/Services/ThemeService.cs
- Cancellation propagation · Async method without CancellationToken: GetIsDarkAsync src/CleanAdmin.Web.Client/Services/ThemeService.cs
- Cancellation propagation · Async method without CancellationToken: SetThemeAsync src/CleanAdmin.Web.Client/Services/ThemeService.cs
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/light.css
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,900 to €29,000, for 98 to 305 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very 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 49. 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: 13,313 lines of product code |
| Comment lines | The estimate prices 11,337 lines. Comment lines count towards the size of 13,313 lines but aren't priced as work. |
| 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 CleanAdmin.ApiService | 3 CleanAdmin.ApiService.Application.Hubs | 4 CleanAdmin.ApiService.Auth.ApiKey | 5 CleanAdmin.ApiService.Clients | 6 CleanAdmin.ApiService.Endpoints.AiChat | 7 CleanAdmin.ApiService.Extensions | 8 CleanAdmin.Domain.AggregatesModel.OrderAggregate | 9 CleanAdmin.Domain.Common | 10 CleanAdmin.Infrastructure.Ai | 11 CleanAdmin.Infrastructure.Utils | 12 CleanAdmin.Shared | 13 CleanAdmin.Web.Client.Infrastructure.Auth | 14 CleanAdmin.ApiService.Application.IntegrationEventHandlers | 15 CleanAdmin.Domain.AggregatesModel.DeliverAggregate | 16 CleanAdmin.Domain.AggregatesModel.MenuAggregate | 17 CleanAdmin.Domain.AggregatesModel.RoleAggregate | 18 CleanAdmin.Web.Client.Infrastructure.Http | 19 CleanAdmin.ApiService.Endpoints.Roles | 20 CleanAdmin.Domain.AggregatesModel.UserAggregate | 21 CleanAdmin.ApiService.Auth | 22 CleanAdmin.ApiService.Auth.Permission | 23 CleanAdmin.ApiService.Endpoints.Authentication | 24 CleanAdmin.Domain.DomainEvents | 25 CleanAdmin.Infrastructure | 26 CleanAdmin.Infrastructure.EntityConfigurations | 27 CleanAdmin.ApiService.Application.DomainEventHandlers | 28 CleanAdmin.ApiService.Application.IntegrationEventConverters | 29 CleanAdmin.ApiService.Application.Queries.Menus | 30 CleanAdmin.ApiService.Application.Queries.Roles | 31 CleanAdmin.ApiService.Application.Queries.Users | 32 CleanAdmin.ApiService.Auth.Middlewares | 33 CleanAdmin.ApiService.Endpoints.Menus | 34 CleanAdmin.ApiService.Endpoints.Users | 35 CleanAdmin.Infrastructure.Repositories | 36 CleanAdmin.MigrationService | 37 CleanAdmin.ApiService.Application.Commands | 38 CleanAdmin.ApiService.Application.Commands.Menus | 39 CleanAdmin.ApiService.Application.Commands.Roles | 40 CleanAdmin.ApiService.Application.Commands.Users |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanAdmin.ApiService | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanAdmin.ApiService.Application.Hubs | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanAdmin.ApiService.Auth.ApiKey | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanAdmin.ApiService.Clients | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanAdmin.ApiService.Endpoints.AiChat | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanAdmin.ApiService.Extensions | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanAdmin.Domain.AggregatesModel.OrderAggregate | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanAdmin.Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanAdmin.Infrastructure.Ai | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanAdmin.Infrastructure.Utils | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanAdmin.Shared | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanAdmin.Web.Client.Infrastructure.Auth | ||||||||||||||||||||||||||||||||||||||||
| 14 CleanAdmin.ApiService.Application.IntegrationEventHandlers | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 CleanAdmin.Domain.AggregatesModel.DeliverAggregate | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 CleanAdmin.Domain.AggregatesModel.MenuAggregate | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 CleanAdmin.Domain.AggregatesModel.RoleAggregate | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 CleanAdmin.Web.Client.Infrastructure.Http | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 CleanAdmin.ApiService.Endpoints.Roles | 6 | |||||||||||||||||||||||||||||||||||||||
| 20 CleanAdmin.Domain.AggregatesModel.UserAggregate | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 CleanAdmin.ApiService.Auth | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 CleanAdmin.ApiService.Auth.Permission | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 CleanAdmin.ApiService.Endpoints.Authentication | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 CleanAdmin.Domain.DomainEvents | 2 | 4 | 5 | 5 | ||||||||||||||||||||||||||||||||||||
| 25 CleanAdmin.Infrastructure | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 CleanAdmin.Infrastructure.EntityConfigurations | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 CleanAdmin.ApiService.Application.DomainEventHandlers | 3 | 8 | ||||||||||||||||||||||||||||||||||||||
| 28 CleanAdmin.ApiService.Application.IntegrationEventConverters | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 CleanAdmin.ApiService.Application.Queries.Menus | 23 | 10 | ||||||||||||||||||||||||||||||||||||||
| 30 CleanAdmin.ApiService.Application.Queries.Roles | 6 | 5 | ||||||||||||||||||||||||||||||||||||||
| 31 CleanAdmin.ApiService.Application.Queries.Users | 6 | 12 | 11 | |||||||||||||||||||||||||||||||||||||
| 32 CleanAdmin.ApiService.Auth.Middlewares | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 CleanAdmin.ApiService.Endpoints.Menus | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 CleanAdmin.ApiService.Endpoints.Users | 3 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 35 CleanAdmin.Infrastructure.Repositories | 5 | |||||||||||||||||||||||||||||||||||||||
| 36 CleanAdmin.MigrationService | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 CleanAdmin.ApiService.Application.Commands | 4 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 38 CleanAdmin.ApiService.Application.Commands.Menus | 8 | 6 | ||||||||||||||||||||||||||||||||||||||
| 39 CleanAdmin.ApiService.Application.Commands.Roles | 5 | 4 | ||||||||||||||||||||||||||||||||||||||
| 40 CleanAdmin.ApiService.Application.Commands.Users | 4 | 1 | 11 | 2 | 9 |
14→8 CleanAdmin.ApiService.Application.IntegrationEventHandlers uses CleanAdmin.Domain.AggregatesModel.OrderAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Application.IntegrationEventHandlers uses a type in CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- The types involved
CleanAdmin.ApiService.Application.IntegrationEventHandlers.OrderPaidIntegrationEvent→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderId
- Direction
- CleanAdmin.ApiService.Application.IntegrationEventHandlers uses CleanAdmin.Domain.AggregatesModel.OrderAggregate, so a change to CleanAdmin.Domain.AggregatesModel.OrderAggregate can break CleanAdmin.ApiService.Application.IntegrationEventHandlers, while a change to CleanAdmin.ApiService.Application.IntegrationEventHandlers can't break CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.IntegrationEventHandlers uses a module listed above it, which is the healthy direction.
15→8 CleanAdmin.Domain.AggregatesModel.DeliverAggregate uses CleanAdmin.Domain.AggregatesModel.OrderAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Domain.AggregatesModel.DeliverAggregate uses a type in CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- The types involved
CleanAdmin.Domain.AggregatesModel.DeliverAggregate.DeliverRecord→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderId
- Direction
- CleanAdmin.Domain.AggregatesModel.DeliverAggregate uses CleanAdmin.Domain.AggregatesModel.OrderAggregate, so a change to CleanAdmin.Domain.AggregatesModel.OrderAggregate can break CleanAdmin.Domain.AggregatesModel.DeliverAggregate, while a change to CleanAdmin.Domain.AggregatesModel.DeliverAggregate can't break CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- Position
- Below the diagonal: CleanAdmin.Domain.AggregatesModel.DeliverAggregate uses a module listed above it, which is the healthy direction.
16→9 CleanAdmin.Domain.AggregatesModel.MenuAggregate uses CleanAdmin.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate uses a type in CleanAdmin.Domain.Common.
- The types involved
CleanAdmin.Domain.AggregatesModel.MenuAggregate.Menu→CleanAdmin.Domain.Common.ISoftDeletable
- Direction
- CleanAdmin.Domain.AggregatesModel.MenuAggregate uses CleanAdmin.Domain.Common, so a change to CleanAdmin.Domain.Common can break CleanAdmin.Domain.AggregatesModel.MenuAggregate, while a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can't break CleanAdmin.Domain.Common.
- Position
- Below the diagonal: CleanAdmin.Domain.AggregatesModel.MenuAggregate uses a module listed above it, which is the healthy direction.
17→9 CleanAdmin.Domain.AggregatesModel.RoleAggregate uses CleanAdmin.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate uses a type in CleanAdmin.Domain.Common.
- The types involved
CleanAdmin.Domain.AggregatesModel.RoleAggregate.Role→CleanAdmin.Domain.Common.ISoftDeletable
- Direction
- CleanAdmin.Domain.AggregatesModel.RoleAggregate uses CleanAdmin.Domain.Common, so a change to CleanAdmin.Domain.Common can break CleanAdmin.Domain.AggregatesModel.RoleAggregate, while a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can't break CleanAdmin.Domain.Common.
- Position
- Below the diagonal: CleanAdmin.Domain.AggregatesModel.RoleAggregate uses a module listed above it, which is the healthy direction.
18→13 CleanAdmin.Web.Client.Infrastructure.Http uses CleanAdmin.Web.Client.Infrastructure.Auth✕
- Connections
- 2 pairs of types, where a type in CleanAdmin.Web.Client.Infrastructure.Http uses a type in CleanAdmin.Web.Client.Infrastructure.Auth.
- The types involved
CleanAdmin.Web.Client.Infrastructure.Http.AccessTokenProvider→CleanAdmin.Web.Client.Infrastructure.Auth.IUserTokenRefresherCleanAdmin.Web.Client.Infrastructure.Http.AccessTokenProvider→CleanAdmin.Web.Client.Infrastructure.Auth.IUserTokenStore
- Direction
- CleanAdmin.Web.Client.Infrastructure.Http uses CleanAdmin.Web.Client.Infrastructure.Auth, so a change to CleanAdmin.Web.Client.Infrastructure.Auth can break CleanAdmin.Web.Client.Infrastructure.Http, while a change to CleanAdmin.Web.Client.Infrastructure.Http can't break CleanAdmin.Web.Client.Infrastructure.Auth.
- Position
- Below the diagonal: CleanAdmin.Web.Client.Infrastructure.Http uses a module listed above it, which is the healthy direction.
19→17 CleanAdmin.ApiService.Endpoints.Roles uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 6 pairs of types, where a type in CleanAdmin.ApiService.Endpoints.Roles uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.ApiService.Endpoints.Roles.CreateRoleResponse→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Roles.DeleteRoleRequest→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Roles.RolePermissionsRequest→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Roles.RolePermissionsResponse→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Roles.UpdateRoleInfoRequest→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Roles.UpdateRolePermissionsRequest→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.ApiService.Endpoints.Roles uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.ApiService.Endpoints.Roles, while a change to CleanAdmin.ApiService.Endpoints.Roles can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Roles uses a module listed above it, which is the healthy direction.
20→9 CleanAdmin.Domain.AggregatesModel.UserAggregate uses CleanAdmin.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Domain.AggregatesModel.UserAggregate uses a type in CleanAdmin.Domain.Common.
- The types involved
CleanAdmin.Domain.AggregatesModel.UserAggregate.User→CleanAdmin.Domain.Common.ISoftDeletable
- Direction
- CleanAdmin.Domain.AggregatesModel.UserAggregate uses CleanAdmin.Domain.Common, so a change to CleanAdmin.Domain.Common can break CleanAdmin.Domain.AggregatesModel.UserAggregate, while a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can't break CleanAdmin.Domain.Common.
- Position
- Below the diagonal: CleanAdmin.Domain.AggregatesModel.UserAggregate uses a module listed above it, which is the healthy direction.
20→17 CleanAdmin.Domain.AggregatesModel.UserAggregate uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 3 pairs of types, where a type in CleanAdmin.Domain.AggregatesModel.UserAggregate uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.Domain.AggregatesModel.UserAggregate.User→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.Domain.AggregatesModel.UserAggregate.UserPermission→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.Domain.AggregatesModel.UserAggregate.UserRole→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.Domain.AggregatesModel.UserAggregate uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.Domain.AggregatesModel.UserAggregate, while a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.Domain.AggregatesModel.UserAggregate uses a module listed above it, which is the healthy direction.
21→20 CleanAdmin.ApiService.Auth uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 2 pairs of types, where a type in CleanAdmin.ApiService.Auth uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.ApiService.Auth.CurrentUser→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Auth.ICurrentUser→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserId
- Direction
- CleanAdmin.ApiService.Auth uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.ApiService.Auth, while a change to CleanAdmin.ApiService.Auth can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Auth uses a module listed above it, which is the healthy direction.
22→20 CleanAdmin.ApiService.Auth.Permission uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Auth.Permission uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.ApiService.Auth.Permission.UserPermissionService→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserId
- Direction
- CleanAdmin.ApiService.Auth.Permission uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.ApiService.Auth.Permission, while a change to CleanAdmin.ApiService.Auth.Permission can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Auth.Permission uses a module listed above it, which is the healthy direction.
23→20 CleanAdmin.ApiService.Endpoints.Authentication uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Endpoints.Authentication uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.ApiService.Endpoints.Authentication.RegisterUserResponse→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserId
- Direction
- CleanAdmin.ApiService.Endpoints.Authentication uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.ApiService.Endpoints.Authentication, while a change to CleanAdmin.ApiService.Endpoints.Authentication can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Authentication uses a module listed above it, which is the healthy direction.
24→8 CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.OrderAggregate✕
- Connections
- 2 pairs of types, where a type in CleanAdmin.Domain.DomainEvents uses a type in CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- The types involved
CleanAdmin.Domain.DomainEvents.OrderCreatedDomainEvent→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderCleanAdmin.Domain.DomainEvents.OrderPaidDomainEvent→CleanAdmin.Domain.AggregatesModel.OrderAggregate.Order
- Direction
- CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.OrderAggregate, so a change to CleanAdmin.Domain.AggregatesModel.OrderAggregate can break CleanAdmin.Domain.DomainEvents, while a change to CleanAdmin.Domain.DomainEvents can't break CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- Position
- Below the diagonal: CleanAdmin.Domain.DomainEvents uses a module listed above it, which is the healthy direction.
24→16 CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.MenuAggregate✕
- Connections
- 4 pairs of types, where a type in CleanAdmin.Domain.DomainEvents uses a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- The types involved
CleanAdmin.Domain.DomainEvents.MenuCreatedDomainEvent→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuCleanAdmin.Domain.DomainEvents.MenuDeletedDomainEvent→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuCleanAdmin.Domain.DomainEvents.MenuSortOrderChangedDomainEvent→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuCleanAdmin.Domain.DomainEvents.MenuUpdatedDomainEvent→CleanAdmin.Domain.AggregatesModel.MenuAggregate.Menu
- Direction
- CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.MenuAggregate, so a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can break CleanAdmin.Domain.DomainEvents, while a change to CleanAdmin.Domain.DomainEvents can't break CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- Position
- Below the diagonal: CleanAdmin.Domain.DomainEvents uses a module listed above it, which is the healthy direction.
24→17 CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 5 pairs of types, where a type in CleanAdmin.Domain.DomainEvents uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.Domain.DomainEvents.RoleDeletedDomainEvent→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleCleanAdmin.Domain.DomainEvents.RoleInfoChangedDomainEvent→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleCleanAdmin.Domain.DomainEvents.RoleMenusChangedDomainEvent→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleCleanAdmin.Domain.DomainEvents.RolePermissionChangedDomainEvent→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleCleanAdmin.Domain.DomainEvents.RolePermissionsChangedDomainEvent→CleanAdmin.Domain.AggregatesModel.RoleAggregate.Role
- Direction
- CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.Domain.DomainEvents, while a change to CleanAdmin.Domain.DomainEvents can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.Domain.DomainEvents uses a module listed above it, which is the healthy direction.
24→20 CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 5 pairs of types, where a type in CleanAdmin.Domain.DomainEvents uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.Domain.DomainEvents.UserCreatedDomainEvent→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserCleanAdmin.Domain.DomainEvents.UserDeletedDomainEvent→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserCleanAdmin.Domain.DomainEvents.UserInfoUpdatedDomainEvent→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserCleanAdmin.Domain.DomainEvents.UserLoginDomainEvent→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserCleanAdmin.Domain.DomainEvents.UserPasswordChangedDomainEvent→CleanAdmin.Domain.AggregatesModel.UserAggregate.User
- Direction
- CleanAdmin.Domain.DomainEvents uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.Domain.DomainEvents, while a change to CleanAdmin.Domain.DomainEvents can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.Domain.DomainEvents uses a module listed above it, which is the healthy direction.
25→16 CleanAdmin.Infrastructure uses CleanAdmin.Domain.AggregatesModel.MenuAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure uses a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- The types involved
CleanAdmin.Infrastructure.ApplicationDbContext→CleanAdmin.Domain.AggregatesModel.MenuAggregate.Menu
- Direction
- CleanAdmin.Infrastructure uses CleanAdmin.Domain.AggregatesModel.MenuAggregate, so a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can break CleanAdmin.Infrastructure, while a change to CleanAdmin.Infrastructure can't break CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure uses a module listed above it, which is the healthy direction.
25→17 CleanAdmin.Infrastructure uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.Infrastructure.ApplicationDbContext→CleanAdmin.Domain.AggregatesModel.RoleAggregate.Role
- Direction
- CleanAdmin.Infrastructure uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.Infrastructure, while a change to CleanAdmin.Infrastructure can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure uses a module listed above it, which is the healthy direction.
25→20 CleanAdmin.Infrastructure uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.Infrastructure.ApplicationDbContext→CleanAdmin.Domain.AggregatesModel.UserAggregate.User
- Direction
- CleanAdmin.Infrastructure uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.Infrastructure, while a change to CleanAdmin.Infrastructure can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure uses a module listed above it, which is the healthy direction.
26→8 CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.OrderAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure.EntityConfigurations uses a type in CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- The types involved
CleanAdmin.Infrastructure.EntityConfigurations.OrderEntityTypeConfiguration→CleanAdmin.Domain.AggregatesModel.OrderAggregate.Order
- Direction
- CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.OrderAggregate, so a change to CleanAdmin.Domain.AggregatesModel.OrderAggregate can break CleanAdmin.Infrastructure.EntityConfigurations, while a change to CleanAdmin.Infrastructure.EntityConfigurations can't break CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure.EntityConfigurations uses a module listed above it, which is the healthy direction.
26→15 CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.DeliverAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure.EntityConfigurations uses a type in CleanAdmin.Domain.AggregatesModel.DeliverAggregate.
- The types involved
CleanAdmin.Infrastructure.EntityConfigurations.DeliverRecordConfiguration→CleanAdmin.Domain.AggregatesModel.DeliverAggregate.DeliverRecord
- Direction
- CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.DeliverAggregate, so a change to CleanAdmin.Domain.AggregatesModel.DeliverAggregate can break CleanAdmin.Infrastructure.EntityConfigurations, while a change to CleanAdmin.Infrastructure.EntityConfigurations can't break CleanAdmin.Domain.AggregatesModel.DeliverAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure.EntityConfigurations uses a module listed above it, which is the healthy direction.
26→16 CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.MenuAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure.EntityConfigurations uses a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- The types involved
CleanAdmin.Infrastructure.EntityConfigurations.MenuEntityTypeConfiguration→CleanAdmin.Domain.AggregatesModel.MenuAggregate.Menu
- Direction
- CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.MenuAggregate, so a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can break CleanAdmin.Infrastructure.EntityConfigurations, while a change to CleanAdmin.Infrastructure.EntityConfigurations can't break CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure.EntityConfigurations uses a module listed above it, which is the healthy direction.
26→17 CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure.EntityConfigurations uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.Infrastructure.EntityConfigurations.RoleEntityTypeConfiguration→CleanAdmin.Domain.AggregatesModel.RoleAggregate.Role
- Direction
- CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.Infrastructure.EntityConfigurations, while a change to CleanAdmin.Infrastructure.EntityConfigurations can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure.EntityConfigurations uses a module listed above it, which is the healthy direction.
26→20 CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.Infrastructure.EntityConfigurations uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.Infrastructure.EntityConfigurations.UserEntityTypeConfiguration→CleanAdmin.Domain.AggregatesModel.UserAggregate.User
- Direction
- CleanAdmin.Infrastructure.EntityConfigurations uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.Infrastructure.EntityConfigurations, while a change to CleanAdmin.Infrastructure.EntityConfigurations can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.Infrastructure.EntityConfigurations uses a module listed above it, which is the healthy direction.
27→22 CleanAdmin.ApiService.Application.DomainEventHandlers uses CleanAdmin.ApiService.Auth.Permission✕
- Connections
- 3 pairs of types, where a type in CleanAdmin.ApiService.Application.DomainEventHandlers uses a type in CleanAdmin.ApiService.Auth.Permission.
- The types involved
CleanAdmin.ApiService.Application.DomainEventHandlers.RolePermissionsChangedDomainEventHandlerForRefreshUsersPermissions→CleanAdmin.ApiService.Auth.Permission.UserPermissionServiceCleanAdmin.ApiService.Application.DomainEventHandlers.UserDeletedDomainEventHandlerForInvalidateUserPermissionCache→CleanAdmin.ApiService.Auth.Permission.UserPermissionServiceCleanAdmin.ApiService.Application.DomainEventHandlers.UserInfoUpdatedDomainEventHandlerForInvalidateUserPermissionCache→CleanAdmin.ApiService.Auth.Permission.UserPermissionService
- Direction
- CleanAdmin.ApiService.Application.DomainEventHandlers uses CleanAdmin.ApiService.Auth.Permission, so a change to CleanAdmin.ApiService.Auth.Permission can break CleanAdmin.ApiService.Application.DomainEventHandlers, while a change to CleanAdmin.ApiService.Application.DomainEventHandlers can't break CleanAdmin.ApiService.Auth.Permission.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.DomainEventHandlers uses a module listed above it, which is the healthy direction.
27→24 CleanAdmin.ApiService.Application.DomainEventHandlers uses CleanAdmin.Domain.DomainEvents✕
- Connections
- 8 pairs of types, where a type in CleanAdmin.ApiService.Application.DomainEventHandlers uses a type in CleanAdmin.Domain.DomainEvents.
- The types involved
CleanAdmin.ApiService.Application.DomainEventHandlers.OrderCreatedDomainEventHandler→CleanAdmin.Domain.DomainEvents.OrderCreatedDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.RoleDeletedDomainEventHandler→CleanAdmin.Domain.DomainEvents.RoleDeletedDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.RolePermissionsChangedDomainEventHandlerForRefreshUsersPermissions→CleanAdmin.Domain.DomainEvents.RolePermissionsChangedDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.UserCreatedDomainEventHandler→CleanAdmin.Domain.DomainEvents.UserCreatedDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.UserDeletedDomainEventHandlerForInvalidateUserPermissionCache→CleanAdmin.Domain.DomainEvents.UserDeletedDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.UserInfoUpdatedDomainEventHandlerForInvalidateUserPermissionCache→CleanAdmin.Domain.DomainEvents.UserInfoUpdatedDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.UserLoginDomainEventHandler→CleanAdmin.Domain.DomainEvents.UserLoginDomainEventCleanAdmin.ApiService.Application.DomainEventHandlers.UserPasswordChangedDomainEventHandler→CleanAdmin.Domain.DomainEvents.UserPasswordChangedDomainEvent
- Direction
- CleanAdmin.ApiService.Application.DomainEventHandlers uses CleanAdmin.Domain.DomainEvents, so a change to CleanAdmin.Domain.DomainEvents can break CleanAdmin.ApiService.Application.DomainEventHandlers, while a change to CleanAdmin.ApiService.Application.DomainEventHandlers can't break CleanAdmin.Domain.DomainEvents.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.DomainEventHandlers uses a module listed above it, which is the healthy direction.
28→14 CleanAdmin.ApiService.Application.IntegrationEventConverters uses CleanAdmin.ApiService.Application.IntegrationEventHandlers✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Application.IntegrationEventConverters uses a type in CleanAdmin.ApiService.Application.IntegrationEventHandlers.
- The types involved
CleanAdmin.ApiService.Application.IntegrationEventConverters.OrderPaidIntegrationEventConverter→CleanAdmin.ApiService.Application.IntegrationEventHandlers.OrderPaidIntegrationEvent
- Direction
- CleanAdmin.ApiService.Application.IntegrationEventConverters uses CleanAdmin.ApiService.Application.IntegrationEventHandlers, so a change to CleanAdmin.ApiService.Application.IntegrationEventHandlers can break CleanAdmin.ApiService.Application.IntegrationEventConverters, while a change to CleanAdmin.ApiService.Application.IntegrationEventConverters can't break CleanAdmin.ApiService.Application.IntegrationEventHandlers.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.IntegrationEventConverters uses a module listed above it, which is the healthy direction.
28→24 CleanAdmin.ApiService.Application.IntegrationEventConverters uses CleanAdmin.Domain.DomainEvents✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Application.IntegrationEventConverters uses a type in CleanAdmin.Domain.DomainEvents.
- The types involved
CleanAdmin.ApiService.Application.IntegrationEventConverters.OrderPaidIntegrationEventConverter→CleanAdmin.Domain.DomainEvents.OrderPaidDomainEvent
- Direction
- CleanAdmin.ApiService.Application.IntegrationEventConverters uses CleanAdmin.Domain.DomainEvents, so a change to CleanAdmin.Domain.DomainEvents can break CleanAdmin.ApiService.Application.IntegrationEventConverters, while a change to CleanAdmin.ApiService.Application.IntegrationEventConverters can't break CleanAdmin.Domain.DomainEvents.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.IntegrationEventConverters uses a module listed above it, which is the healthy direction.
29→16 CleanAdmin.ApiService.Application.Queries.Menus uses CleanAdmin.Domain.AggregatesModel.MenuAggregate✕
- Connections
- 23 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Menus uses a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- The types involved
CleanAdmin.ApiService.Application.Queries.Menus.CheckMenuCircularReferenceQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuHasChildrenQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuNameConflictQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuRoutePathUniqueQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuSortOrderConflictQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.CheckParentMenuExistsQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.GetMenuListQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuStatusCleanAdmin.ApiService.Application.Queries.Menus.GetMenuListQuery→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuTypeCleanAdmin.ApiService.Application.Queries.Menus.GetMenuPermissionTreeQueryHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuCleanAdmin.ApiService.Application.Queries.Menus.GetMenuPermissionTreeQueryHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.GetMenuTreeQueryHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuCleanAdmin.ApiService.Application.Queries.Menus.GetMenuTreeQueryHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.GetNavigationMenusByPermissionCodesQueryHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuCleanAdmin.ApiService.Application.Queries.Menus.GetNavigationMenusByPermissionCodesQueryHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.MenuListItemDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.MenuListItemDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuStatusCleanAdmin.ApiService.Application.Queries.Menus.MenuListItemDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuTypeCleanAdmin.ApiService.Application.Queries.Menus.MenuPermissionTreeNodeDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.MenuTreeNodeDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.MenuTreeNodeDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuStatusCleanAdmin.ApiService.Application.Queries.Menus.MenuTreeNodeDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuTypeCleanAdmin.ApiService.Application.Queries.Menus.UserMenuTreeNodeDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Queries.Menus.UserMenuTreeNodeDto→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuType
- Direction
- CleanAdmin.ApiService.Application.Queries.Menus uses CleanAdmin.Domain.AggregatesModel.MenuAggregate, so a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can break CleanAdmin.ApiService.Application.Queries.Menus, while a change to CleanAdmin.ApiService.Application.Queries.Menus can't break CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Menus uses a module listed above it, which is the healthy direction.
29→25 CleanAdmin.ApiService.Application.Queries.Menus uses CleanAdmin.Infrastructure✕
- Connections
- 10 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Menus uses a type in CleanAdmin.Infrastructure.
- The types involved
CleanAdmin.ApiService.Application.Queries.Menus.CheckMenuCircularReferenceQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuHasChildrenQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuNameConflictQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuRoutePathUniqueQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.CheckMenuSortOrderConflictQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.CheckParentMenuExistsQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.GetMenuListQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.GetMenuPermissionTreeQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.GetMenuTreeQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Menus.GetNavigationMenusByPermissionCodesQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContext
- Direction
- CleanAdmin.ApiService.Application.Queries.Menus uses CleanAdmin.Infrastructure, so a change to CleanAdmin.Infrastructure can break CleanAdmin.ApiService.Application.Queries.Menus, while a change to CleanAdmin.ApiService.Application.Queries.Menus can't break CleanAdmin.Infrastructure.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Menus uses a module listed above it, which is the healthy direction.
30→17 CleanAdmin.ApiService.Application.Queries.Roles uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 6 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Roles uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.ApiService.Application.Queries.Roles.CheckRoleNameConflictQuery→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Roles.GetRoleDetailsByIdsQuery→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Roles.GetRolePermissionsQuery→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Roles.RoleDetailDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Roles.RoleListItemDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Roles.RolePermissionsDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.ApiService.Application.Queries.Roles uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.ApiService.Application.Queries.Roles, while a change to CleanAdmin.ApiService.Application.Queries.Roles can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Roles uses a module listed above it, which is the healthy direction.
30→25 CleanAdmin.ApiService.Application.Queries.Roles uses CleanAdmin.Infrastructure✕
- Connections
- 5 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Roles uses a type in CleanAdmin.Infrastructure.
- The types involved
CleanAdmin.ApiService.Application.Queries.Roles.CheckRoleExistsByNameQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Roles.CheckRoleNameConflictQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Roles.GetRoleDetailsByIdsQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Roles.GetRoleListQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Roles.GetRolePermissionsQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContext
- Direction
- CleanAdmin.ApiService.Application.Queries.Roles uses CleanAdmin.Infrastructure, so a change to CleanAdmin.Infrastructure can break CleanAdmin.ApiService.Application.Queries.Roles, while a change to CleanAdmin.ApiService.Application.Queries.Roles can't break CleanAdmin.Infrastructure.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Roles uses a module listed above it, which is the healthy direction.
31→17 CleanAdmin.ApiService.Application.Queries.Users uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 6 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Users uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.ApiService.Application.Queries.Users.AssignableRoleItemDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Users.GetRolePermissionSyncContextQuery→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Users.GetUserIdsByRoleIdQuery→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Users.RolePermissionSyncContextDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Users.UserListRoleItemDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Queries.Users.UserRoleSummaryDto→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.ApiService.Application.Queries.Users uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.ApiService.Application.Queries.Users, while a change to CleanAdmin.ApiService.Application.Queries.Users can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Users uses a module listed above it, which is the healthy direction.
31→20 CleanAdmin.ApiService.Application.Queries.Users uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 12 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Users uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.ApiService.Application.Queries.Users.CheckRefreshTokenIsValidQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.CheckUserExistsByUsernameExceptIdQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUserIdByNameQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUserIdByNameQueryHandler→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUserIdsByRoleIdQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUserIdsByRoleIdQueryHandler→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUserInfoQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUserPermissionCodesQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.GetUsernameByIdQuery→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.RolePermissionSyncContextDto→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.UserInfoDto→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Queries.Users.UserListItemDto→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserId
- Direction
- CleanAdmin.ApiService.Application.Queries.Users uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.ApiService.Application.Queries.Users, while a change to CleanAdmin.ApiService.Application.Queries.Users can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Users uses a module listed above it, which is the healthy direction.
31→25 CleanAdmin.ApiService.Application.Queries.Users uses CleanAdmin.Infrastructure✕
- Connections
- 11 pairs of types, where a type in CleanAdmin.ApiService.Application.Queries.Users uses a type in CleanAdmin.Infrastructure.
- The types involved
CleanAdmin.ApiService.Application.Queries.Users.CheckRefreshTokenIsValidQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.CheckUserExistsByUsernameExceptIdQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.CheckUserExistsByUsernameQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetAssignableRolesForUserQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetRolePermissionSyncContextQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetUserIdByNameQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetUserIdsByRoleIdQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetUserInfoQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetUserListQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetUserPermissionCodesQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.ApiService.Application.Queries.Users.GetUsernameByIdQueryHandler→CleanAdmin.Infrastructure.ApplicationDbContext
- Direction
- CleanAdmin.ApiService.Application.Queries.Users uses CleanAdmin.Infrastructure, so a change to CleanAdmin.Infrastructure can break CleanAdmin.ApiService.Application.Queries.Users, while a change to CleanAdmin.ApiService.Application.Queries.Users can't break CleanAdmin.Infrastructure.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Queries.Users uses a module listed above it, which is the healthy direction.
32→21 CleanAdmin.ApiService.Auth.Middlewares uses CleanAdmin.ApiService.Auth✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Auth.Middlewares uses a type in CleanAdmin.ApiService.Auth.
- The types involved
CleanAdmin.ApiService.Auth.Middlewares.CurrentUserMiddleware→CleanAdmin.ApiService.Auth.ICurrentUser
- Direction
- CleanAdmin.ApiService.Auth.Middlewares uses CleanAdmin.ApiService.Auth, so a change to CleanAdmin.ApiService.Auth can break CleanAdmin.ApiService.Auth.Middlewares, while a change to CleanAdmin.ApiService.Auth.Middlewares can't break CleanAdmin.ApiService.Auth.
- Position
- Below the diagonal: CleanAdmin.ApiService.Auth.Middlewares uses a module listed above it, which is the healthy direction.
33→16 CleanAdmin.ApiService.Endpoints.Menus uses CleanAdmin.Domain.AggregatesModel.MenuAggregate✕
- Connections
- 8 pairs of types, where a type in CleanAdmin.ApiService.Endpoints.Menus uses a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- The types involved
CleanAdmin.ApiService.Endpoints.Menus.CreateMenuRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Endpoints.Menus.CreateMenuRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuTypeCleanAdmin.ApiService.Endpoints.Menus.CreateMenuResponse→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Endpoints.Menus.DeleteMenuRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Endpoints.Menus.HideMenuRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Endpoints.Menus.ShowMenuRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Endpoints.Menus.UpdateMenuRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Endpoints.Menus.UpdateMenuSortOrderRequest→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuId
- Direction
- CleanAdmin.ApiService.Endpoints.Menus uses CleanAdmin.Domain.AggregatesModel.MenuAggregate, so a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can break CleanAdmin.ApiService.Endpoints.Menus, while a change to CleanAdmin.ApiService.Endpoints.Menus can't break CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Menus uses a module listed above it, which is the healthy direction.
33→21 CleanAdmin.ApiService.Endpoints.Menus uses CleanAdmin.ApiService.Auth✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Endpoints.Menus uses a type in CleanAdmin.ApiService.Auth.
- The types involved
CleanAdmin.ApiService.Endpoints.Menus.GetCurrentUserNavigationMenusEndpoint→CleanAdmin.ApiService.Auth.ICurrentUser
- Direction
- CleanAdmin.ApiService.Endpoints.Menus uses CleanAdmin.ApiService.Auth, so a change to CleanAdmin.ApiService.Auth can break CleanAdmin.ApiService.Endpoints.Menus, while a change to CleanAdmin.ApiService.Endpoints.Menus can't break CleanAdmin.ApiService.Auth.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Menus uses a module listed above it, which is the healthy direction.
34→17 CleanAdmin.ApiService.Endpoints.Users uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 3 pairs of types, where a type in CleanAdmin.ApiService.Endpoints.Users uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.ApiService.Endpoints.Users.CreateUserRequest→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Users.UpdateUserRequest→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Endpoints.Users.UserAssignableRoleItemResponse→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.ApiService.Endpoints.Users uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.ApiService.Endpoints.Users, while a change to CleanAdmin.ApiService.Endpoints.Users can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Users uses a module listed above it, which is the healthy direction.
34→20 CleanAdmin.ApiService.Endpoints.Users uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 3 pairs of types, where a type in CleanAdmin.ApiService.Endpoints.Users uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.ApiService.Endpoints.Users.CreateUserResponse→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Endpoints.Users.DeleteUserRequest→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Endpoints.Users.UpdateUserRequest→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserId
- Direction
- CleanAdmin.ApiService.Endpoints.Users uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.ApiService.Endpoints.Users, while a change to CleanAdmin.ApiService.Endpoints.Users can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Users uses a module listed above it, which is the healthy direction.
34→21 CleanAdmin.ApiService.Endpoints.Users uses CleanAdmin.ApiService.Auth✕
- Connections
- 4 pairs of types, where a type in CleanAdmin.ApiService.Endpoints.Users uses a type in CleanAdmin.ApiService.Auth.
- The types involved
CleanAdmin.ApiService.Endpoints.Users.ChangeCurrentUserPasswordEndpoint→CleanAdmin.ApiService.Auth.ICurrentUserCleanAdmin.ApiService.Endpoints.Users.CurrentUserPermissionCodesEndpoint→CleanAdmin.ApiService.Auth.ICurrentUserCleanAdmin.ApiService.Endpoints.Users.ProfileEndpoint→CleanAdmin.ApiService.Auth.ICurrentUserCleanAdmin.ApiService.Endpoints.Users.UpdateCurrentUserProfileEndpoint→CleanAdmin.ApiService.Auth.ICurrentUser
- Direction
- CleanAdmin.ApiService.Endpoints.Users uses CleanAdmin.ApiService.Auth, so a change to CleanAdmin.ApiService.Auth can break CleanAdmin.ApiService.Endpoints.Users, while a change to CleanAdmin.ApiService.Endpoints.Users can't break CleanAdmin.ApiService.Auth.
- Position
- Below the diagonal: CleanAdmin.ApiService.Endpoints.Users uses a module listed above it, which is the healthy direction.
35→25 CleanAdmin.Infrastructure.Repositories uses CleanAdmin.Infrastructure✕
- Connections
- 5 pairs of types, where a type in CleanAdmin.Infrastructure.Repositories uses a type in CleanAdmin.Infrastructure.
- The types involved
CleanAdmin.Infrastructure.Repositories.DeliverRecordRepository→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.Infrastructure.Repositories.MenuRepository→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.Infrastructure.Repositories.OrderRepository→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.Infrastructure.Repositories.RoleRepository→CleanAdmin.Infrastructure.ApplicationDbContextCleanAdmin.Infrastructure.Repositories.UserRepository→CleanAdmin.Infrastructure.ApplicationDbContext
- Direction
- CleanAdmin.Infrastructure.Repositories uses CleanAdmin.Infrastructure, so a change to CleanAdmin.Infrastructure can break CleanAdmin.Infrastructure.Repositories, while a change to CleanAdmin.Infrastructure.Repositories can't break CleanAdmin.Infrastructure.
- Position
- Below the diagonal: CleanAdmin.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→25 CleanAdmin.MigrationService uses CleanAdmin.Infrastructure✕
- Connections
- 1 pair of types, where a type in CleanAdmin.MigrationService uses a type in CleanAdmin.Infrastructure.
- The types involved
CleanAdmin.MigrationService.ApiDbInitializer→CleanAdmin.Infrastructure.ApplicationDbContext
- Direction
- CleanAdmin.MigrationService uses CleanAdmin.Infrastructure, so a change to CleanAdmin.Infrastructure can break CleanAdmin.MigrationService, while a change to CleanAdmin.MigrationService can't break CleanAdmin.Infrastructure.
- Position
- Below the diagonal: CleanAdmin.MigrationService uses a module listed above it, which is the healthy direction.
37→8 CleanAdmin.ApiService.Application.Commands uses CleanAdmin.Domain.AggregatesModel.OrderAggregate✕
- Connections
- 4 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands uses a type in CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- The types involved
CleanAdmin.ApiService.Application.Commands.CreateOrderCommand→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderIdCleanAdmin.ApiService.Application.Commands.CreateOrderCommandHandler→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderIdCleanAdmin.ApiService.Application.Commands.DeliverGoodsCommand→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderIdCleanAdmin.ApiService.Application.Commands.OrderPaidCommand→CleanAdmin.Domain.AggregatesModel.OrderAggregate.OrderId
- Direction
- CleanAdmin.ApiService.Application.Commands uses CleanAdmin.Domain.AggregatesModel.OrderAggregate, so a change to CleanAdmin.Domain.AggregatesModel.OrderAggregate can break CleanAdmin.ApiService.Application.Commands, while a change to CleanAdmin.ApiService.Application.Commands can't break CleanAdmin.Domain.AggregatesModel.OrderAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands uses a module listed above it, which is the healthy direction.
37→14 CleanAdmin.ApiService.Application.Commands uses CleanAdmin.ApiService.Application.IntegrationEventHandlers✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Application.Commands uses a type in CleanAdmin.ApiService.Application.IntegrationEventHandlers.
- The types involved
CleanAdmin.ApiService.Application.Commands.CreateOrderCommandHandler→CleanAdmin.ApiService.Application.IntegrationEventHandlers.OrderPaidIntegrationEventHandler
- Direction
- CleanAdmin.ApiService.Application.Commands uses CleanAdmin.ApiService.Application.IntegrationEventHandlers, so a change to CleanAdmin.ApiService.Application.IntegrationEventHandlers can break CleanAdmin.ApiService.Application.Commands, while a change to CleanAdmin.ApiService.Application.Commands can't break CleanAdmin.ApiService.Application.IntegrationEventHandlers.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands uses a module listed above it, which is the healthy direction.
37→15 CleanAdmin.ApiService.Application.Commands uses CleanAdmin.Domain.AggregatesModel.DeliverAggregate✕
- Connections
- 2 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands uses a type in CleanAdmin.Domain.AggregatesModel.DeliverAggregate.
- The types involved
CleanAdmin.ApiService.Application.Commands.DeliverGoodsCommand→CleanAdmin.Domain.AggregatesModel.DeliverAggregate.DeliverRecordIdCleanAdmin.ApiService.Application.Commands.DeliverGoodsCommandHandler→CleanAdmin.Domain.AggregatesModel.DeliverAggregate.DeliverRecordId
- Direction
- CleanAdmin.ApiService.Application.Commands uses CleanAdmin.Domain.AggregatesModel.DeliverAggregate, so a change to CleanAdmin.Domain.AggregatesModel.DeliverAggregate can break CleanAdmin.ApiService.Application.Commands, while a change to CleanAdmin.ApiService.Application.Commands can't break CleanAdmin.Domain.AggregatesModel.DeliverAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands uses a module listed above it, which is the healthy direction.
37→35 CleanAdmin.ApiService.Application.Commands uses CleanAdmin.Infrastructure.Repositories✕
- Connections
- 3 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands uses a type in CleanAdmin.Infrastructure.Repositories.
- The types involved
CleanAdmin.ApiService.Application.Commands.CreateOrderCommandHandler→CleanAdmin.Infrastructure.Repositories.IOrderRepositoryCleanAdmin.ApiService.Application.Commands.DeliverGoodsCommandHandler→CleanAdmin.Infrastructure.Repositories.IDeliverRecordRepositoryCleanAdmin.ApiService.Application.Commands.OrderPaidCommandHandler→CleanAdmin.Infrastructure.Repositories.IOrderRepository
- Direction
- CleanAdmin.ApiService.Application.Commands uses CleanAdmin.Infrastructure.Repositories, so a change to CleanAdmin.Infrastructure.Repositories can break CleanAdmin.ApiService.Application.Commands, while a change to CleanAdmin.ApiService.Application.Commands can't break CleanAdmin.Infrastructure.Repositories.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands uses a module listed above it, which is the healthy direction.
38→16 CleanAdmin.ApiService.Application.Commands.Menus uses CleanAdmin.Domain.AggregatesModel.MenuAggregate✕
- Connections
- 8 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Menus uses a type in CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- The types involved
CleanAdmin.ApiService.Application.Commands.Menus.CreateMenuCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Commands.Menus.CreateMenuCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuTypeCleanAdmin.ApiService.Application.Commands.Menus.CreateMenuCommandHandler→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Commands.Menus.DeleteMenuCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Commands.Menus.HideMenuCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Commands.Menus.ShowMenuCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Commands.Menus.UpdateMenuCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuIdCleanAdmin.ApiService.Application.Commands.Menus.UpdateMenuSortOrderCommand→CleanAdmin.Domain.AggregatesModel.MenuAggregate.MenuId
- Direction
- CleanAdmin.ApiService.Application.Commands.Menus uses CleanAdmin.Domain.AggregatesModel.MenuAggregate, so a change to CleanAdmin.Domain.AggregatesModel.MenuAggregate can break CleanAdmin.ApiService.Application.Commands.Menus, while a change to CleanAdmin.ApiService.Application.Commands.Menus can't break CleanAdmin.Domain.AggregatesModel.MenuAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Menus uses a module listed above it, which is the healthy direction.
38→35 CleanAdmin.ApiService.Application.Commands.Menus uses CleanAdmin.Infrastructure.Repositories✕
- Connections
- 6 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Menus uses a type in CleanAdmin.Infrastructure.Repositories.
- The types involved
CleanAdmin.ApiService.Application.Commands.Menus.CreateMenuCommandHandler→CleanAdmin.Infrastructure.Repositories.IMenuRepositoryCleanAdmin.ApiService.Application.Commands.Menus.DeleteMenuCommandHandler→CleanAdmin.Infrastructure.Repositories.IMenuRepositoryCleanAdmin.ApiService.Application.Commands.Menus.HideMenuCommandHandler→CleanAdmin.Infrastructure.Repositories.IMenuRepositoryCleanAdmin.ApiService.Application.Commands.Menus.ShowMenuCommandHandler→CleanAdmin.Infrastructure.Repositories.IMenuRepositoryCleanAdmin.ApiService.Application.Commands.Menus.UpdateMenuCommandHandler→CleanAdmin.Infrastructure.Repositories.IMenuRepositoryCleanAdmin.ApiService.Application.Commands.Menus.UpdateMenuSortOrderCommandHandler→CleanAdmin.Infrastructure.Repositories.IMenuRepository
- Direction
- CleanAdmin.ApiService.Application.Commands.Menus uses CleanAdmin.Infrastructure.Repositories, so a change to CleanAdmin.Infrastructure.Repositories can break CleanAdmin.ApiService.Application.Commands.Menus, while a change to CleanAdmin.ApiService.Application.Commands.Menus can't break CleanAdmin.Infrastructure.Repositories.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Menus uses a module listed above it, which is the healthy direction.
39→17 CleanAdmin.ApiService.Application.Commands.Roles uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 5 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Roles uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.ApiService.Application.Commands.Roles.CreateRoleCommand→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Commands.Roles.CreateRoleCommandHandler→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Commands.Roles.DeleteRoleCommand→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Commands.Roles.UpdateRoleInfoCommand→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleIdCleanAdmin.ApiService.Application.Commands.Roles.UpdateRolePermissionsCommand→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.ApiService.Application.Commands.Roles uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.ApiService.Application.Commands.Roles, while a change to CleanAdmin.ApiService.Application.Commands.Roles can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Roles uses a module listed above it, which is the healthy direction.
39→35 CleanAdmin.ApiService.Application.Commands.Roles uses CleanAdmin.Infrastructure.Repositories✕
- Connections
- 4 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Roles uses a type in CleanAdmin.Infrastructure.Repositories.
- The types involved
CleanAdmin.ApiService.Application.Commands.Roles.CreateRoleCommandHandler→CleanAdmin.Infrastructure.Repositories.IRoleRepositoryCleanAdmin.ApiService.Application.Commands.Roles.DeleteRoleCommandHandler→CleanAdmin.Infrastructure.Repositories.IRoleRepositoryCleanAdmin.ApiService.Application.Commands.Roles.UpdateRoleInfoCommandHandler→CleanAdmin.Infrastructure.Repositories.IRoleRepositoryCleanAdmin.ApiService.Application.Commands.Roles.UpdateRolePermissionsCommandHandler→CleanAdmin.Infrastructure.Repositories.IRoleRepository
- Direction
- CleanAdmin.ApiService.Application.Commands.Roles uses CleanAdmin.Infrastructure.Repositories, so a change to CleanAdmin.Infrastructure.Repositories can break CleanAdmin.ApiService.Application.Commands.Roles, while a change to CleanAdmin.ApiService.Application.Commands.Roles can't break CleanAdmin.Infrastructure.Repositories.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Roles uses a module listed above it, which is the healthy direction.
40→11 CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Infrastructure.Utils✕
- Connections
- 4 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Users uses a type in CleanAdmin.Infrastructure.Utils.
- The types involved
CleanAdmin.ApiService.Application.Commands.Users.ChangePasswordCommandHandler→CleanAdmin.Infrastructure.Utils.IPasswordHasherCleanAdmin.ApiService.Application.Commands.Users.CreateUserCommandHandler→CleanAdmin.Infrastructure.Utils.IPasswordHasherCleanAdmin.ApiService.Application.Commands.Users.LoginUserCommandHandler→CleanAdmin.Infrastructure.Utils.IPasswordHasherCleanAdmin.ApiService.Application.Commands.Users.RegisterUserCommandHandler→CleanAdmin.Infrastructure.Utils.IPasswordHasher
- Direction
- CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Infrastructure.Utils, so a change to CleanAdmin.Infrastructure.Utils can break CleanAdmin.ApiService.Application.Commands.Users, while a change to CleanAdmin.ApiService.Application.Commands.Users can't break CleanAdmin.Infrastructure.Utils.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Users uses a module listed above it, which is the healthy direction.
40→17 CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Domain.AggregatesModel.RoleAggregate✕
- Connections
- 1 pair of types, where a type in CleanAdmin.ApiService.Application.Commands.Users uses a type in CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- The types involved
CleanAdmin.ApiService.Application.Commands.Users.RefreshUserPermissionsByRoleCommand→CleanAdmin.Domain.AggregatesModel.RoleAggregate.RoleId
- Direction
- CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Domain.AggregatesModel.RoleAggregate, so a change to CleanAdmin.Domain.AggregatesModel.RoleAggregate can break CleanAdmin.ApiService.Application.Commands.Users, while a change to CleanAdmin.ApiService.Application.Commands.Users can't break CleanAdmin.Domain.AggregatesModel.RoleAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Users uses a module listed above it, which is the healthy direction.
40→20 CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Domain.AggregatesModel.UserAggregate✕
- Connections
- 11 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Users uses a type in CleanAdmin.Domain.AggregatesModel.UserAggregate.
- The types involved
CleanAdmin.ApiService.Application.Commands.Users.ChangePasswordCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.CreateUserCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.CreateUserCommandHandler→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.DeleteUserCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.LoginUserCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.RefreshUserPermissionsByRoleCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.RegisterUserCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.RegisterUserCommandHandler→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.UpdateCurrentUserBasicInfoCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.UpdateUserInfoCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserIdCleanAdmin.ApiService.Application.Commands.Users.UpdateUserRefreshTokenCommand→CleanAdmin.Domain.AggregatesModel.UserAggregate.UserId
- Direction
- CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Domain.AggregatesModel.UserAggregate, so a change to CleanAdmin.Domain.AggregatesModel.UserAggregate can break CleanAdmin.ApiService.Application.Commands.Users, while a change to CleanAdmin.ApiService.Application.Commands.Users can't break CleanAdmin.Domain.AggregatesModel.UserAggregate.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Users uses a module listed above it, which is the healthy direction.
40→30 CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.ApiService.Application.Queries.Roles✕
- Connections
- 2 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Users uses a type in CleanAdmin.ApiService.Application.Queries.Roles.
- The types involved
CleanAdmin.ApiService.Application.Commands.Users.CreateUserCommand→CleanAdmin.ApiService.Application.Queries.Roles.RoleDetailDtoCleanAdmin.ApiService.Application.Commands.Users.UpdateUserInfoCommand→CleanAdmin.ApiService.Application.Queries.Roles.RoleDetailDto
- Direction
- CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.ApiService.Application.Queries.Roles, so a change to CleanAdmin.ApiService.Application.Queries.Roles can break CleanAdmin.ApiService.Application.Commands.Users, while a change to CleanAdmin.ApiService.Application.Commands.Users can't break CleanAdmin.ApiService.Application.Queries.Roles.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Users uses a module listed above it, which is the healthy direction.
40→35 CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Infrastructure.Repositories✕
- Connections
- 9 pairs of types, where a type in CleanAdmin.ApiService.Application.Commands.Users uses a type in CleanAdmin.Infrastructure.Repositories.
- The types involved
CleanAdmin.ApiService.Application.Commands.Users.ChangePasswordCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.CreateUserCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.DeleteUserCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.LoginUserCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.RefreshUserPermissionsByRoleCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.RegisterUserCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.UpdateCurrentUserBasicInfoCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.UpdateUserInfoCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepositoryCleanAdmin.ApiService.Application.Commands.Users.UpdateUserRefreshTokenCommandHandler→CleanAdmin.Infrastructure.Repositories.IUserRepository
- Direction
- CleanAdmin.ApiService.Application.Commands.Users uses CleanAdmin.Infrastructure.Repositories, so a change to CleanAdmin.Infrastructure.Repositories can break CleanAdmin.ApiService.Application.Commands.Users, while a change to CleanAdmin.ApiService.Application.Commands.Users can't break CleanAdmin.Infrastructure.Repositories.
- Position
- Below the diagonal: CleanAdmin.ApiService.Application.Commands.Users uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 26 | High / Critical |
| A07:2025 — Authentication Failures | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. | +4.2 pts | Low | REDACTED Scanning |
| Resolve the 6 redundant comment finding(s) in Comment Value — start with REDACTED (4), DependencyInjection.cs, WebAppFixture.cs. | +1.4 pts | Low | Comment Value |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +5.3 pts | Medium | Visual & motion safety |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +5.3 pts | Medium | Keyboard semantics |
| Resolve the 1 Banned license finding(s) in License Compliance — start with Directory.Packages.props. | +2.5 pts | Low | License Compliance |
| Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +3.6 pts | Medium | A11y enforcement |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +3.3 pts | Medium | DR & Backup |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), ApplicationDbContextSeed.cs, User.cs. | +1.6 pts | Medium | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Directory.Build.props | 5.8 | Mixed | Explicit Debt: NoWarnInCsproj |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs | 7.1 | Near-clean | Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens) |
| src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs | 7.2 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Directory.Packages.props | 7.2 | Near-clean | License Compliance: Banned license: Hangfire.Redis.StackExchange |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| src/CleanAdmin.Web.Client/Components/PDrawerForm.razor | 7.8 | Near-clean | Code Duplication: Duplicated block (71–75 lines × 2) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/CleanAdmin.ServiceDefaults/Extensions.cs | 8.2 | Near-clean | Explicit Debt: CommentedOutCode |
| src/CleanAdmin.Web.Client/SharedResource.cs | 8.2 | Near-clean | Explicit Debt: BarePragmaDisable |
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 91 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 — 91 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, 185 of 202 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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 MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: NU1301: Unable to load the service index for source https://www.myget.org/F/netcorepal/api/v3/index.json. [CleanAdmin.slnx] The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'." [CleanAdmin.slnx]. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to www.myget.org, and a re-run with it reachable measures this repository.
- 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 312 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: Msbuild failed when processing the file 'src/CleanAdmin.AppHost/CleanAdmin.AppHost.csproj' with message: Unable to load the service index for source https://www.myget.org/F/netcorepal/api/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.".
- 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. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
- 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.
- 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.
- D24 Comment Value — 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D30 Dependency Vulnerabilities — 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. Www.myget.org could not be reached (NU1301: Unable to load the service index for source https://www.myget.org/F/netcorepal/api/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — 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. `src/CleanAdmin.ApiService/Application/Commands/CreateOrderCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/DeliverGoodsCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/DeleteMenuCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/HideMenuCommand.cs`, … (+103 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AC6 Visual & motion safety — 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. 281 further occurrence(s) are not listed individually; the score already reflects all 321.
- 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 AspireAppHost (src/CleanAdmin.AppHost/CleanAdmin.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
- DM8 Value-object opportunities — 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. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — 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. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/CleanAdmin.AppHost/CleanAdmin.AppHost.csproj, src/CleanAdmin.ApiService/CleanAdmin.ApiService.csproj, src/CleanAdmin.Domain/CleanAdmin.Domain.csproj, src/CleanAdmin.Infrastructure/CleanAdmin.Infrastructure.csproj, src/CleanAdmin.MigrationService/CleanAdmin.MigrationService.csproj and 7 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was top-level statements at 20.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with top-level statements (cyclomatic 20). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was top-level statements at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with top-level statements (cognitive 29). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
18 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with CreateMenuCommand.cs, MenuEntityTypeConfiguration.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with UpdateMenuSortOrderCommand.cs, RoleListEndpoint.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with UpdateRolePermissionsCommand.cs, GetRoleListQuery.cs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
13 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
2 of 16 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with Menu.cs, User.cs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
35 test methods: 10 unit, 25 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 3 mock references across 35 tests.
D13 · REDACTED Scanning
5 secret(s) detected.
What to do
- Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
1 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 96 direct `PackageReference`(s), and 154 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.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
Top hotspots: REDACTED (16×20=320)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
7 deducted debt markers + unmeasured dead symbols across 13183 LoC in the .NET projects (0.3/KLoC) → score 9.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 BarePragmaDisable finding(s) in Explicit Debt — start with REDACTED (2), SharedResource.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with Extensions.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
12 projects, 265 source files, 14131 hand-written lines of code (13183 production / 948 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 1504 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 13 inter-project edges (build status unknown — did not finish).
What to do
- Resolve the 1 Shell project finding(s) in Solution Shape — start with CleanAdmin.Infrastructure.Tests.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 3 document(s) read across 10 unit(s).
D24 · Comment Value
6 of 47 judged comments only repeat the code they sit on (12.8 %). 63 comment(s) in another language or script were not judged.
What to do
- Resolve the 6 redundant comment finding(s) in Comment Value — start with REDACTED (4), DependencyInjection.cs, WebAppFixture.cs. — One of this dimension's main actionable groups (6 recommendation-level).
D26 · Project Cohesion
2 of 13 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with CleanAdmin.Web.Client.csproj, CleanAdmin.ApiService.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
D28 · Secrets (history)
9 finding(s): 0 critical, 9 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 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 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)
26 finding(s): 0 critical, 21 high, 5 medium, 0 low. semgrep hit a parse error in 108 file(s) — `src/CleanAdmin.ApiService/Application/Commands/CreateOrderCommand.cs` (line 18), `src/CleanAdmin.ApiService/Application/Commands/DeliverGoodsCommand.cs` (line 9), `src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs` (line 109), `src/CleanAdmin.ApiService/Application/Commands/Menus/DeleteMenuCommand.cs` (line 49), `src/CleanAdmin.ApiService/Application/Commands/Menus/HideMenuCommand.cs` (line 27), … (+103 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 107 of those file(s) — `src/CleanAdmin.ApiService/Application/Commands/CreateOrderCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/DeliverGoodsCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/DeleteMenuCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/HideMenuCommand.cs`, … (+102 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 5 of those file(s) — `src/CleanAdmin.Infrastructure/Repositories/DeliverRecordRepository.cs`, `src/CleanAdmin.Infrastructure/Repositories/OrderRepository.cs`, `src/CleanAdmin.Infrastructure/Repositories/RoleRepository.cs`, `src/CleanAdmin.Infrastructure/Repositories/UserRepository.cs`, `src/CleanAdmin.Web.Client/Exceptions/UserRequiresLoginException.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 17 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (7), REDACTED (3). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 5 high, 2 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: www.myget.org could not be reached (NU1301: Unable to load the service index for source https://www.myget.org/F/netcorepal/api/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.)), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
27 of 27 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 27 of the 162 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), ApplicationDbContextSeed.cs, User.cs. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 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 13 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>. — src/CleanAdmin.Web.Client/Layout/AuthLayout.razor:2
- A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). — src/CleanAdmin.Web.Client/Pages/NotFound.razor:4
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- The repo's own CSS styles .dismiss with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/CleanAdmin.Web.Client/Layout/MainLayout.razor:128
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `#components-reconnect-modal button` sets color: white on background-color: #6b9ed2 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/CleanAdmin.Web.Client/Layout/ReconnectModal.razor.css:91
- `.ant-dropdown-menu-dark .ant-dropdown-menu-item-selected,.ant-dropdown-menu-dark .ant-dropdown-menu-item-selected:hover,.ant-dropdown-menu-dark .ant-dropdown-menu-item-selected>a` sets color: #fff on background-color: #177ddc — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-tabs-card>.ant-tabs-nav .ant-tabs-tab-active,.ant-tabs-card>div>.ant-tabs-nav .ant-tabs-tab-active` sets color: #177ddc on background-color: #141414 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `::selection` sets color: #fff on background-color: #177ddc — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-dropdown-menu-dark .ant-dropdown-menu-item-selected,.ant-dropdown-menu-dark .ant-dropdown-menu-item-selected:hover,.ant-dropdown-menu-dark .ant-dropdown-menu-item-selected>a` sets color: #fff on background-color: #1890ff — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/CleanAdmin.Web/wwwroot/styles/light.css:1
- `.ant-tabs-card>.ant-tabs-nav .ant-tabs-tab-active,.ant-tabs-card>div>.ant-tabs-nav .ant-tabs-tab-active` sets color: #1890ff on background-color: #fff — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/CleanAdmin.Web/wwwroot/styles/light.css:1
- `.ant-alert-close-icon` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-carousel .slick-list:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-carousel .slick-dots li button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-checkbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-collapse>.ant-collapse-item>.ant-collapse-header:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-picker-status-error.ant-picker-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-picker-status-warning.ant-picker-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-picker-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-picker-panel` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-drawer-close` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-dropdown-menu` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-affix-wrapper-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-affix-wrapper>.ant-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-status-error:not(.ant-input-disabled):not(.ant-input-borderless).ant-input-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-status-warning:not(.ant-input-disabled):not(.ant-input-borderless).ant-input-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-affix-wrapper-status-error:not(.ant-input-affix-wrapper-disabled):not(.ant-input-affix-wrapper-borderless).ant-input-affix-wrapper-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-affix-wrapper-status-warning:not(.ant-input-affix-wrapper-disabled):not(.ant-input-affix-wrapper-borderless).ant-input-affix-wrapper-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-affix-wrapper.ant-input-affix-wrapper-rtl>input.ant-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-affix-wrapper-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-affix-wrapper>div.ant-input-number` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-status-error:not(.ant-input-number-disabled):not(.ant-input-number-borderless).ant-input-number-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-status-warning:not(.ant-input-number-disabled):not(.ant-input-number-borderless).ant-input-number-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-affix-wrapper-status-error:not(.ant-input-number-affix-wrapper-disabled):not(.ant-input-number-affix-wrapper-borderless).ant-input-number-affix-wrapper-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-affix-wrapper-status-warning:not(.ant-input-number-affix-wrapper-disabled):not(.ant-input-number-affix-wrapper-borderless).ant-input-number-affix-wrapper-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-input-number-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-list *` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-menu` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-mentions-status-error:not(.ant-mentions-disabled):not(.ant-mentions-borderless).ant-mentions-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-mentions-status-warning:not(.ant-mentions-disabled):not(.ant-mentions-borderless).ant-mentions-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-mentions-focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-mentions>textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- `.ant-mentions-dropdown` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/CleanAdmin.Web/wwwroot/styles/dark.css:1
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 34 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. — src/CleanAdmin.Web/package.json:5
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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
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
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
- `Menu`'s public constructor takes `menuName`, `routePath`, `componentPath`, `icon`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Menu` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/CleanAdmin.Domain/AggregatesModel/MenuAggregate/Menu.cs:97
- `UserRole`'s public constructor takes `roleName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `UserRole` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/CleanAdmin.Domain/AggregatesModel/UserAggregate/UserRole.cs:16
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
- `UserLoginDomainEventHandler` reads `DateTimeOffset.Now` inside `Handle`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/CleanAdmin.ApiService/Application/DomainEventHandlers/UserLoginDomainEventHandler.cs:11
- `UserPasswordChangedDomainEventHandler` reads `DateTimeOffset.Now` inside `Handle`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/CleanAdmin.ApiService/Application/DomainEventHandlers/UserPasswordChangedDomainEventHandler.cs:11
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM4 · Rich vs anemic model
- `UserRole` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/CleanAdmin.Domain/AggregatesModel/UserAggregate/UserRole.cs:10
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/CleanAdmin.ApiService/Application/DomainEventHandlers/RoleDeletedDomainEventHandler.cs:14
- A placeholder e-mail address ("admin@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. (×2) — src/CleanAdmin.ApiService/Endpoints/Users/CreateUserEndpoint.cs:89, src/CleanAdmin.ApiService/Endpoints/Users/UpdateUserEndpoint.cs:86
- A placeholder e-mail address ("superadmin@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/CleanAdmin.ApiService/Extensions/ApplicationDbContextSeed.cs:25
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 9 of 10 project(s) that lack one — worth up to 1.8 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 4/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- Password-hash field compared with `==` — use a constant-time compare to avoid timing oracles (CryptographicOperations.FixedTimeEquals). — src/CleanAdmin.Domain/AggregatesModel/UserAggregate/User.cs:149
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×2) — REDACTED:43, REDACTED:8
What to do
- Compare password hashes with `CryptographicOperations.FixedTimeEquals` (constant time, no timing oracle).
- 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 122/130 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. (×7) — REDACTED:10, src/CleanAdmin.Web.Client/Extensions/WebAssemblyHostExtension.cs:14, src/CleanAdmin.Web.Client/Services/CultureService.cs:27, …
- No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — src/CleanAdmin.ApiService/Auth/Permission/UserPermissionHydrator.cs:54
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
- `html` is text this program did not author, and it is written into the text of an element through `Content(…, "text/html")` 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. — REDACTED:333
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
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- ~0.4 `!` suppressions per 1k syntax nodes — 24 suppression(s) across the 66740 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| 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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | 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 | 96% | Exemplary | Strongest area. |
| Architecture | 81% | Strong | Solid. |
| Maturity | 58% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Adequate — gated by D13, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 70% | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 39% | Adequate — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 42 check(s) not relevant to this codebase
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence 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.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured — www.myget.org could not be reached
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- 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 (13,183 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. Aggregate roots were found in only one source directory (CleanAdmin.Domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 108 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Handler temporal coupling — no events and no event/broker handlers detected — event-driven integration not assessable
- ED2 Event/command shape — no events and no event/broker handlers detected — event-driven integration not assessable
- ED3 Event naming — no events and no event/broker handlers detected — event-driven integration not assessable
- ED4 Outbox / dual-write — no events and no event/broker handlers detected — event-driven integration not assessable
- ED5 Idempotency — 28 mutating command handler(s)/consumer(s) detected and 28 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- 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
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X8 JS interop contract — 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 — 46 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj Directory.Build.props:18
- NoWarnInCsproj Directory.Build.props:18
- NoWarnInCsproj Directory.Build.props:18
- REDACTED
- REDACTED
- REDACTED
- Routed page without a <PageTitle> src/CleanAdmin.Web.Client/Pages/NotFound.razor:4
- Clickable element isn't keyboard-operable src/CleanAdmin.Web.Client/Layout/MainLayout.razor:128
- Banned license: Hangfire.Redis.StackExchange Directory.Packages.props:88
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 94 finding(s)
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Focus outline removed in CSS without a :focus replacement src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Async method without CancellationToken: SendMessageAsync REDACTED:10
- Async method without CancellationToken: SetCulture src/CleanAdmin.Web.Client/Extensions/WebAssemblyHostExtension.cs:14
- Async method without CancellationToken: SetCultureAsync src/CleanAdmin.Web.Client/Services/CultureService.cs:27
- Async method without CancellationToken: GetStoredOrDefaultCultureInfoAsync src/CleanAdmin.Web.Client/Services/CultureService.cs:40
- Async method without CancellationToken: InitializeAsync src/CleanAdmin.Web.Client/Services/ThemeService.cs:27
- Async method without CancellationToken: SaveThemeToCookieAsync src/CleanAdmin.Web.Client/Services/ThemeService.cs:90
- Async method without CancellationToken: ApplyThemeToDocumentAsync src/CleanAdmin.Web.Client/Services/ThemeService.cs:97
- BarePragmaDisable REDACTED:361
- BarePragmaDisable src/CleanAdmin.Web.Client/SharedResource.cs:3
- BarePragmaDisable REDACTED:81
- REDACTED
- REDACTED
- REDACTED
- Low contrast colour pair in CSS (4.2:1) src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Low contrast colour pair in CSS (4.2:1) src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Low contrast colour pair in CSS (3.2:1) src/CleanAdmin.Web/wwwroot/styles/light.css:1
- Low contrast colour pair in CSS (3.2:1) src/CleanAdmin.Web/wwwroot/styles/light.css:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs:41
- Duplicated block (13 lines × 2) src/CleanAdmin.Infrastructure/EntityConfigurations/MenuEntityTypeConfiguration.cs:67
- Duplicated block (7 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Menus/UpdateMenuSortOrderCommand.cs:17
- Duplicated block (7 lines × 2) src/CleanAdmin.ApiService/Endpoints/Roles/RoleListEndpoint.cs:38
- Duplicated block (6 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Roles/UpdateRolePermissionsCommand.cs:14
- Duplicated block (6 lines × 2) src/CleanAdmin.ApiService/Application/Queries/Roles/GetRoleListQuery.cs:21
- Low cohesion: Menu (LCOM4 4) src/CleanAdmin.Domain/AggregatesModel/MenuAggregate/Menu.cs:18
- Low cohesion: User (LCOM4 4) src/CleanAdmin.Domain/AggregatesModel/UserAggregate/User.cs:12
- Constructible in an invalid state: Menu src/CleanAdmin.Domain/AggregatesModel/MenuAggregate/Menu.cs:97
- Constructible in an invalid state: UserRole src/CleanAdmin.Domain/AggregatesModel/UserAggregate/UserRole.cs:16
- Domain type reads the wall clock: UserLoginDomainEventHandler src/CleanAdmin.ApiService/Application/DomainEventHandlers/UserLoginDomainEventHandler.cs:11
- Domain type reads the wall clock: UserPasswordChangedDomainEventHandler src/CleanAdmin.ApiService/Application/DomainEventHandlers/UserPasswordChangedDomainEventHandler.cs:11
- Page without a main landmark src/CleanAdmin.Web.Client/Layout/AuthLayout.razor:2
- Low contrast colour pair in CSS (2.8:1) src/CleanAdmin.Web.Client/Layout/ReconnectModal.razor.css:91
- Low contrast colour pair in CSS (4.4:1) src/CleanAdmin.Web/wwwroot/styles/dark.css:1
- Accessibility enforcement below the top rung src/CleanAdmin.Web/package.json:5
- top-level statements (cyclomatic 20) REDACTED:37
- Hotspot: REDACTED REDACTED:37
- CommentedOutCode src/CleanAdmin.ServiceDefaults/Extensions.cs:99
- top-level statements (cognitive 29) REDACTED:37
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:20
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs:28
- Duplicated block (71–75 lines × 2) src/CleanAdmin.Web.Client/Components/PDrawerForm.razor:168
- Duplicated block (22–31 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs:31
- Duplicated block (25 lines × 2) src/CleanAdmin.Web.Client/Components/PDrawerForm.razor:107
- Duplicated block (16–22 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Menus/UpdateMenuCommand.cs:29
- Duplicated block (16 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:32
- Duplicated block (15 lines × 3) src/CleanAdmin.Web.Client/Pages/Application/SystemManage/Menu/Menu.razor:256
- Duplicated block (11–15 lines × 4) src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs:39
- Duplicated block (13 lines × 4) src/CleanAdmin.ApiService/Application/Commands/Users/UpdateCurrentUserBasicInfoCommand.cs:19
- Duplicated block (12 lines × 6) src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:32
- Duplicated block (11–12 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:20
- Duplicated block (8 lines × 2) src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:59
- Duplicated block (5 lines × 2) src/CleanAdmin.ApiService/Endpoints/Users/CreateUserEndpoint.cs:41
- Coverage not measured — test suite did not build
- Anemic entity: UserRole src/CleanAdmin.Domain/AggregatesModel/UserAggregate/UserRole.cs:10
- No DR/backup evidence
- Password hash compared with `==` src/CleanAdmin.Domain/AggregatesModel/UserAggregate/User.cs:149
- Untrusted text written into markup unescaped REDACTED:333
Minor — 56 finding(s)
- Orphaned file REDACTED:1
- Orphaned file src/CleanAdmin.ApiService/Extensions/ApplicationDbContextSeed.cs:1
- Orphaned file src/CleanAdmin.Domain/AggregatesModel/UserAggregate/User.cs:1
- Orphaned file src/CleanAdmin.ServiceDefaults/Extensions.cs:1
- Orphaned file src/CleanAdmin.Web.Client/Infrastructure/Auth/UserTokenStore.cs:1
- Orphaned file src/CleanAdmin.Web.Client/Extensions/ServiceCollectionExtensions.cs:1
- Orphaned file src/CleanAdmin.Domain/AggregatesModel/MenuAggregate/Menu.cs:1
- Orphaned file src/CleanAdmin.Infrastructure/EntityConfigurations/UserEntityTypeConfiguration.cs:1
- Orphaned file src/CleanAdmin.ApiService/Application/Queries/Menus/GetNavigationMenusByPermissionCodesQuery.cs:1
- Orphaned file src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs:1
- Orphaned file src/CleanAdmin.ApiService/Auth/ApiKey/ApikeyAuth.cs:1
- Orphaned file src/CleanAdmin.Web.Client/Services/ThemeService.cs:1
- Orphaned file src/CleanAdmin.ApiService/Endpoints/Users/CreateUserEndpoint.cs:1
- Orphaned file src/CleanAdmin.ApiService/Endpoints/Users/UpdateUserEndpoint.cs:1
- Orphaned file src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:1
- Orphaned file src/CleanAdmin.ApiService/Auth/UserTokenService.cs:1
- Orphaned file src/CleanAdmin.ApiService/Application/Commands/Menus/UpdateMenuCommand.cs:1
- Orphaned file src/CleanAdmin.ApiService/Endpoints/Menus/CreateMenuEndpoint.cs:1
- Orphaned file src/CleanAdmin.ApiService/Application/Queries/Menus/GetMenuListQuery.cs:1
- Orphaned file src/CleanAdmin.Web.Client/Services/UserPermissionService.cs:1
- Orphaned file src/CleanAdmin.Web.Client/Infrastructure/Auth/UserTokenRefresher.cs:1
- Orphaned file src/CleanAdmin.ApiService/Application/Commands/Users/UpdateUserInfoCommand.cs:1
- Orphaned file src/CleanAdmin.Web.Client/Helpers/JwtParser.cs:1
- Orphaned file src/CleanAdmin.ApiService/Auth/Permission/UserPermissionHydrator.cs:1
- Orphaned file REDACTED:1
- redundant comment REDACTED:74
- redundant comment REDACTED:289
- redundant comment src/CleanAdmin.Infrastructure/DependencyInjection.cs:11
- redundant comment REDACTED:11
- redundant comment REDACTED:37
- redundant comment test/CleanAdmin.ApiService.Tests/Fixtures/WebAppFixture.cs:42
- Placeholder data left in code src/CleanAdmin.ApiService/Endpoints/Users/CreateUserEndpoint.cs:89
- Placeholder data left in code src/CleanAdmin.ApiService/Endpoints/Users/UpdateUserEndpoint.cs:86
- Placeholder data left in code src/CleanAdmin.ApiService/Extensions/ApplicationDbContextSeed.cs:25
- No security response headers detected
- No security response headers detected REDACTED:43
- No security response headers detected REDACTED:8
- Projects may be oversized for their cohesion src/CleanAdmin.Web.Client/CleanAdmin.Web.Client.csproj:1
- Projects may be oversized for their cohesion src/CleanAdmin.ApiService/CleanAdmin.ApiService.csproj:1
- Partial data-retention evidence
- Shell project: CleanAdmin.Infrastructure.Tests test/CleanAdmin.Infrastructure.Tests/CleanAdmin.Infrastructure.Tests.csproj
- REDACTED
- Dormant codebase
- Inverted test pyramid
- Commented-out code src/CleanAdmin.ApiService/Application/DomainEventHandlers/RoleDeletedDomainEventHandler.cs:14
- No ADRs
- Logging is not universal
- No release approval gate
- No changelog
- No performance benchmarks
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
- Silent fallback default on parse failure src/CleanAdmin.ApiService/Auth/Permission/UserPermissionHydrator.cs:56
- Silent fallback default in catch src/CleanAdmin.Web.Client/Helpers/JwtParser.cs:56
Minor — 6 finding(s)
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: Moq
- doc comments repeat the names src/CleanAdmin.ApiService/Auth/UserTokenService.cs:46
- doc comments repeat the names src/CleanAdmin.Web.Client/Extensions/WebAssemblyHostExtension.cs:12
- Off the main sequence: CleanAdmin.Shared src/CleanAdmin.Shared/CleanAdmin.Shared.csproj:1
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-80eca170a1c6452a8d661a6e2d58ea29/history.json --exit-code 0 --source . | 4 | 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-80eca170a1c6452a8d661a6e2d58ea29/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/CleanAdmin.MigrationService/Migrations --exclude src/CleanAdmin.Web.Client/ApiSdk/Api --exclude src/CleanAdmin.Web.Client/ApiSdk/Models . | 26 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list CleanAdmin.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 7 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 108 file(s) — `src/CleanAdmin.ApiService/Application/Commands/CreateOrderCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/DeliverGoodsCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/CreateMenuCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/DeleteMenuCommand.cs`, `src/CleanAdmin.ApiService/Application/Commands/Menus/HideMenuCommand.cs`, … (+103 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Email — 18 field(s)
- CreateUserCommand.Email src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:13
- UpdateCurrentUserBasicInfoCommand.Email src/CleanAdmin.ApiService/Application/Commands/Users/UpdateCurrentUserBasicInfoCommand.cs:9
- UpdateUserInfoCommand.Email src/CleanAdmin.ApiService/Application/Commands/Users/UpdateUserInfoCommand.cs:12
- UserInfoDto.Email src/CleanAdmin.ApiService/Application/Queries/Users/GetUserInfoQuery.cs:12
- GetUserListQuery.Email src/CleanAdmin.ApiService/Application/Queries/Users/GetUserListQuery.cs:8
- UserListItemDto.Email src/CleanAdmin.ApiService/Application/Queries/Users/GetUserListQuery.cs:17
- UserDto.Email src/CleanAdmin.ApiService/Clients/IUserServiceClient.cs:11
- CreateUserRequest.Email src/CleanAdmin.ApiService/Endpoints/Users/CreateUserEndpoint.cs:43
- UpdateCurrentUserProfileRequest.Email src/CleanAdmin.ApiService/Endpoints/Users/UpdateCurrentUserProfileEndpoint.cs:31
- UpdateUserRequest.Email src/CleanAdmin.ApiService/Endpoints/Users/UpdateUserEndpoint.cs:45
- GetUserListRequest.Email src/CleanAdmin.ApiService/Endpoints/Users/UserListEndpoint.cs:34
- User.Email src/CleanAdmin.Domain/AggregatesModel/UserAggregate/User.cs:22
- ListRequestBuilderGetQueryParameters.Email src/CleanAdmin.Web.Client/ApiSdk/Api/User/List/ListRequestBuilder.cs:98
- CleanAdminApiServiceApplicationQueriesUsersUserInfoDto.Email src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceApplicationQueriesUsersUserInfoDto.cs:18
- CleanAdminApiServiceApplicationQueriesUsersUserListItemDto.Email src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceApplicationQueriesUsersUserListItemDto.cs:20
- CleanAdminApiServiceEndpointsUsersCreateUserRequest.Email src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceEndpointsUsersCreateUserRequest.cs:26
- CleanAdminApiServiceEndpointsUsersUpdateCurrentUserProfileRequest.Email src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceEndpointsUsersUpdateCurrentUserProfileRequest.cs:18
- CleanAdminApiServiceEndpointsUsersUpdateUserRequest.Email src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceEndpointsUsersUpdateUserRequest.cs:26
Phone — 18 field(s)
- CreateUserCommand.Phone src/CleanAdmin.ApiService/Application/Commands/Users/CreateUserCommand.cs:14
- UpdateCurrentUserBasicInfoCommand.Phone src/CleanAdmin.ApiService/Application/Commands/Users/UpdateCurrentUserBasicInfoCommand.cs:10
- UpdateUserInfoCommand.Phone src/CleanAdmin.ApiService/Application/Commands/Users/UpdateUserInfoCommand.cs:13
- UserInfoDto.Phone src/CleanAdmin.ApiService/Application/Queries/Users/GetUserInfoQuery.cs:13
- GetUserListQuery.Phone src/CleanAdmin.ApiService/Application/Queries/Users/GetUserListQuery.cs:9
- UserListItemDto.Phone src/CleanAdmin.ApiService/Application/Queries/Users/GetUserListQuery.cs:18
- UserDto.Phone src/CleanAdmin.ApiService/Clients/IUserServiceClient.cs:11
- CreateUserRequest.Phone src/CleanAdmin.ApiService/Endpoints/Users/CreateUserEndpoint.cs:44
- UpdateCurrentUserProfileRequest.Phone src/CleanAdmin.ApiService/Endpoints/Users/UpdateCurrentUserProfileEndpoint.cs:32
- UpdateUserRequest.Phone src/CleanAdmin.ApiService/Endpoints/Users/UpdateUserEndpoint.cs:47
- GetUserListRequest.Phone src/CleanAdmin.ApiService/Endpoints/Users/UserListEndpoint.cs:35
- User.Phone src/CleanAdmin.Domain/AggregatesModel/UserAggregate/User.cs:19
- ListRequestBuilderGetQueryParameters.Phone src/CleanAdmin.Web.Client/ApiSdk/Api/User/List/ListRequestBuilder.cs:111
- CleanAdminApiServiceApplicationQueriesUsersUserInfoDto.Phone src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceApplicationQueriesUsersUserInfoDto.cs:34
- CleanAdminApiServiceApplicationQueriesUsersUserListItemDto.Phone src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceApplicationQueriesUsersUserListItemDto.cs:36
- CleanAdminApiServiceEndpointsUsersCreateUserRequest.Phone src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceEndpointsUsersCreateUserRequest.cs:42
- CleanAdminApiServiceEndpointsUsersUpdateCurrentUserProfileRequest.Phone src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceEndpointsUsersUpdateCurrentUserProfileRequest.cs:26
- CleanAdminApiServiceEndpointsUsersUpdateUserRequest.Phone src/CleanAdmin.Web.Client/ApiSdk/Models/CleanAdminApiServiceEndpointsUsersUpdateUserRequest.cs:34