Executive summary
babaktaremi/Clean-Architecture-Template is rated At risk because critical security findings are open. Its score is held back because it has pieces of business logic tied to the database or web code. It scores 41 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Domain Modelling, at 27, is the weakest lens and counts most in the score. The best first step is moving database and web code out of the business core, worth about 12 points. Raising Domain Modelling to 58 would lift the score to about 52.
Six known security holes in the packages the code depends on can be used by attackers. Five passwords or keys in the code and three in the code's history are open to anyone who can read the repository, and four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed, and the three unsafe settings in infrastructure or container files need changing to safe values. The data field that is written but never read needs removing.
The product code is 4,657 lines, about €7,000 to rebuild.
If Domain Modelling rose from 27 to 58, the lowest score rated Strong, the score would rise from 41 to about 52.
New since the last survey: 12 findings
- Cancellation propagation · Async delegate without CancellationToken: RegisterIdentityServices src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs
- CQS / query purity · Query handler writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken: GetToken.AdminGetTokenQueryHandler src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs
- CQS / query purity · Query handler writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken: GenerateUserToken.GenerateUserTokenQueryHandler src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs
- CQS / query purity · Query handler writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken: TokenRequest.PasswordUserTokenRequestQueryResult src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/PasswordUserTokenRequestQuery.Handler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Order src/Core/CleanArc.Domain/Entities/Order/Order.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Role src/Core/CleanArc.Domain/Entities/User/Role.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: RoleClaim src/Core/CleanArc.Domain/Entities/User/RoleClaim.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: User src/Core/CleanArc.Domain/Entities/User/User.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserClaim src/Core/CleanArc.Domain/Entities/User/UserClaim.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserLogin src/Core/CleanArc.Domain/Entities/User/UserLogin.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRole src/Core/CleanArc.Domain/Entities/User/UserRole.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserToken src/Core/CleanArc.Domain/Entities/User/UserToken.cs
Fixed since the last survey: 127 findings
- Dependency Hygiene · Vulnerable: NuGet.Packaging
- Cancellation propagation · Async method without CancellationToken: CreateNewOrder src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs
- Cancellation propagation · Async method without CancellationToken: GetUserOrders src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs
- Cancellation propagation · Async method without CancellationToken: UpdateOrder src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAllUserOrders src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs
- Cancellation propagation · Async method without CancellationToken: CreateUser REDACTED
- Cancellation propagation · Async method without CancellationToken: TokenRequest REDACTED
- Cancellation propagation · Async method without CancellationToken: ValidateUser REDACTED
- Cancellation propagation · Async method without CancellationToken: RefreshUserToken REDACTED
- Cancellation propagation · Async method without CancellationToken: RequestLogout REDACTED
- Cancellation propagation · Async method without CancellationToken: PasswordTokenRequest REDACTED
- Cancellation propagation · Async method drops its ambient CancellationToken: InvokeAsync src/API/CleanArc.WebFramework/EndpointFilters/ModelStateValidationEndpointFilter.cs
- Cancellation propagation · Async method drops its ambient CancellationToken: ExecuteResultAsync src/API/CleanArc.WebFramework/Filters/ServerErrorResult.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Common/LoggingBehavior.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Common/MetricsBehaviour.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Common/ValidateCommandBehavior.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Common/ValidateCommandBehavior.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Commands/AddAdminCommand/AddAdminCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Commands/AddAdminCommand/AddAdminCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Commands/AddAdminCommand/AddAdminCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Commands/AddOrderCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Commands/AddOrderCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Commands/AddOrderCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Commands/DeleteUserOrdersCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Commands/UpdateUserOrderCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Commands/UpdateUserOrderCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Queries/GetAllOrders/GetAllOrdersQueryHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Order/Queries/GetUserOrders/GetUserOrdersQueryHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Role/Commands/AddRoleCommand/AddRoleCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Role/Commands/UpdateRoleClaimsCommand/UpdateRoleClaimsCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Role/Queries/GetAllRolesQuery/GetAllRolesQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Role/Queries/GetAuthorizableRoutesQuery/GetAuthorizableRoutesQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/RefreshUserTokenCommand/RefreshUserTokenCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/RequestLogout/RequestLogoutCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Commands/RequestLogout/RequestLogoutCommand.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/GetUsers/GetUsersQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/PasswordUserTokenRequestQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/PasswordUserTokenRequestQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/PasswordUserTokenRequestQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/API/Plugins/CleanArc.Web.Plugins.Grpc/Services/OrderGrpcServices.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/API/Plugins/CleanArc.Web.Plugins.Grpc/Services/OrderGrpcServices.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/API/Plugins/CleanArc.Web.Plugins.Grpc/Services/OrderGrpcServices.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/API/CleanArc.Web.Api/Controllers/V1/Admin/OrderManagementController.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs
Rebuild cost: about €7,000 · Estimate
| Cost to rebuild | €2,300 to €12,000, for 39 to 122 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 4,657 lines of product code, of which 40% is declarations and boilerplate, 39% straight logic and 21% logic with branches |
| 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Application.Models.Common | 2 Application.Models.Jwt | 3 Domain.Common | 4 Infrastructure.Identity.Identity.Dtos | 5 Infrastructure.Persistence | 6 SharedKernel.ValidationBase | 7 Domain.Entities.Order | 8 SharedKernel.ValidationBase.Contracts | 9 WebFramework.BaseController | 10 Domain.Entities.User | 11 Application.Contracts | 12 Application.Contracts.Persistence | 13 Application.Models.Identity | 14 Infrastructure.Identity.Identity.Manager | 15 Application.Contracts.Identity | 16 Application.Features.Order.Queries.GetAllOrders | 17 Application.Features.Order.Queries.GetUserOrders | 18 Application.Features.Users.Commands.RefreshUserTokenCommand | 19 Infrastructure.Identity.Identity | 20 Infrastructure.Identity.Identity.SeedDatabaseService | 21 Infrastructure.Identity.Jwt | 22 Infrastructure.Persistence.Repositories.Common | 23 Application.Features.Admin.Commands.AddAdminCommand | 24 Application.Features.Admin.Queries.GetToken | 25 Application.Features.Order.Commands | 26 Application.Features.Role.Commands.AddRoleCommand | 27 Application.Features.Role.Commands.UpdateRoleClaimsCommand | 28 Application.Features.Role.Queries.GetAllRolesQuery | 29 Application.Features.Role.Queries.GetAuthorizableRoutesQuery | 30 Application.Features.Users.Commands.Create | 31 Application.Features.Users.Commands.RequestLogout | 32 Application.Features.Users.Queries.GenerateUserToken | 33 Application.Features.Users.Queries.GetUsers | 34 Application.Features.Users.Queries.TokenRequest | 35 Infrastructure.Identity.Identity.PermissionManager | 36 Infrastructure.Identity.UserManager | 37 Infrastructure.Persistence.Repositories | 38 Web.Api.Controllers.V1.Admin | 39 Web.Api.Controllers.V1.Order | 40 Web.Api.Controllers.V1.UserManagement |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.Models.Common | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.Models.Jwt | ||||||||||||||||||||||||||||||||||||||||
| 3 Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 4 Infrastructure.Identity.Identity.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 5 Infrastructure.Persistence | ||||||||||||||||||||||||||||||||||||||||
| 6 SharedKernel.ValidationBase | ||||||||||||||||||||||||||||||||||||||||
| 7 Domain.Entities.Order | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 SharedKernel.ValidationBase.Contracts | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 WebFramework.BaseController | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Domain.Entities.User | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Application.Contracts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Application.Contracts.Persistence | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 Application.Models.Identity | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Infrastructure.Identity.Identity.Manager | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 Application.Contracts.Identity | 3 | 5 | ||||||||||||||||||||||||||||||||||||||
| 16 Application.Features.Order.Queries.GetAllOrders | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Application.Features.Order.Queries.GetUserOrders | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Application.Features.Users.Commands.RefreshUserTokenCommand | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 19 Infrastructure.Identity.Identity | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 Infrastructure.Identity.Identity.SeedDatabaseService | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 Infrastructure.Identity.Jwt | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 22 Infrastructure.Persistence.Repositories.Common | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 23 Application.Features.Admin.Commands.AddAdminCommand | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 Application.Features.Admin.Queries.GetToken | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 Application.Features.Order.Commands | 3 | 2 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 26 Application.Features.Role.Commands.AddRoleCommand | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 Application.Features.Role.Commands.UpdateRoleClaimsCommand | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Application.Features.Role.Queries.GetAllRolesQuery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Application.Features.Role.Queries.GetAuthorizableRoutesQuery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Application.Features.Users.Commands.Create | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Application.Features.Users.Commands.RequestLogout | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Application.Features.Users.Queries.GenerateUserToken | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 Application.Features.Users.Queries.GetUsers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Application.Features.Users.Queries.TokenRequest | 2 | 1 | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 Infrastructure.Identity.Identity.PermissionManager | 1 | 1 | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 36 Infrastructure.Identity.UserManager | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Infrastructure.Persistence.Repositories | 2 | 1 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 38 Web.Api.Controllers.V1.Admin | 4 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 Web.Api.Controllers.V1.Order | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 Web.Api.Controllers.V1.UserManagement | 1 | 1 | 1 | 1 | 2 |
7→3 Domain.Entities.Order uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Order uses a type in Domain.Common.
- The types involved
CleanArc.Domain.Entities.Order.Order→CleanArc.Domain.Common.BaseEntity
- Direction
- Domain.Entities.Order uses Domain.Common, so a change to Domain.Common can break Domain.Entities.Order, while a change to Domain.Entities.Order can't break Domain.Common.
- Position
- Below the diagonal: Domain.Entities.Order uses a module listed above it, which is the healthy direction.
7→10 Domain.Entities.Order uses Domain.Entities.User part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Order uses a type in Domain.Entities.User.
- The types involved
CleanArc.Domain.Entities.Order.Order→CleanArc.Domain.Entities.User.User
- Direction
- Domain.Entities.Order uses Domain.Entities.User, so a change to Domain.Entities.User can break Domain.Entities.Order, while a change to Domain.Entities.Order can't break Domain.Entities.User.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→6 SharedKernel.ValidationBase.Contracts uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in SharedKernel.ValidationBase.Contracts uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- SharedKernel.ValidationBase.Contracts uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break SharedKernel.ValidationBase.Contracts, while a change to SharedKernel.ValidationBase.Contracts can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: SharedKernel.ValidationBase.Contracts uses a module listed above it, which is the healthy direction.
9→1 WebFramework.BaseController uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in WebFramework.BaseController uses a type in Application.Models.Common.
- The types involved
CleanArc.WebFramework.BaseController.BaseController→CleanArc.Application.Models.Common.OperationResult
- Direction
- WebFramework.BaseController uses Application.Models.Common, so a change to Application.Models.Common can break WebFramework.BaseController, while a change to WebFramework.BaseController can't break Application.Models.Common.
- Position
- Below the diagonal: WebFramework.BaseController uses a module listed above it, which is the healthy direction.
10→3 Domain.Entities.User uses Domain.Common✕
- Connections
- 8 pairs of types, where a type in Domain.Entities.User uses a type in Domain.Common.
- The types involved
CleanArc.Domain.Entities.User.Role→CleanArc.Domain.Common.IEntityCleanArc.Domain.Entities.User.RoleClaim→CleanArc.Domain.Common.IEntityCleanArc.Domain.Entities.User.User→CleanArc.Domain.Common.IEntityCleanArc.Domain.Entities.User.UserClaim→CleanArc.Domain.Common.IEntityCleanArc.Domain.Entities.User.UserLogin→CleanArc.Domain.Common.IEntityCleanArc.Domain.Entities.User.UserRefreshToken→CleanArc.Domain.Common.BaseEntityCleanArc.Domain.Entities.User.UserRole→CleanArc.Domain.Common.IEntityCleanArc.Domain.Entities.User.UserToken→CleanArc.Domain.Common.IEntity
- Direction
- Domain.Entities.User uses Domain.Common, so a change to Domain.Common can break Domain.Entities.User, while a change to Domain.Entities.User can't break Domain.Common.
- Position
- Below the diagonal: Domain.Entities.User uses a module listed above it, which is the healthy direction.
10→7 Domain.Entities.User uses Domain.Entities.Order✕
- Connections
- 1 pair of types, where a type in Domain.Entities.User uses a type in Domain.Entities.Order.
- The types involved
CleanArc.Domain.Entities.User.User→CleanArc.Domain.Entities.Order.Order
- Direction
- Domain.Entities.User uses Domain.Entities.Order, so a change to Domain.Entities.Order can break Domain.Entities.User, while a change to Domain.Entities.User can't break Domain.Entities.Order.
- Position
- Below the diagonal: Domain.Entities.User uses a module listed above it, which is the healthy direction.
11→2 Application.Contracts uses Application.Models.Jwt✕
- Connections
- 1 pair of types, where a type in Application.Contracts uses a type in Application.Models.Jwt.
- The types involved
CleanArc.Application.Contracts.IJwtService→CleanArc.Application.Models.Jwt.AccessToken
- Direction
- Application.Contracts uses Application.Models.Jwt, so a change to Application.Models.Jwt can break Application.Contracts, while a change to Application.Contracts can't break Application.Models.Jwt.
- Position
- Below the diagonal: Application.Contracts uses a module listed above it, which is the healthy direction.
11→10 Application.Contracts uses Domain.Entities.User✕
- Connections
- 1 pair of types, where a type in Application.Contracts uses a type in Domain.Entities.User.
- The types involved
CleanArc.Application.Contracts.IJwtService→CleanArc.Domain.Entities.User.User
- Direction
- Application.Contracts uses Domain.Entities.User, so a change to Domain.Entities.User can break Application.Contracts, while a change to Application.Contracts can't break Domain.Entities.User.
- Position
- Below the diagonal: Application.Contracts uses a module listed above it, which is the healthy direction.
12→7 Application.Contracts.Persistence uses Domain.Entities.Order✕
- Connections
- 1 pair of types, where a type in Application.Contracts.Persistence uses a type in Domain.Entities.Order.
- The types involved
CleanArc.Application.Contracts.Persistence.IOrderRepository→CleanArc.Domain.Entities.Order.Order
- Direction
- Application.Contracts.Persistence uses Domain.Entities.Order, so a change to Domain.Entities.Order can break Application.Contracts.Persistence, while a change to Application.Contracts.Persistence can't break Domain.Entities.Order.
- Position
- Below the diagonal: Application.Contracts.Persistence uses a module listed above it, which is the healthy direction.
12→10 Application.Contracts.Persistence uses Domain.Entities.User✕
- Connections
- 2 pairs of types, where a type in Application.Contracts.Persistence uses a type in Domain.Entities.User.
- The types involved
CleanArc.Application.Contracts.Persistence.IUserRefreshTokenRepository→CleanArc.Domain.Entities.User.UserCleanArc.Application.Contracts.Persistence.IUserRefreshTokenRepository→CleanArc.Domain.Entities.User.UserRefreshToken
- Direction
- Application.Contracts.Persistence uses Domain.Entities.User, so a change to Domain.Entities.User can break Application.Contracts.Persistence, while a change to Application.Contracts.Persistence can't break Domain.Entities.User.
- Position
- Below the diagonal: Application.Contracts.Persistence uses a module listed above it, which is the healthy direction.
13→10 Application.Models.Identity uses Domain.Entities.User✕
- Connections
- 1 pair of types, where a type in Application.Models.Identity uses a type in Domain.Entities.User.
- The types involved
CleanArc.Application.Models.Identity.RolePermissionDto→CleanArc.Domain.Entities.User.Role
- Direction
- Application.Models.Identity uses Domain.Entities.User, so a change to Domain.Entities.User can break Application.Models.Identity, while a change to Application.Models.Identity can't break Domain.Entities.User.
- Position
- Below the diagonal: Application.Models.Identity uses a module listed above it, which is the healthy direction.
14→10 Infrastructure.Identity.Identity.Manager uses Domain.Entities.User✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Identity.Identity.Manager uses a type in Domain.Entities.User.
- The types involved
CleanArc.Infrastructure.Identity.Identity.Manager.AppRoleManager→CleanArc.Domain.Entities.User.RoleCleanArc.Infrastructure.Identity.Identity.Manager.AppSignInManager→CleanArc.Domain.Entities.User.UserCleanArc.Infrastructure.Identity.Identity.Manager.AppUserManager→CleanArc.Domain.Entities.User.User
- Direction
- Infrastructure.Identity.Identity.Manager uses Domain.Entities.User, so a change to Domain.Entities.User can break Infrastructure.Identity.Identity.Manager, while a change to Infrastructure.Identity.Identity.Manager can't break Domain.Entities.User.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.Manager uses a module listed above it, which is the healthy direction.
15→10 Application.Contracts.Identity uses Domain.Entities.User✕
- Connections
- 3 pairs of types, where a type in Application.Contracts.Identity uses a type in Domain.Entities.User.
- The types involved
CleanArc.Application.Contracts.Identity.IAppUserManager→CleanArc.Domain.Entities.User.RoleCleanArc.Application.Contracts.Identity.IAppUserManager→CleanArc.Domain.Entities.User.UserCleanArc.Application.Contracts.Identity.IRoleManagerService→CleanArc.Domain.Entities.User.Role
- Direction
- Application.Contracts.Identity uses Domain.Entities.User, so a change to Domain.Entities.User can break Application.Contracts.Identity, while a change to Application.Contracts.Identity can't break Domain.Entities.User.
- Position
- Below the diagonal: Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
15→13 Application.Contracts.Identity uses Application.Models.Identity✕
- Connections
- 5 pairs of types, where a type in Application.Contracts.Identity uses a type in Application.Models.Identity.
- The types involved
CleanArc.Application.Contracts.Identity.IRoleManagerService→CleanArc.Application.Models.Identity.ActionDescriptionDtoCleanArc.Application.Contracts.Identity.IRoleManagerService→CleanArc.Application.Models.Identity.CreateRoleDtoCleanArc.Application.Contracts.Identity.IRoleManagerService→CleanArc.Application.Models.Identity.EditRolePermissionsDtoCleanArc.Application.Contracts.Identity.IRoleManagerService→CleanArc.Application.Models.Identity.GetRolesDtoCleanArc.Application.Contracts.Identity.IRoleManagerService→CleanArc.Application.Models.Identity.RolePermissionDto
- Direction
- Application.Contracts.Identity uses Application.Models.Identity, so a change to Application.Models.Identity can break Application.Contracts.Identity, while a change to Application.Contracts.Identity can't break Application.Models.Identity.
- Position
- Below the diagonal: Application.Contracts.Identity uses a module listed above it, which is the healthy direction.
16→1 Application.Features.Order.Queries.GetAllOrders uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Order.Queries.GetAllOrders uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Order.Queries.GetAllOrders.GetAllOrdersQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Order.Queries.GetAllOrders uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Order.Queries.GetAllOrders, while a change to Application.Features.Order.Queries.GetAllOrders can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Order.Queries.GetAllOrders uses a module listed above it, which is the healthy direction.
16→12 Application.Features.Order.Queries.GetAllOrders uses Application.Contracts.Persistence✕
- Connections
- 1 pair of types, where a type in Application.Features.Order.Queries.GetAllOrders uses a type in Application.Contracts.Persistence.
- The types involved
CleanArc.Application.Features.Order.Queries.GetAllOrders.GetAllOrdersQueryHandler→CleanArc.Application.Contracts.Persistence.IUnitOfWork
- Direction
- Application.Features.Order.Queries.GetAllOrders uses Application.Contracts.Persistence, so a change to Application.Contracts.Persistence can break Application.Features.Order.Queries.GetAllOrders, while a change to Application.Features.Order.Queries.GetAllOrders can't break Application.Contracts.Persistence.
- Position
- Below the diagonal: Application.Features.Order.Queries.GetAllOrders uses a module listed above it, which is the healthy direction.
17→1 Application.Features.Order.Queries.GetUserOrders uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Order.Queries.GetUserOrders uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Order.Queries.GetUserOrders.GetUserOrdersQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Order.Queries.GetUserOrders uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Order.Queries.GetUserOrders, while a change to Application.Features.Order.Queries.GetUserOrders can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Order.Queries.GetUserOrders uses a module listed above it, which is the healthy direction.
17→12 Application.Features.Order.Queries.GetUserOrders uses Application.Contracts.Persistence✕
- Connections
- 1 pair of types, where a type in Application.Features.Order.Queries.GetUserOrders uses a type in Application.Contracts.Persistence.
- The types involved
CleanArc.Application.Features.Order.Queries.GetUserOrders.GetUserOrdersQueryHandler→CleanArc.Application.Contracts.Persistence.IUnitOfWork
- Direction
- Application.Features.Order.Queries.GetUserOrders uses Application.Contracts.Persistence, so a change to Application.Contracts.Persistence can break Application.Features.Order.Queries.GetUserOrders, while a change to Application.Features.Order.Queries.GetUserOrders can't break Application.Contracts.Persistence.
- Position
- Below the diagonal: Application.Features.Order.Queries.GetUserOrders uses a module listed above it, which is the healthy direction.
18→1 Application.Features.Users.Commands.RefreshUserTokenCommand uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshUserTokenCommand uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Users.Commands.RefreshUserTokenCommand.RefreshUserTokenCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Users.Commands.RefreshUserTokenCommand uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Users.Commands.RefreshUserTokenCommand, while a change to Application.Features.Users.Commands.RefreshUserTokenCommand can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshUserTokenCommand uses a module listed above it, which is the healthy direction.
18→2 Application.Features.Users.Commands.RefreshUserTokenCommand uses Application.Models.Jwt✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshUserTokenCommand uses a type in Application.Models.Jwt.
- The types involved
CleanArc.Application.Features.Users.Commands.RefreshUserTokenCommand.RefreshUserTokenCommandHandler→CleanArc.Application.Models.Jwt.AccessToken
- Direction
- Application.Features.Users.Commands.RefreshUserTokenCommand uses Application.Models.Jwt, so a change to Application.Models.Jwt can break Application.Features.Users.Commands.RefreshUserTokenCommand, while a change to Application.Features.Users.Commands.RefreshUserTokenCommand can't break Application.Models.Jwt.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshUserTokenCommand uses a module listed above it, which is the healthy direction.
18→6 Application.Features.Users.Commands.RefreshUserTokenCommand uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshUserTokenCommand uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Users.Commands.RefreshUserTokenCommand.RefreshUserTokenCommand→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Users.Commands.RefreshUserTokenCommand uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Users.Commands.RefreshUserTokenCommand, while a change to Application.Features.Users.Commands.RefreshUserTokenCommand can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshUserTokenCommand uses a module listed above it, which is the healthy direction.
18→8 Application.Features.Users.Commands.RefreshUserTokenCommand uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshUserTokenCommand uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Users.Commands.RefreshUserTokenCommand.RefreshUserTokenCommand→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Users.Commands.RefreshUserTokenCommand uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Users.Commands.RefreshUserTokenCommand, while a change to Application.Features.Users.Commands.RefreshUserTokenCommand can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshUserTokenCommand uses a module listed above it, which is the healthy direction.
18→11 Application.Features.Users.Commands.RefreshUserTokenCommand uses Application.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshUserTokenCommand uses a type in Application.Contracts.
- The types involved
CleanArc.Application.Features.Users.Commands.RefreshUserTokenCommand.RefreshUserTokenCommandHandler→CleanArc.Application.Contracts.IJwtService
- Direction
- Application.Features.Users.Commands.RefreshUserTokenCommand uses Application.Contracts, so a change to Application.Contracts can break Application.Features.Users.Commands.RefreshUserTokenCommand, while a change to Application.Features.Users.Commands.RefreshUserTokenCommand can't break Application.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshUserTokenCommand uses a module listed above it, which is the healthy direction.
19→10 Infrastructure.Identity.Identity uses Domain.Entities.User✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Identity uses a type in Domain.Entities.User.
- The types involved
CleanArc.Infrastructure.Identity.Identity.AppUserClaimsPrincipleFactory→CleanArc.Domain.Entities.User.User
- Direction
- Infrastructure.Identity.Identity uses Domain.Entities.User, so a change to Domain.Entities.User can break Infrastructure.Identity.Identity, while a change to Infrastructure.Identity.Identity can't break Domain.Entities.User.
- Position
- Below the diagonal: Infrastructure.Identity.Identity uses a module listed above it, which is the healthy direction.
19→14 Infrastructure.Identity.Identity uses Infrastructure.Identity.Identity.Manager✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Identity.Identity uses a type in Infrastructure.Identity.Identity.Manager.
- The types involved
CleanArc.Infrastructure.Identity.Identity.AppUserClaimsPrincipleFactory→CleanArc.Infrastructure.Identity.Identity.Manager.AppRoleManagerCleanArc.Infrastructure.Identity.Identity.AppUserClaimsPrincipleFactory→CleanArc.Infrastructure.Identity.Identity.Manager.AppUserManager
- Direction
- Infrastructure.Identity.Identity uses Infrastructure.Identity.Identity.Manager, so a change to Infrastructure.Identity.Identity.Manager can break Infrastructure.Identity.Identity, while a change to Infrastructure.Identity.Identity can't break Infrastructure.Identity.Identity.Manager.
- Position
- Below the diagonal: Infrastructure.Identity.Identity uses a module listed above it, which is the healthy direction.
20→14 Infrastructure.Identity.Identity.SeedDatabaseService uses Infrastructure.Identity.Identity.Manager✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Identity.Identity.SeedDatabaseService uses a type in Infrastructure.Identity.Identity.Manager.
- The types involved
CleanArc.Infrastructure.Identity.Identity.SeedDatabaseService.SeedDataBase→CleanArc.Infrastructure.Identity.Identity.Manager.AppRoleManagerCleanArc.Infrastructure.Identity.Identity.SeedDatabaseService.SeedDataBase→CleanArc.Infrastructure.Identity.Identity.Manager.AppUserManager
- Direction
- Infrastructure.Identity.Identity.SeedDatabaseService uses Infrastructure.Identity.Identity.Manager, so a change to Infrastructure.Identity.Identity.Manager can break Infrastructure.Identity.Identity.SeedDatabaseService, while a change to Infrastructure.Identity.Identity.SeedDatabaseService can't break Infrastructure.Identity.Identity.Manager.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.SeedDatabaseService uses a module listed above it, which is the healthy direction.
21→2 Infrastructure.Identity.Jwt uses Application.Models.Jwt✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Jwt uses a type in Application.Models.Jwt.
- The types involved
CleanArc.Infrastructure.Identity.Jwt.JwtService→CleanArc.Application.Models.Jwt.AccessToken
- Direction
- Infrastructure.Identity.Jwt uses Application.Models.Jwt, so a change to Application.Models.Jwt can break Infrastructure.Identity.Jwt, while a change to Infrastructure.Identity.Jwt can't break Application.Models.Jwt.
- Position
- Below the diagonal: Infrastructure.Identity.Jwt uses a module listed above it, which is the healthy direction.
21→4 Infrastructure.Identity.Jwt uses Infrastructure.Identity.Identity.Dtos✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Jwt uses a type in Infrastructure.Identity.Identity.Dtos.
- The types involved
CleanArc.Infrastructure.Identity.Jwt.JwtService→CleanArc.Infrastructure.Identity.Identity.Dtos.IdentitySettings
- Direction
- Infrastructure.Identity.Jwt uses Infrastructure.Identity.Identity.Dtos, so a change to Infrastructure.Identity.Identity.Dtos can break Infrastructure.Identity.Jwt, while a change to Infrastructure.Identity.Jwt can't break Infrastructure.Identity.Identity.Dtos.
- Position
- Below the diagonal: Infrastructure.Identity.Jwt uses a module listed above it, which is the healthy direction.
21→10 Infrastructure.Identity.Jwt uses Domain.Entities.User✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Jwt uses a type in Domain.Entities.User.
- The types involved
CleanArc.Infrastructure.Identity.Jwt.JwtService→CleanArc.Domain.Entities.User.User
- Direction
- Infrastructure.Identity.Jwt uses Domain.Entities.User, so a change to Domain.Entities.User can break Infrastructure.Identity.Jwt, while a change to Infrastructure.Identity.Jwt can't break Domain.Entities.User.
- Position
- Below the diagonal: Infrastructure.Identity.Jwt uses a module listed above it, which is the healthy direction.
21→11 Infrastructure.Identity.Jwt uses Application.Contracts✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Jwt uses a type in Application.Contracts.
- The types involved
CleanArc.Infrastructure.Identity.Jwt.JwtService→CleanArc.Application.Contracts.IJwtService
- Direction
- Infrastructure.Identity.Jwt uses Application.Contracts, so a change to Application.Contracts can break Infrastructure.Identity.Jwt, while a change to Infrastructure.Identity.Jwt can't break Application.Contracts.
- Position
- Below the diagonal: Infrastructure.Identity.Jwt uses a module listed above it, which is the healthy direction.
21→12 Infrastructure.Identity.Jwt uses Application.Contracts.Persistence✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Jwt uses a type in Application.Contracts.Persistence.
- The types involved
CleanArc.Infrastructure.Identity.Jwt.JwtService→CleanArc.Application.Contracts.Persistence.IUnitOfWork
- Direction
- Infrastructure.Identity.Jwt uses Application.Contracts.Persistence, so a change to Application.Contracts.Persistence can break Infrastructure.Identity.Jwt, while a change to Infrastructure.Identity.Jwt can't break Application.Contracts.Persistence.
- Position
- Below the diagonal: Infrastructure.Identity.Jwt uses a module listed above it, which is the healthy direction.
21→14 Infrastructure.Identity.Jwt uses Infrastructure.Identity.Identity.Manager✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Jwt uses a type in Infrastructure.Identity.Identity.Manager.
- The types involved
CleanArc.Infrastructure.Identity.Jwt.JwtService→CleanArc.Infrastructure.Identity.Identity.Manager.AppUserManager
- Direction
- Infrastructure.Identity.Jwt uses Infrastructure.Identity.Identity.Manager, so a change to Infrastructure.Identity.Identity.Manager can break Infrastructure.Identity.Jwt, while a change to Infrastructure.Identity.Jwt can't break Infrastructure.Identity.Identity.Manager.
- Position
- Below the diagonal: Infrastructure.Identity.Jwt uses a module listed above it, which is the healthy direction.
22→5 Infrastructure.Persistence.Repositories.Common uses Infrastructure.Persistence✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Persistence.Repositories.Common uses a type in Infrastructure.Persistence.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.Common.BaseAsyncRepository→CleanArc.Infrastructure.Persistence.ApplicationDbContextCleanArc.Infrastructure.Persistence.Repositories.Common.UnitOfWork→CleanArc.Infrastructure.Persistence.ApplicationDbContext
- Direction
- Infrastructure.Persistence.Repositories.Common uses Infrastructure.Persistence, so a change to Infrastructure.Persistence can break Infrastructure.Persistence.Repositories.Common, while a change to Infrastructure.Persistence.Repositories.Common can't break Infrastructure.Persistence.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories.Common uses a module listed above it, which is the healthy direction.
22→12 Infrastructure.Persistence.Repositories.Common uses Application.Contracts.Persistence✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Persistence.Repositories.Common uses a type in Application.Contracts.Persistence.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.Common.UnitOfWork→CleanArc.Application.Contracts.Persistence.IOrderRepositoryCleanArc.Infrastructure.Persistence.Repositories.Common.UnitOfWork→CleanArc.Application.Contracts.Persistence.IUnitOfWorkCleanArc.Infrastructure.Persistence.Repositories.Common.UnitOfWork→CleanArc.Application.Contracts.Persistence.IUserRefreshTokenRepository
- Direction
- Infrastructure.Persistence.Repositories.Common uses Application.Contracts.Persistence, so a change to Application.Contracts.Persistence can break Infrastructure.Persistence.Repositories.Common, while a change to Infrastructure.Persistence.Repositories.Common can't break Application.Contracts.Persistence.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories.Common uses a module listed above it, which is the healthy direction.
23→1 Application.Features.Admin.Commands.AddAdminCommand uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Commands.AddAdminCommand uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Admin.Commands.AddAdminCommand.AddAdminCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Admin.Commands.AddAdminCommand uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Admin.Commands.AddAdminCommand, while a change to Application.Features.Admin.Commands.AddAdminCommand can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Admin.Commands.AddAdminCommand uses a module listed above it, which is the healthy direction.
23→6 Application.Features.Admin.Commands.AddAdminCommand uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Commands.AddAdminCommand uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Admin.Commands.AddAdminCommand.AddAdminCommand→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Admin.Commands.AddAdminCommand uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Admin.Commands.AddAdminCommand, while a change to Application.Features.Admin.Commands.AddAdminCommand can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Admin.Commands.AddAdminCommand uses a module listed above it, which is the healthy direction.
23→8 Application.Features.Admin.Commands.AddAdminCommand uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Commands.AddAdminCommand uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Admin.Commands.AddAdminCommand.AddAdminCommand→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Admin.Commands.AddAdminCommand uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Admin.Commands.AddAdminCommand, while a change to Application.Features.Admin.Commands.AddAdminCommand can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Admin.Commands.AddAdminCommand uses a module listed above it, which is the healthy direction.
23→15 Application.Features.Admin.Commands.AddAdminCommand uses Application.Contracts.Identity✕
- Connections
- 2 pairs of types, where a type in Application.Features.Admin.Commands.AddAdminCommand uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Admin.Commands.AddAdminCommand.AddAdminCommandHandler→CleanArc.Application.Contracts.Identity.IAppUserManagerCleanArc.Application.Features.Admin.Commands.AddAdminCommand.AddAdminCommandHandler→CleanArc.Application.Contracts.Identity.IRoleManagerService
- Direction
- Application.Features.Admin.Commands.AddAdminCommand uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Admin.Commands.AddAdminCommand, while a change to Application.Features.Admin.Commands.AddAdminCommand can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Admin.Commands.AddAdminCommand uses a module listed above it, which is the healthy direction.
24→1 Application.Features.Admin.Queries.GetToken uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Queries.GetToken uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Admin.Queries.GetToken uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Admin.Queries.GetToken, while a change to Application.Features.Admin.Queries.GetToken can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Admin.Queries.GetToken uses a module listed above it, which is the healthy direction.
24→2 Application.Features.Admin.Queries.GetToken uses Application.Models.Jwt✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Queries.GetToken uses a type in Application.Models.Jwt.
- The types involved
CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQueryResult→CleanArc.Application.Models.Jwt.AccessToken
- Direction
- Application.Features.Admin.Queries.GetToken uses Application.Models.Jwt, so a change to Application.Models.Jwt can break Application.Features.Admin.Queries.GetToken, while a change to Application.Features.Admin.Queries.GetToken can't break Application.Models.Jwt.
- Position
- Below the diagonal: Application.Features.Admin.Queries.GetToken uses a module listed above it, which is the healthy direction.
24→6 Application.Features.Admin.Queries.GetToken uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Queries.GetToken uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQuery→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Admin.Queries.GetToken uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Admin.Queries.GetToken, while a change to Application.Features.Admin.Queries.GetToken can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Admin.Queries.GetToken uses a module listed above it, which is the healthy direction.
24→8 Application.Features.Admin.Queries.GetToken uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Queries.GetToken uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQuery→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Admin.Queries.GetToken uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Admin.Queries.GetToken, while a change to Application.Features.Admin.Queries.GetToken can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Admin.Queries.GetToken uses a module listed above it, which is the healthy direction.
24→11 Application.Features.Admin.Queries.GetToken uses Application.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Queries.GetToken uses a type in Application.Contracts.
- The types involved
CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQueryHandler→CleanArc.Application.Contracts.IJwtService
- Direction
- Application.Features.Admin.Queries.GetToken uses Application.Contracts, so a change to Application.Contracts can break Application.Features.Admin.Queries.GetToken, while a change to Application.Features.Admin.Queries.GetToken can't break Application.Contracts.
- Position
- Below the diagonal: Application.Features.Admin.Queries.GetToken uses a module listed above it, which is the healthy direction.
24→15 Application.Features.Admin.Queries.GetToken uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Admin.Queries.GetToken uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQueryHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Admin.Queries.GetToken uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Admin.Queries.GetToken, while a change to Application.Features.Admin.Queries.GetToken can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Admin.Queries.GetToken uses a module listed above it, which is the healthy direction.
25→1 Application.Features.Order.Commands uses Application.Models.Common✕
- Connections
- 3 pairs of types, where a type in Application.Features.Order.Commands uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Order.Commands.AddOrderCommandHandler→CleanArc.Application.Models.Common.OperationResultCleanArc.Application.Features.Order.Commands.DeleteUserOrdersCommandHandler→CleanArc.Application.Models.Common.OperationResultCleanArc.Application.Features.Order.Commands.UpdateUserOrderCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Order.Commands uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Order.Commands, while a change to Application.Features.Order.Commands can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
25→6 Application.Features.Order.Commands uses SharedKernel.ValidationBase✕
- Connections
- 2 pairs of types, where a type in Application.Features.Order.Commands uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Order.Commands.AddOrderCommand→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProviderCleanArc.Application.Features.Order.Commands.UpdateUserOrderCommand→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Order.Commands uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Order.Commands, while a change to Application.Features.Order.Commands can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
25→8 Application.Features.Order.Commands uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 2 pairs of types, where a type in Application.Features.Order.Commands uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Order.Commands.AddOrderCommand→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModelCleanArc.Application.Features.Order.Commands.UpdateUserOrderCommand→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Order.Commands uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Order.Commands, while a change to Application.Features.Order.Commands can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
25→12 Application.Features.Order.Commands uses Application.Contracts.Persistence✕
- Connections
- 3 pairs of types, where a type in Application.Features.Order.Commands uses a type in Application.Contracts.Persistence.
- The types involved
CleanArc.Application.Features.Order.Commands.AddOrderCommandHandler→CleanArc.Application.Contracts.Persistence.IUnitOfWorkCleanArc.Application.Features.Order.Commands.DeleteUserOrdersCommandHandler→CleanArc.Application.Contracts.Persistence.IUnitOfWorkCleanArc.Application.Features.Order.Commands.UpdateUserOrderCommandHandler→CleanArc.Application.Contracts.Persistence.IUnitOfWork
- Direction
- Application.Features.Order.Commands uses Application.Contracts.Persistence, so a change to Application.Contracts.Persistence can break Application.Features.Order.Commands, while a change to Application.Features.Order.Commands can't break Application.Contracts.Persistence.
- Position
- Below the diagonal: Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
25→15 Application.Features.Order.Commands uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Order.Commands uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Order.Commands.AddOrderCommandHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Order.Commands uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Order.Commands, while a change to Application.Features.Order.Commands can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
26→1 Application.Features.Role.Commands.AddRoleCommand uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Commands.AddRoleCommand uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Role.Commands.AddRoleCommand.AddRoleCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Role.Commands.AddRoleCommand uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Role.Commands.AddRoleCommand, while a change to Application.Features.Role.Commands.AddRoleCommand can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Role.Commands.AddRoleCommand uses a module listed above it, which is the healthy direction.
26→6 Application.Features.Role.Commands.AddRoleCommand uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Commands.AddRoleCommand uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Role.Commands.AddRoleCommand.AddRoleCommand→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Role.Commands.AddRoleCommand uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Role.Commands.AddRoleCommand, while a change to Application.Features.Role.Commands.AddRoleCommand can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Role.Commands.AddRoleCommand uses a module listed above it, which is the healthy direction.
26→8 Application.Features.Role.Commands.AddRoleCommand uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Commands.AddRoleCommand uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Role.Commands.AddRoleCommand.AddRoleCommand→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Role.Commands.AddRoleCommand uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Role.Commands.AddRoleCommand, while a change to Application.Features.Role.Commands.AddRoleCommand can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Role.Commands.AddRoleCommand uses a module listed above it, which is the healthy direction.
26→15 Application.Features.Role.Commands.AddRoleCommand uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Commands.AddRoleCommand uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Role.Commands.AddRoleCommand.AddRoleCommandHandler→CleanArc.Application.Contracts.Identity.IRoleManagerService
- Direction
- Application.Features.Role.Commands.AddRoleCommand uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Role.Commands.AddRoleCommand, while a change to Application.Features.Role.Commands.AddRoleCommand can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Role.Commands.AddRoleCommand uses a module listed above it, which is the healthy direction.
27→1 Application.Features.Role.Commands.UpdateRoleClaimsCommand uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Commands.UpdateRoleClaimsCommand uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Role.Commands.UpdateRoleClaimsCommand.UpdateRoleClaimsCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Role.Commands.UpdateRoleClaimsCommand uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Role.Commands.UpdateRoleClaimsCommand, while a change to Application.Features.Role.Commands.UpdateRoleClaimsCommand can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Role.Commands.UpdateRoleClaimsCommand uses a module listed above it, which is the healthy direction.
27→15 Application.Features.Role.Commands.UpdateRoleClaimsCommand uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Commands.UpdateRoleClaimsCommand uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Role.Commands.UpdateRoleClaimsCommand.UpdateRoleClaimsCommandHandler→CleanArc.Application.Contracts.Identity.IRoleManagerService
- Direction
- Application.Features.Role.Commands.UpdateRoleClaimsCommand uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Role.Commands.UpdateRoleClaimsCommand, while a change to Application.Features.Role.Commands.UpdateRoleClaimsCommand can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Role.Commands.UpdateRoleClaimsCommand uses a module listed above it, which is the healthy direction.
28→1 Application.Features.Role.Queries.GetAllRolesQuery uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Queries.GetAllRolesQuery uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Role.Queries.GetAllRolesQuery.GetAllRolesQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Role.Queries.GetAllRolesQuery uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Role.Queries.GetAllRolesQuery, while a change to Application.Features.Role.Queries.GetAllRolesQuery can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Role.Queries.GetAllRolesQuery uses a module listed above it, which is the healthy direction.
28→15 Application.Features.Role.Queries.GetAllRolesQuery uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Queries.GetAllRolesQuery uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Role.Queries.GetAllRolesQuery.GetAllRolesQueryHandler→CleanArc.Application.Contracts.Identity.IRoleManagerService
- Direction
- Application.Features.Role.Queries.GetAllRolesQuery uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Role.Queries.GetAllRolesQuery, while a change to Application.Features.Role.Queries.GetAllRolesQuery can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Role.Queries.GetAllRolesQuery uses a module listed above it, which is the healthy direction.
29→1 Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Role.Queries.GetAuthorizableRoutesQuery.GetAuthorizableRoutesQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Role.Queries.GetAuthorizableRoutesQuery, while a change to Application.Features.Role.Queries.GetAuthorizableRoutesQuery can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses a module listed above it, which is the healthy direction.
29→15 Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Role.Queries.GetAuthorizableRoutesQuery.GetAuthorizableRoutesQueryHandler→CleanArc.Application.Contracts.Identity.IRoleManagerService
- Direction
- Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Role.Queries.GetAuthorizableRoutesQuery, while a change to Application.Features.Role.Queries.GetAuthorizableRoutesQuery can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Role.Queries.GetAuthorizableRoutesQuery uses a module listed above it, which is the healthy direction.
30→1 Application.Features.Users.Commands.Create uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Create uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Users.Commands.Create.UserCreateCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Users.Commands.Create uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Users.Commands.Create, while a change to Application.Features.Users.Commands.Create can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Users.Commands.Create uses a module listed above it, which is the healthy direction.
30→6 Application.Features.Users.Commands.Create uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Create uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Users.Commands.Create.UserCreateCommand→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Users.Commands.Create uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Users.Commands.Create, while a change to Application.Features.Users.Commands.Create can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Users.Commands.Create uses a module listed above it, which is the healthy direction.
30→8 Application.Features.Users.Commands.Create uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Create uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Users.Commands.Create.UserCreateCommand→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Users.Commands.Create uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Users.Commands.Create, while a change to Application.Features.Users.Commands.Create can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Commands.Create uses a module listed above it, which is the healthy direction.
30→15 Application.Features.Users.Commands.Create uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Create uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Users.Commands.Create.UserCreateCommandHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Users.Commands.Create uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Users.Commands.Create, while a change to Application.Features.Users.Commands.Create can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Users.Commands.Create uses a module listed above it, which is the healthy direction.
31→1 Application.Features.Users.Commands.RequestLogout uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RequestLogout uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Users.Commands.RequestLogout.RequestLogoutCommandHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Users.Commands.RequestLogout uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Users.Commands.RequestLogout, while a change to Application.Features.Users.Commands.RequestLogout can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Users.Commands.RequestLogout uses a module listed above it, which is the healthy direction.
31→15 Application.Features.Users.Commands.RequestLogout uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RequestLogout uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Users.Commands.RequestLogout.RequestLogoutCommandHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Users.Commands.RequestLogout uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Users.Commands.RequestLogout, while a change to Application.Features.Users.Commands.RequestLogout can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Users.Commands.RequestLogout uses a module listed above it, which is the healthy direction.
32→1 Application.Features.Users.Queries.GenerateUserToken uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GenerateUserToken uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Users.Queries.GenerateUserToken uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Users.Queries.GenerateUserToken, while a change to Application.Features.Users.Queries.GenerateUserToken can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Users.Queries.GenerateUserToken uses a module listed above it, which is the healthy direction.
32→2 Application.Features.Users.Queries.GenerateUserToken uses Application.Models.Jwt✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GenerateUserToken uses a type in Application.Models.Jwt.
- The types involved
CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQueryHandler→CleanArc.Application.Models.Jwt.AccessToken
- Direction
- Application.Features.Users.Queries.GenerateUserToken uses Application.Models.Jwt, so a change to Application.Models.Jwt can break Application.Features.Users.Queries.GenerateUserToken, while a change to Application.Features.Users.Queries.GenerateUserToken can't break Application.Models.Jwt.
- Position
- Below the diagonal: Application.Features.Users.Queries.GenerateUserToken uses a module listed above it, which is the healthy direction.
32→6 Application.Features.Users.Queries.GenerateUserToken uses SharedKernel.ValidationBase✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GenerateUserToken uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQuery→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Users.Queries.GenerateUserToken uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Users.Queries.GenerateUserToken, while a change to Application.Features.Users.Queries.GenerateUserToken can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Users.Queries.GenerateUserToken uses a module listed above it, which is the healthy direction.
32→8 Application.Features.Users.Queries.GenerateUserToken uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GenerateUserToken uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQuery→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Users.Queries.GenerateUserToken uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Users.Queries.GenerateUserToken, while a change to Application.Features.Users.Queries.GenerateUserToken can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Queries.GenerateUserToken uses a module listed above it, which is the healthy direction.
32→11 Application.Features.Users.Queries.GenerateUserToken uses Application.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GenerateUserToken uses a type in Application.Contracts.
- The types involved
CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQueryHandler→CleanArc.Application.Contracts.IJwtService
- Direction
- Application.Features.Users.Queries.GenerateUserToken uses Application.Contracts, so a change to Application.Contracts can break Application.Features.Users.Queries.GenerateUserToken, while a change to Application.Features.Users.Queries.GenerateUserToken can't break Application.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Queries.GenerateUserToken uses a module listed above it, which is the healthy direction.
32→15 Application.Features.Users.Queries.GenerateUserToken uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GenerateUserToken uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQueryHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Users.Queries.GenerateUserToken uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Users.Queries.GenerateUserToken, while a change to Application.Features.Users.Queries.GenerateUserToken can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Users.Queries.GenerateUserToken uses a module listed above it, which is the healthy direction.
33→1 Application.Features.Users.Queries.GetUsers uses Application.Models.Common✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GetUsers uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Users.Queries.GetUsers.GetUsersQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Users.Queries.GetUsers uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Users.Queries.GetUsers, while a change to Application.Features.Users.Queries.GetUsers can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Users.Queries.GetUsers uses a module listed above it, which is the healthy direction.
33→15 Application.Features.Users.Queries.GetUsers uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GetUsers uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Users.Queries.GetUsers.GetUsersQueryHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Users.Queries.GetUsers uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Users.Queries.GetUsers, while a change to Application.Features.Users.Queries.GetUsers can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Users.Queries.GetUsers uses a module listed above it, which is the healthy direction.
34→1 Application.Features.Users.Queries.TokenRequest uses Application.Models.Common✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.Queries.TokenRequest uses a type in Application.Models.Common.
- The types involved
CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQueryResult→CleanArc.Application.Models.Common.OperationResultCleanArc.Application.Features.Users.Queries.TokenRequest.UserTokenRequestQueryHandler→CleanArc.Application.Models.Common.OperationResult
- Direction
- Application.Features.Users.Queries.TokenRequest uses Application.Models.Common, so a change to Application.Models.Common can break Application.Features.Users.Queries.TokenRequest, while a change to Application.Features.Users.Queries.TokenRequest can't break Application.Models.Common.
- Position
- Below the diagonal: Application.Features.Users.Queries.TokenRequest uses a module listed above it, which is the healthy direction.
34→2 Application.Features.Users.Queries.TokenRequest uses Application.Models.Jwt✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.TokenRequest uses a type in Application.Models.Jwt.
- The types involved
CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQueryResult→CleanArc.Application.Models.Jwt.AccessToken
- Direction
- Application.Features.Users.Queries.TokenRequest uses Application.Models.Jwt, so a change to Application.Models.Jwt can break Application.Features.Users.Queries.TokenRequest, while a change to Application.Features.Users.Queries.TokenRequest can't break Application.Models.Jwt.
- Position
- Below the diagonal: Application.Features.Users.Queries.TokenRequest uses a module listed above it, which is the healthy direction.
34→6 Application.Features.Users.Queries.TokenRequest uses SharedKernel.ValidationBase✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.Queries.TokenRequest uses a type in SharedKernel.ValidationBase.
- The types involved
CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQuery→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProviderCleanArc.Application.Features.Users.Queries.TokenRequest.UserTokenRequestQuery→CleanArc.SharedKernel.ValidationBase.ApplicationBaseValidationModelProvider
- Direction
- Application.Features.Users.Queries.TokenRequest uses SharedKernel.ValidationBase, so a change to SharedKernel.ValidationBase can break Application.Features.Users.Queries.TokenRequest, while a change to Application.Features.Users.Queries.TokenRequest can't break SharedKernel.ValidationBase.
- Position
- Below the diagonal: Application.Features.Users.Queries.TokenRequest uses a module listed above it, which is the healthy direction.
34→8 Application.Features.Users.Queries.TokenRequest uses SharedKernel.ValidationBase.Contracts✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.Queries.TokenRequest uses a type in SharedKernel.ValidationBase.Contracts.
- The types involved
CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQuery→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModelCleanArc.Application.Features.Users.Queries.TokenRequest.UserTokenRequestQuery→CleanArc.SharedKernel.ValidationBase.Contracts.IValidatableModel
- Direction
- Application.Features.Users.Queries.TokenRequest uses SharedKernel.ValidationBase.Contracts, so a change to SharedKernel.ValidationBase.Contracts can break Application.Features.Users.Queries.TokenRequest, while a change to Application.Features.Users.Queries.TokenRequest can't break SharedKernel.ValidationBase.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Queries.TokenRequest uses a module listed above it, which is the healthy direction.
34→11 Application.Features.Users.Queries.TokenRequest uses Application.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.TokenRequest uses a type in Application.Contracts.
- The types involved
CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQueryResult→CleanArc.Application.Contracts.IJwtService
- Direction
- Application.Features.Users.Queries.TokenRequest uses Application.Contracts, so a change to Application.Contracts can break Application.Features.Users.Queries.TokenRequest, while a change to Application.Features.Users.Queries.TokenRequest can't break Application.Contracts.
- Position
- Below the diagonal: Application.Features.Users.Queries.TokenRequest uses a module listed above it, which is the healthy direction.
34→15 Application.Features.Users.Queries.TokenRequest uses Application.Contracts.Identity✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.Queries.TokenRequest uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQueryResult→CleanArc.Application.Contracts.Identity.IAppUserManagerCleanArc.Application.Features.Users.Queries.TokenRequest.UserTokenRequestQueryHandler→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Application.Features.Users.Queries.TokenRequest uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Application.Features.Users.Queries.TokenRequest, while a change to Application.Features.Users.Queries.TokenRequest can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Application.Features.Users.Queries.TokenRequest uses a module listed above it, which is the healthy direction.
35→5 Infrastructure.Identity.Identity.PermissionManager uses Infrastructure.Persistence✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Identity.PermissionManager uses a type in Infrastructure.Persistence.
- The types involved
CleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Infrastructure.Persistence.ApplicationDbContext
- Direction
- Infrastructure.Identity.Identity.PermissionManager uses Infrastructure.Persistence, so a change to Infrastructure.Persistence can break Infrastructure.Identity.Identity.PermissionManager, while a change to Infrastructure.Identity.Identity.PermissionManager can't break Infrastructure.Persistence.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.PermissionManager uses a module listed above it, which is the healthy direction.
35→10 Infrastructure.Identity.Identity.PermissionManager uses Domain.Entities.User✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Identity.PermissionManager uses a type in Domain.Entities.User.
- The types involved
CleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Domain.Entities.User.Role
- Direction
- Infrastructure.Identity.Identity.PermissionManager uses Domain.Entities.User, so a change to Domain.Entities.User can break Infrastructure.Identity.Identity.PermissionManager, while a change to Infrastructure.Identity.Identity.PermissionManager can't break Domain.Entities.User.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.PermissionManager uses a module listed above it, which is the healthy direction.
35→13 Infrastructure.Identity.Identity.PermissionManager uses Application.Models.Identity✕
- Connections
- 5 pairs of types, where a type in Infrastructure.Identity.Identity.PermissionManager uses a type in Application.Models.Identity.
- The types involved
CleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Application.Models.Identity.ActionDescriptionDtoCleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Application.Models.Identity.CreateRoleDtoCleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Application.Models.Identity.EditRolePermissionsDtoCleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Application.Models.Identity.GetRolesDtoCleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Application.Models.Identity.RolePermissionDto
- Direction
- Infrastructure.Identity.Identity.PermissionManager uses Application.Models.Identity, so a change to Application.Models.Identity can break Infrastructure.Identity.Identity.PermissionManager, while a change to Infrastructure.Identity.Identity.PermissionManager can't break Application.Models.Identity.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.PermissionManager uses a module listed above it, which is the healthy direction.
35→14 Infrastructure.Identity.Identity.PermissionManager uses Infrastructure.Identity.Identity.Manager✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Identity.Identity.PermissionManager uses a type in Infrastructure.Identity.Identity.Manager.
- The types involved
CleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Infrastructure.Identity.Identity.Manager.AppRoleManagerCleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Infrastructure.Identity.Identity.Manager.AppUserManager
- Direction
- Infrastructure.Identity.Identity.PermissionManager uses Infrastructure.Identity.Identity.Manager, so a change to Infrastructure.Identity.Identity.Manager can break Infrastructure.Identity.Identity.PermissionManager, while a change to Infrastructure.Identity.Identity.PermissionManager can't break Infrastructure.Identity.Identity.Manager.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.PermissionManager uses a module listed above it, which is the healthy direction.
35→15 Infrastructure.Identity.Identity.PermissionManager uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.Identity.PermissionManager uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Infrastructure.Identity.Identity.PermissionManager.RoleManagerService→CleanArc.Application.Contracts.Identity.IRoleManagerService
- Direction
- Infrastructure.Identity.Identity.PermissionManager uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Infrastructure.Identity.Identity.PermissionManager, while a change to Infrastructure.Identity.Identity.PermissionManager can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Infrastructure.Identity.Identity.PermissionManager uses a module listed above it, which is the healthy direction.
36→10 Infrastructure.Identity.UserManager uses Domain.Entities.User✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Identity.UserManager uses a type in Domain.Entities.User.
- The types involved
CleanArc.Infrastructure.Identity.UserManager.AppUserManagerImplementation→CleanArc.Domain.Entities.User.RoleCleanArc.Infrastructure.Identity.UserManager.AppUserManagerImplementation→CleanArc.Domain.Entities.User.User
- Direction
- Infrastructure.Identity.UserManager uses Domain.Entities.User, so a change to Domain.Entities.User can break Infrastructure.Identity.UserManager, while a change to Infrastructure.Identity.UserManager can't break Domain.Entities.User.
- Position
- Below the diagonal: Infrastructure.Identity.UserManager uses a module listed above it, which is the healthy direction.
36→14 Infrastructure.Identity.UserManager uses Infrastructure.Identity.Identity.Manager✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.UserManager uses a type in Infrastructure.Identity.Identity.Manager.
- The types involved
CleanArc.Infrastructure.Identity.UserManager.AppUserManagerImplementation→CleanArc.Infrastructure.Identity.Identity.Manager.AppUserManager
- Direction
- Infrastructure.Identity.UserManager uses Infrastructure.Identity.Identity.Manager, so a change to Infrastructure.Identity.Identity.Manager can break Infrastructure.Identity.UserManager, while a change to Infrastructure.Identity.UserManager can't break Infrastructure.Identity.Identity.Manager.
- Position
- Below the diagonal: Infrastructure.Identity.UserManager uses a module listed above it, which is the healthy direction.
36→15 Infrastructure.Identity.UserManager uses Application.Contracts.Identity✕
- Connections
- 1 pair of types, where a type in Infrastructure.Identity.UserManager uses a type in Application.Contracts.Identity.
- The types involved
CleanArc.Infrastructure.Identity.UserManager.AppUserManagerImplementation→CleanArc.Application.Contracts.Identity.IAppUserManager
- Direction
- Infrastructure.Identity.UserManager uses Application.Contracts.Identity, so a change to Application.Contracts.Identity can break Infrastructure.Identity.UserManager, while a change to Infrastructure.Identity.UserManager can't break Application.Contracts.Identity.
- Position
- Below the diagonal: Infrastructure.Identity.UserManager uses a module listed above it, which is the healthy direction.
37→5 Infrastructure.Persistence.Repositories uses Infrastructure.Persistence✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Infrastructure.Persistence.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.OrderRepository→CleanArc.Infrastructure.Persistence.ApplicationDbContextCleanArc.Infrastructure.Persistence.Repositories.UserRefreshTokenRepository→CleanArc.Infrastructure.Persistence.ApplicationDbContext
- Direction
- Infrastructure.Persistence.Repositories uses Infrastructure.Persistence, so a change to Infrastructure.Persistence can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Infrastructure.Persistence.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
37→7 Infrastructure.Persistence.Repositories uses Domain.Entities.Order✕
- Connections
- 1 pair of types, where a type in Infrastructure.Persistence.Repositories uses a type in Domain.Entities.Order.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.OrderRepository→CleanArc.Domain.Entities.Order.Order
- Direction
- Infrastructure.Persistence.Repositories uses Domain.Entities.Order, so a change to Domain.Entities.Order can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Domain.Entities.Order.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
37→10 Infrastructure.Persistence.Repositories uses Domain.Entities.User✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Domain.Entities.User.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.UserRefreshTokenRepository→CleanArc.Domain.Entities.User.UserCleanArc.Infrastructure.Persistence.Repositories.UserRefreshTokenRepository→CleanArc.Domain.Entities.User.UserRefreshToken
- Direction
- Infrastructure.Persistence.Repositories uses Domain.Entities.User, so a change to Domain.Entities.User can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Domain.Entities.User.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
37→12 Infrastructure.Persistence.Repositories uses Application.Contracts.Persistence✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Application.Contracts.Persistence.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.OrderRepository→CleanArc.Application.Contracts.Persistence.IOrderRepositoryCleanArc.Infrastructure.Persistence.Repositories.UserRefreshTokenRepository→CleanArc.Application.Contracts.Persistence.IUserRefreshTokenRepository
- Direction
- Infrastructure.Persistence.Repositories uses Application.Contracts.Persistence, so a change to Application.Contracts.Persistence can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Application.Contracts.Persistence.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
37→22 Infrastructure.Persistence.Repositories uses Infrastructure.Persistence.Repositories.Common✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Infrastructure.Persistence.Repositories.Common.
- The types involved
CleanArc.Infrastructure.Persistence.Repositories.OrderRepository→CleanArc.Infrastructure.Persistence.Repositories.Common.BaseAsyncRepositoryCleanArc.Infrastructure.Persistence.Repositories.UserRefreshTokenRepository→CleanArc.Infrastructure.Persistence.Repositories.Common.BaseAsyncRepository
- Direction
- Infrastructure.Persistence.Repositories uses Infrastructure.Persistence.Repositories.Common, so a change to Infrastructure.Persistence.Repositories.Common can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Infrastructure.Persistence.Repositories.Common.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
38→9 Web.Api.Controllers.V1.Admin uses WebFramework.BaseController✕
- Connections
- 4 pairs of types, where a type in Web.Api.Controllers.V1.Admin uses a type in WebFramework.BaseController.
- The types involved
CleanArc.Web.Api.Controllers.V1.Admin.AdminManagerController→CleanArc.WebFramework.BaseController.BaseControllerCleanArc.Web.Api.Controllers.V1.Admin.OrderManagementController→CleanArc.WebFramework.BaseController.BaseControllerCleanArc.Web.Api.Controllers.V1.Admin.RoleManagerController→CleanArc.WebFramework.BaseController.BaseControllerCleanArc.Web.Api.Controllers.V1.Admin.UserManagementController→CleanArc.WebFramework.BaseController.BaseController
- Direction
- Web.Api.Controllers.V1.Admin uses WebFramework.BaseController, so a change to WebFramework.BaseController can break Web.Api.Controllers.V1.Admin, while a change to Web.Api.Controllers.V1.Admin can't break WebFramework.BaseController.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Admin uses a module listed above it, which is the healthy direction.
38→23 Web.Api.Controllers.V1.Admin uses Application.Features.Admin.Commands.AddAdminCommand✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.Admin uses a type in Application.Features.Admin.Commands.AddAdminCommand.
- The types involved
CleanArc.Web.Api.Controllers.V1.Admin.AdminManagerController→CleanArc.Application.Features.Admin.Commands.AddAdminCommand.AddAdminCommand
- Direction
- Web.Api.Controllers.V1.Admin uses Application.Features.Admin.Commands.AddAdminCommand, so a change to Application.Features.Admin.Commands.AddAdminCommand can break Web.Api.Controllers.V1.Admin, while a change to Web.Api.Controllers.V1.Admin can't break Application.Features.Admin.Commands.AddAdminCommand.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Admin uses a module listed above it, which is the healthy direction.
38→24 Web.Api.Controllers.V1.Admin uses Application.Features.Admin.Queries.GetToken✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.Admin uses a type in Application.Features.Admin.Queries.GetToken.
- The types involved
CleanArc.Web.Api.Controllers.V1.Admin.AdminManagerController→CleanArc.Application.Features.Admin.Queries.GetToken.AdminGetTokenQuery
- Direction
- Web.Api.Controllers.V1.Admin uses Application.Features.Admin.Queries.GetToken, so a change to Application.Features.Admin.Queries.GetToken can break Web.Api.Controllers.V1.Admin, while a change to Web.Api.Controllers.V1.Admin can't break Application.Features.Admin.Queries.GetToken.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Admin uses a module listed above it, which is the healthy direction.
38→26 Web.Api.Controllers.V1.Admin uses Application.Features.Role.Commands.AddRoleCommand✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.Admin uses a type in Application.Features.Role.Commands.AddRoleCommand.
- The types involved
CleanArc.Web.Api.Controllers.V1.Admin.RoleManagerController→CleanArc.Application.Features.Role.Commands.AddRoleCommand.AddRoleCommand
- Direction
- Web.Api.Controllers.V1.Admin uses Application.Features.Role.Commands.AddRoleCommand, so a change to Application.Features.Role.Commands.AddRoleCommand can break Web.Api.Controllers.V1.Admin, while a change to Web.Api.Controllers.V1.Admin can't break Application.Features.Role.Commands.AddRoleCommand.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Admin uses a module listed above it, which is the healthy direction.
38→27 Web.Api.Controllers.V1.Admin uses Application.Features.Role.Commands.UpdateRoleClaimsCommand✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.Admin uses a type in Application.Features.Role.Commands.UpdateRoleClaimsCommand.
- The types involved
CleanArc.Web.Api.Controllers.V1.Admin.RoleManagerController→CleanArc.Application.Features.Role.Commands.UpdateRoleClaimsCommand.UpdateRoleClaimsCommand
- Direction
- Web.Api.Controllers.V1.Admin uses Application.Features.Role.Commands.UpdateRoleClaimsCommand, so a change to Application.Features.Role.Commands.UpdateRoleClaimsCommand can break Web.Api.Controllers.V1.Admin, while a change to Web.Api.Controllers.V1.Admin can't break Application.Features.Role.Commands.UpdateRoleClaimsCommand.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Admin uses a module listed above it, which is the healthy direction.
39→9 Web.Api.Controllers.V1.Order uses WebFramework.BaseController✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.Order uses a type in WebFramework.BaseController.
- The types involved
CleanArc.Web.Api.Controllers.V1.Order.OrderController→CleanArc.WebFramework.BaseController.BaseController
- Direction
- Web.Api.Controllers.V1.Order uses WebFramework.BaseController, so a change to WebFramework.BaseController can break Web.Api.Controllers.V1.Order, while a change to Web.Api.Controllers.V1.Order can't break WebFramework.BaseController.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Order uses a module listed above it, which is the healthy direction.
39→25 Web.Api.Controllers.V1.Order uses Application.Features.Order.Commands✕
- Connections
- 2 pairs of types, where a type in Web.Api.Controllers.V1.Order uses a type in Application.Features.Order.Commands.
- The types involved
CleanArc.Web.Api.Controllers.V1.Order.OrderController→CleanArc.Application.Features.Order.Commands.AddOrderCommandCleanArc.Web.Api.Controllers.V1.Order.OrderController→CleanArc.Application.Features.Order.Commands.UpdateUserOrderCommand
- Direction
- Web.Api.Controllers.V1.Order uses Application.Features.Order.Commands, so a change to Application.Features.Order.Commands can break Web.Api.Controllers.V1.Order, while a change to Web.Api.Controllers.V1.Order can't break Application.Features.Order.Commands.
- Position
- Below the diagonal: Web.Api.Controllers.V1.Order uses a module listed above it, which is the healthy direction.
40→9 Web.Api.Controllers.V1.UserManagement uses WebFramework.BaseController✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.UserManagement uses a type in WebFramework.BaseController.
- The types involved
CleanArc.Web.Api.Controllers.V1.UserManagement.UserController→CleanArc.WebFramework.BaseController.BaseController
- Direction
- Web.Api.Controllers.V1.UserManagement uses WebFramework.BaseController, so a change to WebFramework.BaseController can break Web.Api.Controllers.V1.UserManagement, while a change to Web.Api.Controllers.V1.UserManagement can't break WebFramework.BaseController.
- Position
- Below the diagonal: Web.Api.Controllers.V1.UserManagement uses a module listed above it, which is the healthy direction.
40→18 Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Commands.RefreshUserTokenCommand✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.UserManagement uses a type in Application.Features.Users.Commands.RefreshUserTokenCommand.
- The types involved
CleanArc.Web.Api.Controllers.V1.UserManagement.UserController→CleanArc.Application.Features.Users.Commands.RefreshUserTokenCommand.RefreshUserTokenCommand
- Direction
- Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Commands.RefreshUserTokenCommand, so a change to Application.Features.Users.Commands.RefreshUserTokenCommand can break Web.Api.Controllers.V1.UserManagement, while a change to Web.Api.Controllers.V1.UserManagement can't break Application.Features.Users.Commands.RefreshUserTokenCommand.
- Position
- Below the diagonal: Web.Api.Controllers.V1.UserManagement uses a module listed above it, which is the healthy direction.
40→30 Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Commands.Create✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.UserManagement uses a type in Application.Features.Users.Commands.Create.
- The types involved
CleanArc.Web.Api.Controllers.V1.UserManagement.UserController→CleanArc.Application.Features.Users.Commands.Create.UserCreateCommand
- Direction
- Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Commands.Create, so a change to Application.Features.Users.Commands.Create can break Web.Api.Controllers.V1.UserManagement, while a change to Web.Api.Controllers.V1.UserManagement can't break Application.Features.Users.Commands.Create.
- Position
- Below the diagonal: Web.Api.Controllers.V1.UserManagement uses a module listed above it, which is the healthy direction.
40→32 Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Queries.GenerateUserToken✕
- Connections
- 1 pair of types, where a type in Web.Api.Controllers.V1.UserManagement uses a type in Application.Features.Users.Queries.GenerateUserToken.
- The types involved
CleanArc.Web.Api.Controllers.V1.UserManagement.UserController→CleanArc.Application.Features.Users.Queries.GenerateUserToken.GenerateUserTokenQuery
- Direction
- Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Queries.GenerateUserToken, so a change to Application.Features.Users.Queries.GenerateUserToken can break Web.Api.Controllers.V1.UserManagement, while a change to Web.Api.Controllers.V1.UserManagement can't break Application.Features.Users.Queries.GenerateUserToken.
- Position
- Below the diagonal: Web.Api.Controllers.V1.UserManagement uses a module listed above it, which is the healthy direction.
40→34 Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Queries.TokenRequest✕
- Connections
- 2 pairs of types, where a type in Web.Api.Controllers.V1.UserManagement uses a type in Application.Features.Users.Queries.TokenRequest.
- The types involved
CleanArc.Web.Api.Controllers.V1.UserManagement.UserController→CleanArc.Application.Features.Users.Queries.TokenRequest.PasswordUserTokenRequestQueryCleanArc.Web.Api.Controllers.V1.UserManagement.UserController→CleanArc.Application.Features.Users.Queries.TokenRequest.UserTokenRequestQuery
- Direction
- Web.Api.Controllers.V1.UserManagement uses Application.Features.Users.Queries.TokenRequest, so a change to Application.Features.Users.Queries.TokenRequest can break Web.Api.Controllers.V1.UserManagement, while a change to Web.Api.Controllers.V1.UserManagement can't break Application.Features.Users.Queries.TokenRequest.
- Position
- Below the diagonal: Web.Api.Controllers.V1.UserManagement uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 19 | High / Critical |
| A07:2025 — Authentication Failures | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
Roadmap
Top priorities: Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion); Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2); Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion). | +12.0 pts | Medium | Domain ↔ infrastructure boundary |
| Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2). | +1.7 pts | Low | REDACTED Scanning |
| Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED (3). | +1.2 pts | Low | Dependency Hygiene |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). | +1.0 pts | Low | Dependency Hygiene |
| Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. | +0.8 pts | Low | Dependency Hygiene |
| Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED. | +0.6 pts | Low | Explicit Debt |
| Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RoleManagerService.cs. | +0.6 pts | Low | Explicit Debt |
| Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most. | +1.2 pts | Medium | Domain vs controller coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 0.9 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs | 4.8 | Mixed | Code Duplication: Duplicated block (41 lines × 2) |
| src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs | 5.0 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs | 6.0 | Near-clean | Explicit Debt: Dead code: GetEnumValues |
| src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs | 6.0 | Near-clean | Explicit Debt: Dead code: AddSingularizingTableNameConvention |
| src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs | 6.0 | Near-clean | Explicit Debt: Dead code: BaseTypeIsGeneric |
| REDACTED | 6.1 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.2 | Near-clean | Dependency Hygiene: Deprecated: Serilog.Sinks.Elasticsearch |
| REDACTED | 6.4 | Near-clean | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs | 6.4 | Near-clean | Explicit Debt: Dead code: ToInt |
| src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs | 6.7 | Near-clean | Cyclomatic Complexity: ApplySummariesOperationFilter.Process (cyclomatic 21) |
| src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs | 6.7 | Near-clean | Explicit Debt: Dead code: GetDependentAssemblies |
| src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs | 6.7 | Near-clean | Explicit Debt: Dead code: ToGroupedDictionary |
| src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs | 6.7 | Near-clean | Explicit Debt: Dead code: GetUserName |
| src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs | 6.7 | Near-clean | Explicit Debt: Dead code: PasswordlessLoginTokenProviderOptions |
How the grades work
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 81 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 81 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, 290 of 339 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 142 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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.
- 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. `REDACTED`, `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs`, `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs`, `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs`, `src/Core/CleanArc.Application/Common/LoggingBehavior.cs`, … (+19 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — web_api Error pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied Error response from daemon: pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: web_api Error pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied Error response from daemon: pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- P10 Library API & versioning — 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. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P11 BDD / executable specs — 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. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P7 Outbound HTTP resilience — 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. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P8 Schema migrations — 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. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- PF3 Async & latency hygiene — 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. 114 further occurrence(s) are not listed individually; the score already reflects all 154.
- X2 Cancellation propagation — measured, with a gap in what it reached — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ApplySummariesOperationFilter.Process at 21.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ApplySummariesOperationFilter.Process (cyclomatic 21). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ApplySummariesOperationFilter.Process at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ApplySummariesOperationFilter.Process (cognitive 29). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
8 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ApplySummariesOperationFilter.cs (2), LookupProtector.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Duplicated block (41 lines × 2) finding(s) in Code Duplication — start with LookupProtector.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (32–35 lines × 2) finding(s) in Code Duplication — start with LookupProtector.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
12 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 15.5% — 32 file(s) below 50% · 7 method(s) over the CRAP-30 risk line.
What to do
- Resolve the 32 Low coverage finding(s) in Code Coverage — start with AssemblyExtensions.cs, CollectionExtensions.cs, EnumExtentions.cs. — One of this dimension's main actionable groups (32 warning-level).
- Resolve the 3 CRAP 42 finding(s) in Code Coverage — start with LookupProtector.cs, PersonalDataProtector.cs, ServiceCollectionExtension.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 CRAP 30 finding(s) in Code Coverage — start with RoleManagerService.cs, ReflectionExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
4 test methods: 4 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 4 tests.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).
D12 · Dependency Hygiene
35 outdated, 1 vulnerable, 2 deprecated, 1 prerelease packages.
What to do
- Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 49 direct `PackageReference`(s), and 201 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted debt markers + 33 dead symbols across 4657 LoC in the .NET projects (1.7/KLoC) → score 6.6.
What to do
- Resolve the 33 Dead code finding(s) in Explicit Debt — start with StringExtensions.cs (7), ReflectionExtensions.cs (6), ModelBuilderExtensions.cs (3). — One of this dimension's main actionable groups (33 warning-level).
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RoleManagerService.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
12 projects, 164 source files, 4826 hand-written lines of code (4657 production / 169 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 1534 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 20 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 11 unit(s).
D24 · Comment Value
0 of 48 judged comments only repeat the code they sit on (0.0 %). 11 comment(s) in another language or script were not judged.
What to do
- Maintain Comment Value — already on the Gold path. — No findings, and enforcement is at this dimension's ceiling.
D26 · Project Cohesion
0 of 12 projects flagged as possibly oversized/incoherent.
D27 · Navigability
93 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
19 finding(s): 0 critical, 5 high, 14 medium, 0 low. semgrep hit a parse error in 24 file(s) — `REDACTED` (lines 16–17, line 37), `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs` (lines 22–23, line 67), `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs` (line 16), `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs` (line 11), `src/Core/CleanArc.Application/Common/LoggingBehavior.cs` (line 7), … (+19 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 23 of those file(s) — `REDACTED`, `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs`, `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs`, `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs`, `src/Core/CleanArc.Application/Common/LoggingBehavior.cs`, … (+18 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
8 finding(s): 1 critical, 5 high, 1 medium, 1 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 3 high, 3 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
19 of 19 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs. Counted over 19 of the 159 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtension.cs, PersonalDataProtector.cs, LookupProtector.cs. — One of this dimension's main actionable groups (19 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
1 of 457 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
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).
AX3 · Project dependency cycles
- The namespaces CleanArc.Domain.Entities.Order ↔ CleanArc.Domain.Entities.User depend on each other. The lightest dependency in the cycle is CleanArc.Domain.Entities.Order → CleanArc.Domain.Entities.User (CleanArc.Domain.Entities.Order.Order → CleanArc.Domain.Entities.User.User, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/CleanArc.Domain/Entities/Order/Order.cs:5
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
- `IAppUserManager` declares 22 members: `CreateUser`, `CreateUser`, `IsExistUser`, `IsExistUserName`, `GeneratePhoneNumberConfirmationToken`, `GetUserByCode`, `ChangePhoneNumber`, `VerifyUserCode`, `GenerateOtpCode`, `GetUserByPhoneNumber`, `GetByUserName`, `GetUserByIdAsync`, `GetAllUsersAsync`, `CreateUserWithPasswordAsync`, `AddUserToRoleAsync`, `IncrementAccessFailedCountAsync`, `IsUserLockedOutAsync`, `ResetUserLockoutAsync`, `UpdateUserAsync`, `UpdateSecurityStampAsync`, `IsPasswordValidAsync`, `GetRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:6
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion
AX8 · Test isolation
AX9 · CQS / query purity
- `GetToken.AdminGetTokenQueryHandler` is a read (query) handler but its body writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs:9
- `GenerateUserToken.GenerateUserTokenQueryHandler` is a read (query) handler but its body writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs:10
- `TokenRequest.PasswordUserTokenRequestQueryResult` is a read (query) handler but its body writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/PasswordUserTokenRequestQuery.Handler.cs:9
What to do
- Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
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.
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
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.
DM6 · Domain ↔ infrastructure boundary
- `Order` (domain layer) names `User` from `CleanArc.Domain.Entities.User` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/Order/Order.cs:12
- `Role` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/Role.cs:6
- `RoleClaim` (domain layer) names `IdentityRoleClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/RoleClaim.cs:6
- `User` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/User.cs:6
- `UserClaim` (domain layer) names `IdentityUserClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/UserClaim.cs:6
- `UserLogin` (domain layer) names `IdentityUserLogin` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/UserLogin.cs:6
- `UserRole` (domain layer) names `IdentityUserRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/UserRole.cs:6
- `UserToken` (domain layer) names `IdentityUserToken` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Core/CleanArc.Domain/Entities/User/UserToken.cs:6
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
ED5 · Idempotency
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `RemoveUserOldTokens` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×21) — src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17, src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:18, src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:19, …
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 10 of 10 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
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.
P9 · Domain vs controller coverage
- Domain coverage is 4%, against a bar of 50% for this row — the layer carrying the business rules is the least covered part of the codebase that matters most. Measured over the types this analyzer classifies as domain (aggregates, value objects, domain services), so code the classifier does not place in the domain is neither counted for nor against this figure.
What to do
- Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.
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
- Only 0/153 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await UserManager.GetRolesAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:18
- `await base.GenerateClaimsAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:20
- `await manager.GetPhoneNumberAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:34
- `await _roleManger.Roles.Where(c => !c.Name.Equals("admin")).Select(r => _mapper.Map...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:43
- `await _roleManger.CreateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:54
- `await _roleManger.Roles.Include(r => r.Claims) .Include(r => r.Users).FirstOrDefaul...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:61
- `await _userManager.GetUsersInRoleAsync(role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:67, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:197
- `await _userManager.RemoveFromRoleAsync(user, role.Name)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:71
- `await _userManager.UpdateSecurityStampAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:72, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:201
- `await _db.SaveChangesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:78, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:191
- `await _roleManger.Roles .Include(x => x.Claims) .SingleOrDefaultAsync(x => x.Id == ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:130, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:147
- `await this.GetPermissionActionsAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:137
- `await _roleManger.UpdateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:193
- `await _roleManger.FindByIdAsync(roleId.ToString())` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:212
- `await _roleManager.CreateAsync(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:31
- `await _userManager.CreateAsync(user, "qw123321")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:43
- `await _userManager.AddToRoleAsync(user,"admin")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:44
- `await base.ValidateAsync(manager, user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs:15
- `await _getClaimsAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:42
- `await _unitOfWork.UserRefreshTokenRepository.CreateToken(user.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:61
- `await _unitOfWork.CommitAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — REDACTED:62, REDACTED:105
- `await _userManager.Users.AsNoTracking().FirstOrDefaultAsync(u => u.PhoneNumber == p...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:91
- `await this.GenerateAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — REDACTED:92, REDACTED:112
- `await _unitOfWork.UserRefreshTokenRepository.GetTokenWithInvalidation(refreshTokenId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:98
- `await _unitOfWork.UserRefreshTokenRepository.GetUserByRefreshToken(refreshTokenId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:107
- `await _claimsPrincipal.CreateAsync(user)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — REDACTED:119
- `await signInManager.ValidateSecurityStampAsync(context.Principal)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:166
- `await context.Response.WriteAsJsonAsync(response)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:182, src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:192
- `await context.Response.WriteAsJsonAsync(new ApiResult(false, ApiResultStatusCode.Un...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:201
- `await context.Response.WriteAsJsonAsync(new ApiResult(false, ApiResultStatusCode.Fo...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:208
- `await using … = app.Services.CreateAsyncScope()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:219
- `await seedService.Seed()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:222
What to do
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture
- `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:134
- `ValidateAudience`, `ValidateIssuer`, `ValidateLifetime` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — REDACTED:71
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/API/CleanArc.Web.Api/Program.cs:24
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/API/CleanArc.Web.Api/Program.cs:24
What to do
- Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
- Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
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
- `meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 14). Every use of it in `MetricsBehaviour` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw. — src/Core/CleanArc.Application/Common/MetricsBehaviour.cs:14
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 22/73 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. (×33) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:41, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:59, src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:128, …
- Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:171
- No CancellationToken parameter, and the token `app.Lifetime.ApplicationStarted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `app.Lifetime.ApplicationStarted` on, or take a CancellationToken. (×2) — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:217, src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs:25
- No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken. (×3) — src/API/Plugins/CleanArc.Web.Plugins.Grpc/Services/OrderGrpcServices.cs:23, REDACTED:18, REDACTED:53
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×4) — src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:121, src/Core/CleanArc.Application/Common/LoggingBehavior.cs:22, src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:47, …
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This method contradicts itself about `claimsIdentity`: line 150 assigns it with `as ClaimsIdentity`, which hands back null rather than throwing when the value is not a `ClaimsIdentity`, but line 151 then dereferences it directly as `claimsIdentity.Claims` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `claimsIdentity` once before the first use and handle the null case, or cast with `(ClaimsIdentity)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:151
- 1/10 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
- ~0.1 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 6761 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 53% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 79% | Strong | Strongest area. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by D8, D13, P9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 53% | Adequate — gated by D29, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 27% | Weak — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 37 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX2 Stateful singletons — no singleton implementations detected
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — web_api Error pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied Error response from daemon: pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: web_api Error pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied Error response from daemon: pull access denied for bobby-cleanarc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1053 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 7 exposed C# types.
- D23 Boundary Type-Coupling — small single-context codebase (4,657 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 24 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a Domain/Aggregates/ValueObjects layer; 4 repository port(s) loading or saving an aggregate/entity
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (18 CQRS handler(s))
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 36 finding(s)
- Domain depends on infrastructure: Order src/Core/CleanArc.Domain/Entities/Order/Order.cs:12
- Domain depends on infrastructure: Role src/Core/CleanArc.Domain/Entities/User/Role.cs:6
- Domain depends on infrastructure: RoleClaim src/Core/CleanArc.Domain/Entities/User/RoleClaim.cs:6
- Domain depends on infrastructure: User src/Core/CleanArc.Domain/Entities/User/User.cs:6
- Domain depends on infrastructure: UserClaim src/Core/CleanArc.Domain/Entities/User/UserClaim.cs:6
- Domain depends on infrastructure: UserLogin src/Core/CleanArc.Domain/Entities/User/UserLogin.cs:6
- Domain depends on infrastructure: UserRole src/Core/CleanArc.Domain/Entities/User/UserRole.cs:6
- Domain depends on infrastructure: UserToken src/Core/CleanArc.Domain/Entities/User/UserToken.cs:6
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Query handler writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken: GetToken.AdminGetTokenQueryHandler src/Core/CleanArc.Application/Features/Admin/Queries/GetToken/AdminGetTokenQuery.Handler.cs:9
- Query handler writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken: GenerateUserToken.GenerateUserTokenQueryHandler src/Core/CleanArc.Application/Features/Users/Queries/GenerateUserToken/GenerateUserTokenQuery.Handler.cs:10
- Query handler writes persistent state 2 calls away, in UserRefreshTokenRepository.CreateToken: TokenRequest.PasswordUserTokenRequestQueryResult src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/PasswordUserTokenRequestQuery.Handler.cs:9
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/Core/CleanArc.Domain/Entities/Order/Order.cs:5
- WriteOnlyPrivateField src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:25
- NoWarnInCsproj REDACTED:8
- REDACTED
- REDACTED
- REDACTED
Serious — 198 finding(s)
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:18
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:20
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:34
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:43
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:54
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:61
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:67
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:71
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:72
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:78
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:130
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:137
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:147
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:191
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:193
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:197
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:201
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:212
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:31
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:43
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:44
- Awaits without ConfigureAwait(false) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs:15
- Awaits without ConfigureAwait(false) REDACTED:42
- Awaits without ConfigureAwait(false) REDACTED:61
- Async method without CancellationToken: GetRolesAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:41
- Async method without CancellationToken: DeleteRoleAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:59
- Async method without CancellationToken: GetRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:128
- Async method without CancellationToken: ChangeRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:145
- Async method without CancellationToken: GenerateAsync REDACTED:33
- Async method without CancellationToken: GenerateByPhoneNumberAsync REDACTED:89
- Async method without CancellationToken: RefreshToken REDACTED:96
- Async method without CancellationToken: SeedDefaultUsersAsync src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:217
- Async method without CancellationToken: IsExistUser src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:28
- Async method without CancellationToken: IsExistUserName src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:33
- Async method without CancellationToken: GetUserByCode src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:43
- Async method without CancellationToken: GetUserByPhoneNumber src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:72
- Async method without CancellationToken: GetAllUsersAsync src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:88
- Async method without CancellationToken: ListAllAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:21
- Async method without CancellationToken: AddAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:26
- Async method without CancellationToken: UpdateAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:34
- Async method without CancellationToken: DeleteAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:40
- Async method without CancellationToken: CommitAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/UnitOfWork.cs:19
- Async method without CancellationToken: AddOrderAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:10
- Async method without CancellationToken: GetAllUserOrdersAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:15
- Async method without CancellationToken: GetAllOrdersWithRelatedUserAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:20
- Async method without CancellationToken: GetUserOrderByIdAndUserIdAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:27
- Async method without CancellationToken: DeleteUserOrdersAsync src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:37
- Async method without CancellationToken: CreateToken src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:14
- Async method without CancellationToken: GetTokenWithInvalidation src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:21
- Dead code: GetDependentAssemblies src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs:7
- Dead code: ToGroupedDictionary src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs:5
- Dead code: GetEnumValues src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs:8
- Dead code: GetEnumFlags src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs:16
- Dead code: GetUserName src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs:34
- Dead code: AddSingularizingTableNameConvention src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:14
- Dead code: AddSequentialGuidForIdConvention src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:45
- Dead code: RegisterEntityTypeConfiguration src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:85
- Dead code: BaseTypeIsGeneric src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:31
- Dead code: IsEnumerable src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:56
- Dead code: IsEnumerable src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:61
- Dead code: GetBaseTypesAndInterfaces src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:66
- Dead code: IsCustomType src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:82
- Dead code: IsAssignableFromBaseTypeGeneric src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:98
- Dead code: ToInt src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:10
- Dead code: ToNumeric src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:20
- Dead code: ToNumeric src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:25
- Dead code: ToCurrency src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:30
- Dead code: ToCurrency src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:37
- Dead code: En2Fa src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:42
- Dead code: CleanString src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:94
- Dead code: PasswordlessLoginTokenProviderOptions src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:39
- Dead code: IncrementAccessFailedCountAsync src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:23
- Dead code: ResetUserLockoutAsync src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:25
- Dead code: DeleteRoleAsync src/Core/CleanArc.Application/Contracts/Identity/IRoleManagerService.cs:11
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/AssemblyExtensions.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/CollectionExtensions.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs src/Shared/CleanArc.SharedKernel/Extensions/EnumExtentions.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/IdentityExtensions.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/RegExHelpers.cs src/Shared/CleanArc.SharedKernel/Extensions/RegExHelpers.cs:1
- Low coverage: src/Shared/CleanArc.SharedKernel/Extensions/ValidatorExtensions.cs src/Shared/CleanArc.SharedKernel/Extensions/ValidatorExtensions.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/ServiceConfiguration/ServiceCollectionExtensions.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/OrderRepository.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/Common/BaseAsyncRepository.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppErrorDescriber.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppErrorDescriber.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppRoleValidator.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppRoleValidator.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/validator/AppUserValidator.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/SeedDatabaseService/SeedDataBase.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionRequirement.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionRequirement.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionService.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/DynamicPermissionService.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/Extensions/CustomIdentityExtensions.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/KeyRing.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/KeyRing.cs:1
- Low coverage: src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:43
- Duplicated block (6 lines × 2) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:56
- Duplicated block (6 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:208
- CRAP 42: LookupProtector.ByteArraysEqual src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:215
- CRAP 42: PersonalDataProtector.ByteArraysEqual src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:220
- CRAP 42: ServiceCollectionExtension.RegisterIdentityServices src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:30
- Deprecated: Serilog.Sinks.Elasticsearch REDACTED:50
- Deprecated: xunit REDACTED:54
- CommentedOutCode src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17
- CommentedOutCode src/Infrastructure/CleanArc.Infrastructure.CrossCutting/Logging/LoggingConfiguration.cs:59
- TodoComment src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:49
- TodoComment src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs:26
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CRAP 30: RoleManagerService.GetPermissionActionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:83
- CRAP 30: ReflectionHelper.GetBaseTypesAndInterfaces src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:66
- ApplySummariesOperationFilter.Process (cyclomatic 21) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:12
- Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore
- ApplySummariesOperationFilter.Process (cognitive 29) src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:12
- REDACTED
- REDACTED
- Duplicated block (41 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:121
- Duplicated block (32–35 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:46
- Duplicated block (17 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:218
- Duplicated block (7 lines × 2) src/API/CleanArc.WebFramework/Filters/BadRequestResultFilterAttribute.cs:19
- Duplicated block (5 lines × 2) src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:170
- No test project references CleanArc.WebFramework src/API/CleanArc.WebFramework/CleanArc.WebFramework.csproj
- No test project references CleanArc.Web.Api REDACTED
- No test project references CleanArc.Infrastructure.Monitoring REDACTED
- No test project references CleanArc.Web.Plugins.Grpc src/API/Plugins/CleanArc.Web.Plugins.Grpc/CleanArc.Web.Plugins.Grpc.csproj
- No test project references CleanArc.Infrastructure.CrossCutting REDACTED
- CRAP 72: RoleManagerService.ChangeRolePermissionsAsync src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:145
- CRAP 56: ValidatorExtensions.RegisterValidatorsAsServices src/Shared/CleanArc.SharedKernel/Extensions/ValidatorExtensions.cs:10
- Unfinished stub — throws NotImplementedException src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36
- Unfinished stub — throws NotImplementedException src/Infrastructure/CleanArc.Infrastructure.Persistence/Repositories/UserRefreshTokenRepository.cs:36
- Test suite runs only after the merge
- Low domain coverage
- Token validation disabled REDACTED:71
- Disposable created and abandoned in the method that made it src/Core/CleanArc.Application/Common/MetricsBehaviour.cs:14
- Async delegate without CancellationToken: RegisterIdentityServices src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:171
- Symbol treated as nullable, then dereferenced unguarded src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:151
Minor — 69 finding(s)
- Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:17
- Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:18
- Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:19
- Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:21
- Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:24
- Commented-out code src/API/CleanArc.WebFramework/ServiceConfiguration/ServiceCollectionExtension.cs:27
- Commented-out code src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:29
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.CrossCutting/Logging/LoggingConfiguration.cs:57
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:21
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:22
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/AppUserClaimsPrincipleFactory.cs:30
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:68
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:87
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:89
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:91
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:142
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:164
- Commented-out code src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:174
- Commented-out code src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:16
- Commented-out code src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:17
- Commented-out code src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:84
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/PersonalDataProtector.cs:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:1
- Orphaned file src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:1
- Orphaned file src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/UserManager/AppUserManagerImplementation.cs:1
- Orphaned file src/API/CleanArc.Web.Api/Program.cs:1
- Orphaned file src/Shared/CleanArc.SharedKernel/Extensions/ReflectionExtensions.cs:1
- Orphaned file src/API/CleanArc.WebFramework/Filters/ApiResultFilterAttribute.cs:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Persistence/ApplicationDbContext.cs:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file src/Shared/CleanArc.SharedKernel/Extensions/StringExtensions.cs:1
- Orphaned file src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/KeyRing.cs:1
- Orphaned file src/Infrastructure/CleanArc.Infrastructure.CrossCutting/Logging/LoggingConfiguration.cs:1
- Orphaned file src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs:1
- Interpolated log message defeats structured logging src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/PermissionManager/RoleManagerService.cs:121
- Interpolated log message defeats structured logging src/Core/CleanArc.Application/Common/LoggingBehavior.cs:22
- Interpolated log message defeats structured logging src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.Handler.cs:47
- Interpolated log message defeats structured logging src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.Handler.cs:24
- Outdated: Mapster REDACTED:17
- Outdated: Mapster.DependencyInjection REDACTED:18
- Outdated: coverlet.collector REDACTED:13
- ObsoleteWithoutCallers src/API/CleanArc.WebFramework/Filters/ApiResultFilterAttribute.cs:8
- ObsoleteWithoutCallers src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:85
- No security response headers detected
- No security response headers detected src/API/CleanArc.Web.Api/Program.cs:24
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected src/API/CleanArc.Web.Api/Program.cs:24
- Fat interface: IAppUserManager (22 members) src/Core/CleanArc.Application/Contracts/Identity/IAppUserManager.cs:6
- Partial data-retention evidence
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- IL efficiency: 1 authored method(s) exceed the IL budget src/API/CleanArc.WebFramework/Swagger/ApplySummariesOperationFilter.cs:15
- No ADRs
- No rollback/health safety
- No changelog
- No performance benchmarks
- OIDC metadata fetched over HTTP src/Infrastructure/CleanArc.Infrastructure.Identity/ServiceConfiguration/ServiceCollectionExtension.cs:134
- Duplicated predicate src/Infrastructure/CleanArc.Infrastructure.Identity/Identity/DataProtection/LookupProtector.cs:223
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 36 finding(s)
- Outdated: FluentValidation
- Outdated: Microsoft.AspNetCore.OpenApi
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.Extensions.Identity.Stores
- Outdated: Microsoft.Extensions.Hosting.Abstractions
- Outdated: Serilog.Sinks.MSSqlServer
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.AspNetCore.Authorization
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.Extensions.Identity.Core
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Mediator.Abstractions
- Outdated: Mediator.SourceGenerator
- Outdated: System.Linq.Async
- Outdated: Grpc.AspNetCore
- Outdated: Grpc.AspNetCore.Server.Reflection
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Microsoft.Extensions.Logging.Debug
- Outdated: Serilog.AspNetCore
- Outdated: Asp.Versioning.Http
- Outdated: Asp.Versioning.Mvc
- Outdated: Asp.Versioning.Mvc.ApiExplorer
- Outdated: NSwag.AspNetCore
- Outdated: NuGet.Packaging
- doc comments repeat the names src/Shared/CleanArc.SharedKernel/Extensions/ModelBuilderExtensions.cs:13
- doc comments repeat the names src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs:45
- Mock framework: NSubstitute
- Off the main sequence: CleanArc.SharedKernel src/Shared/CleanArc.SharedKernel/CleanArc.SharedKernel.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-0c90c2e0012e41cfa9c41ed7da5731a1/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0c90c2e0012e41cfa9c41ed7da5731a1/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Infrastructure/CleanArc.Infrastructure.Persistence/Migrations . | 19 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list CleanArcTemplate.sln package --vulnerable --include-transitive --format json | 8 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 24 file(s) — `REDACTED`, `src/API/CleanArc.Web.Api/Controllers/V1/Admin/RoleManagerController.cs`, `src/API/CleanArc.Web.Api/Controllers/V1/Order/OrderController.cs`, `src/API/CleanArc.WebFramework/Middlewares/ExceptionHandler.cs`, `src/Core/CleanArc.Application/Common/LoggingBehavior.cs`, … (+19 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d48b99ac3b454d91852e4e347c4f5cf1 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 3 field(s)
- BaseController.UserEmail src/API/CleanArc.WebFramework/BaseController/BaseController.cs:13
- AddAdminCommand.Email src/Core/CleanArc.Application/Features/Admin/Commands/AddAdminCommand/AddAdminCommand.cs:10
- GetUsersQueryResponse.Email src/Core/CleanArc.Application/Features/Users/Queries/GetUsers/GetUsersQuery.Response.cs:9
Name — 2 field(s)
- UserCreateCommand.FamilyName src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.cs:12
- User.FamilyName src/Core/CleanArc.Domain/Entities/User/User.cs:14
Phone — 2 field(s)
- UserCreateCommand.PhoneNumber src/Core/CleanArc.Application/Features/Users/Commands/Create/UserCreateCommand.cs:12
- UserTokenRequestQuery.UserPhoneNumber src/Core/CleanArc.Application/Features/Users/Queries/TokenRequest/UserTokenRequestQuery.cs:10